Re: [Xen-devel] [xen-unstable test] 11946: regressions - FAIL

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 05.05.12 at 02:21, AP <apxeng@xxxxxxxxx> wrote:
> (XEN) *** IRQ BUG found ***
> (XEN) CPU0 -Testing vector 236 from bitmap

236 = 0xec = FIRST_LEGACY_VECTOR + 0x0c, i.e. an IRQ12 coming
in through the 8259A. Something fundamentally fishy must be going
on here, and I would suppose the code in question shouldn't even be
reached for legacy vectors.

Furthermore, calling dump_irqs() from the debugging code with
desc->lock still held makes it impossible to get full output, as that
function wants to lock all initialized IRQ descriptors.

Jan

> 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




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