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
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
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.
** Changed in: linux-rt
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
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
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
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
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
** Attachment added: calltrace.txt
http://launchpadlibrarian.net/29772738/calltrace.txt
--
Real-Time Kernel won't boot on my AMD Athlon 64 X2 Dual Core - Displays Call
Trace
https://bugs.launchpad.net/bugs/407660
You received this bug notification because you are a member of Ubuntu
Bugs,
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).
** Attachment added: cpuid.txt
http://launchpadlibrarian.net/29772755/cpuid.txt
--
Real-Time Kernel won't boot on my AMD Athlon 64
I'm also attaching the output of the lshw command (run on the same computer).
The motherboard is a Gigabyte GA-MA78G-DS3H.
** Attachment added: lshw.txt
http://launchpadlibrarian.net/29772777/lshw.txt
--
Real-Time Kernel won't boot on my AMD Athlon 64 X2 Dual Core - Displays Call
Trace
11 matches
Mail list logo
