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

[Andrew Cooper <andrew.cooper3@xxxxxxxxxx>]

> 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

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