* Unable to randomly boot rootfs (EXT3 or EXT4) from SD: MMC error -110 (TIMEDOUT) @ 2013-07-21 17:07 Kevyn-Alexandre Paré 2013-08-27 21:47 ` Kevyn-Alexandre Paré 0 siblings, 1 reply; 7+ messages in thread From: Kevyn-Alexandre Paré @ 2013-07-21 17:07 UTC (permalink / raw) To: linux-omap, linux-mmc; +Cc: linux-ext4 Hi, I'm trying to figure out why when randomly booting our system after it = have been hard shutdown for some time (couple of minutes to couple of = days) doesn't boot with MMC error?=20 WORKAROUND: Rebooting the system most of the time remove the issue. I try couple of version of Kernel from stable 3.2.47 & 3.4.53 without = success. I try to change FS from EXT3 to EXT4 without success. I try multiple SD.. Any proposition of test that you think that is worth trying, I'm willing = to try. Your opinions will really be appreciated, See below for some output of my environment, http://pastebin.com/qchsr1FQ Thx, -Kevyn-Alexandre Par=E9 ps: My intention are to enable CONFIG_MMC_DEBUG? Try kernel 3.10.1? ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Unable to randomly boot rootfs (EXT3 or EXT4) from SD: MMC error -110 (TIMEDOUT) 2013-07-21 17:07 Unable to randomly boot rootfs (EXT3 or EXT4) from SD: MMC error -110 (TIMEDOUT) Kevyn-Alexandre Paré @ 2013-08-27 21:47 ` Kevyn-Alexandre Paré 2013-08-27 22:01 ` Theodore Ts'o 0 siblings, 1 reply; 7+ messages in thread From: Kevyn-Alexandre Paré @ 2013-08-27 21:47 UTC (permalink / raw) To: linux-omap, linux-mmc; +Cc: linux-ext4 Hi, Another test with 3.4.59 with EXT4 and: tune2fs -o journal_data_ordered -e panic (partition) results in kernel panic: [...] Waiting for root device /dev/mmcblk0p2... mmc0: host does not support reading read-only switch. assuming write-enable. mmc0: new high speed SDXC card at address aaaa mmcblk0: mmc0:aaaa SU64G 59.4 GiB mmcblk0: p1 p2 mmc1: mmc_rescan_try_freq: trying to init card at 400000 Hz mmc1: new SDIO card at address 0001 EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null) VFS: Mounted root (ext4 filesystem) on device 179:2. devtmpfs: mounted Freeing init memory: 220K INIT: version 2.86 booting mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, aborting end_request: I/O error, dev mmcblk0, sector 4391640 mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, aborting end_request: I/O error, dev mmcblk0, sector 4391640 mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, aborting end_request: I/O error, dev mmcblk0, sector 4391640 mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, aborting end_request: I/O error, dev mmcblk0, sector 4391640 mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, aborting end_request: I/O error, dev mmcblk0, sector 131072 Buffer I/O error on device mmcblk0p2, logical block 0 lost page write due to I/O error on mmcblk0p2 EXT4-fs error (device mmcblk0p2): ext4_find_entry:932: inode #131526: comm rc: reading directory lblock 0 Aborting journal on device mmcblk0p2-8. mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, aborting end_request: I/O error, dev mmcblk0, sector 59113472 Buffer I/O error on device mmcblk0p2, logical block 7372800 lost page write due to I/O error on mmcblk0p2 JBD2: Error -5 detected when updating journal superblock for mmcblk0p2-8. mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, aborting end_request: I/O error, dev mmcblk0, sector 59113472 Buffer I/O error on device mmcblk0p2, logical block 7372800 lost page write due to I/O error on mmcblk0p2 JBD2: Error -5 detected when updating journal superblock for mmcblk0p2-8. Kernel panic - not syncing: EXT4-fs (device mmcblk0p2): panic forced after error If you need specific details let me know. thx -KA On Sun, Jul 21, 2013 at 1:07 PM, Kevyn-Alexandre Paré <kevyn.alexandre.pare@gmail.com> wrote: > Hi, > > I'm trying to figure out why when randomly booting our system after it = > have been hard shutdown for some time (couple of minutes to couple of = > days) doesn't boot with MMC error?=20 > > WORKAROUND: > Rebooting the system most of the time remove the issue. > > I try couple of version of Kernel from stable 3.2.47 & 3.4.53 without = > success. > I try to change FS from EXT3 to EXT4 without success. > I try multiple SD.. > > Any proposition of test that you think that is worth trying, I'm willing = > to try. > > Your opinions will really be appreciated, > > See below for some output of my environment, > http://pastebin.com/qchsr1FQ > > Thx, > > -Kevyn-Alexandre Par=E9 > ps: My intention are to enable CONFIG_MMC_DEBUG? Try kernel 3.10.1? -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Unable to randomly boot rootfs (EXT3 or EXT4) from SD: MMC error -110 (TIMEDOUT) 2013-08-27 21:47 ` Kevyn-Alexandre Paré @ 2013-08-27 22:01 ` Theodore Ts'o 2013-08-28 15:22 ` Kevyn-Alexandre Paré 0 siblings, 1 reply; 7+ messages in thread From: Theodore Ts'o @ 2013-08-27 22:01 UTC (permalink / raw) To: Kevyn-Alexandre Paré; +Cc: linux-omap, linux-mmc, linux-ext4 On Tue, Aug 27, 2013 at 05:47:22PM -0400, Kevyn-Alexandre Paré wrote: > mmcblk0: error -110 sending status command, retrying > mmcblk0: error -110 sending status command, retrying > mmcblk0: error -110 sending status command, aborting This looks like a hardware problem; either with the MMC reader, or the MMC/SD card. Can you try swapping out the hardware and see if the problem goes away? - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Unable to randomly boot rootfs (EXT3 or EXT4) from SD: MMC error -110 (TIMEDOUT) 2013-08-27 22:01 ` Theodore Ts'o @ 2013-08-28 15:22 ` Kevyn-Alexandre Paré 2013-08-28 17:56 ` Theodore Ts'o 0 siblings, 1 reply; 7+ messages in thread From: Kevyn-Alexandre Paré @ 2013-08-28 15:22 UTC (permalink / raw) To: Theodore Ts'o; +Cc: linux-omap, linux-mmc, linux-ext4 Hi Ted, On Tue, Aug 27, 2013 at 6:01 PM, Theodore Ts'o <tytso@mit.edu> wrote: > On Tue, Aug 27, 2013 at 05:47:22PM -0400, Kevyn-Alexandre Paré wrote: >> mmcblk0: error -110 sending status command, retrying >> mmcblk0: error -110 sending status command, retrying >> mmcblk0: error -110 sending status command, aborting > > This looks like a hardware problem; either with the MMC reader, or the > MMC/SD card. That's what I thought, thanks. > > Can you try swapping out the hardware and see if the problem goes > away? We try multiple of our system ( Different micro SD from SanDisk + Overo with OMAP3) and they are all doing this with the SanDisk 64GB, 32GB : http://www.sandisk.com/products/memory-cards/microsd/ultra-class10-for-android/?capacity=64GB The problem seem to be easier to reproduce when we just flash the micro SD (partition, format & copy rootfs) at it first boot. Also, when we let the system down for a couple of days and then sometimes we need to reboot the system multiple times before it fall back alright. We found a old patch that was simply increasing the timeout of the host: http://cgit.openembedded.org/cgit.cgi/openembedded/tree/recipes/linux/linux-omap-2.6.39/sakoman/0024-omap-mmc-Adjust-dto-to-eliminate-timeout-errors.patch?h=org.openembedded.dev By settings the timeout to zero I reproduce kind of the same timeout error at every boot. That was expected since I don't let enough time to the controller to respond... Could the mix of that MMC controller and these card is not optimal? Is the driver fully supporting the UHS-I speed grade? Regards, -KA > > - Ted ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Unable to randomly boot rootfs (EXT3 or EXT4) from SD: MMC error -110 (TIMEDOUT) 2013-08-28 15:22 ` Kevyn-Alexandre Paré @ 2013-08-28 17:56 ` Theodore Ts'o 2013-08-29 19:39 ` Kevyn-Alexandre Paré 0 siblings, 1 reply; 7+ messages in thread From: Theodore Ts'o @ 2013-08-28 17:56 UTC (permalink / raw) To: Kevyn-Alexandre Paré; +Cc: linux-omap, linux-mmc, linux-ext4, arnd On Wed, Aug 28, 2013 at 11:22:58AM -0400, Kevyn-Alexandre Paré wrote: > We try multiple of our system ( Different micro SD from SanDisk + > Overo with OMAP3) and they are all doing this with the SanDisk 64GB, > 32GB : > http://www.sandisk.com/products/memory-cards/microsd/ultra-class10-for-android/?capacity=64GB > > The problem seem to be easier to reproduce when we just flash the > micro SD (partition, format & copy rootfs) at it first boot. > Also, when we let the system down for a couple of days and then > sometimes we need to reboot the system multiple times before it fall > back alright. > > We found a old patch that was simply increasing the timeout of the host: > http://cgit.openembedded.org/cgit.cgi/openembedded/tree/recipes/linux/linux-omap-2.6.39/sakoman/0024-omap-mmc-Adjust-dto-to-eliminate-timeout-errors.patch?h=org.openembedded.dev > > By settings the timeout to zero I reproduce kind of the same timeout > error at every boot. That was expected since I don't let enough time > to the controller to respond... > > Could the mix of that MMC controller and these card is not optimal? Is > the driver fully supporting the UHS-I speed grade? I've cc'ed Arnd Bergman who works at Linaro; I suspect that if he doesn't know the answer off the top of his head, he can probably direct you to someone who will. - Ted ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Unable to randomly boot rootfs (EXT3 or EXT4) from SD: MMC error -110 (TIMEDOUT) 2013-08-28 17:56 ` Theodore Ts'o @ 2013-08-29 19:39 ` Kevyn-Alexandre Paré 2013-08-29 19:49 ` Kevyn-Alexandre Paré 0 siblings, 1 reply; 7+ messages in thread From: Kevyn-Alexandre Paré @ 2013-08-29 19:39 UTC (permalink / raw) To: Theodore Ts'o; +Cc: linux-omap, linux-mmc, linux-ext4, arnd On Wed, Aug 28, 2013 at 1:56 PM, Theodore Ts'o <tytso@mit.edu> wrote: > On Wed, Aug 28, 2013 at 11:22:58AM -0400, Kevyn-Alexandre Paré wrote: >> We try multiple of our system ( Different micro SD from SanDisk + >> Overo with OMAP3) and they are all doing this with the SanDisk 64GB, >> 32GB : >> http://www.sandisk.com/products/memory-cards/microsd/ultra-class10-for-android/?capacity=64GB >> >> The problem seem to be easier to reproduce when we just flash the >> micro SD (partition, format & copy rootfs) at it first boot. >> Also, when we let the system down for a couple of days and then >> sometimes we need to reboot the system multiple times before it fall >> back alright. >> >> We found a old patch that was simply increasing the timeout of the host: >> http://cgit.openembedded.org/cgit.cgi/openembedded/tree/recipes/linux/linux-omap-2.6.39/sakoman/0024-omap-mmc-Adjust-dto-to-eliminate-timeout-errors.patch?h=org.openembedded.dev >> >> By settings the timeout to zero I reproduce kind of the same timeout >> error at every boot. That was expected since I don't let enough time >> to the controller to respond... >> >> Could the mix of that MMC controller and these card is not optimal? Is >> the driver fully supporting the UHS-I speed grade? > > I've cc'ed Arnd Bergman who works at Linaro; I suspect that if he > doesn't know the answer off the top of his head, he can probably > direct you to someone who will. > Thx Ted, Here's more details that I manage to gathered. I add logs in drivers/mmc/card/block.c in function mmc_blk_err_check() to grab the command opcode: pr_err("### KA: mmc_blk_err_check CMD %u\n", areq->mrq->cmd->opcode); Steps that I most often reproduce it. Flashing microSD from Ubuntu 12.10 creating 2 partitions (FAT,EXT4) with USB dongle if this may help (we try with different one and the same result happen)? Aug 29 15:26:38 kap kernel: [371788.469842] usb 1-1: new high-speed USB device number 19 using ehci_hcd Aug 29 15:26:38 kap kernel: [371788.655389] usb 1-1: New USB device found, idVendor=0bda, idProduct=0119 Aug 29 15:26:38 kap kernel: [371788.656090] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Aug 29 15:26:38 kap kernel: [371788.656150] usb 1-1: Product: USB2.0-CRW Aug 29 15:26:38 kap kernel: [371788.656173] usb 1-1: Manufacturer: Generic Aug 29 15:26:38 kap kernel: [371788.656187] usb 1-1: SerialNumber: 20090815198100000 Aug 29 15:26:39 kap kernel: [371789.101509] scsi16 : usb-storage 1-1:1.0 Aug 29 15:26:40 kap kernel: [371790.114299] scsi 16:0:0:0: Direct-Access Generic- SD/MMC 1.00 PQ: 0 ANSI: 0 CCS Aug 29 15:26:40 kap kernel: [371790.126066] sd 16:0:0:0: Attached scsi generic sg2 type 0 Aug 29 15:26:40 kap kernel: [371790.962739] sd 16:0:0:0: [sdb] 124735488 512-byte logical blocks: (63.8 GB/59.4 GiB) Aug 29 15:26:40 kap kernel: [371790.967661] sd 16:0:0:0: [sdb] Write Protect is off Aug 29 15:26:40 kap kernel: [371790.967713] sd 16:0:0:0: [sdb] Mode Sense: 03 00 00 00 Aug 29 15:26:40 kap kernel: [371790.971559] sd 16:0:0:0: [sdb] No Caching mode page present Aug 29 15:26:40 kap kernel: [371790.971742] sd 16:0:0:0: [sdb] Assuming drive cache: write through Aug 29 15:26:40 kap kernel: [371790.991103] sd 16:0:0:0: [sdb] No Caching mode page present Aug 29 15:26:40 kap kernel: [371790.991113] sd 16:0:0:0: [sdb] Assuming drive cache: write through Aug 29 15:26:40 kap kernel: [371790.995660] sdb: sdb1 sdb2 Aug 29 15:26:40 kap kernel: [371791.014090] sd 16:0:0:0: [sdb] No Caching mode page present Aug 29 15:26:40 kap kernel: [371791.014101] sd 16:0:0:0: [sdb] Assuming drive cache: write through Aug 29 15:26:40 kap kernel: [371791.014169] sd 16:0:0:0: [sdb] Attached SCSI removable disk Then take the SD but it in the embedded device and boot it. Note that most of the time the next boot pass, with mmc_blk_err_check for CMD 18 & 25. The output of the kernel panic (3.4.59) gives: [...] Waiting for root device /dev/mmcblk0p2... mmc0: host does not support reading read-only switch. assuming write-enable. mmc0: new high speed SDXC card at address aaaa mmcblk0: mmc0:aaaa SU64G 59.4 GiB ### KA: mmc_blk_err_check CMD 18 mmcblk0: p1 p2 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 mmc1: new SDIO card at address 0001 ### KA: mmc_blk_err_check CMD 25 EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null) VFS: Mounted root (ext4 filesystem) on device 179:2. ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 devtmpfs: mounted Freeing init memory: 220K ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 INIT: version 2.86 booting ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 Please wait: boo### KA: mmc_blk_err_check CMD 18 ting... ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 Starting udev ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 25 ### KA: mmc_blk_err_check CMD 25 hub 1-0:1.0: hub_suspend usb usb1: bus auto-suspend, wakeup 1 ehci-omap ehci-omap.0: suspend root hub ### KA: mmc_blk_err_check CMD 25 ### KA: mmc_blk_err_check CMD 25 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 udevd (90): /proc/90/oom_adj is deprecated, please use /proc/90/oom_score_adj instead. ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ads7846 spi1.0: touchscreen, irq 210 ### KA: mmc_blk_err_check CMD 18 input: ADS7846 Touchscreen as /devices/platform/omap2_mcspi.1/spi_master/spi1/spi1.0/input/input0 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 input: twl4030_pwrbutton as /devices/platform/omap_i2c.1/i2c-1/1-0049/twl4030_pwrbutton/input/input1 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 ### KA: mmc_blk_err_check CMD 18 mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, aborting ### KA: mmc_start_req catch error. end_request: I/O error, dev mmcblk0, sector 416 Buffer I/O error on device mmcblk0, logical block 52 ### KA: mmc_blk_err_check CMD 18 mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, aborting ### KA: mmc_start_req catch error. end_request: I/O error, dev mmcblk0, sector 67681792 end_request: I/O error, dev mmcblk0, sector 67681800 end_request: I/O error, dev mmcblk0, sector 67681808 end_request: I/O error, dev mmcblk0, sector 67681816 end_request: I/O error, dev mmcblk0, sector 67681824 end_request: I/O error, dev mmcblk0, sector 67681832 end_request: I/O error, dev mmcblk0, sector 67681840 end_request: I/O error, dev mmcblk0, sector 67681848 end_request: I/O error, dev mmcblk0, sector 67681856 end_request: I/O error, dev mmcblk0, sector 67681864 end_request: I/O error, dev mmcblk0, sector 67681872 end_request: I/O error, dev mmcblk0, sector 67681880 end_request: I/O error, dev mmcblk0, sector 67681888 end_request: I/O error, dev mmcblk0, sector 67681896 end_request: I/O error, dev mmcblk0, sector 67681904 end_request: I/O error, dev mmcblk0, sector 67681912 end_request: I/O error, dev mmcblk0, sector 67681920 end_request: I/O error, dev mmcblk0, sector 67681928 end_request: I/O error, dev mmcblk0, sector 67681936 end_request: I/O error, dev mmcblk0, sector 67681944 end_request: I/O error, dev mmcblk0, sector 67681952 end_request: I/O error, dev mmcblk0, sector 67681960 end_request: I/O error, dev mmcblk0, sector 67681968 end_request: I/O error, dev mmcblk0, sector 67681976 end_request: I/O error, dev mmcblk0, sector 67681984 end_request: I/O error, dev mmcblk0, sector 67681992 end_request: I/O error, dev mmcblk0, sector 67682000 end_request: I/O error, dev mmcblk0, sector 67682008 end_request: I/O error, dev mmcblk0, sector 67682016 end_request: I/O error, dev mmcblk0, sector 67682024 end_request: I/O error, dev mmcblk0, sector 67682032 end_request: I/O error, dev mmcblk0, sector 67682040 ### KA: mmc_blk_err_check CMD 18 mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, aborting ### KA: mmc_start_req catch error. end_request: I/O error, dev mmcblk0, sector 67502720 end_request: I/O error, dev mmcblk0, sector 67502728 end_request: I/O error, dev mmcblk0, sector 67502736 end_request: I/O error, dev mmcblk0, sector 67502744 ### KA: mmc_blk_err_check CMD 18 mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, aborting ### KA: mmc_start_req catch error. end_request: I/O error, dev mmcblk0, sector 416 Buffer I/O error on device mmcblk0, logical block 52 ### KA: mmc_blk_err_check CMD 18 mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, aborting ### KA: mmc_start_req catch error. end_request: I/O error, dev mmcblk0, sector 50528680 ### KA: mmc_blk_err_check CMD 18 mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, aborting ### KA: mmc_start_req catch error. end_request: I/O error, dev mmcblk0, sector 67502720 ### KA: mmc_blk_err_check CMD 18 mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, aborting ### KA: mmc_start_req catch error. end_request: I/O error, dev mmcblk0, sector 67502960 end_request: I/O error, dev mmcblk0, sector 67502968 ### KA: mmc_blk_err_check CMD 18 mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, aborting ### KA: mmc_start_req catch error. end_request: I/O error, dev mmcblk0, sector 67681792 ### KA: mmc_blk_err_check CMD 18 mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, aborting ### KA: mmc_start_req catch error. end_request: I/O error, dev mmcblk0, sector 512 Buffer I/O error on device mmcblk0, logical block 64 ### KA: mmc_blk_err_check CMD 18 mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, aborting ### KA: mmc_start_req catch error. end_request: I/O error, dev mmcblk0, sector 50766416 ### KA: mmc_blk_err_check CMD 18 mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, aborting ### KA: mmc_start_req catch error. end_request: I/O error, dev mmcblk0, sector 67502960 ### KA: mmc_blk_err_check CMD 18 mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, aborting ### KA: mmc_start_req catch error. end_request: I/O error, dev mmcblk0, sector 67681792 ### KA: mmc_blk_err_check CMD 18 mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, aborting ### KA: mmc_start_req catch error. end_request: I/O error, dev mmcblk0, sector 512 Buffer I/O error on device mmcblk0, logical block 64 ### KA: mmc_blk_err_check CMD 18 mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, aborting ### KA: mmc_start_req catch error. end_request: I/O error, dev mmcblk0, sector 50766416 udevd-work[220]: exec of program '/lib/udev/usb_id' failed ### KA: mmc_blk_err_check CMD 25 mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, aborting ### KA: mmc_start_req catch error. end_request: I/O error, dev mmcblk0, sector 131072 Buffer I/O error on device mmcblk0p2, logical block 0 lost page write due to I/O error on mmcblk0p2 EXT4-fs error (device mmcblk0p2): ext4_find_entry:932: inode #1572945: comm udevd: reading directory lblock 0 ### KA: mmc_blk_err_check CMD 25 mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, aborting ### KA: mmc_start_req catch error. end_request: I/O error, dev mmcblk0, sector 25559216 Buffer I/O error on device mmcblk0p2, logical block 3178518 EXT4-fs warning (device mmcblk0p2): ext4_end_bio:250: I/O error writing to inode 786588 (offset 0 size 4096 starting block 3194903) end_request: I/O error, dev mmcblk0, sector 25559224 Buffer I/O error on device mmcblk0p2, logical block 3178519 EXT4-fs warning (device mmcblk0p2): ext4_end_bio:250: I/O error writing to inode 786590 (offset 0 size 4096 starting block 3194904) Aborting journal on device mmcblk0p2-8. EXT4-fs (mmcblk0p2): previous I/O error to superblock detected EXT4-fs (mmcblk0p2): previous I/O error to superblock detected EXT4-fs (mmcblk0p2): previous I/O error to superblock detected ### KA: mmc_blk_err_check CMD 25 mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, aborting ### KA: mmc_start_req catch error. end_request: I/O error, dev mmcblk0, sector 25578592 Buffer I/O error on device mmcblk0p2, logical block 3180940 EXT4-fs warning (device mmcblk0p2): ext4_end_bio:250: I/O error writing to inode 786591 (offset 0 size 4096 starting block 3197325) end_request: I/O error, dev mmcblk0, sector 25578600 Buffer I/O error on device mmcblk0p2, logical block 3180941 EXT4-fs warning (device mmcblk0p2): ext4_end_bio:250: I/O error writing to inode 786592 (offset 0 size 4096 starting block 3197326) end_request: I/O error, dev mmcblk0, sector 25578608 Buffer I/O error on device mmcblk0p2, logical block 3180942 EXT4-fs warning (device mmcblk0p2): ext4_end_bio:250: I/O error writing to inode 786593 (offset 0 size 4096 starting block 3197327) ### KA: mmc_blk_err_check CMD 25 mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, aborting ### KA: mmc_start_req catch error. end_request: I/O error, dev mmcblk0, sector 59113472 Buffer I/O error on device mmcblk0p2, logical block 7372800 lost page write due to I/O error on mmcblk0p2 JBD2: Error -5 detected when updating journal superblock for mmcblk0p2-8. ### KA: mmc_blk_err_check CMD 18 JBD2: Detected IO errors while flushing file data on mmcblk0p2-8 mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, aborting ### KA: mmc_start_req catch error. end_request: I/O error, dev mmcblk0, sector 32 Buffer I/O error on device mmcblk0, logical block 4 ### KA: mmc_blk_err_check CMD 18 mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, aborting ### KA: mmc_start_req catch error. end_request: I/O error, dev mmcblk0, sector 50766416 ### KA: mmc_blk_err_check CMD 18 mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, aborting ### KA: mmc_start_req catch error. end_request: I/O error, dev mmcblk0, sector 67502720 ### KA: mmc_blk_err_check CMD 18 mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, aborting ### KA: mmc_start_req catch error. end_request: I/O error, dev mmcblk0, sector 32 Buffer I/O error on device mmcblk0, logical block 4 ### KA: mmc_blk_err_check CMD 18 mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, aborting ### KA: mmc_start_req catch error. end_request: I/O error, dev mmcblk0, sector 50766416 ### KA: mmc_blk_err_check CMD 25 mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, aborting ### KA: mmc_start_req catch error. end_request: I/O error, dev mmcblk0, sector 131072 Buffer I/O error on device mmcblk0p2, logical block 0 lost page write due to I/O error on mmcblk0p2 ### KA: mmc_blk_err_check CMD 25 mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, aborting ### KA: mmc_start_req catch error. end_request: I/O error, dev mmcblk0, sector 59113472 Buffer I/O error on device mmcblk0p2, logical block 7372800 lost page write due to I/O error on mmcblk0p2 JBD2: Error -5 detected when updating journal superblock for mmcblk0p2-8. ### KA: mmc_blk_err_check CMD 18 Kernel panic - not syncing: EXT4-fs (device mmcblk0p2): panic forced after error thx, -KA -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Unable to randomly boot rootfs (EXT3 or EXT4) from SD: MMC error -110 (TIMEDOUT) 2013-08-29 19:39 ` Kevyn-Alexandre Paré @ 2013-08-29 19:49 ` Kevyn-Alexandre Paré 0 siblings, 0 replies; 7+ messages in thread From: Kevyn-Alexandre Paré @ 2013-08-29 19:49 UTC (permalink / raw) To: Theodore Ts'o; +Cc: linux-omap, linux-mmc, linux-ext4, arnd I forgot to mention that I was not able to reproduce it yet with the CONFIG_MMC_DEBUG=y Since this is simply slowing down the boot could this be a timeout problem that is to limit and fail to soon? -KA On Thu, Aug 29, 2013 at 3:39 PM, Kevyn-Alexandre Paré <kevyn.alexandre.pare@gmail.com> wrote: > On Wed, Aug 28, 2013 at 1:56 PM, Theodore Ts'o <tytso@mit.edu> wrote: >> On Wed, Aug 28, 2013 at 11:22:58AM -0400, Kevyn-Alexandre Paré wrote: >>> We try multiple of our system ( Different micro SD from SanDisk + >>> Overo with OMAP3) and they are all doing this with the SanDisk 64GB, >>> 32GB : >>> http://www.sandisk.com/products/memory-cards/microsd/ultra-class10-for-android/?capacity=64GB >>> >>> The problem seem to be easier to reproduce when we just flash the >>> micro SD (partition, format & copy rootfs) at it first boot. >>> Also, when we let the system down for a couple of days and then >>> sometimes we need to reboot the system multiple times before it fall >>> back alright. >>> >>> We found a old patch that was simply increasing the timeout of the host: >>> http://cgit.openembedded.org/cgit.cgi/openembedded/tree/recipes/linux/linux-omap-2.6.39/sakoman/0024-omap-mmc-Adjust-dto-to-eliminate-timeout-errors.patch?h=org.openembedded.dev >>> >>> By settings the timeout to zero I reproduce kind of the same timeout >>> error at every boot. That was expected since I don't let enough time >>> to the controller to respond... >>> >>> Could the mix of that MMC controller and these card is not optimal? Is >>> the driver fully supporting the UHS-I speed grade? >> >> I've cc'ed Arnd Bergman who works at Linaro; I suspect that if he >> doesn't know the answer off the top of his head, he can probably >> direct you to someone who will. >> > > Thx Ted, > > Here's more details that I manage to gathered. I add logs in > drivers/mmc/card/block.c in function mmc_blk_err_check() to grab the > command opcode: > pr_err("### KA: mmc_blk_err_check CMD %u\n", areq->mrq->cmd->opcode); > > Steps that I most often reproduce it. > Flashing microSD from Ubuntu 12.10 creating 2 partitions (FAT,EXT4) > with USB dongle if this may help (we try with different one and the > same result happen)? > > Aug 29 15:26:38 kap kernel: [371788.469842] usb 1-1: new high-speed > USB device number 19 using ehci_hcd > Aug 29 15:26:38 kap kernel: [371788.655389] usb 1-1: New USB device > found, idVendor=0bda, idProduct=0119 > Aug 29 15:26:38 kap kernel: [371788.656090] usb 1-1: New USB device > strings: Mfr=1, Product=2, SerialNumber=3 > Aug 29 15:26:38 kap kernel: [371788.656150] usb 1-1: Product: USB2.0-CRW > Aug 29 15:26:38 kap kernel: [371788.656173] usb 1-1: Manufacturer: Generic > Aug 29 15:26:38 kap kernel: [371788.656187] usb 1-1: SerialNumber: > 20090815198100000 > Aug 29 15:26:39 kap kernel: [371789.101509] scsi16 : usb-storage 1-1:1.0 > Aug 29 15:26:40 kap kernel: [371790.114299] scsi 16:0:0:0: > Direct-Access Generic- SD/MMC 1.00 PQ: 0 ANSI: 0 CCS > Aug 29 15:26:40 kap kernel: [371790.126066] sd 16:0:0:0: Attached scsi > generic sg2 type 0 > Aug 29 15:26:40 kap kernel: [371790.962739] sd 16:0:0:0: [sdb] > 124735488 512-byte logical blocks: (63.8 GB/59.4 GiB) > Aug 29 15:26:40 kap kernel: [371790.967661] sd 16:0:0:0: [sdb] Write > Protect is off > Aug 29 15:26:40 kap kernel: [371790.967713] sd 16:0:0:0: [sdb] Mode > Sense: 03 00 00 00 > Aug 29 15:26:40 kap kernel: [371790.971559] sd 16:0:0:0: [sdb] No > Caching mode page present > Aug 29 15:26:40 kap kernel: [371790.971742] sd 16:0:0:0: [sdb] > Assuming drive cache: write through > Aug 29 15:26:40 kap kernel: [371790.991103] sd 16:0:0:0: [sdb] No > Caching mode page present > Aug 29 15:26:40 kap kernel: [371790.991113] sd 16:0:0:0: [sdb] > Assuming drive cache: write through > Aug 29 15:26:40 kap kernel: [371790.995660] sdb: sdb1 sdb2 > Aug 29 15:26:40 kap kernel: [371791.014090] sd 16:0:0:0: [sdb] No > Caching mode page present > Aug 29 15:26:40 kap kernel: [371791.014101] sd 16:0:0:0: [sdb] > Assuming drive cache: write through > Aug 29 15:26:40 kap kernel: [371791.014169] sd 16:0:0:0: [sdb] > Attached SCSI removable disk > > Then take the SD but it in the embedded device and boot it. Note that > most of the time the next boot pass, with mmc_blk_err_check for CMD 18 > & 25. > > The output of the kernel panic (3.4.59) gives: > [...] > Waiting for root device /dev/mmcblk0p2... > mmc0: host does not support reading read-only switch. assuming write-enable. > mmc0: new high speed SDXC card at address aaaa > mmcblk0: mmc0:aaaa SU64G 59.4 GiB > ### KA: mmc_blk_err_check CMD 18 > mmcblk0: p1 p2 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > mmc1: new SDIO card at address 0001 > ### KA: mmc_blk_err_check CMD 25 > EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null) > VFS: Mounted root (ext4 filesystem) on device 179:2. > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > devtmpfs: mounted > Freeing init memory: 220K > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > INIT: version 2.86 booting > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > Please wait: boo### KA: mmc_blk_err_check CMD 18 > ting... > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > Starting udev > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 25 > ### KA: mmc_blk_err_check CMD 25 > hub 1-0:1.0: hub_suspend > usb usb1: bus auto-suspend, wakeup 1 > ehci-omap ehci-omap.0: suspend root hub > ### KA: mmc_blk_err_check CMD 25 > ### KA: mmc_blk_err_check CMD 25 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > udevd (90): /proc/90/oom_adj is deprecated, please use > /proc/90/oom_score_adj instead. > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ads7846 spi1.0: touchscreen, irq 210 > ### KA: mmc_blk_err_check CMD 18 > input: ADS7846 Touchscreen as > /devices/platform/omap2_mcspi.1/spi_master/spi1/spi1.0/input/input0 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > input: twl4030_pwrbutton as > /devices/platform/omap_i2c.1/i2c-1/1-0049/twl4030_pwrbutton/input/input1 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > ### KA: mmc_blk_err_check CMD 18 > mmcblk0: error -110 sending status command, retrying > mmcblk0: error -110 sending status command, retrying > mmcblk0: error -110 sending status command, aborting > ### KA: mmc_start_req catch error. > end_request: I/O error, dev mmcblk0, sector 416 > Buffer I/O error on device mmcblk0, logical block 52 > ### KA: mmc_blk_err_check CMD 18 > mmcblk0: error -110 sending status command, retrying > mmcblk0: error -110 sending status command, retrying > mmcblk0: error -110 sending status command, aborting > ### KA: mmc_start_req catch error. > end_request: I/O error, dev mmcblk0, sector 67681792 > end_request: I/O error, dev mmcblk0, sector 67681800 > end_request: I/O error, dev mmcblk0, sector 67681808 > end_request: I/O error, dev mmcblk0, sector 67681816 > end_request: I/O error, dev mmcblk0, sector 67681824 > end_request: I/O error, dev mmcblk0, sector 67681832 > end_request: I/O error, dev mmcblk0, sector 67681840 > end_request: I/O error, dev mmcblk0, sector 67681848 > end_request: I/O error, dev mmcblk0, sector 67681856 > end_request: I/O error, dev mmcblk0, sector 67681864 > end_request: I/O error, dev mmcblk0, sector 67681872 > end_request: I/O error, dev mmcblk0, sector 67681880 > end_request: I/O error, dev mmcblk0, sector 67681888 > end_request: I/O error, dev mmcblk0, sector 67681896 > end_request: I/O error, dev mmcblk0, sector 67681904 > end_request: I/O error, dev mmcblk0, sector 67681912 > end_request: I/O error, dev mmcblk0, sector 67681920 > end_request: I/O error, dev mmcblk0, sector 67681928 > end_request: I/O error, dev mmcblk0, sector 67681936 > end_request: I/O error, dev mmcblk0, sector 67681944 > end_request: I/O error, dev mmcblk0, sector 67681952 > end_request: I/O error, dev mmcblk0, sector 67681960 > end_request: I/O error, dev mmcblk0, sector 67681968 > end_request: I/O error, dev mmcblk0, sector 67681976 > end_request: I/O error, dev mmcblk0, sector 67681984 > end_request: I/O error, dev mmcblk0, sector 67681992 > end_request: I/O error, dev mmcblk0, sector 67682000 > end_request: I/O error, dev mmcblk0, sector 67682008 > end_request: I/O error, dev mmcblk0, sector 67682016 > end_request: I/O error, dev mmcblk0, sector 67682024 > end_request: I/O error, dev mmcblk0, sector 67682032 > end_request: I/O error, dev mmcblk0, sector 67682040 > ### KA: mmc_blk_err_check CMD 18 > mmcblk0: error -110 sending status command, retrying > mmcblk0: error -110 sending status command, retrying > mmcblk0: error -110 sending status command, aborting > ### KA: mmc_start_req catch error. > end_request: I/O error, dev mmcblk0, sector 67502720 > end_request: I/O error, dev mmcblk0, sector 67502728 > end_request: I/O error, dev mmcblk0, sector 67502736 > end_request: I/O error, dev mmcblk0, sector 67502744 > ### KA: mmc_blk_err_check CMD 18 > mmcblk0: error -110 sending status command, retrying > mmcblk0: error -110 sending status command, retrying > mmcblk0: error -110 sending status command, aborting > ### KA: mmc_start_req catch error. > end_request: I/O error, dev mmcblk0, sector 416 > Buffer I/O error on device mmcblk0, logical block 52 > ### KA: mmc_blk_err_check CMD 18 > mmcblk0: error -110 sending status command, retrying > mmcblk0: error -110 sending status command, retrying > mmcblk0: error -110 sending status command, aborting > ### KA: mmc_start_req catch error. > end_request: I/O error, dev mmcblk0, sector 50528680 > ### KA: mmc_blk_err_check CMD 18 > mmcblk0: error -110 sending status command, retrying > mmcblk0: error -110 sending status command, retrying > mmcblk0: error -110 sending status command, aborting > ### KA: mmc_start_req catch error. > end_request: I/O error, dev mmcblk0, sector 67502720 > ### KA: mmc_blk_err_check CMD 18 > mmcblk0: error -110 sending status command, retrying > mmcblk0: error -110 sending status command, retrying > mmcblk0: error -110 sending status command, aborting > ### KA: mmc_start_req catch error. > end_request: I/O error, dev mmcblk0, sector 67502960 > end_request: I/O error, dev mmcblk0, sector 67502968 > ### KA: mmc_blk_err_check CMD 18 > mmcblk0: error -110 sending status command, retrying > mmcblk0: error -110 sending status command, retrying > mmcblk0: error -110 sending status command, aborting > ### KA: mmc_start_req catch error. > end_request: I/O error, dev mmcblk0, sector 67681792 > ### KA: mmc_blk_err_check CMD 18 > mmcblk0: error -110 sending status command, retrying > mmcblk0: error -110 sending status command, retrying > mmcblk0: error -110 sending status command, aborting > ### KA: mmc_start_req catch error. > end_request: I/O error, dev mmcblk0, sector 512 > Buffer I/O error on device mmcblk0, logical block 64 > ### KA: mmc_blk_err_check CMD 18 > mmcblk0: error -110 sending status command, retrying > mmcblk0: error -110 sending status command, retrying > mmcblk0: error -110 sending status command, aborting > ### KA: mmc_start_req catch error. > end_request: I/O error, dev mmcblk0, sector 50766416 > ### KA: mmc_blk_err_check CMD 18 > mmcblk0: error -110 sending status command, retrying > mmcblk0: error -110 sending status command, retrying > mmcblk0: error -110 sending status command, aborting > ### KA: mmc_start_req catch error. > end_request: I/O error, dev mmcblk0, sector 67502960 > ### KA: mmc_blk_err_check CMD 18 > mmcblk0: error -110 sending status command, retrying > mmcblk0: error -110 sending status command, retrying > mmcblk0: error -110 sending status command, aborting > ### KA: mmc_start_req catch error. > end_request: I/O error, dev mmcblk0, sector 67681792 > ### KA: mmc_blk_err_check CMD 18 > mmcblk0: error -110 sending status command, retrying > mmcblk0: error -110 sending status command, retrying > mmcblk0: error -110 sending status command, aborting > ### KA: mmc_start_req catch error. > end_request: I/O error, dev mmcblk0, sector 512 > Buffer I/O error on device mmcblk0, logical block 64 > ### KA: mmc_blk_err_check CMD 18 > mmcblk0: error -110 sending status command, retrying > mmcblk0: error -110 sending status command, retrying > mmcblk0: error -110 sending status command, aborting > ### KA: mmc_start_req catch error. > end_request: I/O error, dev mmcblk0, sector 50766416 > udevd-work[220]: exec of program '/lib/udev/usb_id' failed > > ### KA: mmc_blk_err_check CMD 25 > mmcblk0: error -110 sending status command, retrying > mmcblk0: error -110 sending status command, retrying > mmcblk0: error -110 sending status command, aborting > ### KA: mmc_start_req catch error. > end_request: I/O error, dev mmcblk0, sector 131072 > Buffer I/O error on device mmcblk0p2, logical block 0 > lost page write due to I/O error on mmcblk0p2 > EXT4-fs error (device mmcblk0p2): ext4_find_entry:932: inode #1572945: > comm udevd: reading directory lblock 0 > ### KA: mmc_blk_err_check CMD 25 > mmcblk0: error -110 sending status command, retrying > mmcblk0: error -110 sending status command, retrying > mmcblk0: error -110 sending status command, aborting > ### KA: mmc_start_req catch error. > end_request: I/O error, dev mmcblk0, sector 25559216 > Buffer I/O error on device mmcblk0p2, logical block 3178518 > EXT4-fs warning (device mmcblk0p2): ext4_end_bio:250: I/O error > writing to inode 786588 (offset 0 size 4096 starting block 3194903) > end_request: I/O error, dev mmcblk0, sector 25559224 > Buffer I/O error on device mmcblk0p2, logical block 3178519 > EXT4-fs warning (device mmcblk0p2): ext4_end_bio:250: I/O error > writing to inode 786590 (offset 0 size 4096 starting block 3194904) > Aborting journal on device mmcblk0p2-8. > EXT4-fs (mmcblk0p2): previous I/O error to superblock detected > EXT4-fs (mmcblk0p2): previous I/O error to superblock detected > EXT4-fs (mmcblk0p2): previous I/O error to superblock detected > ### KA: mmc_blk_err_check CMD 25 > mmcblk0: error -110 sending status command, retrying > mmcblk0: error -110 sending status command, retrying > mmcblk0: error -110 sending status command, aborting > ### KA: mmc_start_req catch error. > end_request: I/O error, dev mmcblk0, sector 25578592 > Buffer I/O error on device mmcblk0p2, logical block 3180940 > EXT4-fs warning (device mmcblk0p2): ext4_end_bio:250: I/O error > writing to inode 786591 (offset 0 size 4096 starting block 3197325) > end_request: I/O error, dev mmcblk0, sector 25578600 > Buffer I/O error on device mmcblk0p2, logical block 3180941 > EXT4-fs warning (device mmcblk0p2): ext4_end_bio:250: I/O error > writing to inode 786592 (offset 0 size 4096 starting block 3197326) > end_request: I/O error, dev mmcblk0, sector 25578608 > Buffer I/O error on device mmcblk0p2, logical block 3180942 > EXT4-fs warning (device mmcblk0p2): ext4_end_bio:250: I/O error > writing to inode 786593 (offset 0 size 4096 starting block 3197327) > ### KA: mmc_blk_err_check CMD 25 > mmcblk0: error -110 sending status command, retrying > mmcblk0: error -110 sending status command, retrying > mmcblk0: error -110 sending status command, aborting > ### KA: mmc_start_req catch error. > end_request: I/O error, dev mmcblk0, sector 59113472 > Buffer I/O error on device mmcblk0p2, logical block 7372800 > lost page write due to I/O error on mmcblk0p2 > JBD2: Error -5 detected when updating journal superblock for mmcblk0p2-8. > ### KA: mmc_blk_err_check CMD 18 > JBD2: Detected IO errors while flushing file data on mmcblk0p2-8 > mmcblk0: error -110 sending status command, retrying > mmcblk0: error -110 sending status command, retrying > mmcblk0: error -110 sending status command, aborting > ### KA: mmc_start_req catch error. > end_request: I/O error, dev mmcblk0, sector 32 > Buffer I/O error on device mmcblk0, logical block 4 > ### KA: mmc_blk_err_check CMD 18 > mmcblk0: error -110 sending status command, retrying > mmcblk0: error -110 sending status command, retrying > mmcblk0: error -110 sending status command, aborting > ### KA: mmc_start_req catch error. > end_request: I/O error, dev mmcblk0, sector 50766416 > ### KA: mmc_blk_err_check CMD 18 > mmcblk0: error -110 sending status command, retrying > mmcblk0: error -110 sending status command, retrying > mmcblk0: error -110 sending status command, aborting > ### KA: mmc_start_req catch error. > end_request: I/O error, dev mmcblk0, sector 67502720 > ### KA: mmc_blk_err_check CMD 18 > mmcblk0: error -110 sending status command, retrying > mmcblk0: error -110 sending status command, retrying > mmcblk0: error -110 sending status command, aborting > ### KA: mmc_start_req catch error. > end_request: I/O error, dev mmcblk0, sector 32 > Buffer I/O error on device mmcblk0, logical block 4 > ### KA: mmc_blk_err_check CMD 18 > mmcblk0: error -110 sending status command, retrying > mmcblk0: error -110 sending status command, retrying > mmcblk0: error -110 sending status command, aborting > ### KA: mmc_start_req catch error. > end_request: I/O error, dev mmcblk0, sector 50766416 > ### KA: mmc_blk_err_check CMD 25 > mmcblk0: error -110 sending status command, retrying > mmcblk0: error -110 sending status command, retrying > mmcblk0: error -110 sending status command, aborting > ### KA: mmc_start_req catch error. > end_request: I/O error, dev mmcblk0, sector 131072 > Buffer I/O error on device mmcblk0p2, logical block 0 > lost page write due to I/O error on mmcblk0p2 > ### KA: mmc_blk_err_check CMD 25 > mmcblk0: error -110 sending status command, retrying > mmcblk0: error -110 sending status command, retrying > mmcblk0: error -110 sending status command, aborting > ### KA: mmc_start_req catch error. > end_request: I/O error, dev mmcblk0, sector 59113472 > Buffer I/O error on device mmcblk0p2, logical block 7372800 > lost page write due to I/O error on mmcblk0p2 > JBD2: Error -5 detected when updating journal superblock for mmcblk0p2-8. > ### KA: mmc_blk_err_check CMD 18 > Kernel panic - not syncing: EXT4-fs (device mmcblk0p2): panic forced after error > > thx, > > -KA ^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2013-08-29 19:49 UTC | newest] Thread overview: 7+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2013-07-21 17:07 Unable to randomly boot rootfs (EXT3 or EXT4) from SD: MMC error -110 (TIMEDOUT) Kevyn-Alexandre Paré 2013-08-27 21:47 ` Kevyn-Alexandre Paré 2013-08-27 22:01 ` Theodore Ts'o 2013-08-28 15:22 ` Kevyn-Alexandre Paré 2013-08-28 17:56 ` Theodore Ts'o 2013-08-29 19:39 ` Kevyn-Alexandre Paré 2013-08-29 19:49 ` Kevyn-Alexandre Paré
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).