From: Keith Owens <kaos@ocs.com.au>
To: "Andrew Morton" <morton@nortelnetworks.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.2-ac21
Date: Fri, 23 Mar 2001 13:16:18 +1100 [thread overview]
Message-ID: <6054.985313778@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Fri, 23 Mar 2001 01:50:49 -0000." <3ABAABF9.294E89BD@asiapacificm01.nt.com>
On Fri, 23 Mar 2001 01:50:49 +0000,
"Andrew Morton" <morton@nortelnetworks.com> wrote:
>Keith Owens 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.
I know why it was turned off by default. The annoying this is that now
the *only* way to activate the watchdog is via a boot command. It is
not possible to compile a standard debugging kernel with this option
turned on, you have to rely on every user setting the boot options for
every kernel. If it is going to be off by default there should be a
way to patch the kernel to make it on by default.
next prev parent reply other threads:[~2001-03-23 2:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-22 23:02 Linux 2.4.2-ac21 Frank de Lange
2001-03-23 1:35 ` Keith Owens
2001-03-23 1:50 ` Andrew Morton
2001-03-23 2:16 ` Keith Owens [this message]
2001-03-23 14:13 ` Admin Mailing Lists
2001-03-23 14:40 ` Adrian Bunk
-- strict thread matches above, loose matches on Subject: below --
2001-03-22 18:35 Alan Cox
2001-03-22 19:20 ` Geert Uytterhoeven
2001-03-22 23:25 ` Sergey Kubushin
2001-03-22 23:36 ` Alan Cox
2001-03-23 0:11 ` Sergey Kubushin
2001-03-23 7:52 ` Geert Uytterhoeven
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=6054.985313778@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=morton@nortelnetworks.com \
/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