Re: Crash with vnd

[Martti Kuparinen <martti.kuparinen%iki.fi@localhost>]

Martti Kuparinen wrote:
> Manuel Bouyer wrote:
>
> > Ho, I've just seen yamt@'s commit, how many interrupts are you using ?
> > dmesg should show you ...
>
>
>
> xen1:~> dmesg | grep interrupt
> debug events interrupting at irq 0
> misdirect events interrupting at irq 1
> uhci0: interrupting at physical irq 16, irq 3
> uhci1: interrupting at physical irq 19, irq 4
> Intel 6300ESB Advanced Interrupt Controller (interrupt system, interface 
> 0x20, revision 0x02) at pci0 dev 29 function 5 not configured
> ehci0: interrupting at physical irq 23, irq 5
> piixide0: primary channel interrupting at physical irq 14, irq 6
> piixide0: secondary channel interrupting at physical irq 15, irq 7
> wm0: interrupting at physical irq 18, irq 9
> wm1: interrupting at physical irq 24, irq 10
> wm2: interrupting at physical irq 25, irq 11
> wm3: interrupting at physical irq 21, irq 12


xen1:~> dmesg | grep irq
debug events interrupting at irq 0
misdirect events interrupting at irq 1
Domain controller: using irq 2
uhci0: interrupting at physical irq 16, irq 3
uhci1: interrupting at physical irq 19, irq 4
ehci0: interrupting at physical irq 23, irq 5
piixide0: primary channel interrupting at physical irq 14, irq 6
piixide0: secondary channel interrupting at physical irq 15, irq 7
pckbc0: using irq 1 for kbd slot
wm0: interrupting at physical irq 18, irq 9
wm1: interrupting at physical irq 24, irq 10
wm2: interrupting at physical irq 25, irq 11
wm3: interrupting at physical irq 21, irq 12
Xen clock: using irq 13