From Bugzilla Helper: User-Agent: Mozilla/4.75 [en] (X11; U; SunOS 5.6 sun4u) Description of problem: Booting vmlinuz fails with "Kernel panic: Aiee, killing interrupt handler! In interupt handler - not syncing" Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Boot "boot.img" from Disk 2. Return (or also text Return) 3. Wait for crash after loading vmlinuz Additional info:
On a laptop, you should probably be using the pcmcia.img to boot from. Does that avoid the problem?
I tried the installation also with the pcmcia.img, but it showed up the same problem.
This seems to be a kernel problem. Changing component.
is there anything before the "aieee" line ?
I do not get always the same messages. What i get also is "CPU#0: Machine Check Exception: 0x 107000 (type 0x 9)." Now i have got this (after removing the cdrom drive): <0>Kernel panic: Attempted to kill the idle task! In idle task - not syncing I cannot see all messages because the system hangs after booting and shift-pageup does not work any more.
"CPU#0: Machine Check Exception: 0x 107000 (type 0x 9)." usually means that your cpu tells you it's bust ;( However, some machines have a wiring mistake on the motherboard and trigger this when there's not really a fault, you can add "nomce" to the kernel commandline (eg type "linux nomce" on the syslinux prompt) to circumvent this.
Compaq 586 laptops show spurious mce's. Boot with "nomce" as a boot option and it should not show any more strange MCE errors. The "nomce" should not be needed in the errata kernel either. Alan
"linux nomce" on the syslinux prompt does help!!! Now X crashs, but text mode does it. Thanks for your help.
Excellent If after you grab the kernel errata X still crashes stick in a seperate bug report for that.