Comment 776 for bug 993187

Revision history for this message
Frank Schilder (f-schilder) wrote :

I think this bug is assigned to the wrong package. It is very likely a kernel problem. On my hardware, the kernel actually detects the lock. I posted extracts from the syslog file recovered after a hard reset in the following two posts to another thread on the same problem: <a href="https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1154006/comments/42">1154006#42</a> and <a href="https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1154006/comments/46">1154006#46</a>. The lines to look for are

Apr 10 18:58:51 ceylon kernel: [ 2412.456005] ioatdma 0000:00:08.0: reset
Apr 10 18:58:52 ceylon kernel: [ 2412.603756] BUG: soft lockup - CPU#3 stuck for 22s! [svn:5127]

in #42 and

Apr 14 13:16:12 ceylon kernel: [18557.572005] ioatdma 0000:00:08.0: reset
Apr 14 13:16:12 ceylon kernel: [18557.772001] INFO: rcu_sched detected stall on CPU 1 (t=15000 jiffies)
Apr 14 13:16:12 ceylon kernel: [18557.772002] sending NMI to all CPUs:

in #46. I just went back to 10.04, the instability of 12.04 is just ridiculous. I hope that a kernel developer is following this discussion and might find a hint in the syslog extracts I posted under the other number.