Re: [Xen-devel] cpuidle and un-eoid interrupts at the local apic

[Andrew Cooper <andrew.cooper3@xxxxxxxxxx>]

On 07/09/2013 14:27, Thimo E. wrote:
> Hello again,
>
> I've disabled the internal network card and used another one, problem
> still exists. I had two crashed during 5 minutes, frustrating.
> So (assuming disabling the internal card in the bios is working) the
> source of the problem is not the internal NIC.
>
> Every time the pending EOI error occurs I see the mysterious interrupt
> >>29<<. Only the vectors are changing. See below a summary of the last
> 5 crashes.
>
> My Questions:
> - How can I see to which hardware device int 29 belongs ? I can't find
> int 29 in /proc/interrupts or lspci -vv nor in kernel dmesg or xen
> dmesg ?!?!
> - Andrew, what does your output "domain-list=0:276" mean and why is it
> alway 0:276 for interrupt 29 ? Is it the VM number ?
>
> 1)
> (XEN)   irq 29, vector 0x21
> (XEN)    IRQ:  29 affinity:4 vec:21 type=PCI-MSI status=00000010
> in-flight=0 domain-list=0:276(----),
>
> 2)
> (XEN)   irq 29, vector 0x26
> (XEN)    IRQ:  29 affinity:8 vec:26 type=PCI-MSI status=00000010
> in-flight=0 domain-list=0:276(----),
>
> 3)
> (XEN)   irq 29, vector 0x31
> (XEN)    IRQ:  29 affinity:2 vec:24 type=PCI-MSI status=00000010
> in-flight=0 domain-list=0:276(----),
>
> 4)
> (XEN)   irq 29, vector 0x2e
> (XEN)    IRQ:  29 affinity:8 vec:7e type=PCI-MSI status=00000010
> in-flight=0 domain-list=0:276(----),
>
> 5)
> (XEN)   irq 29, vector 0x3b
> (XEN)    IRQ:  29 affinity:2 vec:3b type=PCI-MSI status=00000010
> in-flight=0 domain-list=0:276(----),
>

irq 29 is just an internal Xen number for accounting all interrupts.  It
doesn't mean anything specific regarding hardware etc.  The vector and
affinity would expect to change as dom0s vcpus are moved around by the
scheduler.

domain-list=0 means that this interrupt is targeted at dom0 (It is a
list because certain interrupts have to be shared my more than 1
domain).  Helpfully, the keyhandler truncates the pirq field, so 276 is
unlikely to be correct.  As it is a dom0 MSI, I am guessing it actually
matches up with interrupt 1276 in /proc/interrupts, if there is one.

Can you provide the results of `xl debug-keys iMQ`, and attach
/proc/interrupts to this email (just in case the setup has changed after
playing with your BIOS)

~Andrew

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel