[Bug 1160204] New: Failure to boot with latest version of ucode-amd
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1160204 Bug ID: 1160204 Summary: Failure to boot with latest version of ucode-amd Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Critical Priority: P5 - None Component: Other Assignee: bnc-team-screening@forge.provo.novell.com Reporter: microfocus@wdqb.uk QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0 Build Identifier: If the current Tumbleweed version of ucode-amd is installed (20191118-1.1) then the machine resets just after GRUB as the kernel is being loaded. If ucode-amd is downgraded to the version in Leap 15.1 (20190618-lp151.2.6.1) the machine boots successfully. Reproducible: Always Steps to Reproduce: 1. Create a live USB image of Tumbleweed (tested 20191228) 2. Boot from this USB stick 3. Hit ENTER on the default selection in GRUB, or wait for it to time-out Actual Results: Grub prints "Loading initial ramdisk", then the machine immediately resets. Expected Results: Grub prints "Loading initial ramdisk", then the boot sequence proceeds. The machine has dual AMD EPYC 7282 16-core processors and a Supermicro H11DSi-NT motherboard. The failure seems to occur before the kernel is loaded, so loglevel parameters do not result in any useful data being printed before the reset. The problem can be reproduced either with a live USB stick or with a fresh install of Tumbleweed with default settings. Deselecting "ucode-amd" in the installer resolves the issue. Installing "ucode-amd" from the Leap 15.1 update repository also results in a functional system. It is just the version of "ucode-amd" in Tumbleweed (and Leap 15.2) that appears to be the issue. -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1160204
http://bugzilla.opensuse.org/show_bug.cgi?id=1160204#c3
--- Comment #3 from Will Bainbridge
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1160204
http://bugzilla.opensuse.org/show_bug.cgi?id=1160204#c4
--- Comment #4 from Will Bainbridge
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1160204
http://bugzilla.opensuse.org/show_bug.cgi?id=1160204#c5
Will Bainbridge
See if the newest release fixes your issue:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/ tree/amd-ucode/microcode_amd_fam17h.bin
I can confirm that copying this file to /lib/firmware/amd-ucode/microcode_amd_fam17h.bin, running mkinitrd, and rebooting resolves the issue. Many thanks. I guess I now just need to wait until this update becomes part of the main Tumbleweed release. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com