From: "Herbert Pötzl" <herbert@13thfloor.at>
To: linux-kernel@vger.kernel.org
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: NMI appears to be stuck! (2.4.22-rc2 on dual Athlon)
Date: Sun, 17 Aug 2003 23:28:24 +0200 [thread overview]
Message-ID: <20030817212824.GA9025@www.13thfloor.at> (raw)
Hi All!
Still no nmi_watchdog on dual Athlon systems?
Linux version 2.4.22-rc2 on dual
processor : 0
vendor_id : AuthenticAMD
cpu family : 6
model : 6
model name : AMD Athlon(tm) MP 1800+
stepping : 2
cpu MHz : 1533.401
cache size : 256 KB
Total of 2 processors activated (6127.61 BogoMIPS). ENABLING IO-APIC IRQs ..TIMER: vector=0x31 pin1=2 pin2=0 activating NMI Watchdog ... done. testing NMI watchdog ... CPU#0: NMI appears to be stuck! testing the IO APIC....................... .................................... done. Using local APIC timer interrupts. calibrating APIC timer ...
just for curiosity, if I do not give the nmi_watchdog=1
option on the kernel boot line, the nmi seems to work fine?
# cat /proc/interrupts
CPU0 CPU1
0: 4275 2602 IO-APIC-edge timer
1: 0 2 IO-APIC-edge keyboard
2: 0 0 XT-PIC cascade
4: 157 150 IO-APIC-edge serial
8: 1 0 IO-APIC-edge rtc
9: 169 186 IO-APIC-level acpi
15: 12 3 IO-APIC-edge ide1
16: 1195 1155 IO-APIC-level aic7xxx
17: 149 144 IO-APIC-level eth1
19: 1 3 IO-APIC-level eth0
NMI: 4034 3577
LOC: 6782 6777
ERR: 0
MIS: 0
is this intentional, or have I missed something
terrible important? if you need more information,
let me know ...
TIA,
Herbert
next reply other threads:[~2003-08-17 21:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-17 21:28 Herbert Pötzl [this message]
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
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=20030817212824.GA9025@www.13thfloor.at \
--to=herbert@13thfloor.at \
--cc=alan@lxorguk.ukuu.org.uk \
--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
all inboxes | Powered by JetHome®