mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Francois Romieu <romieu@cogenit.fr>
To: PinkFreud <pf-kernel@mirkwood.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Are we going too fast? [upatch]
Date: Tue, 14 Aug 2001 19:38:17 +0200	[thread overview]
Message-ID: <20010814193817.A30391@se1.cogenit.fr> (raw)
In-Reply-To: <Pine.LNX.4.20.0108141219001.769-100000@eriador.mirkwood.net>
In-Reply-To: <Pine.LNX.4.20.0108141219001.769-100000@eriador.mirkwood.net>; from pf-kernel@mirkwood.net on Tue, Aug 14, 2001 at 12:25:34PM -0400

PinkFreud <pf-kernel@mirkwood.net> :
[...]
> >From Documentation/nmi_watchdog.txt:
> NOTE: currently the NMI-oopser is enabled unconditionally on x86 SMP
> boxes.

My 2.4.8 tree seems to disagree with the doc:
find . -name \*[ch] | xargs fgrep nmi_watchdog | grep =
./arch/i386/kernel/traps.c:int nmi_watchdog = 0;
./arch/i386/kernel/traps.c:__setup("nmi_watchdog=", setup_nmi_watchdog);
./arch/i386/kernel/io_apic.c:           nmi_watchdog = 0;

> I'm not specifically enabling it in LILO, but according to the docs, it's
> enabled already.  Unfortunately, the lockup happens when switching between
> virtual consoles, so even if something WERE printed to the screen, I'm unlikely
> to see it.

Let's hope Mr Murphy took some vacation and please give a try at 
append="nmi_watchdog=1". 

> Side note: The lockup does *NOT* occur on 2.2.19 with SMP.

The console code differs a lot. Trace would help.

-- 
Ueimor

      reply	other threads:[~2001-12-04  0:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-14 16:25 Are we going too fast? PinkFreud
2001-08-14 17:38 ` Francois Romieu [this message]

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=20010814193817.A30391@se1.cogenit.fr \
    --to=romieu@cogenit.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pf-kernel@mirkwood.net \
    /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®