Visit Jeremy's Blog.
Go Back > Forums > Linux Forums > Linux - Hardware
User Name
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?


  Search this Thread
Old 12-03-2005, 01:40 PM   #1
Registered: Oct 2003
Location: Zürich
Distribution: Debian
Posts: 537

Rep: Reputation: 39
APIC eror on CPU0: 40(40)

Hi all,

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.

Most interestingly:
>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?
Old 12-03-2005, 02:44 PM   #2
Registered: Oct 2003
Location: Zürich
Distribution: Debian
Posts: 537

Original Poster
Rep: Reputation: 39
I should mention that this time several of the partitions are using the ReiserFS file system. In previous installations, all partitions except swap were using ext3. Maybe that could make a difference. At least it gives me something to try if I don't make any progress.
Old 12-04-2005, 01:05 PM   #3
Registered: Oct 2003
Location: Zürich
Distribution: Debian
Posts: 537

Original Poster
Rep: Reputation: 39
For the benefit of any future forum searchers...

It turned out to be my ATA/IDE cable. It has suffered some damage at one of the connectors -- the one the Linux drive was attached to. On a hunch I stole the CD-ROMs' IDE cable, and everything is smooth now. As soon as I can pick up another cable, of course, I'll have CD again. (I went to the store today to pick one up and they wanted 40 SFR for it, when I can order it for 11. )

Anyway, no flashing BIOS, no disabling APIC, and my two older hdds are probably fine, too.
Old 12-05-2005, 04:45 PM   #4
LQ Newbie
Registered: Dec 2005
Posts: 14

Rep: Reputation: 0
It appears not to be the problem in your case, but I had very similar errors, and an unstable system, when running a SMP kernel on a single-processor system. (Also for the benifit of future searchers )


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
get cpu0 and cpu1 to work like one ? Soulstealer Linux - Hardware 2 04-28-2005 08:55 AM
APIC error on CPU0: 00(02) on a dual athlon running SMP kernel asalford Linux - Hardware 0 08-30-2004 11:23 PM
can anyone help me pl with this eror i a python script safrout Programming 0 08-03-2004 02:38 AM
kernel:CPU0:machine check exception:0000000000000004 madhabendra Red Hat 0 06-10-2004 11:49 PM
XT-PIC vs. IO-APIC-edge vs. IO-APIC-level pebraun Linux - Newbie 0 04-19-2004 04:10 PM > Forums > Linux Forums > Linux - Hardware

All times are GMT -5. The time now is 08:38 PM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration