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:	Mon, 5 Mar 2007 21:26:48 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Andi Kleen <ak@...e.de>
Cc:	Len Brown <lenb@...nel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org,
	Arjan van de Ven <arjan@...radead.org>,
	Adrian Bunk <bunk@...sta.de>,
	Alan Cox <alan@...rguk.ukuu.org.uk>
Subject: Re: [patch] disable NMI watchdog by default


* Andi Kleen <ak@...e.de> wrote:

> > There are multiple machines not booting because of nmi_watchdog.
> > Some of them are documented here:
> > http://bugzilla.kernel.org/show_bug.cgi?id=7839
> > 
> > We used to think this was the "nolapic" bug,
> > but it is actually the "nmi_watchdog=0" bug.
> 
> I thought that one was worked around by Ingo's patch to not do nmi 
> watchdog during ACPI methods, wasn't it?

unfortunately that only made the lockups on my laptop rarer, it didnt 
totally solve it. My workaround was only done for init acpi methods 
(bootup) - it was getting really ugly when i tried to extend it to all 
ACPI execution. I'd guess the situation on those other systems is 
similar.

Maybe we could take only the 32-bit side of my patch, because that's 
what is most affected by legacies. Although i suspect Windows still 
doesnt inject NMIs in 64-bit mode either, so i dont think there's any 
fundamental difference in terms of breakage in the future, it's just 
that 64-bit systems and 64-bit testing is 1:5 - 1:10 rarer than 32-bit 
testing.

dunno. A distro can still patch the NMI watchdog on, easily. If you 
think it's a better approach i can make this a .config option - just 
like CONFIG_DETECT_SOFTLOCKUP: CONFIG_DETECT_HARDLOCKUP, which would 
default to off?

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