https://bugzilla.suse.com/show_bug.cgi?id=1197192 https://bugzilla.suse.com/show_bug.cgi?id=1197192#c18 --- Comment #18 from Thomas Blume <thomas.blume@suse.com> --- (In reply to Antonio Feijoo from comment #17)

Created attachment 857649 [details] Resume sanity check patch

Let's try to unlock this situation. After checking that this cannot be solved via systemd, I think we have two options to fix this via dracut:

1. Create a custom SUSE patch (see attachment), so dracut will not add the resume module if there is an incorrect resume command line parameter. We have to assume that this would not be accepted upstream with a 99% probability. Test package: https://build.opensuse.org/package/show/home:afeijoo:branches:openSUSE: Factory:bsc1197192/dracut

2. Revert https://github.com/openSUSE/dracut/commit/fe239c23 and reopen bug 1192506 forever, assuming that any possible solution would break existing autoyast profiles with wrong resume parameters. Provide https://www.suse.com/en-en/support/kb/doc/?id=000020287 every time someone complains about hibernation not working after a fresh installation.

Any thoughts on this?

The sanity check looks ok. Still, we should point out that this can fail with autoyast profiles providing an resume parameter. It would only work if the resume parameter on the machine, where the profile is created, is identical to the local resume device. -- You are receiving this mail because: You are on the CC list for the bug.