From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: [BUG] Assertion '(sp == 0) || (peoi[sp-1].vector < vector)' failed at irq.c:1163 Date: Mon, 18 Jan 2016 10:35:01 +0000 Message-ID: <569CBFD5.2010609@citrix.com> References: <5698D0C1.6000808@alstadheim.priv.no> <5698D297.8030700@citrix.com> <569BAA4A.8010501@alstadheim.priv.no> <569BB05B.1000801@citrix.com> <569BC1C1.6090307@alstadheim.priv.no> <569C1E98.8020802@alstadheim.priv.no> <569CCD2002000078000C7E3C@prv-mh.provo.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <569CCD2002000078000C7E3C@prv-mh.provo.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich , =?UTF-8?Q?H=c3=a5kon_Alstadheim?= Cc: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On 18/01/16 10:31, Jan Beulich wrote: >>>> On 18.01.16 at 00:07, 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. ~Andrew