[Xen-users] PCI interrupts in domU not working?

[Tony Hoyle <tmh@xxxxxxxxxxxx>]

Hi,

Before I upgraded to xen 3.1 I was running asterisk in a domU quite 
happily, talking to its pci interface in the dom0.  When I upgraded to 
xen 3.1 it broke and I forgot about it.  Now I'm trying to get it to 
work again..
Basically everything works except the domU never seems to get any 
interrupts, so no data flows.  The device configures, and is active, but 
 zttest just hangs and although you can dial out on it there's no sound.
The device seems to be getting through OK:

dom0:
05:00.0 Communication controller: Tiger Jet Network Inc. Tiger3XX 
Modem/ISDN interface
        Subsystem: Unknown device 8085:0003
        Flags: bus master, medium devsel, latency 32, IRQ 20
        I/O ports at c000 [size=256]
        Memory at f9100000 (32-bit, non-prefetchable) [size=4K]
        Capabilities: [40] Power Management version 2



domU:
00:00.0 Communication controller: Tiger Jet Network Inc. Tiger3XX 
Modem/ISDN interface
        Subsystem: Unknown device 8085:0003
        Flags: bus master, medium devsel, latency 32, IRQ 20
        I/O ports at c000 [size=256]
        Memory at f9100000 (32-bit, non-prefetchable) [size=4K]
        Capabilities: [40] Power Management version 2

           CPU0
 20:          0  Phys-irq-level     wcfxo
256:     164020  Dynamic-irq-level     timer0
257:          0  Dynamic-irq-level     resched0
258:          0  Dynamic-irq-level     callfunc0
259:        421  Dynamic-irq-level     xenbus
260:        484  Dynamic-irq-level     xencons
261:      79270  Dynamic-irq-level     blkif
262:      20133  Dynamic-irq-level     blkif
263:         20  Dynamic-irq-level     blkif
264:      25043  Dynamic-irq-level     eth0
NMI:          0
LOC:          0
ERR:          0


In the dom0 dmesg I can see:
pciback 0000:05:00.0: seizing device
ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 20 (level, low) -> IRQ 20
ACPI: PCI interrupt for device 0000:05:00.0 disabled

So how do I get it un-disabled?  Presumably there's some setting that 
was default in xen 3.0.4 but needs to be explicit in xen 3.1, but I 
can't find any reference to it.
Tony

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