<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><div><span>You should be able to prevent crashes by disabling nmi watchdog using "nmi_watchdog=0" boot option.</span></div><div><br><span></span></div><div><span>Sincerely,</span></div><div><span>Burhan</span></div><div><br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><font face="Arial" size="2"><hr size="1"><b><span style="font-weight: bold;">From:</span></b> Lennart Sorensen <lsorense-1wCw9BSqJbv44Nm34jS7GywD8/FfD2ys@public.gmane.org><br><b><span style="font-weight: bold;">To:</span></b> tlug-lxSQFCZeNF4@public.gmane.org<br><b><span style="font-weight: bold;">Sent:</span></b> Tuesday, November 8, 2011 12:04:43 PM<br><b><span style="font-weight:
bold;">Subject:</span></b> Re: [TLUG]: Kernel Panic panic<br></font><br>On Tue, Nov 08, 2011 at 11:47:41AM -0500, Peter King wrote:<br>> After upgrading to 3.1.0, one of my computers began randomly crashing, usually<br>> after a day or two. The first time it happened I jotted down the start of the<br>> message:<br>> <br>> Uhhuh. NMI received for unknown reason 2d on CPU0.<br>> Do you have a strange powersaving mode enabled?<br>> Dazed and confused, but trying to continue<br>> Process swapper...<br>> <snip><br>> Kernel Panic -not syncing: softlockup: hung tasks<br>> PID:0, comm: swapper Not tainted 3.1.0-gentoo #1<br>> <br>> The other crashes have uniformly mentioned swapper and softlockup, but not NMI.<br>> My understanding, after googling around, is that this error message is not uncommon<br>> and not informative -- it says that swapper (pid 0) has quit
doing its job, which,<br>> since it runs everything, doesn't say much about where the particular problem <br>> could lie. The other crashes also identify swapper as the hung process.<br>> <br>> I reverted to 3.0.6, to see whether it was a kernel problem, but now the computer<br>> has crashed again. Perhaps a problem with the 3.x kernels?<br>> <br>> Next time I get physically near it I'll run an extended version of memtest, to see<br>> whether this is caused by flaky memory. A few months ago this computer was too<br>> touchy to accept either new gigabyte ethernet cards or new RAM. Perhaps the hardware<br>> is failing.<br>> <br>> Any ideas for further diagnostics? The log files are completely uninformative. The<br>> filesystems are not even close to being full, and, up until recently, it seemed to<br>> be running reliably. Thanks for any suggestions.<br><br>It seems to be an issue that has hit various people with
3.1, 3.0, 2.6.39,<br>etc, back to around 2.6.37. Something to do with an NMI watchdog rewrite<br>and some bad interaction with suspend/powermanagement.<br><br>Seems it is still being worked on, since no one quite has figured out what happens.<br><br>-- <br>Len Sorensen<br>--<br>The Toronto Linux Users Group. Meetings: <a href="http://gtalug.org/" target="_blank">http://gtalug.org/</a><br>TLUG requests: Linux topics, No HTML, wrap text below 80 columns<br>How to UNSUBSCRIBE: <a href="http://gtalug.org/wiki/Mailing_lists" target="_blank">http://gtalug.org/wiki/Mailing_lists</a><br><br><br></div></div></blockquote></div></div></body></html>