Skip to contentSkip to conversation

APIC error on CPU0: 04(04)

DISCUSSION Kacper Wysocki 1 participant 1 message Feb 21, 2003

lore
Share & tools
lore
#0 lore raw

(my apologies for quirky webmail formatting)
Thanks Ravi and thanks Vladimir for your interest in my problem.

1. I _was_ hoping it would be as simple as changing the bios setting- I did find the setting you describe, and I changed it from 1.4 to 1.1. Alas, it didn't help. Following suite, I set my bios settings to "fail-safe" mode, which resulted in being able to boot win2000 again (it reset the machine every time I would select it from lilo, which is, by the way, the same thing the BeOS Developer Edition does on this new mobo), but I did _not_ get an SMP machine to go playing in the inane kindergarden that windoze is.

2. The mobo is brand new- so is the bios, newest is 1.3 which is what I have. I'm going to reflash it as you said as soon as I finish this mail.

3. My other processor burnt, thus the reason I'm running only one processor. The mobo takes both single and dual processor configurations, however as of this date MSI has only tested it up to the 2200MP. This might be a factor(I'm running 2400MP), but if so I would find it extremely strange. I am running at 133MHz fsb after all. I'll have to that up with MSI should the need arise to actually call tech support. (If all else fails, shoot yourself in the leg.)

4. I'm going to try re-seating the processor, although the manual says that if you're running uniprocessor then you can(should?) only use the primary socket. I'm also going to try obtaining a 2200MP, but this will be after I talk to MSI. Before my purchase I mailed MSI with the question whether the k7d master-l would support the 2400MP, and they said there was no reason it shouldn't.

I'm still getting the APIC error, I'm still able to boot off bf-2.4 debian rescue disks, but naught much else. My old debian boot disks, along with the newest knoppix (20/1/2003) just result in blank screens after the familiar "Loading <kernel> ......"

There's something seriously wrong here, and I hope someone can clue me in to what it is and what to do about it. My new motherboard is next to useless in this condition, and I don't know anybody who'd like to pay for that.

Regards,
Kacper

Vladimir:

Quoted 4 lines

I have an SMP machine, but with a ASUS board. I had to disable in my BIOS MPS 1.4 support to get it to work with APIC. MPS is Intel's Multiprocessor Specification. Apparently the difference between 1.1 and 1.4 is just a "tightening" of the specifications.

Ravi:

Quoted 1 line

1. It _might_ be a bad CPU. We see this occasionally, and often it is a bad

CPU.

Quoted 1 line

2. It _might_ be a bad CPU socket. You might try booting in the other socket

to

Quoted 4 lines

see if that works.
3. It _might_ be the motherboard cannot use a _single_ MP2400 processor. This is unlikely, but check the manual on this to be sure.
4. Finally, you might have to re-flash the BIOS. Often, the earlier versions

of

Quoted 45 lines

BIOSes for AMD-based motherboards do not support the later processors.

Quoted 43 lines

Hi all,
I've recently acquired an MSI k7d Master-L mobo and am currently running it
with one 2400 MP CPU. Sadly, booting linux seems to be next to impossible -
bootup works on debian boot-floppies kernels (2.4 and 2.2-based) but spews out
the following error, in great volume, on all my kernel compiles:

APIC error on CPU0: 04(04)

The occurs immediately after boot, at which point this message floods the
screen until I hard-reset the machine.

A couple of google searches yielded nothing too informative- I've found some
references to the Abit BP6 board having similar problems, this being due to a
faulty APIC implementation by the mobo manufacturer. I also found one other
person with the same problem- he finally managed to boot by disabling APIC in
the kernel config as below.

I've tried 2.4.19, 2.4.20 and 2.5.62 kernels, smp enabled or not. I've tried passing noapic or disableapic to lilo at boottime/append. I've tried going into .config (I usually do this through menuconfig) and

undefining or setting =n to all references to APIC (ie. CONFIG_APIC_GOOD=n,
CONFIG_IO_APIC=n, CONFIG_APIC_LOCAL=n).

All to no avail.

I have yet to try 2.0 and 2.2 kernels, but I would rather not, as I really
need the features in 2.4

I'm very much in hope that someone here can help me... I'm an experienced
linux user, but this is my first try at smp and I don't know what an apic is.