mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@osdl.org>
To: Kirill Korotaev <dev@sw.ru>
Cc: "Martin J. Bligh" <mbligh@mbligh.org>,
	Andrew Morton <akpm@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 08:48:37 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.58.0505170844550.18337@ppc970.osdl.org> (raw)
In-Reply-To: <42899797.2090702@sw.ru>



On Tue, 17 May 2005, Kirill Korotaev wrote:
> 
> BTW, why NMI watchdog is disabled by default? We constantly making it on 
> by default in our kernels and had no problems with it.
> I send a patch attached which tunes NMI watchdog by config option...

I really don't want NMI watchdogs enabled by default. It's historically 
been _very_ fragile on some systems. Whether that has been due to harware 
or sw bugs, I dunno, but it's definitely been problematic.

		Linus

  parent reply	other threads:[~2005-05-17 15:50 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
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 [this message]
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=Pine.LNX.4.58.0505170844550.18337@ppc970.osdl.org \
    --to=torvalds@osdl.org \
    --cc=akpm@osdl.org \
    --cc=dev@sw.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@mbligh.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®