[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 4 Apr 2013 11:33:02 +0200
From: Borislav Petkov <bp@...en8.de>
To: Jiri Slaby <jslaby@...e.cz>
Cc: "Rafael J. Wysocki" <rjw@...k.pl>,
Bjorn Helgaas <bhelgaas@...gle.com>, x86@...nel.org,
lkml <linux-kernel@...r.kernel.org>,
Konstantin Khlebnikov <khlebnikov@...nvz.org>
Subject: Re: Uhhuh. NMI received for unknown reason 2c on CPU 0.
On Thu, Apr 04, 2013 at 09:32:09AM +0200, Jiri Slaby wrote:
> And yesterday I plugged in an ethernet cable for a wihle and guess
> what happened today: Uhhuh. NMI received for unknown reason 2c on CPU
> 0.
>
> Still holds that this is the first time since Jan.
Yeah, you could try my sure-fire way to trigger it:
* boot the box without any "nmi_watchdog" tweaks on the kernel cmdline -
i.e. it should be enabled.
* turn off NMI watchdog through powertop or directly through
/proc/sys/kernel/nmi_watchdog
* suspend to disk
Now when you resume, you should either see unknown reason 2c or 3c.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists