Hi Bruce,<div><br></div><div>The build I'm using already includes Denys' patch.</div><div><br></div><div>I was referring to Tomas' original problem, in which the MMC card successfully initialized, but the kernel still panics while trying to mount mmcblk0p2. These two seem unrelated, unless I'm mistaken.</div>
<div><br><div class="gmail_quote">On Tue, Jun 12, 2012 at 4:10 PM, Bruce Ashfield <span dir="ltr"><<a href="mailto:bruce.ashfield@gmail.com" target="_blank">bruce.ashfield@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Tue, Jun 12, 2012 at 7:00 PM, Ryan Julian <<a href="mailto:ryanjulian@berkeley.edu">ryanjulian@berkeley.edu</a>> wrote:<br>
> Tomas Frydrych <tf+lists.yocto@...> writes:<br>
>> This is a different issue. I get this too with one particular MMC card,<br>
>> but with 2.6.37 kernel, if I unplug this card and plug it back in the<br>
>> boot resumes and completes successfully. If I do this with the 3.0.2<br>
>> kernel, the bug I described with the associated kernel panic then kicks in.<br>
>><br>
>> Tomas<br>
>><br>
>> ><br>
>> ><br>
>> ><br>
>> > _______________________________________________<br>
>> > yocto mailing list<br>
>> > yocto@...<br>
>> > <a href="https://lists.yoctoproject.org/listinfo/yocto" target="_blank">https://lists.yoctoproject.org/listinfo/yocto</a><br>
>><br>
>><br>
><br>
> Bruce and Tomas,<br>
> Did you ever find a solution to this issue?<br>
><br>
> I'm encountering the same issue on the BB-xM Rev C. I've tested on two different<br>
> boards from different production runs, both with an error identical to Tomas'.<br>
> I'd be happy to run tests/provide logs if given instructions.<br>
<br>
We did. Denys provided us a fix, the only one that was available at the time:<br>
<br>
commit a49b0ec1356bb15a6a8c76b76c464ab3f1f61840<br>
Author: Bruce Ashfield <<a href="mailto:bruce.ashfield@windriver.com">bruce.ashfield@windriver.com</a>><br>
Date: Tue Apr 17 13:45:47 2012 -0400<br>
<br>
meta/beagleboard: disable CONFIG_PREEMPT<br>
<br>
The boot hangs with the message:<br>
mmc0: error -110 whilst initialising SD card<br>
<br>
The MMC driver has issues initializing when PREEMPT is enabled<br>
(either forced<br>
or voluntary). Unplugging and then plugging the card back will reset the<br>
driver and continue booting. Alternatively, disable preemption.<br>
<br>
Signed-off-by: Denys Dmytriyenko <<a href="mailto:denys@ti.com">denys@ti.com</a>><br>
Signed-off-by: Bruce Ashfield <<a href="mailto:bruce.ashfield@windriver.com">bruce.ashfield@windriver.com</a>><br>
<br>
:000000 100644 0000000... 0cbeb5a... A bsp/beagleboard/no-preempt.cfg<br>
:000000 100644 0000000... 1e75e15... A bsp/beagleboard/no-preempt.scc<br>
<br>
Cheers,<br>
<br>
Bruce<br>
<br>
><br>
> Thanks!<br>
><br>
> -Ryan<br>
><br>
><br>
><br>
> _______________________________________________<br>
> yocto mailing list<br>
> <a href="mailto:yocto@yoctoproject.org">yocto@yoctoproject.org</a><br>
> <a href="https://lists.yoctoproject.org/listinfo/yocto" target="_blank">https://lists.yoctoproject.org/listinfo/yocto</a><br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
<br>
--<br>
"Thou shalt not follow the NULL pointer, for chaos and madness await<br>
thee at its end"<br>
</font></span></blockquote></div><br></div>