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

On 22/01/2016 08:57, Håkon Alstadheim wrote: > Den 17. jan. 2016 16:25, skrev Andrew Cooper: >> On 17/01/16 15:16, Andrew Cooper wrote: > This isn't the first time we have seen this on Haswell processors. Do > you have microcode loading set up? > > ~Andrew > Still

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

>>> On 22.01.16 at 10:20, wrote: > ** sp 1, irq 107, vec 0x3b > **peoi[0] = {107, 0x3b, 0} > Assertion '(sp == 0) || (peoi[sp-1].vector < vector)' failed at irq.c:1172 > [ Xen-4.6.0 x86_64 debug=y Tainted:C ] > > Xen call trace: >[]

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

>>> On 18.01.16 at 11:35, wrote: > 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

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

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

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

>>> 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

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

Den 18. jan. 2016 11:31, skrev Jan Beulich: 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

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

On 17/01/2016 23:07, Håkon Alstadheim wrote: > Den 17. jan. 2016 17:30, skrev Håkon Alstadheim: >> Den 17. jan. 2016 16:16, skrev Andrew Cooper: >>> On 17/01/16 14:50, Håkon Alstadheim wrote: Den 15. jan. 2016 12:05, skrev Andrew Cooper: > On 15/01/16 10:58, Håkon Alstadheim wrote: >>

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

On 17/01/16 14:50, Håkon Alstadheim wrote: > Den 15. jan. 2016 12:05, skrev Andrew Cooper: >> On 15/01/16 10:58, Håkon Alstadheim wrote: >>> CPUINFO: >>> vendor_id: GenuineIntel >>> cpu family: 6 >>> model: 63 >>> model name: Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz >>> >>> #

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

On 17/01/16 15:16, Andrew Cooper wrote: > >>> This isn't the first time we have seen this on Haswell processors. Do >>> you have microcode loading set up? >>> >>> ~Andrew >>> >> Still happening with kernel-genkernel-x86_64-4.1.15-gentoo and updated >> cpu microcode, using microcode from 20151106.

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

Den 17. jan. 2016 16:16, skrev Andrew Cooper: > On 17/01/16 14:50, Håkon Alstadheim wrote: >> Den 15. jan. 2016 12:05, skrev Andrew Cooper: >>> On 15/01/16 10:58, Håkon Alstadheim wrote: CPUINFO: vendor_id: GenuineIntel cpu family: 6 model: 63 model name

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

On 15/01/16 10:58, Håkon Alstadheim wrote: > This is just a preliminary report, mostly just for the record. > > I will report again if this keeps happening after 4.7 is out, or upon > request. Anyone working on this, please mail me and request more > information. I have available logs from dom0

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

On 01/15/2016 12:05 PM, Andrew Cooper wrote: On 15/01/16 10:58, Håkon Alstadheim wrote: This is just a preliminary report, mostly just for the record. I will report again if this keeps happening after 4.7 is out, or upon request. Anyone working on this, please mail me and request more

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

On 01/15/2016 01:42 PM, Jan Beulich wrote: On 15.01.16 at 13:32, wrote: placed microcode.bin in /boot/microcode.bin booted with : --- xen_commandline: ssd-xen-debug-marker console_timestamps=date loglvl=all guest_loglvl=all sync_console

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

>>> On 15.01.16 at 13:32, wrote: > placed microcode.bin in /boot/microcode.bin > > booted with : > --- > xen_commandline: ssd-xen-debug-marker console_timestamps=date > loglvl=all guest_loglvl=all sync_console iommu=1,verbose,debug >

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

On 01/15/2016 02:09 PM, Ian Campbell wrote: On Fri, 2016-01-15 at 13:49 +0100, Håkon Alstadheim wrote: On 01/15/2016 01:42 PM, Jan Beulich wrote: On 15.01.16 at 13:32, wrote: placed microcode.bin in /boot/microcode.bin booted with : --- xen_commandline

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

On 01/15/2016 01:49 PM, Håkon Alstadheim wrote: On 01/15/2016 01:42 PM, Jan Beulich wrote: On 15.01.16 at 13:32, wrote: placed microcode.bin in /boot/microcode.bin booted with : --- xen_commandline: ssd-xen-debug-marker console_timestamps=date