Re: [Xen-devel] [BUG] Assertion '(sp == 0) || (peoi[sp-1].vector < vector)' failed at irq.c:1163

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 18.01.16 at 11:35, <andrew.cooper3@xxxxxxxxxx> wrote:
> On 18/01/16 10:31, Jan Beulich wrote:
>>>>> On 18.01.16 at 00:07, <hakon@xxxxxxxxxxxxxxxxxx> wrote:
>>> There we go :-/ . Log attached from boot to assertion-failure with
>>> loglvl=all guest_loglvl=all . Some of the log output might be a bit
>>> cryptic, they are notes to myself from local boot-scripts, basically
>>> firing up my router/name-server/dhcp-server and waiting until services
>>> are ready before continuing.
>>>
>>> ---
>>> (XEN) [2016-01-17 22:46:38] **peoi[0] = {107, 0x40, 0}
>> According to
>>
>> (XEN) [2016-01-17 16:50:49] IOAPIC[0]: Set PCI routing entry (1-3 -> 0x40 -> 
>> IRQ 3 
> Mode:0 Active:0)
>>
>> this might be the serial console, albeit IRQ 107 contradicts this
>> afaict. Does this also occur without serial console? Are we
>> perhaps wrongly re-using vector 0x40 (and if so might this be
>> fixed with -unstable commit fc0c3fa2ad, in turn requiring
>> e509b8e09c)?
> 
> I also had a bug in the first patch which printed the vector as 0x%u,
> fixed in the second to be %#x.  As such, the actual vector on the
> pending EOI stack is 0x28.

That wouldn't make it any better, as then, considering the other
similar messages, we would have to conclude it's the vector of
some other Xen internally used device (the IOMMU?), which again
shouldn't be used by guest IRQ unless it got recycled (albeit I don't
think e.g. IOMMU vectors get recycled at all).

HÃkon, considering

(XEN) Failed to enable Interrupt Remapping: Will not enable x2APIC.

plus

(XEN) Intel VT-d Interrupt Remapping enabled.

(a logging inconsistency addressed on -unstable already) could you
check your BIOS setup whether you can make firmware permit use
of x2APIC mode? And could you try whether the issue goes away
with "maxcpus=6" (or less) on the Xen command line?

Also, you appear to be doing GPU pass-through - is the problem
connected to that?

Jan

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