On Fri, 11 Jun 2010, Maxim Levitsky wrote: > On Thu, 2010-06-10 at 22:54 +0100, Mark Hills wrote: > > On Thu, 10 Jun 2010, Maxim Levitsky wrote: [...] > > > Did you do a suspend/resume cycle before this test? > > > > No, I didn't suspect or resume the laptop. The dmesg is from a cold > > reboot, where I let the machine boot, then inserted the card (and the same > > in the previous email) > > In fact, you need to undo the work of CONFIG_MMC_RICOH_MMC you need to > shutdown the system and then boot into kernel that hasn't this option. > But anyway, I don't think its to blame.
Sorry, perhaps I wasn't clear. I did a full kernel compile, installing it and the new modules (without CONFIG_MMC_RICOH_MMC), then I re-booted and tried again to produce the new dmesg. > Thanks for kernel log I hope I get enough clues from it. > I am interested in this problem because this isn't first time I seen it. Okay, well it is promising that you think it should be working. Good luck finding any clues. > It might be related to too high clock or hispeed mode that card doesn't > support. > > As suggested, try 'debug_quirks=1' too. I have tried with and without this, with the same error. > Best regards, > Maxim Levitsky -- Mark -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
