Bug 235538

Summary: i686 fc6 xen kernel crashes on boot during agpgart init
Product: [Fedora] Fedora Reporter: George Shearer <doc>
Component: kernel-xenAssignee: Eduardo Habkost <ehabkost>
Status: CLOSED WONTFIX QA Contact: Virtualization Bugs <virt-bugs>
Severity: high Docs Contact:
Priority: medium    
Version: 6CC: tchung, xen-maint
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-02-27 00:04:00 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Full bootlog of xen kernel boot up and crash. none

Description George Shearer 2007-04-06 21:02:23 UTC
Description of problem:

fc6 i686 kernel crashes on boot during agpgart init. Regular non-xen kernel
works fine.

Version-Release number of selected component (if applicable):

kernel-2.6.19 and newer official FC6 released kernels. I have not tried any
older kernels.

How reproducible:

Happens every single time reliably.

Steps to Reproduce:
1. Tell Grub to boot on Xen kernel.
2. Watch dmesg.. 
3.
  
Actual results:

During boot:

Linux agpgart interface v0.101 (c) Dave Jones
agpgart: Detected an Intel 965G Chipset.
BUG: unable to handle kernel NULL pointer dereference at virtual address 00000008
...

Expected results:

Not to crash..

Additional info:

Setting agp=no in kernel boot flags of dom0 fixes this problem.

Hardware configuration:

Gigabyte GA-965P-DS3 motherboard (rev 1.0, bios F10)
Intel Conroe E6400 (Core 2 Duo) CPU
4-gigs DDR2-800
ICH8 Northbridge.

Please note that non-xen kernels work very happily and very reliably on this system.

Comment 1 George Shearer 2007-04-06 21:02:23 UTC
Created attachment 151897 [details]
Full bootlog of xen kernel boot up and crash.

Comment 2 Chris Lalancette 2008-02-27 00:04:00 UTC
This report targets FC6, which is now end-of-life.

Please re-test against Fedora 7 or later, and if the issue persists, open a new bug.

Thanks