[Bug 913996] Applying Critical Updates Causes System to no longer boot (ucode-intel / ucode-amd problem?)
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.suse.com/show_bug.cgi?id=913996
--- Comment #82 from Peter Kirchgeßner
So basically 13.2 has never applied microcode successfully on that box, correct? Not even the installer kernel works.
If "never applied microcode successfully" means applying microcode *and* the kernel works afterwards, you are right. Up to now it seems to me that applying the microcode implies hangup of the kernel. Following your instructions, I did this: Installed package ucode-amd. Copied /lib/firmware/amd-ucode (containing 4 files) to a different name. Uninstalled package ucode-amd. Run mkinitrd and saw the messages *** Generating early-microcode cpio image *** *** Constructing AuthenticAMD.bin **** Because you wrote this should not be printed,I renamed the remaining /lib/firmware/amd-ucode (containing two files) to a different name. Run mkinitrd. This showed only *** Generating early-microcode cpio image *** dis_ucode_ldr is not on the kernel parameters. So I rebooted. Kernel 3.16.7-21-desktop bootet properly. Restored the amd-ucode-directory that kept the 4 files. Did as root echo 1 > /sys/devices/system/cpu/microcode/reload The kernel still works. The following has been added to dmesg: [ 182.862248] microcode: CPU0: new patch_level=0x010000c7 [ 182.862288] microcode: CPU1: new patch_level=0x010000c7 Earlier in the log file you can find [ 1.323063] microcode: CPU0: patch_level=0x0100009f [ 1.323160] microcode: CPU1: patch_level=0x0100009f The complete dmesg is attached as dmesg.after. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com