APIC error on CPU0: 02(02)
I just bought a shiny new Athlon 2400+ and popped it in my biostar M7VIB with an up to date bios.
I'm running 2.6.0-test1-mm2, and I get tons of "APIC error on CPU0:
02(02)" messages. Can someone tell me what is going on?
Info about my machine's hardware:
http://www.enodev.com/info.html
Quoting Shawn <[email protected]>:
Quoted 8 lines
I just bought a shiny new Athlon 2400+ and popped it in my biostar M7VIB with an up to date bios.
I'm running 2.6.0-test1-mm2, and I get tons of "APIC error on CPU0:
02(02)" messages. Can someone tell me what is going on?Info about my machine's hardware:
http://www.enodev.com/info.html
I had the same problem on my Athlon-MP 2400+ on a Chaintech board (but my Athlon-XP 2500+ on an nForce2 board booted fine) by disabling IO-APIC and SMP in the kernel (I only have one processor atm).
-sandalle
-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/
Quoted 5 lines · Shawn
I just bought a shiny new Athlon 2400+ and popped it in my biostar M7VIB with an up to date bios.
I'm running 2.6.0-test1-mm2, and I get tons of "APIC error on CPU0:
02(02)" messages. Can someone tell me what is going on?
in the ol' BP6 times (dual Celeron) APIC errors where reported (by certain 2.4.x kernels, previous versions simply ignored them) when an error occured while the CPUs where communicating ...
as far as I understood, the communication between APIC and CPU is checksummed (a very simple checksum, like a parity) and if this checksum is invalid, the action is restarted, so this okay, because an error was avoided, but because the checksum is so simple (IIRC only two bits), chances are good that some faulty communication will go undetected ...
please, I'm no expert on Athlon APIC or such stuff, so this could be total bullshit, but maybe some APIC expert will comment on that ;)
best,
Herbert
Quoted 7 lines
Info about my machine's hardware:
http://www.enodev.com/info.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/