| 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
| ||
|
Message-ID: <515D2C79.7040904@suse.cz> Date: Thu, 04 Apr 2013 09:32:09 +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 03/01/2013 01:55 PM, Jiri Slaby wrote: > On 01/31/2013 02:24 PM, Borislav Petkov wrote: >> On Thu, Jan 31, 2013 at 02:18:05PM +0100, Borislav Petkov wrote: >>>> And if I pass nmi_watchdog=0 to the image kernel, it should be gone I >>>> guess. >>> >>> How do you pass options the image kernel? >> >> Yep, passing "nmi_watchdog=0" to the kernel (both when you boot and >> when you resume) fixes the issue - no more unknown NMIs. Did only 3 s/r >> cycles though. > > FWIW the last time I saw the unhandled NMI was on 31st Jan. Since I > disabled NMI watchdog no more unhandled NMIs. I have to add that I don't > use ethernet at all. 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. -- 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