Bug 219378 - Boot crash: XEN) Unknoen Interrupt
Summary: Boot crash: XEN) Unknoen Interrupt
Alias: None
Product: Fedora
Classification: Fedora
Component: xen   
(Show other bugs)
Version: 6
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Xen Maintainance List
QA Contact: Martin Jenner
Depends On:
TreeView+ depends on / blocked
Reported: 2006-12-12 20:41 UTC by Nicolai Raaschou
Modified: 2008-02-26 23:48 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-02-26 23:48:18 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Nicolai Raaschou 2006-12-12 20:41:47 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727)

Description of problem:
When i try to boot on the default boot option (Fedora Core(2.6.18-1.2798.fc6xen)) this happends:

XEN) Command line:/xen.gz-2.6.18-1.2798.fc6
XEN) Physican RAM map:
XEN) (LOTS of characters here)
XEN) (LOTS of characters here)
XEN) (LOTS of characters here)
XEN) (LOTS of characters here)
XEN) (And so on)
Then i come to this:
XEN) ACPI: RSDP (v002 HP-CPC                                           ) @ 0x000f8050
XEN) Unknown interrupt

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

How reproducible:

Steps to Reproduce:
1. Start the PC
2. Choose the default booting option/wait the 5 seconds for it to choose it for itself

Actual Results:
The same

Expected Results:
I guess start FC 6

Additional info:

Comment 1 Richard W.M. Jones 2007-03-19 15:06:26 UTC

Do you still have this problem on FC6 with the latest
updates (kernel-xen-2.6.19-1.2911.6.5.fc6)?

Comment 2 Red Hat Bugzilla 2007-07-25 00:03:55 UTC
change QA contact

Comment 3 Chris Lalancette 2008-02-26 23:48:18 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.


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