https://bugzilla.suse.com/show_bug.cgi?id=1215826 https://bugzilla.suse.com/show_bug.cgi?id=1215826#c2 --- Comment #2 from Tristan Miller <psychonaut@nothingisreal.com> --- (In reply to Felix Miata from comment #1)

Something to try: Remove resume=/dev/sda2 from /etc/default/grub and /boot/grub2/grub.cfg entirely, or replacing it with resume=UUID=<swapUUID> or resume=LABEL=<swapLABEL> (using the actual UUID or LABEL from lsblk -f or blkid). To test whether this is the right track, strike the E key at the Grub menu and change resume=/dev/sda2 to noresume before proceeding with boot. Noresume means what it spells, but it should boot straight away if I'm right.

Yes, using noresume or resume=UUID=<swapUUID> seems to solve the problem. I noticed when looking up the UUID of the swap device that it was always /dev/sdb2 when booting from the 6.4.12 kernel, whereas when booting from the 6.5.4 kernel it was sometimes /dev/sda2 and sometimes /dev/sdb2. So I think the real problem here is that the 6.5.4 kernel doesn't assign device names in the same consistent manner than 6.4.12 did, so you can't rely on these names in the bootloader. I think that nowadays a fresh install of Tumbleweed will always use the device's UUID, but my system was first installed back in 2014 and so was still using the old /dev/sdXY-style identifiers. -- You are receiving this mail because: You are on the CC list for the bug.