From: Andrew Cooper <andrew.cooper3@citrix.com>
To: "Thimo E." <abc@digithi.de>
Cc: "Zhang, Yang Z" <yang.z.zhang@intel.com>,
xen-devel <xen-devel@lists.xenproject.org>,
Keir Fraser <keir@xen.org>, Jan Beulich <JBeulich@suse.com>
Subject: Re: cpuidle and un-eoid interrupts at the local apic
Date: Sat, 7 Sep 2013 18:02:18 +0100 [thread overview]
Message-ID: <522B5C1A.1050100@citrix.com> (raw)
In-Reply-To: <522B29BC.3010003@digithi.de>
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
next prev parent reply other threads:[~2013-09-07 17:02 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-31 20:32 cpuidle and un-eoid interrupts at the local apic Andrew Cooper
2013-06-03 14:30 ` Jan Beulich
2013-07-31 8:30 ` Thimo E.
2013-07-31 9:47 ` Andrew Cooper
2013-08-02 22:50 ` Thimo E.
2013-08-02 23:32 ` Andrew Cooper
2013-08-05 12:45 ` Jan Beulich
2013-08-05 14:51 ` Andrew Cooper
2013-08-09 21:27 ` Thimo E.
2013-08-09 21:40 ` Andrew Cooper
2013-08-09 21:44 ` Andrew Cooper
2013-08-11 17:46 ` Thimo E.
2013-08-12 6:02 ` Zhang, Yang Z
2013-08-12 8:49 ` Zhang, Yang Z
2013-08-12 8:57 ` Jan Beulich
2013-08-12 11:52 ` Thimo E
2013-08-12 12:04 ` Andrew Cooper
2013-08-19 15:14 ` Thimo E.
2013-08-20 5:43 ` Thimo Eichstädt
2013-08-20 8:40 ` Jan Beulich
2013-08-20 8:50 ` Zhang, Yang Z
2013-08-23 7:22 ` Thimo Eichstädt
2013-08-23 7:30 ` Zhang, Yang Z
2013-08-27 1:03 ` Zhang, Yang Z
2013-09-04 18:32 ` Thimo E.
2013-09-04 18:55 ` Andrew Cooper
2013-09-04 19:56 ` Thimo E.
2013-09-04 20:54 ` Andrew Cooper
2013-09-05 1:45 ` Zhang, Yang Z
2013-09-05 7:20 ` Thimo E.
2013-09-05 1:15 ` Zhang, Yang Z
2013-09-17 2:09 ` Zhang, Yang Z
2013-09-17 7:39 ` Thimo E.
2013-09-17 7:43 ` Zhang, Yang Z
2013-09-17 21:04 ` Thimo E.
2013-09-18 1:18 ` Zhang, Xiantao
2013-09-18 17:24 ` Thimo E.
2013-09-18 12:06 ` Andrew Cooper
2013-08-12 13:54 ` Thimo E
2013-08-12 14:06 ` Andrew Cooper
2013-08-13 1:43 ` Zhang, Yang Z
2013-08-13 6:39 ` Thimo E.
2013-08-13 11:39 ` Wu, Feng
2013-08-13 12:46 ` Andrew Cooper
2013-08-12 9:10 ` Andrew Cooper
2013-08-12 5:50 ` Zhang, Yang Z
2013-08-12 8:20 ` Jan Beulich
2013-08-12 9:28 ` Andrew Cooper
2013-08-12 10:05 ` Jan Beulich
2013-08-12 10:27 ` Andrew Cooper
2013-08-14 2:53 ` Zhang, Yang Z
2013-08-14 7:51 ` Thimo E.
2013-08-14 9:52 ` Andrew Cooper
2013-09-07 13:27 ` Thimo E.
2013-09-07 17:02 ` Andrew Cooper [this message]
2013-09-07 23:37 ` Thimo E.
2013-09-08 9:53 ` Andrew Cooper
2013-09-08 10:24 ` Thimo E.
2013-09-09 13:16 ` Andrew Cooper
2013-09-09 14:48 ` Thimo Eichstädt
2013-09-09 15:12 ` Andrew Cooper
2013-09-09 7:59 ` Jan Beulich
2013-09-09 12:53 ` Andrew Cooper
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=522B5C1A.1050100@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=abc@digithi.de \
--cc=keir@xen.org \
--cc=xen-devel@lists.xenproject.org \
--cc=yang.z.zhang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).