Can't boot: mp-bios bug timer not connected to io-acp

dmesg > dmes.txt

This should be fixed in the next kernel upload.

Hi again

I've just downloaded knot cd2 and this issue is still happening, same error. Feel free to ask for any relevant information.

Thanks

Can I re-open this bug then?

It seems that it hasn't been fixed.

I've just tried today's daily live cd and the bug remains.

Can you please attach the output of lspci and describe the hardware?

lspci output. It's been run in my dapper installation since I can't boot with edgy.

This is an acer ferrari 4005 WMLi turion machine:
- AMD Turion 64 ML-37 2GHz, 64KB L1 Cache, 1MB L2 Cache
- ATI Radeon Xpress 200P chipset with Mobility Radeon X700 GPU and 128MB video memory
- 1GB DDR333

Hi

Today I tried to use acpi=off as a kernel parameter and the live cd manages to boot.

I was going to use this to get some information from the edgy kernel (lscpi, dmesg, etc) but unfortunately this (expensive but apparently crappy) laptop has another bug with X that defaults the display to the external monitor (vga out) (https://launchpad.net/distros/ubuntu/+source/xserver-xorg-video-ati/+bug/22985). This can be easy fixed by editing xorg.conf, but unfortunately (again) it seems that automatic logon is only enabled in the graphical session and not on consoled based logins.

I tried to login as ubuntu/ubuntu, kubuntu/kubuntu (since this time I was using a kububuntu edgy cd) with no success.

Is there a wiki page or something with this kind of information? (the default user/password details in live cd's, I thought it was ubuntu/ubuntu but it seems that's not correct.)

Thanks.

lspci output from dapper (this time with attachment!)

lspci -v

lspci -vv

Hi again

I forgot to say that this is the i386 edgy cd's I'm trying. I'll try to download the amd64 knot cd2 to see if this bug happens.

Thanks

I've tried booting the amd64 edgy knot cd 2 and it works.

Here's the dmesg & lspci -v output from the edgy kernel

lspci -v (from the amd64 cd)

Hi

I've just downloaded Knotcd3. The error is still there, but I managed to boot with kernel parameters: noapic nolapic

I haven't been able to get new dmest & lspci info because of the other bug this hardware suffers (tvout), I'll try again later and I succed post some info.

Thanks

I am having the same problem...i am running a Compaq R4000 series laptop fyi. This bug better be fixed by the release of edgy. If there is anything i can do to help let me know :)

Could all of you with problems boot without the "quiet splash" parameters in order to check what the final line of kernel output really is? Does the

skip_acpi_timer_override

kernel parameter help?

This is the output after the BIOS bug line when i exclude the "quiet splash" option:
trying to set up timer (IRQ0) through the 8259A ... failed
trying to set up timer as virtual wire ICQ ... failed
trying to set up timer as ExtINT IRQ ... <7> APIC error on CPU0:00(48)

When booting with the "skip"acpi_timer_override" option on it only gets to the BIOS Bug line and stops. So it makes no difference.

btw...the urgency on this bug should be moved up...without this big fixed my computer won;t work with edgy :'(

Sorry, that should have been

acpi_skip_timer_override

not

skip_acpi_timer_override

Also, does this happen with any other distros?

Oh, and one last thing - can you boot the amd64 version with

apic=verbose

and provide the contents of /var/log/dmesg?

no i have not had any problems with any other distro's...i will download the 64 bit version and try booting with the "apic=verbose" and provide /var/log/dmesg

Hi again

I've downloaded amd64 knot cd3 and booted with apic=verbose, but since X doesn't start correctly and I don't know the console login details I can't provide /var/log/dmesg. The only thing I can say is that the error message of this bug appears on console but it doesn't prevent the amd64 kernel from booting.

Please, can someone provide the login details so I can get dmesg log? Or fix this in a new build, I've already filed a bug: https://launchpad.net/distros/ubuntu/+bug/60757
Thanks

Hi again

I've managed to enter by booting into single mode. Here's the /var/log/dmesg from the amd64 knotcd3 kernel with parameters: single apic=verbose.

For the record, I must say that since my delete key wasn't properly mapped in single mode it was a quite a pain, even for this little task. I hope this helps

hi

the x86 iso booted fine with acpi_skip_timer_override

The bug mentiond "bug timer not connected", is not a bug. It gets taken care a few lines later with an alternate timer source.

So someone confirm why their system isn't booting. It's not because of the timer.

hmm...anybody with this problem do you possably have a Broadcom 4318 wireless card?

Looks like a leftover section of an old patch that's causing problems.

Ben, can you commit this ASAP?

could this be commited so we can test it :) i am excited to try out edgy :)

I too am having this issue with an ASUSTeK motherboard, Core2Duo 6700 CPU, NVIDIA chipset machine.

If I cold boot 2.6.17-10-generic it hangs with:-

MP-BIOS bug: 8254 timer not conected to IO-APIC
PCI: BIOS Bug: MCFG area at e0000000 is not E820-reserved
PCI: Not using MMCONFIG.

If I cold boot 2.6.17-10-generic without splash and quiet (and with or without acpi_skip_timer_override) it gets to:-

io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)

If I then warm boot (hit reset button) after that, again without splash and quiet (and with or without acpi_skip_timer_override), it pauses at the same "io scheduler" but then moves on afer a few seconds and hangs at:-

ACPI: PCI Interrupt Link [LUB0] enabled at IRQ 21
ACPI: PCI Interrupt 0000:00:0b.0[A] -> Link [LUB0] -> GSI 21 (level, low) -> IRQ 74
ohci_hcd 0000:00:0b.0: OHCI Host Controller
ohci_hcd 0000:00:0b.0: new USB bus registered, assigned bus number 1

Booting with noapic only boots just fine.

Latest 2.6.17-generic appears to boot okay now without needing any special parameters, still reporting this message, but continues past it.

Hmm, spoke too soon. Still needs noacpi.

Linux wopr 2.6.17-10-generic #2 SMP Fri Oct 6 00:36:14 UTC 2006 i686 GNU/Linux

Can you boot without the "quiet splash" arguments and see where it hangs? I suspect that it's nothing to do with this message at all.

If I boot without quiet and nosplash it stops here (manually transcribed)

usbcore: registered new driver usbfs
usbcore: registered new driver hub
ACPI: PCI Interrupt Link [LUB0] =enabled at IRQ 21
ACPI: PCI Interrupt 0000:00:0b.0[A] -> Link [LUB0] -> GSI 21 (level, low) -> IRQ 74
ohci_hcd 0000:00:0b.0: OHCI Host Controller
ohci_hcd 0000:00:0b.0: new USB bus registered, assigned bus number 1

If I use "noapic" it boots fine.

This was marked Fix Committed against 2.6.15 a while ago but I see no evidence anything actually went into Dapper to resolve this. Also, this was marked "Fix Released" against 2.6.17 anyways. I'm going to close this against 2.6.15. If anyone is still experiencing issues with this specific bug, the Hardy Heron 8.04 Alpha series is currently under development and contains an updated version of the kernel - http://www.ubuntu.com/testing . Please test and open a new bug report if the issue still exists. Thanks.