From: Andrew Cooper <andrew.cooper3@citrix.com>
To: AP <apxeng@gmail.com>
Cc: "Keir (Xen.org)" <keir@xen.org>,
Daniel De Graaf <dgdegra@tycho.nsa.gov>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: [xen-unstable test] 11946: regressions - FAIL
Date: Sat, 5 May 2012 12:04:39 +0100 [thread overview]
Message-ID: <4FA50947.8030703@citrix.com> (raw)
In-Reply-To: <CAGU+auvu7DzVbRavS74AmNDOb3gS-dVHr3inVJFYZQQVbVMe6Q@mail.gmail.com>
> Thanks, that fixed it. Here is what I see now:
>
> (XEN) *** IRQ BUG found ***
> (XEN) CPU0 -Testing vector 236 from bitmap
> 37,41,49,51,64,72,80,88,96,104,120,136,145,152,158,160,168,175,182,192,200,211
> (XEN) Guest interrupt information:
> (XEN) IRQ: 0 affinity:01 vec:f0 type=IO-APIC-edge
> status=00000000 mapped, unbound
> (XEN) IRQ: 1 affinity:01 vec:d3 type=IO-APIC-edge
> status=00000030 in-flight=0 domain-list=0: 1(-S--),
> (XEN) IRQ: 2 affinity:ff vec:e2 type=XT-PIC
> status=00000000 mapped, unbound
> (XEN) IRQ: 3 affinity:01 vec:40 type=IO-APIC-edge
> status=00000002 mapped, unbound
> (XEN) IRQ: 4 affinity:01 vec:48 type=IO-APIC-edge
> status=00000002 mapped, unbound
> (XEN) IRQ: 5 affinity:01 vec:50 type=IO-APIC-edge
> status=00000002 mapped, unbound
> (XEN) IRQ: 6 affinity:01 vec:58 type=IO-APIC-edge
> status=00000002 mapped, unbound
> (XEN) IRQ: 7 affinity:01 vec:60 type=IO-APIC-edge
> status=00000002 mapped, unbound
> (XEN) IRQ: 8 affinity:08 vec:29 type=IO-APIC-edge
> status=00000030 in-flight=0 domain-list=0: 8(-S--),
> (XEN) IRQ: 9 affinity:02 vec:25 type=IO-APIC-level
> status=00000030 in-flight=0 domain-list=0: 9(-S--),
> (XEN) IRQ: 10 affinity:01 vec:78 type=IO-APIC-edge
> status=00000002 mapped, unbound
> (XEN) IRQ: 11 affinity:01 vec:88 type=IO-APIC-edge
> status=00000002 mapped, unbound
> [ 5129.737147] [drm:i915_hangcheck_ring_idle] *ERROR* Hangcheck timer
> elapsed... blt ring idle [waiting on 1800652, at 1800652], missed IRQ?
>
> Let me know if you need any more info.
> Thanks,
> AP
>
There should be quite a lot more irq information dumped than just that.
Was there any more on the console or had it given up by that point? It
might be worth trying to set synchronous console to get all of that
debug information?
How easy is this error to reproduce for you? I never managed to
reproduce it reliably enough to be able to debug?
If you could provide your Xen boot console log, that would be very useful
~Andrew
next prev parent reply other threads:[~2012-05-05 11:04 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-13 20:16 [xen-unstable test] 11946: regressions - FAIL xen.org
2012-02-14 10:44 ` Ian Campbell
2012-02-14 19:17 ` Daniel De Graaf
2012-03-27 10:36 ` Ian Campbell
2012-03-27 10:52 ` Jan Beulich
2012-05-04 19:48 ` AP
2012-05-04 20:11 ` Andrew Cooper
2012-05-05 0:21 ` AP
2012-05-05 11:04 ` Andrew Cooper [this message]
2012-05-05 18:41 ` AP
2012-05-05 19:06 ` AP
2012-05-07 8:10 ` Jan Beulich
2012-05-07 11:50 ` Andrew Cooper
2012-05-07 13:34 ` Jan Beulich
2012-05-07 14:41 ` Andrew Cooper
2012-05-07 14:50 ` Jan Beulich
2012-05-07 15:40 ` Andrew Cooper
2012-05-07 15:43 ` Jan Beulich
2012-05-07 14:54 ` Jan Beulich
2012-05-07 15:51 ` Andrew Cooper
2012-05-07 18:29 ` AP
2012-05-08 6:37 ` Jan Beulich
2012-05-05 10:33 ` Ian Campbell
2012-05-05 11:11 ` 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=4FA50947.8030703@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=apxeng@gmail.com \
--cc=dgdegra@tycho.nsa.gov \
--cc=keir@xen.org \
--cc=xen-devel@lists.xensource.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).