RE: nforce2 bugs?

Maciej W. Rozycki
2004-09-30T16:59:59Z

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).

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?

Maciej