VMware Cloud Community
Erik_Zandboer
Expert
Expert
Jump to solution

ALERT: APIC: 1354 error on console

Hi, I have just build me an ESX whitebox, and it works fine. However, this morning the console displayed a few errors in red. Looking at /var/log/vmkernel, I see these errors back:

Nov 20 08:45:28 Phillip vmkernel: 0:10:03:19.372 cpu0:1083)ALERT: APIC: 1354: APICID 0x00 - ESR = 0x40 Nov 20 09:11:31 Phillip vmkernel: 0:10:29:22.956 cpu1:1063)ALERT: APIC: 1354: APICID 0x01 - ESR = 0x40

I know my config is not supported, yet built specifically as an ESX testbox. The config:

MSI K9AG NEO2-Digital ATX

AMD 64 X2 4000+

4x 1GB DDR2 667

1x Intel pro1000/GT NIC

Adaptec 29160

The system is still running OK. Does anyone have any idea what the problem might be?

Some extra info: I am running ESX 3.0.2 update1 with all current updates (three in total).

Visit my blog at http://www.vmdamentals.com
0 Kudos
1 Solution

Accepted Solutions
aleph0
Hot Shot
Hot Shot
Jump to solution

did you manage to resolve the problem?

cheers

\aleph0

____________________________

###############

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!

\aleph0 ____________________________ http://virtualaleph.blogspot.com/ ############### If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!

View solution in original post

0 Kudos
4 Replies
Erik_Zandboer
Expert
Expert
Jump to solution

kick

Anyone any idea at all?

Visit my blog at http://www.vmdamentals.com
0 Kudos
aleph0
Hot Shot
Hot Shot
Jump to solution

try disabling APIC in the kernel starting parameters:

in the bootloader conf file youl find something like that:

=========================================

image=/boot/vmlinuz-2.4.9-34smp

label=linux

root=/dev/sda2

initrd=/boot/initrd-2.4.9-34smp.img

read-only

==========================================

just add

append="noapic"

\aleph0

____________________________

###############

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!

\aleph0 ____________________________ http://virtualaleph.blogspot.com/ ############### If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!
aleph0
Hot Shot
Hot Shot
Jump to solution

did you manage to resolve the problem?

cheers

\aleph0

____________________________

###############

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!

\aleph0 ____________________________ http://virtualaleph.blogspot.com/ ############### If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!
0 Kudos
Erik_Zandboer
Expert
Expert
Jump to solution

Hi,

Yes and no. If I specify NOAPIC in the boot options, I get the a red console text telling me that the noapic option was used, but the system is using PIC. I should make sure that is what I want (DO I want that??). I can also disable APIC in the BIOS, however, even if I do, I still get the APIC errors. Starting with the APIC in BIOS disabled AND using the noapic bootoption also results in the "make sure noapic is what you want". So basically, I still have no clue as to what is the better option: Start with noapic, or start normally and live with the APIC errors on the console.... Basically, the systems work ok in either "mode"... If you have any more details about the pros and cons of having APIC in combination with ESX I am very interested...!!

Visit my blog at http://www.vmdamentals.com
0 Kudos