public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kirill Korotaev <dev@sw.ru>
To: Andrew Morton <akpm@osdl.org>
Cc: mbligh@mbligh.org, torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] NMI watchdog config option (was: Re: [PATCH] NMI lockup and AltSysRq-P dumping calltraces on _all_ cpus via NMI IPI)
Date: Tue, 17 May 2005 14:41:43 +0400	[thread overview]
Message-ID: <4289CA67.60405@sw.ru> (raw)
In-Reply-To: <20050517001542.40e6c6b7.akpm@osdl.org>

[-- Attachment #1: Type: text/plain, Size: 869 bytes --]

> Kirill Korotaev <dev@sw.ru> wrote:
> 
>>BTW, why NMI watchdog is disabled by default?
> 
> 
> There was a significantly large string of reports of dying PCs in the
> 2.4.early timeframe.  These machines would mysteriously lock up after
> considerable periods of time and the problem was cured by disabling the NMI
> watchdog.  Nobody was ever able to solve it, so we changed it to default to
> off.
Hmm, it is strange, since we used 2.4 kernels with watchdog for years 
(starting from 2.4.1)...

> So much has changed in there that we might have fixed it by accident, and I
> do recall a couple of fundamental and subtle NMI bugs being fixed.  So
> yeah, it might be worth enabling it by default again.  Care to send a patch
> which does that?
I attached the patch which turns NMI watchdog on by default on i386.

Signed-Off-By: Pavel Emelianov <xemul@sw.ru>

Kirill

[-- Attachment #2: diff-ms-nmiwd-20050517 --]
[-- Type: text/plain, Size: 435 bytes --]

--- linux-2.6.12-rc4/arch/i386/kernel/nmi.c.nmiwd	2005-05-07 09:20:31.000000000 +0400
+++ linux-2.6.12-rc4/arch/i386/kernel/nmi.c	2005-05-17 13:47:38.000000000 +0400
@@ -34,7 +34,7 @@
 
 #include "mach_traps.h"
 
-unsigned int nmi_watchdog = NMI_NONE;
+unsigned int nmi_watchdog = NMI_IO_APIC;
 extern int unknown_nmi_panic;
 static unsigned int nmi_hz = HZ;
 static unsigned int nmi_perfctr_msr;	/* the MSR to reset in NMI handler */

  reply	other threads:[~2005-05-17 11:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-11 15:57 [PATCH] NMI lockup and AltSysRq-P dumping calltraces on _all_ cpus via NMI IPI Kirill Korotaev
2005-05-16 22:34 ` Martin J. Bligh
2005-05-17  7:04   ` [PATCH] NMI watchdog config option (was: Re: [PATCH] NMI lockup and AltSysRq-P dumping calltraces on _all_ cpus via NMI IPI) Kirill Korotaev
2005-05-17  7:15     ` Andrew Morton
2005-05-17 10:41       ` Kirill Korotaev [this message]
2005-05-17 14:01       ` Martin J. Bligh
2005-05-17 22:16         ` Andrew Morton
2005-05-17 22:26           ` Martin J. Bligh
2005-05-17 17:30       ` Valdis.Kletnieks
2005-05-17 15:48     ` Linus Torvalds
2005-05-17 15:59       ` Maciej W. Rozycki
2005-05-17 16:32         ` Linus Torvalds
2005-05-17 17:04           ` Maciej W. Rozycki
2005-05-17 17:20             ` Linus Torvalds
2005-05-17 17:44               ` Maciej W. Rozycki
2005-05-17 17:25     ` Valdis.Kletnieks

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=4289CA67.60405@sw.ru \
    --to=dev@sw.ru \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@mbligh.org \
    --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