https://bugzilla.suse.com/show_bug.cgi?id=1217083 https://bugzilla.suse.com/show_bug.cgi?id=1217083#c3 --- Comment #3 from Roeland Jansen --- it's all intel -- so I would think it's not used at all. I taboo'd the package and a restart was ok there. Directly all back. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1217083 https://bugzilla.suse.com/show_bug.cgi?id=1217083#c6 --- Comment #6 from Roeland Jansen --- both on the laptop upstairs and on the vm it was definitely the case. what I did was: laptop above (in the unbootable state): started rescue, mounted all on /mnt, including rbound /proc /sys and /dev; chrooted, removed the ucode-amd package only and it started. the vm I use at work, installed all the packages -- broken, snapshotted back and incrementally in junks and w/o ucode-amd it booted. In a different setting while updating a client 12.4 --> 15.5 offline, I had the same where even two out of four PVs were missing. The LVs found were / and /usr. (SLES) In the mean time (about a week), I believe packages have updated on our RMTs and then it started working. It's what I observed, not 100% conclusive. And just got word that a collegue of mine had the same issues, several lv's not seen. he's kicking the remote RMT to update and tries to re-update from a previous snapshot. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1217083 https://bugzilla.suse.com/show_bug.cgi?id=1217083#c8 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kernel-bugs@opensuse.org |dracut-maintainers@suse.de Flags| |needinfo? --- Comment #8 from Takashi Iwai --- Then it's not an issue of amd-ucode itself, but something screwed up with dracut (or the info fed to dracut). If it were a problem of CPU ucode, you won't reach at that point at all. Tossed to dracut maintainers. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1217083 https://bugzilla.suse.com/show_bug.cgi?id=1217083#c10 --- Comment #10 from Roeland Jansen --- if I literally throw away that package, it boots. And what I just got from my collgue: all packages installed, vmware and model name : Intel(R) Xeon(R) Gold 6338N CPU @ 2.20GHz as CPU seen on the VM's, he installed 15.5 (SLES) --> missing lv's and pv's he just removed ucode-intel and it boots.... regarding the question about the output of `dracut -f --debug test.img`? I then need to forcefully f* up one instance. Not sure if we can do. At work, these vm's ertainly cannot be f* up. The images are not unified ones, specifically built on all the respective images. I even have see a VM where both ucode-intel AND ucode-amd were installed as rpm's. The plot thickens. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1217083 https://bugzilla.suse.com/show_bug.cgi?id=1217083#c12 --- Comment #12 from Roeland Jansen --- collegue of mine and I will be at the office and will try and see if we can replay it with a new vm and talked to my collegue and we will try to reproduce a new vm with this issue and send the test.img will also read the story above and act on it. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1217083 https://bugzilla.suse.com/show_bug.cgi?id=1217083#c14 --- Comment #14 from Roeland Jansen --- we're going to redo the test. my collegue mentioned that when the boot started to fail, he had also seen an UEFI entry in grub, like what I mentioned as well in one of the first times I wrote this report. And his environment also legacy boot. We'll update you later today I hope -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1217083 https://bugzilla.suse.com/show_bug.cgi?id=1217083#c16 --- Comment #16 from Roeland Jansen --- Created attachment 870934 --> https://bugzilla.suse.com/attachment.cgi?id=870934&action=edit dracut debug log of a failed system -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1217083 https://bugzilla.suse.com/show_bug.cgi?id=1217083#c18 --- Comment #18 from Roeland Jansen --- and as an add bonus: the boot log w/o ucode above as said boots. After this we installed ucode-intel ; it fired off dracut and it fails to boot afterwards. It stalls at rechaedtargetbasic system after that, dracut initqueue complains that timeouts happen while not being able to find all LVs. Don't think that the ucode itse;f is the issue but something that triggers dracut to create a failed initrd? -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1217083 https://bugzilla.suse.com/show_bug.cgi?id=1217083#c26 --- Comment #26 from Antonio Feijoo --- (In reply to Roeland Jansen from comment #25)

well....

The problem is that it's at home and work a TW issue (3 or 4 systems) AND it also is a same issue on SLES (*) (at work)

100% same issue, same problem, no PVs found after update. We do know the work-around" - on all the systems, removing ucode* upfront.

(*) I could just skip it and let it go like "if someone else has this issue, I don't care" but to me that's not helping.

Two different teams looking at it to me doesn't seem to me effective use of resources?

SLE is a commercial product, therefore all its incidents must be handled through the SUSE Customer Center (https://scc.suse.com/). That does not mean different teams, but different processes. Thank you for your understanding and I hope this does not cause you any inconvenience. Other than that, I suspect (it's the only thing I can do with the info I have) that you are experiencing at least 2 different issues: - 1 : Tumbleweed update from 23031107 to 20231108 on two laptops with Intel CPU => problem with ucode-amd (comment #0, comment #3) - 2 : SLES 15.5, update? laptop or vm? with Intel CPU => problem with ucode-intel (comment #10) Both Tumbleweed and SLE have different kernel, dracut, firmware versions... Tumbleweed is a rolling release, so it's very unlikely that an issue with a TW update is related to an issue in SLE. BTW, AFAIK microcode only affects physical CPUs, the vm guests do not have microcode of it's own, so it's even more strange that a ucode package is breaking a vm. And, as Takashi said in comment #8, a problem with a microcode should not allow the system to get this far in the boot process. So, it'd great if you can provide the Tumbleweed logs requested in comment #11 (`dracut -f --debug test.img 2>&1 &> dracut.log`), and the file /run/initramfs/rdsosreport.txt after trying to boot with the generated initramfs test.img, passing also `rd.debug` to the kernel command line. Thanks! -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1217083 https://bugzilla.suse.com/show_bug.cgi?id=1217083#c19 --- Comment #19 from Antonio Feijoo ---

//etc/os-release@4(source): PRETTY_NAME='SUSE Linux Enterprise Server 15 SP5'

The logs you are providing are from SLE, so please provide the Tumbleweed logs. If this is only about a SLE bug, you should open a L3 incident, so it can be addressed correctly. Thank you. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1217083 Antonio Feijoo changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo? | -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1217083 Antonio Feijoo changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(tiwai@suse.com) -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1217083 https://bugzilla.suse.com/show_bug.cgi?id=1217083#c31 --- Comment #31 from Maintenance Automation --- SUSE-RU-2024:1081-1: An update that has four fixes can now be installed. Category: recommended (important) Bug References: 1217083, 1219841, 1220485, 1221675 Maintenance Incident: [SUSE:Maintenance:33012](https://smelt.suse.de/incident/33012/) Sources used: Basesystem Module 15-SP5 (src): dracut-055+suse.382.g80b55af2-150500.3.18.1 openSUSE Leap 15.5 (src): dracut-055+suse.382.g80b55af2-150500.3.18.1 SUSE Linux Enterprise Micro 5.5 (src): dracut-055+suse.382.g80b55af2-150500.3.18.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.