From: Ingo Molnar <mingo@elte.hu>
To: Andi Kleen <ak@suse.de>
Cc: Len Brown <lenb@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Arjan van de Ven <arjan@infradead.org>,
Adrian Bunk <bunk@stusta.de>, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [patch] disable NMI watchdog by default
Date: Mon, 5 Mar 2007 21:26:48 +0100 [thread overview]
Message-ID: <20070305202648.GA2184@elte.hu> (raw)
In-Reply-To: <200703052054.45292.ak@suse.de>
* Andi Kleen <ak@suse.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
next prev parent reply other threads:[~2007-03-05 20:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-05 12:20 [patch] disable NMI watchdog by default Ingo Molnar
2007-03-05 14:49 ` Arjan van de Ven
2007-03-05 17:42 ` Len Brown
2007-03-05 19:54 ` Andi Kleen
2007-03-05 20:26 ` Ingo Molnar [this message]
2007-03-05 20:40 ` Linus Torvalds
2007-03-07 3:06 ` Roland Dreier
2007-03-07 14:56 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2007-01-14 9:29 Ingo Molnar
2007-01-14 14:45 ` Henrique de Moraes Holschuh
2007-01-14 16:45 ` Arjan van de Ven
2007-03-05 16:02 ` Bill Davidsen
2007-03-08 19:44 ` Avi Kivity
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070305202648.GA2184@elte.hu \
--to=mingo@elte.hu \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjan@infradead.org \
--cc=bunk@stusta.de \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox