linux-kernel - Re: Uhhuh. NMI received for unknown reason 2c on CPU 0.

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]

Message-ID: <510977FB.3030707@suse.cz>
Date:	Wed, 30 Jan 2013 20:43:55 +0100
From:	Jiri Slaby <jslaby@...e.cz>
To:	Borislav Petkov <bp@...en8.de>,
	Bjorn Helgaas <bhelgaas@...gle.com>, x86@...nel.org,
	lkml <linux-kernel@...r.kernel.org>,
	Konstantin Khlebnikov <khlebnikov@...nvz.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: Uhhuh. NMI received for unknown reason 2c on CPU 0.

On 01/30/2013 06:44 PM, Borislav Petkov wrote:
> On Wed, Jan 30, 2013 at 10:27:42AM -0700, Bjorn Helgaas wrote:
>> You're right, I don't think we're quite ready to merge those patches.
>> But if your NMI is easy to reproduce, it might be worth removing
>> e1000e altogether to see if it still happens.
> 
> That's the problem - I've seen it only once so far. I'll watch out for
> it and do the above when I find a reliable way of reproducing it. Will
> keep you posted.

It happens here too. Dunno what is the root cause. I *think* that it
never happened unless I used ethernet. Other than that I see no pattern.

Attaching -C 20 grep of messages over the last half year if there is
something that may help somehow.

-- 
js
suse labs

View attachment "lll" of type "text/plain" (73519 bytes)