new install, kernel panic, not syncing

Bug #161132 reported by Michael on 2007-11-09
Affects Status Importance Assigned to Milestone
linux-source-2.6.15 (Ubuntu)

Bug Description

Tried instaling Ubuntu 6.06 on computer
Got kernal panic under default boot option.

Got this message when booted with debug parameter.

[4294671.007000] CPU: L1 I Cache: 64k (64 bytes/line), D cache 64K (6 bytes/line)
[4294671.007000] CPU: L2 Cache: 512k (64 bytes/line)
[4294671.007000] mtrr: v2.0 (20020519)
[4294671.007000] CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 5000+ stepping 02 [4294671.007000] Enabling fast FPU save and restore... done.
[4294671.007000] Enabling unmasked SIMD FPU exception support... done.
[4294671.007000] Checking 'hlt' instruction... Ok.
[4294671.013000] ACPI: Looking for DSDT ... not found!
[4294671.017000] Getting VERSION: 80050010
[4294671.017000] Getting VERSION: 80050010
[4294671.017000] Getting ID: 0
[4294671.017000] Getting LVT0: 700
[4294671.017000] Getting LVT1: 400
[4294671.017000] enabled ExtINT on CPU#0
[4294671.017000] ENABLING IO-APIC IRQs
[4294671.017000] Synchronizing Arb IDs.
[4294671.018000] ..TIMER: vector=0x31 apic1=0 pin1=0 apic2=-1 pin2=-1
[4294671.019000] ..MP-BIOS bug: 8254 timer not connected to I0-APIC
[4294671.819800] ... trying to set up timer (IRQ0) through the 8259A ... failed. [4294671.019000] ...trying to set up timer as Virtual Wire IRQ... failed.
[4294671.019000] ...trying to set up timer as ExtINT IRQ... failed :(.
[4294671.129000] Kernel panic - not syncing: I0-APIC + timer doesn't work!
Boot with apic=debug and send a report. Then try booting with the 'noapic' option
[4294671.129000] _

Booting with noapic parameter works.
Hardware is Gigabyte GA-M59SLI-S5 Motherboard, AMD64 x2 5000 Processor

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at . I have classified this bug as a bug in linux-source-2.6.15.

Now that the 7.10 Gutsy Gibbon release of Ubuntu is out, we were wondering if you can still reproduce this issue with the current release? You can simply test this by using the LiveCD of the 7.10 Gutsy Gibbon release. You can download and try the new version of Ubuntu from . Please report back your results. Thanks in advance!

wolfger (wolfger) wrote :

Over 5 months with no response. We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in linux-source-2.6.15:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers