Bug 242101 - F7 x86_64 DVD on P965 chipset panics on boot.
F7 x86_64 DVD on P965 chipset panics on boot.
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
x86_64 Linux
low Severity high
: ---
: ---
Assigned To: Kernel Maintainer List
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2007-06-01 13:45 EDT by Matt Darcy
Modified: 2007-11-30 17:12 EST (History)
1 user (show)

See Also:
Fixed In Version: 2.6.21
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-09-13 15:23:33 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Matt Darcy 2007-06-01 13:45:33 EDT
Description of problem:
Booting the F7 x86_64 DVD on an MSI P965-Neo-F running the lastest 1.18 bios
based on the Intel P965 chipset with 4 GB in 2x2GB 800mhz DD2 Ram with an Intel
C2d E4400 2ghz cpu the kernel panics with a stack trace followed by

Code: Bad Rip Value
Kernel Panic - not syncing: Aiee, Killing interrupt handler!

Version-Release number of selected component (if applicable):
Fedora 7 x86_64 initial release DVD 

How reproducible:
Every time

Steps to Reproduce:
1. Burn F7 x86_64 DVD
2. Boot DVd on hardware listed above
3. Watch file
Actual results:
Kernel Panic

Expected results:
Installer start

Additional info:
Comment 1 Matt Darcy 2007-06-01 14:17:31 EDT
This appears to have been noted in the 2.6.21 kernel and noted by Fedora 7 testers.

Comment 2 Chuck Ebbert 2007-06-01 18:10:03 EDT
booting with kernel parameter "agp=off" should work
Comment 3 Matt Darcy 2007-06-01 19:13:03 EDT
Booting passes the panic.

Please close. 

thank you for your response.
Comment 4 Christopher Brown 2007-09-13 15:23:33 EDT
I'm reviewing this bug as part of the kernel bug triage project, an attempt to
isolate current bugs in the fedora kernel.


Closing as per request.


Note You need to log in before you can comment on or make changes to this bug.