[Xen-devel] domU and dom0 hung with Xen console interrupt binding showing in-flight=1, (---M)

[Dante Cinco <dantecinco@xxxxxxxxx>]

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