Comment 13 for bug 286285

Have been encountering kernel panics very frequently here, both while the system is active and idle, although never with much justification. (Just basic use aboard some pretty meaty hardware). I just recently noticed the message in the log after remembering to check it.

System does slow down frequently and hang without kernel panics, which suggests scheduler problems.

Regrettably my previous logs have been erased so I have no way of finding out whether old lockups were caused by the same issue. I was actually away when this happened and returned hours later to find my computer in a panicked state. At this point I am just guessing that this bug killed it since it is the last thing in my log.

I am attaching my syslog, as well as user.log and daemon.log...

For quick reference, here is the offending snippet from syslog, line 72:
Oct 24 11:52:43 dylan-laptop kernel: [17183.342141] BUG: scheduling while atomic: swapper/0/0x00000100

Here is something I found in daemon.log a few seconds before the crash:
Oct 24 11:13:07 dylan-laptop NetworkManager: <info> (wlan0): supplicant connection state change: 7 -> 6
Oct 24 11:13:07 dylan-laptop NetworkManager: <info> (wlan0): supplicant connection state change: 6 -> 7
Oct 24 11:51:47 dylan-laptop NetworkManager: <info> (wlan0): supplicant connection state change: 7 -> 6
Oct 24 11:51:47 dylan-laptop NetworkManager: <info> (wlan0): supplicant connection state change: 6 -> 7
Oct 24 11:52:22 dylan-laptop NetworkManager: <info> (wlan0): supplicant connection state change: 7 -> 6
Oct 24 11:52:22 dylan-laptop NetworkManager: <info> (wlan0): supplicant connection state change: 6 -> 7
That event doesn't happen very often, so may be related. Still possibly a coincidence.

The event at 17:31 and onwards is restarting after a hard power off.