From: Joerg Sommrey <jo@sommrey.de>
To: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: local-/io-apic nmi watchdog failing on S2466
Date: Wed, 17 Nov 2004 18:31:18 +0100 [thread overview]
Message-ID: <20041117173118.GA5211@sommrey.de> (raw)
Hello,
I'm still having problems with nmi watchdog on my S2466 board. I tried lots
of different configurations with a large number of 2.6 kernels (vanilla,
-mm, -ac) all with the same result: no working nmi watchdog, neither with
local- nor with io-apic. I still wonder if anybody out there has ever
succeeded with a working nmi watchdog on Tyan Tiger MPX.
The symptoms are:
nmi_watchdog=1:
===============
dmesg:
testing NMI watchdog ... CPU#0: NMI appears to be stuck!
/proc/interrupts:
no NMI count
nmi_watchdog=2:
===============
dmesg:
testing NMI watchdog ... OK.
/proc/interupts:
NMI count increments
recovery from lockup:
none
nmi_watchdog=2 clock=pit:
=========================
dmesg:
testing NMI watchdog ... CPU#0: NMI appears to be stuck!
/proc/interrupts:
NMI count increments, but rate is ~ 1/20s
recovery from lockup:
none
The lockup-test is done with a little program that Ingo posted on this
list:
int
main(void) {
iopl(3);
while (1)
asm("cli");
return 0;
}
The only reaction I can see from this test: after some seconds (5+) the LEDs
on the keyboard start blinking when nmi_watchdog=2 and clock!=pit.
Always need to hit the reset button :-(
What else could I try? Are there any BIOS-settings relevant to a
working nmi-watchdog? What information is needed to track down this
problem?
Maybe it's the board's failure, but as there *are* counted NMIs I still
hope there is a software solution to this problem.
Thanks,
-jo
--
-rw-r--r-- 1 jo users 63 2004-11-17 17:45 /home/jo/.signature
next reply other threads:[~2004-11-17 17:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-17 17:31 Joerg Sommrey [this message]
2004-11-17 21:33 ` local-/io-apic nmi watchdog failing on S2466 Chris Wedgwood
2004-11-17 22:59 ` Joerg Sommrey
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=20041117173118.GA5211@sommrey.de \
--to=jo@sommrey.de \
--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