Skip to contentSkip to conversation

IO-APIC on nforce2 [PATCH] + [PATCH] for nmi_debug=1 + [PATCH] for idle=C1halt, 2.6.5

DISCUSSION Andi Kleen 2 participants 2 messages Apr 15, 2004 – Apr 21, 2004 5 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

Andi Kleen

author
#5 lore raw
Quoted 4 lines · Len Brown

While I don't want to get into the business of maintaining a dmi_scan entry for every system with this issue, I think it might be a good idea to add a couple of example entries for high volume systems for which there is no BIOS fix available.

Or do a generic fix: check for the PCI-ID of the Nforce2 and when it is true and the timer is wrong just correct it. That's ugly, but it's probably the best solution for such a common issue (and the IO-APIC code is already filled with workarounds anyways)

One problem is that this likely must happen before the PCI quirks run. In the x86-64 code I have special "early PCI scanning" code for this that could be copied. I don't have a Nforce2, but when someone is willing to test I can do a patch for this.

-Andi

P.S.: This problem of reference BIOS bugs getting haunting Linux even after they are long fixed is unfortunately common :-(

#6 lore raw
Quoted 11 lines · Andi Kleen
Quoted 4 lines · Len Brown

While I don't want to get into the business of maintaining a dmi_scan entry for every system with this issue, I think it might be a good idea to add a couple of example entries for high volume systems for which there is no BIOS fix available.

Or do a generic fix: check for the PCI-ID of the Nforce2 and when it is true and the timer is wrong just correct it. That's ugly, but it's probably the best solution for such a common issue (and the IO-APIC code is already filled with workarounds anyways)

IMO the fact that the IOAPIC code is full of workarounds is a reason NOT to add another one.

Quoted 4 lines

One problem is that this likely must happen before the PCI quirks run. In the x86-64 code I have special "early PCI scanning" code for this that could be copied. I don't have a Nforce2, but when someone is willing to test I can do a patch for this.

If this issue had no other fix, I'd agree that the complexity is worth it. But a BIOS upgrade fixes this -- so I think dmi-scan simplicity is the way to go.

-Len