Hi, I'm getting a strange regression with mmci.c at v3.5-rc4 -> v3.5-rc5: Bootup: v3.5-rc4: mmci-pl18x 20098000.sd: mmc0: PL180 manf 41 rev0 at 0x20098000 irq 15,13 (pio) mmci-pl18x 20098000.sd: no DMA platform data mmc0: new SD card at address bd34 mmcblk0: mmc0:bd34 SD02G 1.83 GiB mmcblk0: error -5 transferring data, sector 0, nr 8, cmd response 0x900, card status 0xb00 mmcblk0: retrying using single block read mmcblk0: p1 v3.5-rc5: mmci-pl18x 20098000.sd: mmc0: PL180 manf 41 rev0 at 0x20098000 irq 15,13 (pio) mmci-pl18x 20098000.sd: no DMA platform data mmc0: new SD card at address bd34 mmcblk0: mmc0:bd34 SD02G 1.83 GiB mmcblk0: error -5 transferring data, sector 0, nr 8, cmd response 0x0, card status 0x900 mmcblk0: retrying using single block read mmcblk0: error -5 transferring data, sector 0, nr 8, cmd response 0x0, card status 0x0 end_request: I/O error, dev mmcblk0, sector 0 mmcblk0: error -5 transferring data, sector 1, nr 7, cmd response 0x0, card status 0x0 end_request: I/O error, dev mmcblk0, sector 1 mmcblk0: error -5 transferring data, sector 2, nr 6, cmd response 0x0, card status 0x0 end_request: I/O error, dev mmcblk0, sector 2 Buffer I/O error on device mmcblk0, logical block 0 mmcblk0: unable to read partition table This happens on bootup with _some_ cards that already have the "error -5" in v3.5-rc4. This was ok where up to v3.5-rc4, it worked on a subsequent retry as above. Unfortunately, it now fails with v3.5-rc5. Unfortunately, I can't see a relevant change in the mmci driver or mmc host code. An indirect timing issue on bootup? Inserting cards _after_ bootup generally works. SoC is LPC32XX. Thanks in advance. Roland -- 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
