This is a really strange oops.
Is this the bcm43xx/softmac from plain vanilla 2.6.20?

The stack backtrace seems slightly corrupted.
Could you turn on bcm43xx debugging and softmac debugging messages and try to 
reproduce to get a better oops message? Also try to turn on kernel-hacking 
options like slab-debugging and all locking debugging options.

-- 
[feisty] bcm43xx driver causes kernel OOPS onload
https://launchpad.net/bugs/77280

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to