Ubuntu
linux-source-2.6.22 package

"BIOS Bug" while booting and later on a lot of "APIC error on CPU0: 40(40)"

Bug #121406 reported by FriedChicken on 2007-06-20

Affects		Status	Importance	Assigned to	Milestone
	linux-source-2.6.22 (Ubuntu)	Invalid	Undecided	Unassigned

Bug Description

Binary package hint: linux-image-2.6.22-6-386

Directly after GRUB there comes this message just before the splash screen is shown:
   [ 23.873968] PCI: BIOS Bug: MCFG area at e0000000 is not E820-reserved
   [ 23.874166] PCI: PCI BIOS revision 2.10 entry at 0xf0031, last bus=1
   [ 23.938788] PnPBIOS: Disabled by ACPI PNP

And after booting dmesg shows very often things like "[15549.240000] APIC error on CPU0: 40(40)" very often.
Both messages I don't receive under Feisty but under Gutsy

There are also problems with ata2 as you can see in the dmesg-log. And I can't understand why SCSI-emulation is used. Is this neccessary or a bug? On the boot cd it isn't used and under Feisty either.
Maybe there's a relation that my network deviced are called lo, wlan0, eth2 and eth3 instead of lo, wlan0, eth0 and eth1 as it is under Feisty

My System is a ASUS Notekook A6Km with an AMD Turion64 ML-37.

Revision history for this message

FriedChicken (domlyons) wrote on 2007-06-20:

My dmesg Edit (20.9 KiB, text/plain)

Revision history for this message

FriedChicken (domlyons) wrote on 2007-06-23:

Maybe the "bcm43xx"-module produces the APIC errors. On Feisty I had blacklisted this module and used ndiswrapper instead.

But what does that BIOS bug mean?

Revision history for this message

Kyle McMartin (kyle) wrote on 2007-06-27:

It means there's a bug in your BIOS, there's nothing that we can do about it other than advise you to upgrade your BIOS from your motherboard manufacturers website.

The use of "SCSI emulation" is normal, because when using libata, disk drives are exposed through the SCSI subsystem.

Revision history for this message

Kyle McMartin (kyle) wrote on 2007-06-27:

Rejecting as invalid as there's really no bug here, just warnings. Please run the Linux Firmware Kit from http://www.linuxfirmwarekit.org/ to test your BIOS.