On 13 April 2016 at 12:40, Richard Ash <richardashaudacity@xxxxxxxxxxxxxx> wrote: > I am regularly suffering system lock-ups caused by the above error on > my custom board based on the Xilinx Zynq 7000 Soc. The error from the > kernel is always exactly the same (including all the same hex values): > > mmcblk0: error -110 sending stop command, original cmd response > 0x900, card status 0xe00 [...] > This problem originally showed up in a Xilinx kernel based on 3.18, I > have subsequently upgraded the kernel to the Xilinx v2105.4.01 which > is based on mainline 4.0.0, with no change in the messages and > results. I am about to start on trying to run a stock mainline kernel > to see if I can reproduce the problem there (although this generates > other issues with drivers for the Xilinx QSPI controller). I have now repeated the test using kernel 4.5.1 from kernel.org, which supports enough hardware to get a serial console and test the SD card. I am seeing effectively the same error mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400e00 This is the same message as before, except that the card status value is printed wider. However I left the console open after it happened, and received the following messages on it, in a block maybe a minute or two later: mmc0: Card stuck in programming state! mmcblk0 card_busy_detect mmc0: card never left busy state blk_update_request: I/O error, dev mmcblk0, sector 24060 Buffer I/O error on dev mmcblk0p1, logical block 15868, lost async page write blk_update_request: I/O error, dev mmcblk0, sector 24061 Buffer I/O error on dev mmcblk0p1, logical block 15869, lost async page write mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, retrying mmcblk0: error -110 sending status command, aborting blk_update_request: I/O error, dev mmcblk0, sector 38551 Buffer I/O error on dev mmcblk0p1, logical block 30359, lost async page write Where do I take this from here? Richard -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
