Description of problem:
On my Macbook I get APIC related Kernel Panics on most (~4/5) boots - complete
message below. Boot with 'apic=debug' does not give any extra information.
Version-Release number of selected component (if applicable):
Currently running 2.6.18-1.2768.fc6, but problems really began about 4 kernels
ago (I believe 2641). Before that, I had the same panics about 1/15 boots.
# uname -a
Linux fedbook 2.6.18-1.2768.fc6 #1 SMP Wed Oct 11 18:23:51 EDT 2006 i686 i686
Most boots (aprox. 4 of 5)
Steps to Reproduce:
boot without 'noapic'
attempted 'apic=debug' but results are the same and no extra information is given.
Screen shows the following (copied by hand, so hopefully no errors):
ACPI: Core revision 20060707
CPU0: Intel Genuine Intel(R) CPU 1400 @ 1.83GHZ stepping 08
SMP Alternatives: switching to SMP code
Booting processor 1/1 eip 3000
CPU 1 irqstacks, hard=c07af000 soft=c078f000
Calibrating delay using timer specific routine.. 3661.89 BogoMIPS (lpj=7323789)
monitor/mwait feature present
CPU: L1 I code: 32K, L1 D cache: 32K
CPU: L2 cache: 2048K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 1
Intel machine check architecture supported
Intel machine check reporting enabled on CPU#1
CPU1: Intel Geniuine Intel(R) CPU 1400 @ 1.83GHz stepping 08
Total of 2 processors activated (3915.84 BogoMIPS)
..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
..MP-BIOS bug: 8254 timer not connected to IO-APIC
...trying to set up timer (IRQ0) through the 8259A ... failed.
...trying to set up timer as Virtual Wire IRQ... failed.
...trying to set up timer as ExtINT IRQ... failed.
Kernel panic - not syncing: IO-APIC + timer doesn't work! Boot with apic=debug
and send a report. Then try booting with the 'noapic' option
Using the released version of Fedora Core 6, I get the same problem. I am
running a 2Ghz Macbook. I demoed FC6, T2 and did not encounter this problem.
Since I've install the latest kernel update 2.6.18-1.2849.fc6 the problem seems
to have been fixed - in 5 reboots, I've had no kernel panics on the Macbook.
Should this bug be closed now?
Closing per comment #11. Feel free to reopen this bug if the problem recurs.