I’ve heard (but can’t remember where, sadly) that this is *not* a sign of the mmcblk device wearing out. It’s actually (according to my, possibly faulty, recollection) indicative of a difference in understanding between uboot and Linux as to what the partition table should look like for an mmcblk device. Whatever is doing the read is referring to an address beyond the end of the logical device because it thinks the logical device is bigger than it actually is.
In any case, I’ve been getting it on reboots for years and not had any difficulty. It only shows up on booting, not during actual run-time. Maybe somebody on the list can fill in the details? Hope this helps! Rick On Mar 25, 2015, at 2:47 PM, Gilles <codecompl...@free.fr> wrote: > ========= > # dmesg | tail > [42113305.934129] mmcblk0: error -110 transferring data, sector > 1230482, nr 6, c md response 0x900, card status 0x0 > [42113305.944295] end_request: I/O error, dev mmcblk0, sector 1230482 > [42113306.123221] mmcblk0: error -110 transferring data, sector > 1230480, nr 8, c md response 0x900, card status > 0xb00 > [42113306.133560] mmcblk0: retrying using single block read > [42113306.306724] mmcblk0: error -110 transferring data, sector > 1230480, nr 8, c md response 0x900, card status 0x0 > [42113306.316885] end_request: I/O error, dev mmcblk0, sector 1230480 > [42113306.490929] mmcblk0: error -110 transferring data, sector > 1230481, nr 7, c md response 0x900, card status 0x0 > [42113306.501094] end_request: I/O error, dev mmcblk0, sector 1230481 > [42113306.676773] mmcblk0: error -110 transferring data, sector > 1230483, nr 5, c md response 0x900, card status 0x0 > [42113306.686937] end_request: I/O error, dev mmcblk0, sector 1230483 > ========= -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/2665a39c-3e16-41cb-8a16-b3b0134d6...@pobox.com
