Hi Ben, Thanks for the pointer the the thread. What they did was exactly what I did (and then later reverted). I guess my "lame hack attempt" wasn't so lame after all.
It works fine on my "mule" board with more memory and two Ethernet ports, but fails on the production board having less memory and only one Ethernet port. This probably means that I need to look into something else. In our setup, the DTS always says two Ethernet ports. It may be that the failure of the probe in the case of the non-existent Ethernet port causes the kernel panic when the order of execution of those two functions are reversed. Thanks again. This gives me a few more leads to chase down. Darcy On Fri, 2008-08-15 at 10:48 -0700, Benjamin Krill wrote: > Hi Darcy, > > >The bug normally goes unnoticed until you turn on spinlock and/or > >rtmutex debuggging in the kernel config - then the debugging magic > >checks will catch it during boot. > > Have a look at thread: > http://ozlabs.org/pipermail/linuxppc-dev/2008-August/061631.html > > cheers > ben > -- Regards, Darcy -------------- Darcy L. Watkins - Senior Software Developer Tranzeo Wireless Technologies, Inc. 19273 Fraser Way, Pitt Meadows, BC, Canada V3Y 2V4 T:604-460-6002 ext:410 http://www.tranzeo.com _______________________________________________ Linuxppc-embedded mailing list [email protected] https://ozlabs.org/mailman/listinfo/linuxppc-embedded
