Bug 249941 - Kernel > 2.6.21-1.3228.fc7 panics
Summary: Kernel > 2.6.21-1.3228.fc7 panics
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 7
Hardware: x86_64
OS: Linux
low
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-07-28 10:06 UTC by Benny
Modified: 2007-11-30 22:12 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2007-11-26 22:45:02 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Benny 2007-07-28 10:06:56 UTC 
Description of problem:
With pup I updated kernel 2.6.21-1.3228.fc7
When I boot the new kernel I get the message:
"Kernel panic - not syncing: Aiee, killing interrupt handler" after that nothing
happens. 
Since then I also installed a newer kernel through yum (pup) and still the same
problem.

Version-Release number of selected component (if applicable):
Kernel > 2.6.21-1.3228.fc7

How reproducible:
Unknown to me

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Peter van Egdom 2007-11-20 21:28:10 UTC 
Changing version from "fc4test1" to "f7" as "kernel-2.6.21-1.3228.fc7" is an
update for Fedora release 7.

Can you still boot the system with an older kernel on your Fedora system?
Comment 2 Benny 2007-11-21 11:34:09 UTC 
Every kernel similar or older to kernel kernel-2.6.21-1.3228.fc7 fails at a
certain point.
Comment 3 Chuck Ebbert 2007-11-21 18:13:14 UTC 
We need to see the entire oops message. Can you boot with the kernel option
"vga=791" and take a picture of the screen, then attach that to this bugzilla?
Comment 4 Benny 2007-11-21 20:23:07 UTC 
Okay will do that coming Saturday, when I'm near the computer. 
Stay tuned.
Comment 5 Benny 2007-11-26 22:45:02 UTC 
Unfortunately I cannot get a hold of the computer where this event occurred, sorry.
Note You need to log in before you can comment on or make changes to this bug.