On 4/2/06, Michael Buesch <[EMAIL PROTECTED]> wrote: > > David: FYI, my kernel locked hard over at MIT yesterday. I wasn't > > using the network (not public wifi AFAIK) but something upset the > > driver. No logs. Version:
> So how can you say the bcm43xx driver caused the lockup? Can't be 100% certain but it was going crazy trying to associate and constantly failing. I have only a hunch that it was that right now but it fits with lots of errors in the kernel ringbuffer right before it fell over - when I have something reproducible then I'll track it down. Jon. _______________________________________________ Bcm43xx-dev mailing list [email protected] http://lists.berlios.de/mailman/listinfo/bcm43xx-dev
