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-users

[Xen-users] dom0 failing to boot on Intel Xeon.

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] dom0 failing to boot on Intel Xeon.
From: Tyler MacDonald <tyler@xxxxxx>
Date: Wed, 25 Jun 2008 15:46:20 -0700
Delivery-date: Wed, 25 Jun 2008 15:48:39 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
Has anybody run into this? The system is dual Intel Xeon-Harpertown
5430-Quadcore.. I've tried Xen 3.1.3, 3.2.1, and unstable (3.3) without
success, they all give error messages similar to this one. The system is
running Debian etch.

        Thanks,
                Tyler



e1000: 0000:04:00.1: e1000_probe: (PCI Express:2.5Gb/s:Width x4) 
00:30:48:c1:3d:8d
e1000: eth1: e1000_probe: Intel(R) PRO/1000 Network Connection
BUG: soft lockup detected on CPU#0!

Call Trace:
 <IRQ> [<ffffffff80258c10>] softlockup_tick+0xd8/0xea
 [<ffffffff8020ee87>] timer_interrupt+0x3a7/0x401
 [<ffffffff80258efc>] handle_IRQ_event+0x4e/0x96
 [<ffffffff80258fe8>] __do_IRQ+0xa4/0x105
 [<ffffffff8020b1ac>] call_softirq+0x1c/0x28
 [<ffffffff8020cf95>] do_IRQ+0x65/0x73
 [<ffffffff8034e6ba>] evtchn_do_upcall+0x13c/0x1fb
 [<ffffffff8020ace2>] do_hypervisor_callback+0x1e/0x2c
 <EOI> [<ffffffff802ed4dd>] __delay+0x8/0x10
 [<ffffffff880303b7>] :aacraid:aac_fib_send+0x27e/0x2eb
 [<ffffffff8022715a>] __activate_task+0x27/0x39
 [<ffffffff8802c94b>] :aacraid:aac_get_adapter_info+0x69/0x471
 [<ffffffff8802baa1>] :aacraid:aac_probe_one+0x288/0x4a3
 [<ffffffff802f5ffa>] pci_device_probe+0x4c/0x75
 [<ffffffff80347994>] driver_probe_device+0x52/0xa8
 [<ffffffff80347ac3>] __driver_attach+0x6d/0xaa
 [<ffffffff80347a56>] __driver_attach+0x0/0xaa
 [<ffffffff80347395>] bus_for_each_dev+0x43/0x6e
 [<ffffffff80346ff3>] bus_add_driver+0x7e/0x130
 [<ffffffff802f6195>] __pci_register_driver+0x57/0x7d
 [<ffffffff8803b033>] :aacraid:aac_init+0x33/0x6e
 [<ffffffff8024c311>] sys_init_module+0x16cc/0x1883
 [<ffffffff8020a4fc>] system_call+0x68/0x6d
 [<ffffffff8020a494>] system_call+0x0/0x6d

aacraid: aac_fib_send: first asynchronous command timed out.
Usually a result of a PCI interrupt routing problem;
update mother board BIOS or consider utilizing one of
the SAFE mode kernel options (acpi, apic etc)
BUG: soft lockup detected on CPU#1!

Call Trace:
 <IRQ> [<ffffffff80258c10>] softlockup_tick+0xd8/0xea
 [<ffffffff8020ee87>] timer_interrupt+0x3a7/0x401
 [<ffffffff80258efc>] handle_IRQ_event+0x4e/0x96
 [<ffffffff80258fe8>] __do_IRQ+0xa4/0x105
 [<ffffffff8020b1ac>] call_softirq+0x1c/0x28
 [<ffffffff8020cf95>] do_IRQ+0x65/0x73
 [<ffffffff8034e6ba>] evtchn_do_upcall+0x13c/0x1fb
 [<ffffffff8020ace2>] do_hypervisor_callback+0x1e/0x2c
 <EOI> [<ffffffff802ed4dd>] __delay+0x8/0x10
 [<ffffffff880303b7>] :aacraid:aac_fib_send+0x27e/0x2eb
 [<ffffffff8802f188>] :aacraid:aac_send_shutdown+0x5c/0x7a
 [<ffffffff8802bc1b>] :aacraid:aac_probe_one+0x402/0x4a3
 [<ffffffff802f5ffa>] pci_device_probe+0x4c/0x75
 [<ffffffff80347994>] driver_probe_device+0x52/0xa8
 [<ffffffff80347ac3>] __driver_attach+0x6d/0xaa
 [<ffffffff80347a56>] __driver_attach+0x0/0xaa
 [<ffffffff80347395>] bus_for_each_dev+0x43/0x6e
 [<ffffffff80346ff3>] bus_add_driver+0x7e/0x130
 [<ffffffff802f6195>] __pci_register_driver+0x57/0x7d
 [<ffffffff8803b033>] :aacraid:aac_init+0x33/0x6e
 [<ffffffff8024c311>] sys_init_module+0x16cc/0x1883
 [<ffffffff8020a4fc>] system_call+0x68/0x6d
 [<ffffffff8020a494>] system_call+0x0/0x6d


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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] dom0 failing to boot on Intel Xeon., Tyler MacDonald <=