From: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
To: Bob <recbo@nishanet.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Catching NForce2 lockup with NMI watchdog
Date: Tue, 9 Dec 2003 15:21:30 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.55.0312091514130.20948@jurand.ds.pg.gda.pl> (raw)
In-Reply-To: <3FD3DFEB.1010902@nishanet.com>
On Sun, 7 Dec 2003, Bob wrote:
> I have append="nmi_watchdog=1" ? Nothing "nmi" or "NMI" is logged.
>
> cat /proc/interrupts
> CPU0
> 0: 241105839 XT-PIC timer
> 1: 27337 IO-APIC-edge i8042
> 2: 0 XT-PIC cascade
> 8: 1 IO-APIC-edge rtc
> 9: 0 IO-APIC-level acpi
> 12: 217952 IO-APIC-edge i8042
> 14: 22 IO-APIC-edge ide0
> 15: 24 IO-APIC-edge ide1
> 16: 4245875 IO-APIC-level 3ware Storage Controller, yenta, yenta
> 17: 5428737 IO-APIC-level eth0
> 21: 0 IO-APIC-level NVidia nForce2
> NMI: 0
> LOC: 241091187
> ERR: 0
> MIS: 6
You don't have the NMI watchdog working, because the timer interrupt is
configured as an 8259A interrupt ("XT-PIC" for IRQ 0 in the output above).
This usually means the wiring of a particular system doesn't provide any
other alternative or configuration data provided by the BIOS is broken.
The timer interrupt has to be configured as an I/O APIC interrupt for the
watchdog to work, or you can select "nmi_watchdog=2" for an alternative
watchdog internal to processors if they support it.
--
+ Maciej W. Rozycki, Technical University of Gdansk, Poland +
+--------------------------------------------------------------+
+ e-mail: macro@ds2.pg.gda.pl, PGP key available +
next prev parent reply other threads:[~2003-12-09 14:22 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-05 4:54 Catching NForce2 lockup with NMI watchdog Jesse Allen
2003-12-05 7:40 ` Mikael Pettersson
2003-12-05 8:33 ` Josh McKinney
2003-12-05 12:14 ` Mikael Pettersson
2003-12-05 14:19 ` Craig Bradney
2003-12-05 17:05 ` Craig Bradney
2003-12-05 18:11 ` Josh McKinney
2003-12-05 8:58 ` Mike Fedyk
2003-12-05 12:06 ` Mikael Pettersson
2003-12-08 2:20 ` Bob
2003-12-09 14:21 ` Maciej W. Rozycki [this message]
2003-12-09 16:35 ` Bob
2003-12-10 13:41 ` Maciej W. Rozycki
2003-12-12 16:01 ` bill davidsen
2003-12-12 16:47 ` Maciej W. Rozycki
2003-12-12 16:57 ` Richard B. Johnson
2003-12-12 17:21 ` Maciej W. Rozycki
2003-12-13 5:16 ` Bill Davidsen
2003-12-15 13:23 ` Maciej W. Rozycki
2003-12-12 22:27 ` George Anzinger
2003-12-15 13:13 ` Maciej W. Rozycki
2003-12-15 21:42 ` George Anzinger
2003-12-16 13:37 ` Maciej W. Rozycki
2003-12-16 13:57 ` Richard B. Johnson
2003-12-16 15:47 ` Maciej W. Rozycki
2003-12-16 16:44 ` Richard B. Johnson
2003-12-16 16:50 ` Maciej W. Rozycki
2003-12-16 17:26 ` George Anzinger
2003-12-16 20:54 ` Maciej W. Rozycki
2003-12-16 21:53 ` George Anzinger
2003-12-17 14:03 ` Maciej W. Rozycki
2003-12-05 19:11 Allen Martin
2003-12-05 20:18 ` cheuche+lkml
2003-12-05 20:34 ` Prakash K. Cheemplavam
2003-12-05 21:02 ` Mike Fedyk
2003-12-05 20:55 ` Jesse Allen
2003-12-06 3:20 ` Jesse Allen
2003-12-05 20:36 ` Jesse Allen
2003-12-05 22:55 ` Mike Fedyk
2003-12-05 23:11 ` Craig Bradney
2003-12-05 20:56 Allen Martin
2003-12-05 22:41 b
2003-12-07 19:58 Fixes for nforce2 hard lockup, apic, io-apic, udma133 covered Ian Kumlien
2003-12-08 2:07 ` Ross Dickson
2003-12-09 18:12 ` Catching NForce2 lockup with NMI watchdog Ian Kumlien
2003-12-09 22:04 ` Craig Bradney
2003-12-09 23:13 ` Ian Kumlien
2003-12-10 6:14 ` Bob
2003-12-10 7:51 ` Craig Bradney
2003-12-13 3:56 Ross Dickson
2003-12-15 13:16 ` Maciej W. Rozycki
2003-12-17 18:14 Ross Dickson
2003-12-17 21:41 ` George Anzinger
2003-12-17 21:48 ` George Anzinger
2003-12-18 1:30 ` Ross Dickson
2003-12-18 14:32 ` Maciej W. Rozycki
2003-12-19 4:17 ` Ross Dickson
2003-12-19 15:35 ` Maciej W. Rozycki
2003-12-18 14:04 ` Maciej W. Rozycki
2003-12-18 14:22 ` Craig Bradney
2003-12-19 5:38 ` Ross Dickson
2003-12-19 10:36 ` Craig Bradney
2003-12-19 4:06 ` Ross Dickson
2003-12-19 15:33 ` Maciej W. Rozycki
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=Pine.LNX.4.55.0312091514130.20948@jurand.ds.pg.gda.pl \
--to=macro@ds2.pg.gda.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=recbo@nishanet.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;
as well as URLs for NNTP newsgroup(s).