http://bugzilla.opensuse.org/show_bug.cgi?id=960392 Bug ID: 960392 Summary: leap do not start, resume uuid problem, workaround available Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-maintainers@forge.provo.novell.com Reporter: jdd@dodin.org QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- I already had this problem after testing hibernation on my desktop computer. (http://lists.opensuse.org/opensuse/2015-12/msg00550.html) but now it occurs without hibernation (at least no voluntary hibernation), but looks very similar. It seems very similar of the bug 944659. I have a work around. As in bug 944659, the computer do not start. Very soon after loading the kernel, the keyboard activates, the display also, the monitor receives signal but display a black screen. Only way to recover is switching off the computer. The "crash" seems to be related to a bad resume uuid in the kernel option line. Removing this "resume=..." option allow normal boot and subsequent boot is ok. journalctrl do not show any log for the faulty boot (was expected, crash too early). This situation is probably due to the following: I have three disks in the computer, with many Linux/windows installs - mostly openSUSE. I have one swap partition on each disk. The "resume" option of the kernel pointed to a wrong swap partition. All this is proved but the reason not clear in my mind. Wrong in the sense it didn't point to the new ssd swap partition, but to one of the old HDD. This leap install is around a week old. I made it on a new ssd plugged on a e-sata dock, used it full for openSUSE Leap. As I created a swap partition on this disk I though that this one was used and didn't take attention at this part of the yast report (may be I should have done). When I had the bug for the first time, as reported on the mailing list, I found three swap lines in the fstab file. I commented away the two not related to the new ssd and the incorrect one for the ssd and added again the ssd swap partition with YaST. This obviously didn't corrected the resume line in the grub kernel options. That said, I didn't touche the other disks during this period, but there was clearly a conflict between fstab and the kernel options. Right now I removed this grub kernel option with YaST - I do not need hibernation on this desktop computer. I fear I'm not that clear, feel free to ask for infos thanks jdd -- You are receiving this mail because: You are on the CC list for the bug.