On Tue, Feb 15, 2011 at 06:29:48PM +0100, Wolfram Sang wrote: > On Tue, Feb 15, 2011 at 05:19:17PM +0000, Russell King - ARM Linux wrote: > > On Tue, Feb 15, 2011 at 06:13:41PM +0100, Wolfram Sang wrote: > > > MMC fails for me (note: the card works fine with an mx35-based board) > > > > > > mmc0: new high speed MMC card at address 0001 > > > mmcblk0: mmc0:0001 AF HMP 247 MiB > > > mmcblk0: retrying using single block read > > > mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900 > > > end_request: I/O error, dev mmcblk0, sector 0 > > > > EILSEQ means CRC failure. Probably unrelated. > > Even if it works in another setup? As a result of the above, I can't read the > partition table of that MMC. The mx35 can do so. CRC is generated to protect the link between the card and the host. It means that the CRC computed by the card for the transfer and the CRC computed by the host didn't match. In other words, data was corrupted in some way between the card and the MMC host. -- 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
