IOAPIC Sickness in 2.3.99 with PPro single processor systems

From: Jeff V. Merkey (jmerkey@timpanogas.com)
Date: Wed Apr 05 2000 - 10:20:32 EST


On a dual processor PPro system with one of the processors removed,
2.3.99 during boot gets

IOAPIC: (some text here, the screen scrolls so fast it's hard to read)
  REG 0000004
  REG 0000004
  This Should Never Happen !!!!

which scrolls on the screen so fast, you can't even read it
intelligently. It happens before the root fs is mounted, so none of it
makes it into the /var/log/messages file. What's different about this
system is that it is a Dual PPro Server with one of the processors
removed. MPS tables are present in memory on these systems even
uniprocessor. What looks like it happening is someone is detecting 2
processors listed in the MPS tables (these systems are 1.4 MPS), then
trying to send an IPI message to a non-existent Local APIC on the other
processor (for some reason, this system still reports two processors in
the MPS tables. NT, NetWare, and MANOS all handle this just fine, it
looks like Linux is expecting the other processor to really be there,
then barf when it cannot send a STARTUP_IPI message to it. I tried the
IOAPIC in UP Mode option in config as well as SMP (SMP=N does not seem
to build anymore), but 2.3.99 still gets this behavior.

Jeff

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Fri Apr 07 2000 - 21:00:14 EST