On Thursday 25 May 2006 16:16, Jason Lunz wrote: > On Thu, May 25, 2006 at 02:02:37PM +0200, Michael Buesch wrote: > > Uh, don't let me dangling like this. :) > > Could you please try to reproduce the lockup and catch > > an oops? It's important, because it may be caused by bcm43xx. > > I will, but I've been quite busy at work and I have only a free hour or > so each night when I can try things out. So it may take a few days to > pin down what's going on. I'll let you know how tonight's run goes. > > In case I wasn't clear, I *did* look for an oops, but there was none in > syslog and it locked up in X, so there wasn't one on screen either. I'll > try next time with serial console. > > Do you have any suggestions about what config would best stress it? I > went with smp+full preempt to try and simulate smp races on the single > processor I have.
The spinlock debugging related options under Kernel Hacking should catch all bugs. Especially the spinlock recursion detection on your UP system. _______________________________________________ Bcm43xx-dev mailing list [email protected] http://lists.berlios.de/mailman/listinfo/bcm43xx-dev
