On Tue, Jul 13, 2010 at 1:06 AM, Jan Beulich <[email protected]> wrote: > 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 <[email protected]>, Peter Oruba /var/log/boot.msg:udevd[782]: reading '/lib/udev/rules.d/89-microcode.rules' as rules file /var/log/boot.msg:udevd[783]: mknod '/dev/cpu/microcode' c10:184 /var/log/messages:Jul 13 09:25:16 server udevadm[2813]: device 0x622140 has devpath '/devices/platform/microcode' /var/log/messages:Jul 13 09:25:16 server udevadm[2813]: device 0x622140 has devpath '/devices/virtual/misc/microcode' /var/log/messages:Jul 13 09:25:16 server udevadm[2813]: device 0x6335f0 has devpath '/devices/platform/microcode' /var/log/messages:Jul 13 09:25:16 server udevadm[2813]: device 0x6336b0 has devpath '/devices/virtual/misc/microcode' /var/log/messages:Jul 13 09:25:16 server udevadm[2813]: device 0x6336b0 filled with db symlink data '/dev/cpu/microcode' /var/log/messages:Jul 13 09:25:16 server udevadm[2813]: device 0x6336b0 filled with db symlink data '/dev/cpu/microcode' /var/log/messages:Jul 13 09:25:16 server udevadm[2813]: device 0x6336b0 filled with db symlink data '/dev/cpu/microcode' /var/log/messages:Jul 13 09:25:16 server udevadm[2813]: device 0x6336b0 filled with db symlink data '/dev/cpu/microcode' /var/log/messages:Jul 13 09:25:16 server udevadm[2813]: device 0x6336b0 filled with db symlink data '/dev/cpu/microcode' /var/log/messages:Jul 13 09:25:24 server udevadm[4032]: device 0x622140 has devpath '/devices/platform/microcode' /var/log/messages:Jul 13 09:25:24 server udevadm[4032]: device 0x622140 has devpath '/devices/virtual/misc/microcode' /var/log/messages:Jul 13 09:25:24 server udevadm[4032]: device 0x63e220 has devpath '/devices/platform/microcode' /var/log/messages:Jul 13 09:25:24 server udevadm[4032]: device 0x633d90 has devpath '/devices/virtual/misc/microcode' /var/log/messages:Jul 13 09:25:24 server udevadm[4032]: device 0x633d90 filled with db symlink data '/dev/cpu/microcode' /var/log/messages:Jul 13 09:25:24 server udevadm[4032]: device 0x633d90 filled with db symlink data '/dev/cpu/microcode' /var/log/messages:Jul 13 09:25:24 server udevadm[4032]: device 0x633d90 filled with db symlink data '/dev/cpu/microcode' /var/log/messages:Jul 13 09:25:24 server udevadm[4032]: device 0x633d90 filled with db symlink data '/dev/cpu/microcode' /var/log/messages:Jul 13 09:25:24 server udevadm[4032]: device 0x633d90 filled with db symlink data '/dev/cpu/microcode' /var/log/messages:Jul 13 09:25:33 server BLKTAPCTRL[4995]: blktapctrl.c:793: Found driver: [ramdisk image (ram)] what's useful here, then? GMC kernel is, apparently, ok -- or at least, better. 11.3 @ http://download.opensuse.org/repositories/Kernel:/openSUSE-11.3/openSUSE_11.3 is not. ignore .../Kernel:/openSUSE-11.3/openSUSE_11.3, as (i assume) GMC -> 11.3 release? -- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
