Bug 1798816 - System does not resume after hibernation, instead starts fresh boot
Summary: System does not resume after hibernation, instead starts fresh boot
Keywords:
Status: CLOSED DUPLICATE of bug 1795422
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 33
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-06 04:56 UTC by David Ross
Modified: 2021-04-13 09:01 UTC (History)
18 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2021-04-13 09:01:59 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Kernel journalctl output from boot after attempted hibernation (97.83 KB, text/plain)
2020-02-06 04:56 UTC, David Ross
no flags Details
Kernel journalctl output from boot which terminates in attempted hibernation (97.95 KB, text/plain)
2020-02-06 04:57 UTC, David Ross
no flags Details
My /etc/fstab - unmodified from Fedora installation (608 bytes, text/plain)
2020-02-06 04:58 UTC, David Ross
no flags Details
Fedora 33 kernel log rebooting after hibernate (91.09 KB, text/plain)
2020-11-05 11:39 UTC, David Ross
no flags Details
Fedora 33 kernel log including attempted hibernation (91.09 KB, text/plain)
2020-11-05 11:40 UTC, David Ross
no flags Details

Description David Ross 2020-02-06 04:56:29 UTC
Created attachment 1658081 [details]
Kernel journalctl output from boot after attempted hibernation

1. Please describe the problem:

The system hibernates successfully. However, on the following boot, it's as if there was no hibernation image - the system boots fresh.

This is on a few weeks old Fedora 31 install.

I've looked at other bugs with the symptoms, but I'm unsure how to identify which one my system is experiencing. Notably, I have a correct resume paramater in /etc/default/grub:

GRUB_CMDLINE_LINUX="resume=UUID=61bedd90-037c-4dd6-a147-dfc9ba36f92b rhgb quiet"

61bedd... is indeed the UUID of my swap partition.

2. What is the Version-Release number of the kernel:

Linux thinkfedora 5.4.15-200.fc31.x86_64 #1 SMP Tue Jan 28 09:08:32 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :

This is my first Fedora install. No previous kernels tested.

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:

Run "systemctl hibernate" to hibernate the system. Press the power button restart system.

5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:

Yes - same issue on the rawhide kernel.

6. Are you running any modules that not shipped with directly Fedora's kernel?:

I've installed ecryptfs-utils, but nothing else related to the kernel.

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.

Comment 1 David Ross 2020-02-06 04:57:32 UTC
Created attachment 1658083 [details]
Kernel journalctl output from boot which terminates in attempted hibernation

Comment 2 David Ross 2020-02-06 04:58:31 UTC
Created attachment 1658084 [details]
My /etc/fstab - unmodified from Fedora installation

Comment 3 Ben Cotton 2020-11-03 16:18:35 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '31'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 31 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 David Ross 2020-11-05 11:39:37 UTC
Created attachment 1726844 [details]
Fedora 33 kernel log rebooting after hibernate

Comment 5 David Ross 2020-11-05 11:40:24 UTC
Created attachment 1726845 [details]
Fedora 33 kernel log including attempted hibernation

Comment 6 David Ross 2020-11-05 11:41:50 UTC
This still occurs on Fedora 33, on the same system. Same symptoms.

I've not tried Rawhide kernels within the last few months, and it doesn't really seem worth it given that this bug hasn't changed at all otherwise over the past year.

Comment 7 David Tardon 2021-04-13 09:01:59 UTC

*** This bug has been marked as a duplicate of bug 1795422 ***


Note You need to log in before you can comment on or make changes to this bug.