Got my new hdd, ensured that the first (windows) disk was secure, and installed Sarge 3.1r0a on the new disk (hdb). Upon rebooting to confiugure the newly installed system, I started getting endless errors as in the subject line:
APIC error on CPU0: 40(40)
I rebooted with ctl+alt+del, and the messages still came. They kicked the blue configuration screens off, making further configuration impossible. So, I rebooted with Knoppix (take that, windows) to have a look what Google could tell me.
Google tells me the following:
* Advanced Programmable Interrupt Controller (APIC, not ACPI, heh)
* It could be a hardware problem "somewhere," and in any case it's due to interrupts that APIC can't handle.
* The problem appears to be most common to SiS chipsets, which my motherboard uses (an MSI board with SiS 648 chipset).
* It can reportedly be solved on some boards by a BIOS upgrade.
>Apr 5 23:16:20 lfs kernel: APIC error on CPU0: 60(60)
>Apr 5 23:16:31 lfs kernel: APIC error on CPU0: 60(60)
>kernel is 2.6.5 with reiser4 patch.
Send Illegal Vector and Receive Illegal Vector at the same time.
This is more interesting than the usual 40(40) errors
(just Receive Illegal Vector), since 60 implies that the
CPU itself is the source of the bogus vector, whereas 40
usually implies a crap mainboard.
My guess is that either your hardware (whatever it is,
you didn't leave any clues) has problems with a noisy
APIC bus, broken chipset, or something like that, or
you enabled ACPI and the ACPI tables are crap.
Thus, the problem is only "Receive Illegal Vector."
The suggestion came not infrequently to simply to boot without APIC (with a bootcheat in GRUB, for example, which I can't really get to unless I do it with Knoppix.) I don't like this solution, it's inelegant. Besides, I just had Sarge stable installed -- like 3 times in the last month, the disks were dying, or so it seems; perhaps my mobo is getting screwy and it just seemed like disk errors -- and the error never happened. The only thing that's changed in the setup is a new hard-drive. It's the same chipset and same installation media.
I figure it's entirely possible that my mainboard has recently started to hit the wall. I've never flashed a BIOS, and would hate to start on the machine I currently rely on. (Windows is working, and so it's unacceptable to ruin the machine just for "that Linux stuff.") Besides, if it didn't happen in the previous installations, chances are the BIOS upgrade is not what is needed.
Even if turning APIC is inelegant, it just might be preferable to risking my mainboard's BIOS over. (Plus, just thinking of writing down and resetting all those values, ick.)
What possibilities might I be overlooking? What would you do in my position?
Ignore the problem and it'll go away?