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

["Håkon Alstadheim" <hakon@alstadheim.priv.no>]

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, <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).
>> Get with the times :-) . Under EFI it most definitely wants a file-name.
>> Not entirely sure about the file FORMAT though.
>>
>>   From xen-command-line.html
>>    "Note further that use of this option has an unspecified effect when
>> used with xen.efi (there the concept of modules doesn't exist, and the
>> blob gets specified via the ucode=<filename> config file/section entry;
>> see EFI configuration file description).
>>
>>   From efi.html
>>
>>    "ucode=<filename>
>>
>>       Specifies a CPU microcode blob to load. (x86 only)
> This needs to go in your xen.cfg file (alongside kernel= ramdisk= etc), not
> on the xen command line.
>
> Ian.
>

Ahh (face + palm) .  It dawned on me right after I sent my previous. Now 
I DO get some acknowledgement of microcode.bin in the console-log, but 
/proc/cpuinfo still reports microcode    : 0x31, so it seems stale 
microcode is not the issue :-/



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