From: Andrew Cooper <andrew.cooper3@citrix.com>
To: "Jan Beulich" <JBeulich@suse.com>,
"Håkon Alstadheim" <hakon@alstadheim.priv.no>
Cc: xen-devel@lists.xen.org
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 [thread overview]
Message-ID: <569CBFD5.2010609@citrix.com> (raw)
In-Reply-To: <569CCD2002000078000C7E3C@prv-mh.provo.novell.com>
On 18/01/16 10:31, Jan Beulich wrote:
>>>> On 18.01.16 at 00:07, <hakon@alstadheim.priv.no> 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
next prev parent reply other threads:[~2016-01-18 10:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-15 10:58 [BUG] Assertion '(sp == 0) || (peoi[sp-1].vector < vector)' failed at irq.c:1163 Håkon Alstadheim
2016-01-15 11:05 ` Andrew Cooper
2016-01-15 12:32 ` Håkon Alstadheim
2016-01-15 12:42 ` Jan Beulich
2016-01-15 12:49 ` Håkon Alstadheim
2016-01-15 13:09 ` Ian Campbell
2016-01-15 13:20 ` Håkon Alstadheim
2016-01-15 14:34 ` Håkon Alstadheim
2016-01-17 14:50 ` Håkon Alstadheim
2016-01-17 15:16 ` Andrew Cooper
2016-01-17 15:25 ` Andrew Cooper
2016-01-22 8:57 ` Håkon Alstadheim
2016-01-22 9:20 ` Andrew Cooper
2016-01-22 10:06 ` Jan Beulich
2016-01-17 16:30 ` Håkon Alstadheim
2016-01-17 23:07 ` Håkon Alstadheim
2016-01-17 23:12 ` Andrew Cooper
2016-01-18 10:31 ` Jan Beulich
2016-01-18 10:35 ` Andrew Cooper [this message]
2016-01-18 10:54 ` Jan Beulich
2016-01-18 16:35 ` Håkon Alstadheim
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=569CBFD5.2010609@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=hakon@alstadheim.priv.no \
--cc=xen-devel@lists.xen.org \
/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).