From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?Q?H=c3=a5kon_Alstadheim?= Subject: Re: [BUG] Assertion '(sp == 0) || (peoi[sp-1].vector < vector)' failed at irq.c:1163 Date: Fri, 15 Jan 2016 15:34:00 +0100 Message-ID: <56990358.2060006@alstadheim.priv.no> References: <5698D0C1.6000808@alstadheim.priv.no> <5698D297.8030700@citrix.com> <5698E6F4.4050703@alstadheim.priv.no> <5698F73202000078000C73C4@prv-mh.provo.novell.com> <5698EACD.6030906@alstadheim.priv.no> Mime-Version: 1.0 Content-Type: text/plain; charset="windows-1252"; Format="flowed" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <5698EACD.6030906@alstadheim.priv.no> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On 01/15/2016 01:49 PM, H=E5kon 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=3Ddate >>> loglvl=3Dall guest_loglvl=3Dall sync_console iommu=3D1,verbose,debug >>> iommu_inclusive_mapping=3D1 com1=3D115200,8n1 console=3Dcom1 dom0_max_v= cpus=3D4 >>> dom0_vcpus_pin=3D1 dom0_mem=3D8G,max:8G cpufreq=3Dxen:performance,verbo= se >>> tmem=3D1 sched_smt_power_savings=3D1 apic_verbosity=3Ddebug e820-verbos= e=3D1 >>> core_parking=3Dpower ucode=3Dmicrocode.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=3D config file/section = > entry; see EFI configuration file description). > > From efi.html > > "ucode=3D > > Specifies a CPU microcode blob to load. (x86 only) > > >>> #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 >> >> My fingers running faster than my head here. Managed to generate a blob = that Xen accepts with command "iucode_tool microcode.dat -S -w = microcode.bin" (missed the -S before). ucode=3Dmicrocode.bin on a line by itself in the config. Now the file actually loads, there is indeed an update, to 0x36 in my case. If the error at irq.c:1163 keeps happening, I'll be sure to report = again. :-~ Humbly, thanks H=E5kon. Sorry for all the noise.