Bug 196534 - FC5 Xen boot - crash in kernel osl.c
Summary: FC5 Xen boot - crash in kernel osl.c
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xen
Version: 5
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Xen Maintainance List
QA Contact: Martin Jenner
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-06-24 03:44 UTC by philip ross
Modified: 2008-02-26 23:12 UTC (History)
2 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2008-02-26 23:12:20 UTC


Attachments (Terms of Use)
grub config; cpuinfo; boot log (13.24 KB, text/plain)
2006-06-24 03:44 UTC, philip ross
no flags Details

Description philip ross 2006-06-24 03:44:48 UTC
Description of problem:

During boot of Xen, kernel panics with message "kernel BUG at
drivers/acpi/osl.c:509". 

PC is AMD Duron.

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

xen.gz-2.6.16-1.2133_FC5
vmlinuz-2.6.16-1.2133_FC5xen0


How reproducible:

Everytime on this PC.

Steps to Reproduce:
1. Boot xen using grub configuration attached
2.
3.
  
Actual results:

boot log attached
-- kernel panic



Expected results:

a successful boot of Linux kernel

Additional info:

Comment 1 philip ross 2006-06-24 03:44:48 UTC
Created attachment 131476 [details]
grub config;  cpuinfo;  boot log

Comment 2 Stephen Tweedie 2007-03-16 15:11:52 UTC
Is this still reproducible on the latest stable release+updates?  Thanks.


Comment 3 philip ross 2007-03-16 21:04:37 UTC
(In reply to comment #2)
> Is this still reproducible on the latest stable release+updates?  Thanks.
> 
Yes, I just installed FC6+updates this week, tried it, it crashed.  I didn't log
the error, but it was in the same area.
philip

Comment 4 Red Hat Bugzilla 2007-07-24 23:55:58 UTC
change QA contact

Comment 5 Chris Lalancette 2008-02-26 23:12:20 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



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