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 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Xen 4.0.x Dom0 rhel5.x kernel crashing

To: "Ajishrao.r" <ajishrao@xxxxxxxxx>
Subject: Re: [Xen-devel] Xen 4.0.x Dom0 rhel5.x kernel crashing
From: Pasi Kärkkäinen <pasik@xxxxxx>
Date: Mon, 25 Jul 2011 21:32:35 +0300
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 25 Jul 2011 11:33:16 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <CAM2F+9sbnnM0HF4HOM-=RLi0w8WSkHkJtQXgqKYXhY4nEQaN9w@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <CAM2F+9sbnnM0HF4HOM-=RLi0w8WSkHkJtQXgqKYXhY4nEQaN9w@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
On Mon, Jul 25, 2011 at 09:29:09PM +0530, Ajishrao.r wrote:
>    Hey,
> 
>    I was trying to install latest xen on rhel5.4 but xen crashes with
>    following error:
> 

small correction:
Actually it's not Xen crashing - it's the rhel5 dom0 Linux kernel that crashes.

Redhat tests the rhel5 kernel-xen with the rhel5 version of Xen (3.1.2 + 
patches),
so there's probably some incompatibility in the kernel with newer Xen 
hypervisor.

-- Pasi

>    Loading libata.ko module
>    usb 6-1: new full speed USB device using uhci_hcd and address 2
>    Loading ahci.ko module
>    ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 19 (level, low) -> IRQ 21
>    usb 6-1: configuration #1 chosen from 1 choice
>    input: ServerEngines SE USB Device as /class/input/input0
>    input: USB HID v1.11 Keyboard [ServerEngines SE USB Device] on
>    usb-0000:00:1d.0-1
>    input: ServerEngines SE USB Device as /class/input/input1
>    input: USB HID v1.11 Mouse [ServerEngines SE USB Device] on
>    usb-0000:00:1d.0-1
>    ahci 0000:00:1f.2: AHCI 0001.0200 32 slots 4 ports 1.5 Gbps 0xf impl SATA
>    mode
>    ahci 0000:00:1f.2: flags: 64bit ncq sntf stag pm led clo pmp pio slum part
>    ems
>    IRQ handler type mismatch for IRQ 275
> 
>    Call Trace:
>     [<ffffffff802b2eb2>] setup_irq+0x1b7/0x1cf
>     [<ffffffff880ecdd3>] :ahci:ahci_interrupt+0x0/0x471
>     [<ffffffff802b2f7a>] request_irq+0xb0/0xd6
>     [<ffffffff802b3de1>] devm_request_irq+0x5d/0x92
>     [<ffffffff880ecdd3>] :ahci:ahci_interrupt+0x0/0x471
>     [<ffffffff880bb7cc>] :libata:ata_host_activate+0x9f/0xf9
>     [<ffffffff880ecd9c>] :ahci:ahci_init_one+0x9a2/0x9d9
>     [<ffffffff8034caa5>] pci_device_probe+0x4c/0x75
>     [<ffffffff803afd8d>] pci_bus_probe_wrapper+0x80/0x89
>     [<ffffffff8034c98e>] pci_match_device+0x13/0xbe
>     [<ffffffff8034ca4d>] pci_bus_match+0x14/0x20
>     [<ffffffff803a880d>] driver_probe_device+0x52/0xaa
>     [<ffffffff803a893c>] __driver_attach+0x65/0xb6
>     [<ffffffff803a88d7>] __driver_attach+0x0/0xb6
>     [<ffffffff803a813a>] bus_for_each_dev+0x43/0x6e
>     [<ffffffff803a7d76>] bus_add_driver+0x76/0x110
>     [<ffffffff8034cd69>] __pci_register_driver+0x51/0xa6
>     [<ffffffff802a1d4f>] sys_init_module+0xaf/0x1f2
>     [<ffffffff80260106>] system_call+0x86/0x8b
>     [<ffffffff80260080>] system_call+0x0/0x8b
> 
>    ACPI: PCI interrupt for device 0000:00:1f.2 disabled
>    ahci: probe of 0000:00:1f.2 failed with error -16
>    Loading dm-mod.ko module
>    device-mapper: uevent: version 1.0.3
>    device-mapper: ioctl: 4.11.5-ioctl (2007-12-12) initialised:
>    [1]dm-devel@xxxxxxxxxx
>    Loading dm-log.ko module
>    Loading dm-mirror.ko module
>    Loading dm-zero.ko module
>    Loading dm-snapshot.ko module
>    Loading dm-mem-cache.ko module
>    Loading dm-region_hash.ko module
>    Loading dm-message.ko module
>    Loading dm-raid45.ko module
>    device-mapper: dm-raid45: initialized v0.2594l
>    Waiting for driver initialization.
>    Scanning and configuring dmraid supported devices
>    Scanning logical volumes
>      Reading all physical volumes.  This may take a while...
>    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
>    setuproot: error mounting /proc: No such file or directory
>    setuproot: error mounting /sys: No such file or directory
>    Switching to new root and running init.
>    unmounting old /dev
>    unmounting old /proc
>    unmounting old /sys
>    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
> 
>    Any help? How do move forward to debug the error?
> 
>    -Ajish
> 
> References
> 
>    Visible links
>    1. mailto:dm-devel@xxxxxxxxxx

> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>