From: George Anzinger <george@mvista.com>
To: macro@ds2.pg.gda.pl
Cc: bill davidsen <davidsen@tmr.com>, linux-kernel@vger.kernel.org
Subject: Re: Catching NForce2 lockup with NMI watchdog
Date: Fri, 12 Dec 2003 14:27:38 -0800 [thread overview]
Message-ID: <3FDA40DA.20409@mvista.com> (raw)
In-Reply-To: <brcoob$a02$1@gatekeeper.tmr.com>
Having had cause to try and figure out all this, I vote for the following being
included in the source somewhere...
-g
bill davidsen wrote:
> In article <Pine.LNX.4.55.0312101421540.31543@jurand.ds.pg.gda.pl>,
> Maciej W. Rozycki <macro@ds2.pg.gda.pl> wrote:
>
> | The I/O APIC NMI watchdog utilizes the property of being transparent to a
> | single IRQ source of a specially reconfigured 8259A PIC (the master one in
> | the IA32 PC architecture). There are more prerequisites that have to be
> | met and all indeed are for a 100% compatible PC as specified by the
> | Intel's Multiprocessor Specification.
> |
> | 1. The INT output of the master 8259A PIC has to be connected to the LINT0
> | (or LINTIN0; the name varies by implementations) inputs of all local APICs
> | in the system.
> |
> | 2a. The OUT0 output of the 8254 PIT (IOW the timer source) has to be
> | directly connected to the INTIN2 input of the first I/O APIC.
> |
> | 2b. Alternatively the INT output of the master 8259A PIC has to be
> | connected to the INTIN0 input of the first I/O APIC.
> |
> | 3. There must be no glue logic that would change logical properties of the
> | signal between the INT output of the master 8259A PIC and the respective
> | APIC interrupt inputs.
> |
> | In practice, assuming the MP IRQ routing information provided the BIOS has
> | been correct (which is not always the case), prerequisites #1 and #2 have
> | been met so far, but #3 has proved to be occasionally problematic.
>
> In practice many system seem to take a good bit of guessing and testing.
> I have an old P-II which only works with acpi=force and nmi_watchdog=2,
> for instance.
>
> It would be nice if there were a program which could poke at the
> hardware and suggest options which might work, as in eliminating the
> ones which can be determined not to work. Absent that trial and error
> rule, unfortunately.
--
George Anzinger george@mvista.com
High-res-timers: http://sourceforge.net/projects/high-res-timers/
Preemption patch: http://www.kernel.org/pub/linux/kernel/people/rml
next prev parent reply other threads:[~2003-12-12 22:29 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
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 [this message]
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=3FDA40DA.20409@mvista.com \
--to=george@mvista.com \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@ds2.pg.gda.pl \
/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).