WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Xen

xen-users

[Top] [All Lists]

[Xen-users] Dom0 crashes on boot with an IRQ conflict

To: Xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Dom0 crashes on boot with an IRQ conflict
From: James Penick <jpenick@xxxxxxxxx>
Date: 2011年6月13日 22:51:21 -0700
Cc:
Delivery-date: 2011年6月13日 22:52:54 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=JeSzuLLLl0kyKWhREi0fVwZlO3UOLMFWtrdyXJHc+mY=; b=ugrSKXf2Z2Z3zFVZZpToyZ41mkAP8wLZWjuWMHvzrHg+PbCxwO0QKFxd9z8mIdVgPZ Sk6/5aDCNddYH7YgIX8OUByDOgm1CcgXoGW/7Qp8GeC9dD1pu5F1lqknrwcDqWzoWv4z Ql61/9bYGiDOv7ud6b/9sOmrefmPW0S0vItto=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=tYNbi22LG772xENKMIZ263BKKCHU9Ycpb56wQXjqufa1nKB6G5xvpRpbpL1dXHfGaV oqy2C3U28AzbxTO5fpY1xaU/LuldEua+lgTRoryI3X0HVhbi7Ghe4BU3bTiCDuXnLTYp YeXS50oHcPd2t4Hub5ap3jdVxpXxtvXlmTX3s=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hey folks,
 I've recently compiled and installed Xen 4.1 on a machine running
RHEL 5.4. Unfortunately when booting via Xen there's an IRQ conflict
which prevents dom0 from loading the SATA drivers. This is followed by
a kernel panic because LVM can't find the root volume.
This is the salient bit from the boot log:
ahci .&checktime(0000,00,1,':')f.2: AHCI 0001.0200 32 slots 4 ports 1.5 Gbps 0xf impl SATA mode
ahci .&checktime(0000,00,1,':')f.2: flags: 64bit ncq sntf stag pm led clo pmp pio slum part ems
IRQ handler type mismatch for IRQ 275
Call Trace:
 [<ffffffff802b595d>] setup_irq+0x1b7/0x1cf
 [<ffffffff880ec18e>] :ahci:ahci_interrupt+0x0/0x644
 [<ffffffff802b5a25>] request_irq+0xb0/0xd6
 [<ffffffff802b686c>] devm_request_irq+0x5d/0x92
 [<ffffffff880ec18e>] :ahci:ahci_interrupt+0x0/0x644
 [<ffffffff880bb780>] :libata:ata_host_activate+0x97/0xf1
 [<ffffffff880ec078>] :ahci:ahci_init_one+0xa2c/0xa5e
 [<ffffffff80352b1e>] pci_device_probe+0x4c/0x75
 [<ffffffff803b882c>] pci_bus_probe_wrapper+0x80/0x89
 [<ffffffff80352a07>] pci_match_device+0x13/0xbe
 [<ffffffff80352ac6>] pci_bus_match+0x14/0x20
 [<ffffffff803b1266>] driver_probe_device+0x52/0xaa
 [<ffffffff803b1395>] __driver_attach+0x65/0xb6
 [<ffffffff803b1330>] __driver_attach+0x0/0xb6
 [<ffffffff803b0b6d>] bus_for_each_dev+0x43/0x6e
 [<ffffffff803b07a9>] bus_add_driver+0x76/0x110
 [<ffffffff80352de2>] __pci_register_driver+0x51/0xa6
 [<ffffffff802a4380>] sys_init_module+0xaf/0x1f2
 [<ffffffff80260106>] system_call+0x86/0x8b
 [<ffffffff80260080>] system_call+0x0/0x8b
ahci: probe of .&checktime(0000,00,1,':')f.2 failed with error -16
[...]
Activating logical volumes
 Volume group "sys" not found
Creating root device.
Mounting root filesystem.
mount: could not find filesystem '/dev/root'
Setting up other filesystems.
Setting up new root fs
setuproot: moving /dev failed: No such file or directory
no fstab.sys, mounting internal defaults
[...]
switchroot: mount failed: No such file or directory
Kernel panic - not syncing: Attempted to kill init!
 (XEN) Domain 0 crashed: rebooting machine in 5 seconds.
I've tried fiddling with some kernel settings like irqpoll, noapic,
turning off acpi. But to no avail.
grub.conf:
title Red Hat Enterprise Linux Server Supertaco 4.x (2.6.18-164.el5xen)
 root (hd0,0)
 kernel /xen-4.1.0.gz dom0_mem=1024M dom0_max_vcpus=0 console=com1
com1=9600,8n1
 module /vmlinuz-2.6.18-238.el5xen ro root=/dev/sys/root
hda=noprobe panic=5 console=ttyS0,9600
 module /initrd-2.6.18-238.el5xen.img
Now, i've tried RHEL 5.3 and RHEL 5.6. Running 2.6.18-164.el5xen and
2.6.18-238.el5xen. Things work fine when I use Xen-3.1.2
Anyone have any suggestions on how to make Xen-4.1 play nice with the
IRQs for my SATA driver?R
thanks!
-James
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Dom0 crashes on boot with an IRQ conflict, James Penick <=
Previous by Date: [Xen-users] Re: 3.0.0-rc2: Xen: powernow-k8: Kernel panic - not syncing: Attempted to kill init! , Konrad Rzeszutek Wilk
Next by Date: [Xen-users] Invitation to connect on LinkedIn , Yashodhar Pareek via LinkedIn
Previous by Thread: [Xen-users] XCP PXEboot , jgpsilver2011
Next by Thread: [Xen-users] Invitation to connect on LinkedIn , Yashodhar Pareek via LinkedIn
Indexes: [Date] [Thread] [Top] [All Lists]

Copyright ©, Citrix Systems Inc. All rights reserved. Legal and Privacy
Citrix This site is hosted by Citrix

AltStyle によって変換されたページ (->オリジナル) /