On Saturday 27 May 2006 23:19, you 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 tried this setup again, and yes, it looks like bcm43xx. I have a photo > of the oops here: > > http://gehennom.net/~lunz/bcm43xx_crash.jpg > > It takes an hour or two of traffic flood to reproduce the crash. Let me > know if you need any more information.
Oh, yes. That's really an interresting oops. I guess the interrupt, which is used for bcm, is used by another device, too. Is that right? Could you show us your /proc/interrupts please? In the "interrupt-shared" case it is indeed possible to deadlock. I will do an updated patch, which tries to solve this. -- Greetings Michael. [2007: Knorkator (Germany) - 12 points] _______________________________________________ Bcm43xx-dev mailing list [email protected] http://lists.berlios.de/mailman/listinfo/bcm43xx-dev
