From: Andi Kleen <ak@suse.de>
To: Len Brown <lenb@kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>,
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 20:54:45 +0100 [thread overview]
Message-ID: <200703052054.45292.ak@suse.de> (raw)
In-Reply-To: <200703051242.45635.lenb@kernel.org>
On Monday 05 March 2007 18:42, Len Brown wrote:
> On Monday 05 March 2007 07:20, Ingo Molnar wrote:
> >
> > Linus,
> >
> > Andrew sent the patch below (which is now months old and has been in -mm
> > for some time) towards Andi's tree 4 weeks ago, but apparently it fell
> > into a black hole there - the patch is still not upstream!
> >
> > This is a must-have for v2.6.21
>
> I agree.
> 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?
-Andi
next prev parent reply other threads:[~2007-03-05 19:55 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 [this message]
2007-03-05 20:26 ` Ingo Molnar
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=200703052054.45292.ak@suse.de \
--to=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=mingo@elte.hu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.