MP-BIOS bug: 8254 timer not connected to IO-APIC

[All Yours]

"..MP-BIOS bug: 8254 timer not connected to IO-APIC" message when booting.

Apparently it is not a functional bug, since you can found the next process in the "dmesg"

[ 0.464029] ..MP-BIOS bug: 8254 timer not connected to IO-APIC
[ 0.464029] ...trying to set up timer (IRQ0) through the 8259A ...
[ 0.464029] ..... (found apic 0 pin 0) ...
[ 0.505291] ....... works.

This is very annoying since Feisty.

And also I have got "Aperture beyond 4GB. Ignoring" message as well (which is found in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/271070).

I am using Intrepid beta (AMD64). Kernel version is 2.6.27-7.11-generic.
My laptop is Dell Inspiron 1501, AMD Turion 64 x 2, 2GB (ram).

Hope you can fix it.

All Yours.

[All Yours (sjy22kr)]

After upgrading to 2.6.27-7.11-generic, it is still there.

All Yours

[All Yours (sjy22kr)]

I meant 2.6.27-7.13-generic.

Sorry for the confusion.

All Yours.

[zasq (zasq)]

Hi. Same problem here with kernel 2.6.27-9-generic.
I'm not sure whether this is a functional bug or not. Could I/O error and problems with usb-devices be related to this? See for example: https://bugs.launchpad.net/bugs/88746 (there you can also find my log-files).

[dcam (david-pastornet)]

Confirming...I see the same with 2.6.27-9-generic

[Cyberlion (rodrigoleao)]

Confiming... the same problem with 2.6.27-9-generic.

[Jorge Devoto (jdevoto)]

Hi

I have a Toshiba satellite A70 with Phoenix bios running Ubuntu 8.10
kernel 2.6.27-11-server
and I get the same message (from dmesg)

[ 0.400000] ..MP-BIOS bug: 8254 timer not connected to IO-APIC
[ 0.400000] ...trying to set up timer (IRQ0) through the 8259A ...
[ 0.400000] ..... (found apic 0 pin 2) ...
[ 0.501963] ....... works.

But apparently the computer is working fine.
ANy help?

[Jorge Devoto (jdevoto)]

I would like to add new information: the computer hangs from time to time.

[joaquinbb (joaquin-sistemasprogresivos)]

Hi,

I a new computer with Intel 4 Cores, and with the same phrase appearing and followed by : Kernel panic - not syncing : IO-APIC + timer doesn't work ! Boot with apic=debug and send report (not working to send a report). Then try booting with the 'noapic' option, which adding this to the different options to boot works well, I have been working a couple of days like this, but computer was very slow.
Finally I have found in the BIOS Setup that under Advanced BIOS Features, the option : Installer OS Select was equal to Windows, and if you change to Others, everything goes well, you do not need to add the argument noapic, and the computer runs much faster.

[Mike Hicks (hick0088)]

I get the "MP-BIOS bug" message whenever I try to run the x86_64 version of Ubuntu on QEMU (0.10.0-1ubuntu1).

    qemu-system-x86_64 -cdrom ubuntu-9.04-desktop-amd64.iso

I'm not sure if this is a bug in QEMU or the kernel (or both...)

[JohnMitchell (johnlmitchell)]

I'm getting the identical error as Mike: "MP-BIOS" croaks quite early on in a qemu-x86_64 boot of a Ubuntu disc.

In my case:
   qemu-system-x86_64 -cdrom isos/mini-x86.iso -boot d

If I enable "Command-line expert install" I get slightly more detail:

MP-BIOS bug, trying to set up timer, found apic 0 pin 0, failed.
==> "trying to set up timer as Virtual Wire IRQ..." then it hangs.

(A second point: I'm using a wireless PCI card as my main Internet connection. I know that most wireless drivers don't support bridging, which affected my VirtualBox install. I can't imagine it's related. but it's a point to consider.)

uname -a
Linux sally 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009 x86_64 GNU/Linux
dpkg -l 'qemu*' | egrep ^ii
ii qemu 0.10.0-1ubuntu1 fast processor emulator
ii qemu-launcher 1.7.4-1 GTK+ front-end to QEMU computer emulator

[JohnMitchell (johnlmitchell)]

Searching for the "virtual wire irq" led me to our friends at Red Hat, who have a workaround:

In my case:
   qemu-system-x86_64 -hda /var/qemu/vdisk.img -cdrom isos/mini-x86.iso -boot d

I used the magic string "install noapic" to start the normal install process.

https://bugzilla.redhat.com/show_bug.cgi?id=502058

[Brian McG (brianmcgoldrick)]

Have had the same bug on a HP Pavilion zv5213ap notebook since hardy - now running up to date jaunty. Unsure if it's relevant but the notebook ocassionally drops to busybox at boot and does not resume from standby.

[Brian McG (brianmcgoldrick)]

Forgot to attach dmesg output in previous post

[Forest Bond (forest-bond)]

FWIW, this seems to be relevant and suggests a fix:

http://linux.derkeiler.com/Mailing-Lists/Kernel/2009-04/msg10563.html

Personally, I'd love to see this fixed in Jaunty.

-Forest

[kernel-janitor (kernel-janitor)]

Hi All,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/releases/karmic . If the issue remains, please run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 283489

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Lexen (lexen1)]

   I would like to confirm that this is still an issue in the latest build of ubuntu karmic. I am using the alternative amd64 iso on qemu. I got around the problem by pressing F6 and picking the second option that said "no acpi." Unfortunately, it crashed about a minute and a half later, but it could help get you to the next step.

[Brett Sutton (bsutton)]

Architecture: i386
Dependencies:

DistroRelease: Ubuntu 9.04
Package: linux None [modified: /var/lib/dpkg/info/linux.list]
PackageArchitecture: i386
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_AU.UTF-8
Uname: Linux 2.6.28-15-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[sadicote (mzsade)]

Same here, Linux 2.6.28-15-generic i686, single user. And everybody seems to be happy with having to use the 'noapic' solution. Meanwhile, Canonical keeps rolling out distros like car models (more power to them), but i wish they would pause to clean up this nasty imperfection--it's been so long!

[Oedipe (oedipe)]

Still i get the same problem here running 2.6.28-15 on a Dell Inspiron 1000. It's been loooong time and that bug is still not fixed. Please, please, do something about that. Also my fan is constantly running and i have been forced to put the "noapic" thing at boot time.

[Oedipe (oedipe)]

Just updated to 2.6.28-16 a few minutes ago. Same bug again and again ! Also if i don't mention the "noapic" "nolapic" thing, my laptop is burning and the fan is always "On".

This bug affects many users and it's a shame it has not been resolved yet ! Waiting for stable Karmic and if it's not resolved going to another distro or even to windows.

Instead of producing shit every 6 months, take time to release STABLE kernels that don't harm our laptops !

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]