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

[Xen-devel] domU and dom0 hung with Xen console interrupt binding showin

To: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] domU and dom0 hung with Xen console interrupt binding showing in-flight=1, (---M)
From: Dante Cinco <dantecinco@xxxxxxxxx>
Date: Mon, 28 Jun 2010 11:22:36 -0700
Delivery-date: Mon, 28 Jun 2010 11:23:34 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=8+9beAHH/HtcVJRVU+4rNE0nJ3OIUUS7+Iz0FGrLjy0=; b=OuYahqCsgigYnMRIzA5ZOTEmspMtZjMNxbFKViIldUP9AvXjpZY09t9aXKq/Gqoypa w3s8orrX+6O6JQCilSjVfDZiPM+pG4PK0PNyU4QxITSEHVIlAS4L6K9pbXCbxFSQ8o8x YME+4+Ar+Jrw1x77B1ebaaZ6sSO070aOSvKs4=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=tm01ZEuYfXR3FbHcP7/pOMsTuhrLTHkeBIsBm4nQ1oEeBzW5RSxWHoBysyQl6JOKPD sspbc1Y2bX9qVyDsTiwxE2gVQdco1pRMmQssIfzb/A32/lw/fBa1oYgbxnG6gd04SPfG nh1yYYFuauzNw7vCeio/1L/ntunI6N6hJFIqY=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
I have an HP Proliant DL380-G6 (dual Xeon E5540 @ 2.53GHz) with Xen 4.0.0 and dom0 Linux 2.6.32.12 x86_64 pvops and domU Linux kernel 2.6.30.1 x86_64. I'm using PCI passthrough (pci-stub) to pass my 4-port 8Gb PMC-Sierra Fibre Channel HBA to domU. After running I/Os for several hours, both dom0 and domU hangs and the Xen console shows the interrupt binding below where IRQ 66 shows in-flight=1 and mask set (---M). What's the best way to debug this problem?

(XEN)    IRQ:  66 affinity:00000000,00000000,00000000,00000001 vec:b9 type=PCI-MSI         status=00000010 in-flight=1 domain-list=1: 79(---M),
(XEN)    IRQ:  67 affinity:00000000,00000000,00000000,00000004 vec:d9 type=PCI-MSI         status=00000010 in-flight=0 domain-list=1: 78(----),
(XEN)    IRQ:  68 affinity:00000000,00000000,00000000,00000010 vec:22 type=PCI-MSI         status=00000010 in-flight=0 domain-list=1: 77(----),
(XEN)    IRQ:  69 affinity:00000000,00000000,00000000,00000040 vec:2a type=PCI-MSI         status=00000010 in-flight=0 domain-list=1: 76(----),

(XEN) 07:00.3 - dom 1   - MSIs < 69 >
(XEN) 07:00.2 - dom 1   - MSIs < 68 >
(XEN) 07:00.1 - dom 1   - MSIs < 67 >
(XEN) 07:00.0 - dom 1   - MSIs < 66 >

(XEN)  MSI    66 vec=b9  fixed  edge   assert phys    cpu dest=00000000 mask=0/0/-1
(XEN)  MSI    67 vec=d9  fixed  edge   assert phys    cpu dest=00000004 mask=0/0/-1
(XEN)  MSI    68 vec=22  fixed  edge   assert phys    cpu dest=00000002 mask=0/0/-1
(XEN)  MSI    69 vec=2a  fixed  edge   assert phys    cpu dest=00000006 mask=0/0/-1

Thanks.

Dante
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>