public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ross Dickson <ross@datscreative.com.au>
To: "Maciej W. Rozycki" <macro@linux-mips.org>,
	Andy Currid <ACurrid@nvidia.com>
Cc: "Prakash K. Cheemplavam" <prakashkc@gmx.de>,
	Allen Martin <AMartin@nvidia.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	white phoenix <white.phoenix@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: nforce2 bugs?
Date: Fri, 1 Oct 2004 13:41:04 +1000	[thread overview]
Message-ID: <200410011341.04506.ross@datscreative.com.au> (raw)
In-Reply-To: <Pine.LNX.4.58L.0409301705180.25286@blysk.ds.pg.gda.pl>

On Friday 01 October 2004 02:59, Maciej W. Rozycki wrote:
> On Thu, 30 Sep 2004, Andy Currid wrote:
> 
> > I'm taking a look at the patches discussed in other recent emails on the
> > list, but I'm curious about the timer issue that Maciej notes here. In
> > systems running in IOAPIC mode where this problem has been observed, is
> > ACPI enabled?
> 
>  One I can test a bit has indeed ACPI enabled.
> 
> > I strongly suspect that it is. Some BIOSes on nForce systems contain an
> > incorrect INT override for the timer interrupt in their ACPI tables,
> > indicating that in IOAPIC mode the timer interrupts on IRQ2 rather than
> > IRQ0. The kernel honors the override, then notices the timer interrupt
> > isn't working and subsequently rescues the situation by configuring the
> > timer in ExtInt mode. That recovers the timer interrupt but I suspect
> > that configuration may be responsible for the "noisy" behavior (it's a
> > faulty configuration).

It is indeed the other way around, the clock skew occurs on some Mobos
with timer interrupts routed to the IntIn0 and to my knowledge is not evident
in the ExtInt routing mode.
The downside of using the ExtInt routing mode is that you can no longer use
nmi_watchdog=1 because it only works on nforce2 boards with IntIn0 timer routing.

> 
>  The firmware (BIOS) reports I/O APIC interrupts correctly on this box --
> there's no override for IRQ0.  Timer interrupts work correctly in the
> ExtInt mode.  They only fail in the I/O APIC mode.
> 
>  Older reports from the list show exactly the same problem, e.g.  
> "http://www.uwsg.iu.edu/hypermail/linux/kernel/0404.1/0739.html", which is
> probably one of the earliest references to the clock skew problem with I/O
> APIC routing.  As I believe both the 8254 and 8259A and the I/O APIC are
> internal to the chipset, I doubt that can be a problem specific to board
> design; it may be a firmware fault, though, such as an initialization bug.  
> As Ross used to maintain temporary workarounds for nforce2 problems, he
> may be able to comment on what reports he received.  Ross?

An earlier Thread on the Topic of the time skew with I/O Apic routing:
http://linux.derkeiler.com/Mailing-Lists/Kernel/2004-01/3129.html

A couple of Skewing Mobos Involved:
Abit NF7-S V2.0 motherboard. 
A7N8X Deluxe mobo/Athlon

Maybe they are using the same revision of non GPU nforce2 silicon?
I personally never had any clock skew but I have only used Mobos with graphics
onboard, several Albatron KM18G and an Epox 8RGA+

-Ross



> 
>   Maciej
> 
> 
> 


  reply	other threads:[~2004-10-01  3:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-30 15:43 nforce2 bugs? Andy Currid
2004-09-30 16:59 ` Maciej W. Rozycki
2004-10-01  3:41   ` Ross Dickson [this message]
2004-10-01 11:16     ` Jesse Stockall
  -- strict thread matches above, loose matches on Subject: below --
2004-10-02  2:13 Jesse Allen
2004-09-29 22:42 white phoenix
2004-09-29 22:17 ` Alan Cox
2004-09-30  0:32   ` white phoenix
2004-09-30  9:25   ` Prakash K. Cheemplavam
2004-09-30 14:24     ` 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=200410011341.04506.ross@datscreative.com.au \
    --to=ross@datscreative.com.au \
    --cc=ACurrid@nvidia.com \
    --cc=AMartin@nvidia.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@linux-mips.org \
    --cc=prakashkc@gmx.de \
    --cc=white.phoenix@gmail.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