I also am having the same issue. I thought it was broken hardware so I bought a new one and the same thing happened again. I found that I can usually induce the errors by transferring a large amount of files using scp.
I'm going to check UART0 for additional information once I get the cabling set up. I really hope this gets patched soon, it's a very irritating bug. One time I was able to get some debug information before the I/O errors consumed everything, not sure if it's helpful in any way. Here's the last few lines given from dmesg [14188.582576] wlan0: RX AssocResp from 06:18:d6:57:8c:90 (capab=0x431 status=0 aid=2) [14188.593611] wlan0: associated [14188.641133] wlcore: Association completed. [25043.096569] hrtimer: interrupt took 136276 ns [30864.563462] mmcblk1: error -110 sending status command, retrying [30864.597101] mmcblk1: error -110 sending status command, retrying [30864.638167] mmcblk1: error -110 sending status command, aborting [30864.644451] blk_update_request: I/O error, dev mmcblk1, sector 3487760 [30864.651172] blk_update_request: I/O error, dev mmcblk1, sector 3487768 [30864.657840] blk_update_request: I/O error, dev mmcblk1, sector 3487776 [30864.664510] blk_update_request: I/O error, dev mmcblk1, sector 3487784 [30864.671146] blk_update_request: I/O error, dev mmcblk1, sector 3487792 [30864.677767] blk_update_request: I/O error, dev mmcblk1, sector 3487800 [30864.684382] blk_update_request: I/O error, dev mmcblk1, sector 3487808 [30864.690996] blk_update_request: I/O error, dev mmcblk1, sector 3487816 [30864.697652] blk_update_request: I/O error, dev mmcblk1, sector 3487824 [30864.708291] Aborting journal on device mmcblk1p1-8. [30864.769510] mmcblk1: error -110 sending status command, retrying [30864.817684] mmcblk1: error -110 sending status command, retrying [30864.865245] mmcblk1: error -110 sending status command, aborting [30864.871498] blk_update_request: I/O error, dev mmcblk1, sector 8192 [30864.877900] Buffer I/O error on dev mmcblk1p1, logical block 0, lost sync page write [30864.886607] EXT4-fs error (device mmcblk1p1): ext4_journal_check_start:56: Detected aborted journal [30864.895940] EXT4-fs (mmcblk1p1): Remounting filesystem read-only [30864.902042] EXT4-fs (mmcblk1p1): previous I/O error to superblock detected [30865.101035] mmcblk1: error -110 sending status command, retrying [30865.115710] mmcblk1: error -110 sending status command, retrying And here are the last few lines of /var/log/syslog Aug 4 20:37:33 beaglebone connmand[794]: ntp: time slew -0.003904 s Aug 4 20:37:33 beaglebone rsyslogd-2007: action 'action 17' suspended, next retry is Fri Aug 4 20:39:03 2017 [try http://www.rsyslog.com/e/2007 ] Aug 4 20:39:04 beaglebone rsyslogd-2007: action 'action 17' suspended, next retry is Fri Aug 4 20:40:34 2017 [try http://www.rsyslog.com/e/2007 ] Aug 4 20:40:35 beaglebone rsyslogd-2007: action 'action 17' suspended, next retry is Fri Aug 4 20:42:05 2017 [try http://www.rsyslog.com/e/2007 ] Aug 4 20:42:14 beaglebone rsyslogd-2007: action 'action 17' suspended, next retry is Fri Aug 4 20:43:44 2017 [try http://www.rsyslog.com/e/2007 ] Aug 4 20:43:56 beaglebone rsyslogd-2007: action 'action 17' suspended, next retry is Fri Aug 4 20:45:26 2017 [try http://www.rsyslog.com/e/2007 ] Aug 4 20:45:27 beaglebone rsyslogd-2007: action 'action 17' suspended, next retry is Fri Aug 4 20:46:57 2017 [try http://www.rsyslog.com/e/2007 ] Aug 4 20:46:57 beaglebone rsyslogd-2007: action 'action 17' suspended, next retry is Fri Aug 4 20:48:27 2017 [try http://www.rsyslog.com/e/2007 ] Aug 4 20:48:32 beaglebone rsyslogd-2007: action 'action 17' suspended, next retry is Fri Aug 4 20:50:02 2017 [try http://www.rsyslog.com/e/2007 ] Aug 4 20:50:13 beaglebone rsyslogd-2007: action 'action 17' suspended, next retry is Fri Aug 4 20:51:43 2017 [try http://www.rsyslog.com/e/2007 ] Aug 4 20:51:47 beaglebone rsyslogd-2007: action 'action 17' suspended, next retry is Fri Aug 4 20:53:17 2017 [try http://www.rsyslog.com/e/2007 ] Aug 4 20:53:17 beaglebone rsyslogd-2007: action 'action 17' suspended, next retry is Fri Aug 4 20:54:47 2017 [try http://www.rsyslog.com/e/2007 ] Aug 4 20:54:37 beaglebone connmand[794]: ntp: time slew -0.010474 s Aug 4 20:54:47 beaglebone rsyslogd-2007: action 'action 17' suspended, next retry is Fri Aug 4 20:56:17 2017 [try http://www.rsyslog.com/e/2007 ] Aug 4 20:56:17 beaglebone rsyslogd-2007: action 'action 17' suspended, next retry is Fri Aug 4 20:57:47 2017 [try http://www.rsyslog.com/e/2007 ] Aug 4 20:57:47 beaglebone rsyslogd-2007: action 'action 17' suspended, next retry is Fri Aug 4 20:59:17 2017 [try http://www.rsyslog.com/e/2007 ] Aug 4 20:59:22 beaglebone rsyslogd-2007: action 'action 17' suspended, next retry is Fri Aug 4 21:00:52 2017 [try http://www.rsyslog.com/e/2007 ] Aug 4 21:01:02 beaglebone rsyslogd-2007: action 'action 17' suspended, next retry is Fri Aug 4 21:02:32 2017 [try http://www.rsyslog.com/e/2007 ] Aug 4 21:02:32 beaglebone rsyslogd-2007: action 'action 17' suspended, next retry is Fri Aug 4 21:04:02 2017 [try http://www.rsyslog.com/e/2007 ] Aug 4 21:04:03 beaglebone rsyslogd-2007: action 'action 17' suspended, next retry is Fri Aug 4 21:05:33 2017 [try http://www.rsyslog.com/e/2007 ] Aug 4 21:05:33 beaglebone rsyslogd-2007: action 'action 17' suspended, next retry is Fri Aug 4 21:07:03 2017 [try http://www.rsyslog.com/e/2007 ] Aug 4 21:07:03 beaglebone rsyslogd-2007: action 'action 17' suspended, next retry is Fri Aug 4 21:08:33 2017 [try http://www.rsyslog.com/e/2007 ] Aug 4 21:08:33 beaglebone rsyslogd-2007: action 'action 17' suspended, next retry is Fri Aug 4 21:10:03 2017 [try http://www.rsyslog.com/e/2007 ] Aug 4 21:10:12 beaglebone rsyslogd-2007: action 'action 17' suspended, next retry is Fri Aug 4 21:11:42 2017 [try http://www.rsyslog.com/e/2007 ] Aug 4 21:11:41 beaglebone connmand[794]: ntp: time slew -0.009679 s Aug 4 21:11:51 beaglebone rsyslogd-2007: action 'action 17' suspended, next retry is Fri Aug 4 21:13:21 2017 [try http://www.rsyslog.com/e/2007 ] Aug 4 21:13:22 beaglebone rsyslogd-2007: action 'action 17' suspended, next retry is Fri Aug 4 21:14:52 2017 [try http://www.rsyslog.com/e/2007 ] Aug 4 21:14:53 beaglebone rsyslogd-2007: action 'action 17' suspended, next retry is Fri Aug 4 21:16:23 2017 [try http://www.rsyslog.com/e/2007 ] Aug 4 21:16:35 beaglebone rsyslogd-2007: action 'action 17' suspended, next retry is Fri Aug 4 21:18:05 2017 [try http://www.rsyslog.com/e/2007 ] Aug 4 21:17:01 beaglebone CRON[4839]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Aug 4 21:17:01 beaglebone kernel: [30864.563462] mmcblk1: error -110 sending status command, retrying Aug 4 21:17:01 beaglebone kernel: [30864.597101] mmcblk1: error -110 sending status command, retrying Aug 4 21:17:01 beaglebone kernel: [30864.638167] mmcblk1: error -110 sending status command, aborting Aug 4 21:17:01 beaglebone kernel: [30864.644451] blk_update_request: I/O error, dev mmcblk1, sector 3487760 Aug 4 21:17:01 beaglebone kernel: [30864.651172] blk_update_request: I/O error, dev mmcblk1, sector 3487768 Aug 4 21:17:01 beaglebone kernel: [30864.657840] blk_update_request: I/O error, dev mmcblk1, sector 3487776 Aug 4 21:17:01 beaglebone kernel: [30864.664510] blk_update_request: I/O error, dev mmcblk1, sector 3487784 Aug 4 21:17:01 beaglebone kernel: [30864.671146] blk_update_request: I/O error, dev mmcblk1, sector 3487792 Aug 4 21:17:01 beaglebone kernel: [30864.677767] blk_update_request: I/O error, dev mmcblk1, sector 3487800 Aug 4 21:17:01 beaglebone kernel: [30864.684382] blk_update_request: I/O error, dev mmcblk1, sector 3487808 Aug 4 21:17:01 beaglebone kernel: [30864.690996] blk_update_request: I/O error, dev mmcblk1, sector 3487816 Aug 4 21:17:01 beaglebone kernel: [30864.697652] blk_update_request: I/O error, dev mmcblk1, sector 3487824 On Thursday, August 3, 2017 at 4:07:15 PM UTC-4, Jeffrey Obadal wrote: > > Any update on this problem. I ordered a beaglebone blue from Arrow and I'm > having the same problems. Writing/reading to the eMMC just randomly fails. > They sent me another one, this ones a little better... but eventually i get > input/output errors. I thought it was the power supply maybe at first, but > I hooked them up to a known googd power supply that's 12V 5A (60w) and it > still does this. > > On Friday, May 19, 2017 at 5:02:02 AM UTC-5, Niels Jakob Buch wrote: >> >> I just checked and the JST-SH connector pins, inside the terminal are >> only 1mm apart. >> https://is.alicdn.com/img/pb/863/022/524/524022863_862.jpg >> >> I guess I will wait for the wire assemblies. >> >> On Friday, 19 May 2017 00:06:02 UTC+2, William Hermans wrote: >>> >>> >>> >>> On Thu, May 18, 2017 at 2:06 PM, Niels Jakob Buch <njb...@gmail.com> >>> wrote: >>> >>>> Argh, waiting on a pile of JST-XX connectors to get the Blue-world up >>>> and running. But thanks! >>>> >>> >>> So, I actually have no idea of the pin pitch on those JST headers. But >>> the serial debug cable I bought years ago, and still use. Has fairly thin >>> slip on connectors. You only need RXD, TXD, and ground connected. The cable >>> I bought was a Prolific PL2303HX cable very similar to the one stocked at >>> Adafruit https://www.adafruit.com/product/954 >>> >>> I actually bought mine off ebay for less than $3, but shipping took a >>> lot longer too. Adafruit is stating on their page there that they're now >>> using SilLabs something or another because of driver stability. But I've >>> never experienced a problem with the PL2303HX cable. >>> >>> Anyway, my point is that you may not need a JST connector for this >>> purpose. >>> >> -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/e41f0e13-3458-4614-b78c-f6c7b1265ab0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
