From: Bill Davidsen <davidsen@tmr.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Andi Kleen <ak@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: [patch] disable NMI watchdog by default
Date: Mon, 05 Mar 2007 11:02:45 -0500 [thread overview]
Message-ID: <45EC3F25.5060308@tmr.com> (raw)
In-Reply-To: <20070114092926.GA14465@elte.hu>
Ingo Molnar wrote:
> From: Ingo Molnar <mingo@elte.hu>
> Subject: [patch] disable NMI watchdog by default
>
> there's a new NMI watchdog related problem: KVM crashes on certain
> bzImages because ... we enable the NMI watchdog by default (even if the
> user does not ask for it) , and no other OS on this planet does that so
> KVM doesnt have emulation for that yet. So KVM injects a #GP, which
> crashes the Linux guest:
>
> general protection fault: 0000 [#1]
> PREEMPT SMP
> Modules linked in:
> CPU: 0
> EIP: 0060:[<c011a8ae>] Not tainted VLI
> EFLAGS: 00000246 (2.6.20-rc5-rt0 #3)
> EIP is at setup_apic_nmi_watchdog+0x26d/0x3d3
>
> and no, i did /not/ request an nmi_watchdog on the boot command line!
>
> Solution: turn off that darn thing! It's a debug tool, not a 'make life
> harder' tool!!
>
> with this patch the KVM guest boots up just fine.
>
> And with this my laptop (Lenovo T60) also stops its sporadic hard
> hanging (sometimes in acpi_init(), sometimes later during bootup,
> sometimes much later during actual use) as well. It hung with both
> nmi_watchdog=1 and nmi_watchdog=2, so it's generally the fact of NMI
> injection that is causing problems, not the NMI watchdog variant, nor
> any particular bootup code.
>
> The patch is unintrusive.
I'm missing something, what limits this to systems running under kvm?
--
Bill Davidsen <davidsen@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
next prev parent reply other threads:[~2007-03-05 16:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-14 9:29 [patch] disable NMI watchdog by default 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 [this message]
2007-03-08 19:44 ` Avi Kivity
-- strict thread matches above, loose matches on Subject: below --
2007-03-05 12:20 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
2007-03-05 20:40 ` Linus Torvalds
2007-03-07 3:06 ` Roland Dreier
2007-03-07 14:56 ` Andi Kleen
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=45EC3F25.5060308@tmr.com \
--to=davidsen@tmr.com \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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