mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Lundell <linux@lundell-bros.com>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org, kaos@ocs.com.au
Subject: NMI watchdog stability
Date: Wed, 18 Sep 2002 16:55:13 -0700	[thread overview]
Message-ID: <p05111a08b9aec118552d@[10.2.2.25]> (raw)
In-Reply-To: <3D88F2D7.DD8519E6@digeo.com>

Back in March 2001, Keith Owens wrote and Andrew Morton replied:
At 4:47pm -0700 9/18/02, Jonathan Lundell wrote:
>  >
>>  Am I the only person who is annoyed that nmi watchdog is now off by
>>  default and the only way to activate it is by a boot parameter? You
>>  cannot even patch the kernel to build a version that has nmi watchdog
>>  on because the startup code runs out of the __setup routine, no boot
>>  parameter, no watchdog.
>
>It was causing SMP boxes to crash mysteriously after
>several hours or days. Quite a lot of them. Nobody
>was able to explain why, so it was turned off.

This was in the context of 2.4.2-ac21. More of the thread,with no 
conclusive result, can be found at 
http://www.uwsg.iu.edu/hypermail/linux/kernel/0103.2/0906.html

Was there any resolution? Was the problem real, did it get fixed, and 
is it safe to turn on the local-APIC-based NMI ticker on a 2.4.9 SMP 
system? (I'm stuck with 2.4.9, actually Red Hat's 2.4.9-31, for 
external reasons.) What was the nature of the mysterious crashes?

Thanks.
-- 
/Jonathan Lundell.

  reply	other threads:[~2002-09-18 23:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-18 14:46 [BENCHMARK] contest results for 2.5.36 Con Kolivas
2002-09-18 16:41 ` Andrew Morton
2002-09-18 16:50   ` Rik van Riel
2002-09-19  8:05     ` Daniel Phillips
2002-09-19  8:14       ` Con Kolivas
2002-09-18 21:17   ` Con Kolivas
2002-09-18 21:40     ` Andrew Morton
2002-09-18 23:55       ` Jonathan Lundell [this message]
2002-09-19 12:07         ` NMI watchdog stability John Levon
2002-09-19 13:20           ` Richard B. Johnson

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='p05111a08b9aec118552d@[10.2.2.25]' \
    --to=linux@lundell-bros.com \
    --cc=akpm@digeo.com \
    --cc=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®