lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 04 Apr 2013 11:38:21 +0200
From:	Jiri Slaby <jslaby@...e.cz>
To:	Borislav Petkov <bp@...en8.de>, "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 04/04/2013 11:33 AM, Borislav Petkov wrote:
> 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.

Oh, this reminds me that this time it might be unrelated to yesterday's
use of ethernet. Because today, I resumed the system by a kernel which I
didn't pass nmi_watchdog=0 to.

Hmm. So you can silently ignore the report I sent today :).

And sure, the way you describe above "works" for me to trigger the
issue... I just wanted to note the ethernet may interfere.

Anyway, I will bake some hack to disable NMI before jumping to the
resumed kernel and will see what happens...

-- 
js
suse labs
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ