lkml.org 
[lkml]   [2006]   [Dec]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: [patch] x86_64: do not enable the NMI watchdog by default
Date

> 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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2006-12-07 18:27    [W:0.053 / U:41.800 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site