On Tue, Feb 15, 2011 at 06:13:41PM +0100, Wolfram Sang wrote: > > > Ah, yes. I can also see the problem here after turning on > > DEBUG_SPINLOCK. > > Ah, okay. After turning it off, it works a lot better :) That doesn't mean the problem is fixed. The spinlock debugging is there to find broken code, and it's saying that the code is broken, and in this case its saying that there's potential for deadlock. > 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. > SDIO card locks the machine. Is it supposed to work already? Guess it's the spinlock causing that problem. -- 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
