Real-Time Kernel won't boot on my AMD Athlon 64 X2 Dual Core - Displays Call Trace

[luvr]

I installed UbuntuStudio 9.04 from the "ubuntustudio-9.04-alternate-amd64.iso" DVD.

The installation went OK, but as soon as I boot up the computer, it displays a Call Trace and locks up. The only way out is a hard reset.

I subsequently installed the real-time kernel 2.6.28-3-rt (which come with UbuntuStudio 9.04) on top of a plain Ubuntu install, with the same results.

Since the system locks up firmly whenever I attempt to boot it, there's not much more that I can do in terms of diagnostics; the Call Trace doesn't seem to get saved onto disk, I had to manually type it over in order to obtain a copy of it (see the "calltrace.txt" attachment).

[luvr (luc-vanrompaey)]

I'm attaching the output from the "cpuid" command.
(The command was run under Ubuntu 8.10 on one of the machines on which I attempted to run UbuntuStudio 9.04).

[luvr (luc-vanrompaey)]

I'm also attaching the output of the "lshw" command (run on the same computer).
The motherboard is a Gigabyte GA-MA78G-DS3H.

[kingken (kensands22)]

I have the same problem, the same motherboard (latest bios installed) and a phenom x 3 processor, so perhaps it's the motherboard rather than the processor? I'm actually testing with 64studio but it's the same kernel I believe and based on ubuntu sources. I can actually get it to fully boot if I pass the nolapic option and disable the lan in the bios.

I'm happy to try out anything and give as much info as anyone needs on this.

[luvr (luc-vanrompaey)]

> I can actually get it to fully boot if I pass the nolapic option and disable the lan in the bios.

Hmmm... That doesn't work for me. I simply get a message stating that the local APIC cannot be found, after which my system still locks up. Enabling or disabling the LAN in BIOS doesn't change a thing.

There must be more to it than just the LAN option--different CPU models, different disk configurations, or whatnot?

[kingken (kensands22)]

with the nolapic option does the system still lock up with the same tick_handle_periodic() trace?
that lets it boot on mine after fiving the no local apic message and emulating in software thing. however the system does completely freeze up after 10 minutes or so use where before it's been solid for days, so there are certainly issues with something. I've emailed gigabyte asking them to have a look at this thread to at very least pass comment on if the issue is with the kernel or might be the bios.

[luvr (luc-vanrompaey)]

> with the nolapic option does the system still lock up with the same tick_handle_periodic() trace?

Nope... No trace. The only output that appears on screen, is the following two lines:

[ 0.212982] BIOS bug, local APIC #0 not detected!...
[ 0.213018] ... forcing use of dummy APIC emulation.(tell your hw vendor)

And at that point, nothing more happens.

[Alessio Igor Bogani (abogani)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that could be fixed in the Beta release of Karmic Koala. It would help us greatly if you could test with it! Thanks again and we appreciate your help.

[luvr (luc-vanrompaey)]

I have just installed the real-time kernel on my Ubuntu 9.10 beta system, and I'm running with it right now; "uname -a" gives the following output:

Linux wkst1 2.6.31-7-rt #9-Ubuntu SMP PREEMPT RT Wed Oct 7 22:08:13 UTC 2009 i686 GNU/Linux

The bug certainly seems to be resolved.
This is great news!

[Alessio Igor Bogani (abogani)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu - Karmic Koala.

This is a significant bug in Ubuntu. If you need a fix for the bug in previous versions of Ubuntu, please do steps 1 and 2 of the SRU Procedure [1] to bring the need to a developer's attention.

[1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure