mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jamie Lokier <jamie@shareable.org>
To: Zwane Mwaikambo <zwane@linuxpower.ca>
Cc: "Herbert Pötzl" <herbert@13thfloor.at>,
	"Willy Tarreau" <willy@w.ods.org>,
	linux-kernel@vger.kernel.org,
	"Alan Cox" <alan@lxorguk.ukuu.org.uk>
Subject: Re: NMI appears to be stuck! (2.4.22-rc2 on dual Athlon)
Date: Mon, 18 Aug 2003 01:16:16 +0100	[thread overview]
Message-ID: <20030818001616.GA4761@mail.jlokier.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.53.0308171822391.9067@montezuma.mastecende.com>

Zwane Mwaikambo wrote:
> > > mine works fine only with nmi_watchdog=2. Don't know why. 
> > > It's an ASUS A7M266D.
> > 
> > hmm, nmi_watchdog=2 on the kernel boot line gives no
> > difference to booting without, at least according to
> > the boot messages ...
> 
> nmi_watchdog=2 will work on the majority of i686+ (performance 
> counters with NMI delivery mode) boxes and you can check whether it's 
> enabled by doing cat /proc/interrupts and watching if the NMI line ticks 
> at a decent rate. nmi_watchdog=1 tends to be harder for hardware 
> manufacturers to get right (for some reason or other).

Is it possible to try both at boot time and pick the one which works?

-- Jamie

  parent reply	other threads:[~2003-08-18  0:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-17 21:28 Herbert Pötzl
2003-08-17 22:11 ` Willy Tarreau
2003-08-17 22:28   ` Herbert Pötzl
2003-08-17 22:28     ` Zwane Mwaikambo
2003-08-17 22:49       ` Herbert Pötzl
2003-08-18  0:16       ` Jamie Lokier [this message]
2003-08-18  7:10         ` Zwane Mwaikambo
2003-08-17 23:40 ` Karel Kulhavý
2003-08-17 22:05   ` Herbert Pötzl

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=20030818001616.GA4761@mail.jlokier.co.uk \
    --to=jamie@shareable.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=herbert@13thfloor.at \
    --cc=linux-kernel@vger.kernel.org \
    --cc=willy@w.ods.org \
    --cc=zwane@linuxpower.ca \
    /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®