https://bugzilla.novell.com/show_bug.cgi?id=847158
https://bugzilla.novell.com/show_bug.cgi?id=847158#c34
--- Comment #34 from Dirk Weber
... I have put fixed ucode-intel and ucode-amd packages here: ftp.suse.com/pub/people/trenn/13.1_microcode_updates Installing should trigger mkinitrd. When initrd is created there is an additional line now: Microcode: ... telling the user whether a suitable microcode update has been found and added to initrd. If one is found, rebooting must result in a microcode update (check dmesg or /var/log/messages).
For AMD I gave it a try and run into strang issues (but on a 13.1 Milestone 4 system): - AMD microcode got added to initrd correctly, but reboot did not result in an update. Triggering microcode reload manually: echo 1 >/sys/devices/system/cpu/microcode/reload resulted in updating only some of the 16 cores:
Would be great if others can give the packages a try.
I have tested your ucode-amd package. mkinitrd is run after installation and gives this output: .. Microcode: Adding AMD microcode microcode_amd.bin Microcode: Adding AMD microcode microcode_amd.bin .. it seems that the body of the script lib/mkinitrd/scripts/setup-amd_microcode.sh is duplicated? # lsinitrd initrd-3.11.6-4-desktop | grep ucode lib/firmware/amd-ucode lib/firmware/amd-ucode/microcode_amd.bin.asc lib/firmware/amd-ucode/microcode_amd.bin shows that the microcode is included in the initrd, but I think the path/filename is not correct and therefore it is not found at boot time. According to https://www.kernel.org/doc/Documentation/x86/early-microcode.txt the name should be kernel/x86/microcode/AuthenticAMD.bin and this is also the path which appears in /usr/src/linux/arch/x86/kernel/microcode_amd_early.c Besides it seems that the ucode file should be in a separate cpio prepended to the standard initrd, see comment #11 which shows an example of successful early update with AMD CPU. But please also mind comment #18 and related bnc#852007 where successful creation of an initrd including the ucode update almost resulted in an unbootable system - luckily I had a backup initrd. BTW: is there a kernel parameter which inhibits early microcode update which can be used to boot the system in case the early update makes the system unbootable and all available initrds contain the microcode? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.