Immediately before the OOPs, the following syslog reliably repeats
(different specific values, obviously):

Feb 15 03:30:19 localhost kernel: [ 2817.984000] ADDRCONF(NETDEV_CHANGE): eth1: 
link becomes ready
Feb 15 03:30:19 localhost kernel: [ 2818.020000] ssb: Switching to core 0
Feb 15 03:30:19 localhost kernel: [ 2818.020000] ssb: Switching to core 1
Feb 15 03:30:19 localhost kernel: [ 2818.020000] KERNEL: assertion 
(!atomic_read(&sk->sk_wmem_alloc)) failed at net/unix/af_unix.c (344)
Feb 15 03:30:19 localhost kernel: [ 2818.020000] KERNEL: assertion 
(sk_unhashed(sk)) failed at net/unix/af_unix.c (345)
Feb 15 03:30:19 localhost kernel: [ 2818.020000] KERNEL: assertion 
(!sk->sk_socket) failed at net/unix/af_unix.c (346)
Feb 15 03:30:19 localhost kernel: [ 2818.020000] Attempt to release alive unix 
socket: c8cffac0
Feb 15 03:30:19 localhost kernel: [ 2818.024000] KERNEL: assertion 
(!atomic_read(&sk->sk_wmem_alloc)) failed at net/unix/af_unix.c (344)
Feb 15 03:30:19 localhost kernel: [ 2818.024000] KERNEL: assertion 
(sk_unhashed(sk)) failed at net/unix/af_unix.c (345)
Feb 15 03:30:19 localhost kernel: [ 2818.024000] KERNEL: assertion 
(!sk->sk_socket) failed at net/unix/af_unix.c (346)
Feb 15 03:30:19 localhost kernel: [ 2818.024000] Attempt to release alive unix 
socket: c8cffac0
Feb 15 03:30:19 localhost kernel: [ 2818.024000] KERNEL: assertion 
(!atomic_read(&sk->sk_wmem_alloc)) failed at net/unix/af_unix.c (344)

-- 
[feisty] bcm43xx driver causes hard-lock on association
https://launchpad.net/bugs/85318

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

Reply via email to