From: Craig Bradney <cbradney@zip.com.au>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Ross Dickson <ross@datscreative.com.au>,
george@mvista.com, linux-kernel@vger.kernel.org
Subject: Re: Catching NForce2 lockup with NMI watchdog
Date: Thu, 18 Dec 2003 15:22:43 +0100 [thread overview]
Message-ID: <1071757363.18749.42.camel@athlonxp.bradney.info> (raw)
In-Reply-To: <Pine.LNX.4.55.0312181347540.23601@jurand.ds.pg.gda.pl>
Just as an FYI, still going strong here with the old api and ioapic
patches. 5d 20h now.
When the official 2.6.0 comes to Gentoo Linux I can try that with
whatever patches people are finding stable for these nforce fixes.
Anyone had any luck in talking to ASUS re a BIOS update?
Craig
On Thu, 2003-12-18 at 15:04, Maciej W. Rozycki wrote:
> On Thu, 18 Dec 2003, Ross Dickson wrote:
>
> > Here is where to find Intel's MP arch spec Maceij mentions.
> > I had to find it recently wrt nforce2 issues
> >
> > http://www.intel.com/design/pentium/datashts/24201606.pdf
> >
> > Section 3.6.1 Apic Architecture is relevant
> > particularly
> > Section 3.6.2.2 Virtual Wire Mode
>
> BTW, I have revision 1.1 as well in case anyone was interested in the
> differences.
>
> > I would like to add a footnote to highlight a potential gotcha as I
> > understand it.
> >
> > To clarify, the xt pic 8259A does not in itself have a transparent mode
> > as would a logic buffer or inverter. It always needs inta cycles to
> > function. In PIC mode it is wired to processor pins as per old 8086 and
> > original cpu architecture provides the inta cycles to it (bypasses apic,
> > apic seems off).
>
> It does have such a mode. ;-) You just have not to ack a pending
> interrupt -- if a request goes away, the INT output gets deasserted as
> well. We are super cautious though and we reprogram the 8259A into the
> AEOI mode to prevent a lockup in case INTA cycles escape to the 8259A
> (which is theoretically possible for a broken design of an i82489DX-based
> system). See the 8259A datasheet for details.
>
> > I certainly agree with Marceij's comments that mixed mode of having 8254 PIT
> > routed via the 8259A was never meant to occur alongside ioapic handling of
> > the other interrupts. It is very problematic not to mention confusing.
>
> Well, the true "mixed mode", i.e. where certain interrupts are delivered
> as I/O APIC (either LoPri or Fixed) interrupts and others are routed
> through an 8259A controller and delivered as ExtINTA interrupts was
> specifically designed to work since the i8248DX APIC. What wasn't
> designed but works by the properties of the 8259A PIC is the transparent
> "through-8259A" mode.
>
> Maciej
next prev parent reply other threads:[~2003-12-18 14:23 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-17 18:14 Catching NForce2 lockup with NMI watchdog 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2003-12-13 3:56 Ross Dickson
2003-12-15 13:16 ` Maciej W. Rozycki
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-05 22:41 b
2003-12-05 20:56 Allen Martin
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 4:54 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
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
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=1071757363.18749.42.camel@athlonxp.bradney.info \
--to=cbradney@zip.com.au \
--cc=george@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@ds2.pg.gda.pl \
--cc=ross@datscreative.com.au \
/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).