https://bugzilla.suse.com/show_bug.cgi?id=1218005 https://bugzilla.suse.com/show_bug.cgi?id=1218005#c23 --- Comment #23 from Takashi Iwai <tiwai@suse.com> --- (In reply to Anders Stedtlund from comment #22)

- 5.14.21-150500.53 Boot OK! - 5.14.21-150500.55.7 Boot OK with pcie_aspm=off

Replace modules in 5.14.21-150500.55.7-default with modules from 5.14.21-150500.53-default. Boot OK!

That's an interesting result. Then I scratched a wrong surface. It might be that the previous test with module replacement didn't work properly. The next step would be to identify which module actually breaks. It'll be great help for understanding what's going wrong. You can copy back the new modules from the saved directory (*-55.7-default.old) to *-55.7-default directory again, piece-by-piece. e.g. let's begin with the main suspect, nvme driver modules: % rm -r /lib/modules/5.14.21-150500.55.7-default/kernel/drivers/nvme % cp -a /lib/modules/5.14.21-150500.55.7-default.old/kernel/drivers/nvme lib/modules/5.14.21-150500.55.7-default/kernel/drivers/ % depmod -a % dracut -f --kver 5.14.21-150500.55.7-default This will replace the all nvme modules back to the *-55.7 again. Retest with this. If this breaks the boot, it's one (or more) of nvme modules. You can try again by copying each *.ko.zst from *-53-default directory and narrow down the culprit. OTOH, if replacing nvme drivers don't break, it's something else. Try to replace each directory until you hit. -- You are receiving this mail because: You are the assignee for the bug.