From: "Jan Beulich" <JBeulich@suse.com>
To: "Håkon Alstadheim" <hakon@alstadheim.priv.no>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>, xen-devel@lists.xen.org
Subject: Re: [BUG] Assertion '(sp == 0) || (peoi[sp-1].vector < vector)' failed at irq.c:1163
Date: Fri, 15 Jan 2016 05:42:10 -0700 [thread overview]
Message-ID: <5698F73202000078000C73C4@prv-mh.provo.novell.com> (raw)
In-Reply-To: <5698E6F4.4050703@alstadheim.priv.no>
>>> On 15.01.16 at 13:32, <hakon@alstadheim.priv.no> 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
> iommu_inclusive_mapping=1 com1=115200,8n1 console=com1 dom0_max_vcpus=4
> dom0_vcpus_pin=1 dom0_mem=8G,max:8G cpufreq=xen:performance,verbose
> tmem=1 sched_smt_power_savings=1 apic_verbosity=debug e820-verbose=1
> core_parking=power ucode=microcode.bin
> ---
This can't work - did you look at the command line documentation?
You can't specify a file name here - there's no file system driver
inside the hypervisor, and hence it can't read files (it instead has
to rely on the boot loader bringing those into memory for it).
> #cat /proc/cpuinfo | grep micro
> says: microcode : 0x31
>
> This is no change from previous boot.
> Now: How do I know wheter 0x31 is the newest?
By checking - for the precise model and stepping of your CPU(s) -
the information in the blob (which admittedly is a little cumbersome,
but without knowing model and stepping I also can't try to help).
Jan
next prev parent reply other threads:[~2016-01-15 12:42 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 [this message]
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
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=5698F73202000078000C73C4@prv-mh.provo.novell.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.