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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20130130174402.GB23980@pd.tnic>
Date:	Wed, 30 Jan 2013 18:44:02 +0100
From:	Borislav Petkov <bp@...en8.de>
To:	Bjorn Helgaas <bhelgaas@...gle.com>
Cc:	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 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.

Thanks.

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