Re: [opensuse-virtual] @ 11.3 xen Dom0 boot, "microcode: error! Wrong microcode patch file"
On 09.07.10 at 17:15, 0bo0 <0.bugs.only.0@gmail.com> wrote: On Fri, Jul 9, 2010 at 12:46 AM, Jan Beulich
wrote: The question then is why request_firmware() succeeds. We're not talking about a kernel you built yourself, do we? no, not custom. atm, this is,
uname -a Linux server 2.6.34.1-2-xen #1 SMP 2010-07-06 15:11:07 +0200 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a LSB Version: core-2.0-noarch:core-3.2-noarch:core-4.0-noarch:core-2.0-x86_64:core-3.2-x86_64:core-4. 0-x86_64:desktop-4.0-amd64:desktop-4.0-noarch:graphics-2.0-amd64:graphics-2.0-noarch:g raphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch Distributor ID: SUSE LINUX Description: openSUSE 11.3 (x86_64) Release: 11.3 Codename: n/a grep base /etc/zypp/repos.d/Kernel_113.repo
baseurl=http://download.opensuse.org/repositories/Kernel:/openSUSE-11.3/open SUSE_11.3
Again, this is a different thing. Can we please finally get to know how a native kernel of the same version behaves?
You may want to set udev_log="info" in /etc/udev/udev.conf and USE_SYSLOG="yes" in /etc/sysconfig/hardware/config to get relevant output from /lib/udev/firmware.sh.
You may want to set udev_log="info" in /etc/udev/udev.conf and USE_SYSLOG="yes" in /etc/sysconfig/hardware/config to get
mkdir -p /etc/sysconfig/hardware
udev_log="info" < -- /etc/udev/udev.conf USE_SYSLOG="yes" <-- /etc/sysconfig/hardware/config to get
reboot uname -a Linux server 2.6.34.1-2-default #1 SMP 2010-07-06 15:11:07 +0200 x86_64 x86_64 x86_64 GNU/Linux
egrep -i "amd|microcode" /var/log/* ...
And for comparison the same with 2.6.34.1-2-xen ? On -default, the messages clearly indicate that request_firmware() is failing on that file (as expected), but the fact that Xen gets presented with a firmware image at all requires that request_firmware() is not failing as expected on -xen. Jan -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-virtual+help@opensuse.org
And for comparison the same with 2.6.34.1-2-xen ? On -default, the messages clearly indicate that request_firmware() is failing on that file (as expected), but the fact that Xen gets presented with a firmware image at all requires that request_firmware() is not failing as expected on -xen.
since an update to 2.6.34.1-5-default, 2.6.34.1-5-xen, (re)providing both cases:
uname -a
Linux server 2.6.34.1-5-default #1 SMP 2010-07-10 08:18:53 +0200
x86_64 x86_64 x86_64 GNU/Linux
egrep -i "amd|microcode" /var/log/*
/var/log/boot.msg:<6>[ 0.000000] RAMDISK: 374ec000 - 37ff0000
/var/log/boot.msg:<4>[ 0.000000] ACPI: SSDT 00000000cff87950 0088C
(v01 A M I POWERNOW 00000001 AMD 00000001)
/var/log/boot.msg:<6>[ 0.000000] #2 [00374ec000 - 0037ff0000]
RAMDISK
/var/log/boot.msg:<6>[ 0.108010] Performance Events: AMD PMU driver.
/var/log/boot.msg:<6>[ 0.389802] CPU0: AMD Phenom(tm) II X4 920
Processor stepping 02
/var/log/boot.msg:<6>[ 6.083093] ehci_hcd 0000:00:12.2: applying
AMD SB600/SB700 USB freeze workaround
/var/log/boot.msg:<6>[ 6.410162] ehci_hcd 0000:00:13.2: applying
AMD SB600/SB700 USB freeze workaround
/var/log/boot.msg:<6>[ 70.915237] EDAC amd64_edac: Ver: 3.3.0 Jul 11 2010
/var/log/boot.msg:<5>[ 70.927231] EDAC amd64: This node reports
that Memory ECC is currently disabled, set F3x44[22] (0000:00:18.3).
/var/log/boot.msg:<5>[ 70.949943] EDAC amd64: ECC disabled in the
BIOS or no ECC capability, module will not load.
/var/log/boot.msg:<4>[ 71.006870] amd64_edac: probe of 0000:00:18.2
failed with error -22
/var/log/boot.msg:<6>[ 101.088689] microcode: CPU0: patch_level=0x1000086
/var/log/boot.msg:<6>[ 101.100306] platform microcode: firmware:
requesting amd-ucode/microcode_amd.bin
/var/log/boot.msg:<3>[ 161.096370] microcode: failed to load file
amd-ucode/microcode_amd.bin
/var/log/boot.msg:<6>[ 161.110175] microcode: CPU1: patch_level=0x1000086
/var/log/boot.msg:<6>[ 161.122496] platform microcode: firmware:
requesting amd-ucode/microcode_amd.bin
/var/log/boot.msg:<3>[ 182.369752] microcode: failed to load file
amd-ucode/microcode_amd.bin
/var/log/boot.msg:<6>[ 182.385287] microcode: CPU2: patch_level=0x1000086
/var/log/boot.msg:<6>[ 182.397612] platform microcode: firmware:
requesting amd-ucode/microcode_amd.bin
/var/log/boot.msg:<3>[ 184.577443] microcode: failed to load file
amd-ucode/microcode_amd.bin
/var/log/boot.msg:<6>[ 184.592314] microcode: CPU3: patch_level=0x1000086
/var/log/boot.msg:<6>[ 184.604648] platform microcode: firmware:
requesting amd-ucode/microcode_amd.bin
/var/log/boot.msg:<3>[ 185.349984] microcode: failed to load file
amd-ucode/microcode_amd.bin
/var/log/boot.msg:<6>[ 185.364348] microcode: Microcode Update
Driver: v2.00
On 12.07.10 at 17:55, 0bo0 <0.bugs.only.0@gmail.com> wrote: And for comparison the same with 2.6.34.1-2-xen ? On -default, the messages clearly indicate that request_firmware() is failing on that file (as expected), but the fact that Xen gets presented with a firmware image at all requires that request_firmware() is not failing as expected on -xen.
since an update to 2.6.34.1-5-default, 2.6.34.1-5-xen, (re)providing both cases:
uname -a Linux server 2.6.34.1-5-default #1 SMP 2010-07-10 08:18:53 +0200 x86_64 x86_64 x86_64 GNU/Linux egrep -i "amd|microcode" /var/log/* ... /var/log/boot.msg:<6>[ 6.083093] ehci_hcd 0000:00:12.2: applying AMD SB600/SB700 USB freeze workaround /var/log/boot.msg:<6>[ 6.410162] ehci_hcd 0000:00:13.2: applying AMD SB600/SB700 USB freeze workaround /var/log/boot.msg:<6>[ 70.915237] EDAC amd64_edac: Ver: 3.3.0 Jul 11 2010 /var/log/boot.msg:<5>[ 70.927231] EDAC amd64: This node reports that Memory ECC is currently disabled, set F3x44[22] (0000:00:18.3). /var/log/boot.msg:<5>[ 70.949943] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. /var/log/boot.msg:<4>[ 71.006870] amd64_edac: probe of 0000:00:18.2 failed with error -22 /var/log/boot.msg:<6>[ 101.088689] microcode: CPU0: patch_level=0x1000086 /var/log/boot.msg:<6>[ 101.100306] platform microcode: firmware: requesting amd-ucode/microcode_amd.bin /var/log/boot.msg:<3>[ 161.096370] microcode: failed to load file amd-ucode/microcode_amd.bin ... uname -a Linux server 2.6.34.1-5-xen #1 SMP 2010-07-10 08:18:53 +0200 x86_64 x86_64 x86_64 GNU/Linux ... /var/log/boot.msg:<6>[ 2.419834] ehci_hcd 0000:00:12.2: applying AMD SB600/SB700 USB freeze workaround /var/log/boot.msg:<6>[ 2.459433] ehci_hcd 0000:00:13.2: applying AMD SB600/SB700 USB freeze workaround /var/log/boot.msg:<6>[ 9.565472] platform microcode: firmware: requesting amd-ucode/microcode_amd.bin /var/log/boot.msg:<6>[ 9.798936] microcode: Microcode Update Driver: v2.00-xen
, Peter Oruba
The timing is completely different, and the log appears to confirm that the loading of the file fails (as expected) on native, but doesn't on Xen. Neither of the two I can explain without more detailed analysis. I suggest opening a bug report, attaching the full native and Xen boot.msg. Jan -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-virtual+help@opensuse.org
On Tue, Jul 13, 2010 at 1:06 AM, Jan Beulich
The timing is completely different, and the log appears to confirm that the loading of the file fails (as expected) on native, but doesn't on Xen.
Neither of the two I can explain without more detailed analysis. I suggest opening a bug report, attaching the full native and Xen boot.msg.
before i do ...
for another bug, I switched
--- Linux server 2.6.34.1-5-xen #1 SMP 2010-07-10 08:18:53
+0200 x86_64 x86_64 x86_64 GNU/Linux <-- KOTD
+++ Linux server 2.6.34-12-xen #1 SMP 2010-06-29 02:39:08
+0200 x86_64 x86_64 x86_64 GNU/Linux <-- GMC
and now, checking THIS issue, no more microcode issues/errors ...
egrep -i "amd|microcode" /var/log/*
/var/log/boot.msg:<6>[ 0.000000] RAMDISK: 008af000 - 02475000
/var/log/boot.msg:<4>[ 0.000000] ACPI: SSDT 00000000cff87950 0088C
(v01 A M I POWERNOW 00000001 AMD 00000001)
/var/log/boot.msg:<6>[ 2.462448] ehci_hcd 0000:00:12.2: applying
AMD SB600/SB700 USB freeze workaround
/var/log/boot.msg:<6>[ 2.473331] ehci_hcd 0000:00:13.2: applying
AMD SB600/SB700 USB freeze workaround
/var/log/boot.msg:<6>[ 15.094072] platform microcode: firmware:
requesting amd-ucode/microcode_amd.bin
/var/log/boot.msg:<6>[ 27.946193] microcode: Microcode Update
Driver: v2.00-xen
participants (2)
-
0bo0
-
Jan Beulich