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]

Date:	Wed, 30 Jan 2013 23:17:06 +0100
From:	Jiri Slaby <jslaby@...e.cz>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
CC:	Borislav Petkov <bp@...en8.de>,
	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 01/30/2013 10:39 PM, Rafael J. Wysocki wrote:
>> What is cool is that I have steps to reproduce:
>> 1) boot
>> 2) run the attached script (turn on all possible power savings -- in
>> fact everything what powertop suggests)
>> 3) suspend to _disk_ (mem is not enough, BIOS apparently has to
>> interfere here)
> 
> No, I don't think it's the BIOS.  Most likely the boot kernel.

Or that...

>> 4) resume from disk
>> 5) boom
>>
>> I tried to remove also wireless drivers, no change.
> 
> Is the resume boot kernel the same as the one in the image?

Yeah, the same ones: 3.7.5

-- 
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/