From: Andi Kleen <ak@suse.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: Len Brown <lenb@kernel.org>,
linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: [patch] x86_64: do not enable the NMI watchdog by default
Date: Thu, 7 Dec 2006 18:24:33 +0100 [thread overview]
Message-ID: <200612071824.33169.ak@suse.de> (raw)
In-Reply-To: <20061207121135.GA15529@elte.hu>
> and it needs to be
> undone via the patch attached further below.
I disagree. And it has often saved my ass on 64bit. I
On 32bit it might be reevaluated -- i didn't expect that amount
of laptop firmware bugs triggered by it, but I'm not quite
ready to give up on that yet.
> If Andi wants to debug stuff via the NMI wachdog, he should use the
> nmi_watchdog=2 boot option:
This means for most lockups which are hard to reproduce we don't
get any backtrace.
And nmi_watchdog=2 is bad because it runs at HZ frequency
and has quite high overhead.
> also, lock debugging facilities catch lockup possibilities (and actual
> lockups) alot more efficiently,
Production kernels don't have lock debugging enabled because it
has far too much overhead.
> 8 were caught by lockdep, 8 by atomicity checks in the scheduler, 7 by
> DEBUG_PREEMPT and 1 by DEBUG_SPINLOCK.
None of which is enabled on non debug kernels.
> Note: zero were caught by the NMI watchdog, and i run the NMI watchdog
> enabled by default on all architectures, and i have serial logging of
> everything.
Sure lock debugging will probably catch most of this earlier,
but we don't have it usually.
-Andi
next prev parent reply other threads:[~2006-12-07 17:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-06 22:30 [patch] ACPI, i686, x86_64: fix laptop bootup hang in init_acpi() Ingo Molnar
2006-12-06 23:57 ` Len Brown
2006-12-07 11:08 ` Ingo Molnar
2006-12-07 12:11 ` [patch] x86_64: do not enable the NMI watchdog by default Ingo Molnar
2006-12-07 12:30 ` Alan
2006-12-07 20:38 ` Andrew Morton
2006-12-07 20:47 ` Ingo Molnar
2006-12-07 20:49 ` Ingo Molnar
2006-12-07 20:55 ` [patch] net: dev_watchdog() locking fix Ingo Molnar
2006-12-07 21:06 ` Herbert Xu
2006-12-08 23:19 ` Andrew Morton
2006-12-08 23:59 ` Herbert Xu
2006-12-09 22:02 ` David Miller
2006-12-11 7:45 ` Andrew Morton
2006-12-11 7:51 ` Herbert Xu
2006-12-11 7:56 ` Ingo Molnar
2006-12-11 20:09 ` Andrew Morton
2006-12-07 17:24 ` Andi Kleen [this message]
2006-12-07 2:28 ` [patch] ACPI, i686, x86_64: fix laptop bootup hang in init_acpi() Sergio Monteiro Basto
2006-12-07 4:47 ` Karsten Wiese
2006-12-07 11:09 ` Ingo Molnar
2006-12-07 11:24 ` Ingo Molnar
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=200612071824.33169.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@osdl.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