Bug 1592788 - Fedora workstation 27 does not resume from hibernate [NEEDINFO]
Summary: Fedora workstation 27 does not resume from hibernate
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 27
Hardware: i686
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-06-19 10:11 UTC by asrivaths
Modified: 2018-08-29 15:07 UTC (History)
16 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-08-29 15:07:38 UTC
Type: Bug
Embargoed:
jforbes: needinfo?


Attachments (Terms of Use)
journal log after reboot (295.97 KB, text/x-vhdl)
2018-06-19 10:11 UTC, asrivaths
no flags Details

Description asrivaths 2018-06-19 10:11:12 UTC
Created attachment 1452871 [details]
journal log after reboot

Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.Hibernate from xfce 'logout...' button.
2.Power on pc.

Actual results:
Hibernate does not resume with an error did not find image.

Expected results:
Should resume correctly.

Additional info:
I changed the kernel command line to resume from swap partition.

Here's my /etc/default/grub:
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
GRUB_DEFAULT=saved
GRUB_DISABLE_SUBMENU=true
GRUB_TERMINAL_OUTPUT="console"
GRUB_CMDLINE_LINUX="rd.lvm.lv=fedora/root rd.lvm.lv=fedora/00 rhgb quiet resume=/dev/mapper/fedora-00"

GRUB_DISABLE_RECOVERY="true"
[root@localhost asrivaths]# swapon -s
Filename                                Type            Size    Used    Priority
/dev/dm-1                               partition       4194300 0       -2

and I set log level of systemd to debug by sending it a RTMIN+22:
kill -s 56 1
got 56 by adding 22 to RTMIN from 'kill -l'

I then hibernated the system and rebooted and added systemd log level kernel command line param:
systemd.log_level=debug

The system did not boot properly for some reason and just hung.  It also seems to have messed up the clock (it was ahead by exactly 5:30 hours which is how much my timezone is ahead of GMT).  I booted it again without log level set to debug and it booted but could not find swap image in /dev/mapper/fedora-00.
The journal log before hibernate is appended below and the attachment shows journal log after reboot (this shows the change in clock time).  This also shows the final shutdown where it can be seen that the swap partition name is correct:
Jun 18 19:53:49 localhost.localdomain systemd[1]: Deactivated swap /dev/disk/by-id/dm-name-fedora-00.
Jun 18 19:53:49 localhost.localdomain systemd[1]: Deactivated swap /dev/dm-1.
Jun 18 19:53:49 localhost.localdomain systemd[1]: Deactivated swap /dev/mapper/fedora-00.

journal log before hibernate:
===============================================================================
Jun 18 15:53:09 localhost.localdomain systemd[1]: Received SIGRTMIN+22 from PID 
1870 (bash).
Jun 18 15:53:09 localhost.localdomain systemd[1]: Setting log level to debug.
Jun 18 15:53:34 localhost.localdomain systemd[1]: systemd-udevd.service: Got notification message from PID 572 (WATCHDOG=1)
Jun 18 15:54:34 localhost.localdomain systemd[1]: systemd-journald.service: Got notification message from PID 542 (WATCHDOG=1)
Jun 18 15:54:34 localhost.localdomain systemd[1]: systemd-logind.service: Got notification message from PID 805 (WATCHDOG=1)
Jun 18 15:55:34 localhost.localdomain systemd[1]: systemd-journald.service: Got notification message from PID 542 (WATCHDOG=1)
Jun 18 15:55:34 localhost.localdomain systemd[1]: systemd-udevd.service: Got notification message from PID 572 (WATCHDOG=1)
Jun 18 15:55:36 localhost.localdomain smartd[722]: Device: /dev/sdb [SAT], 1 Currently unreadable (pending) sectors
Jun 18 15:55:36 localhost.localdomain smartd[722]: Device: /dev/sdb [SAT], 1 Offline uncorrectable sectors
Jun 18 15:55:43 localhost.localdomain systemd[1]: systemd-logind.service: Got notification message from PID 805 (WATCHDOG=1)
Jun 18 15:55:43 localhost.localdomain NetworkManager[815]: <info>  [1529317543.2559] manager: sleep requested (sleeping: no  enabled: yes)
Jun 18 15:55:43 localhost.localdomain NetworkManager[815]: <info>  [1529317543.2713] manager: sleeping...
Jun 18 15:55:43 localhost.localdomain NetworkManager[815]: <info>  [1529317543.3217] manager: NetworkManager state is now ASLEEP
Jun 18 15:55:43 localhost.localdomain systemd[1]: SELinux access check scon=system_u:system_r:systemd_logind_t:s0 tcon=system_u:object_r:power_unit_file_t:s0 tclass=service perm=start path=/usr/lib/systemd/system/hibernate.target cmdline=/usr/lib/systemd/systemd-logind: 0
Jun 18 15:55:44 localhost.localdomain systemd[1]: SELinux access check scon=system_u:system_r:systemd_logind_t:s0 tcon=system_u:object_r:power_unit_file_t:s0 tclass=service perm=start path=/usr/lib/systemd/system/hibernate.target cmdline=/usr/lib/systemd/systemd-logind: 0
Jun 18 15:55:44 localhost.localdomain systemd[1]: hibernate.target: Trying to enqueue job hibernate.target/start/replace-irreversibly
Jun 18 15:55:44 localhost.localdomain systemd[1]: sleep.target: Installed new job sleep.target/start as 1969
Jun 18 15:55:44 localhost.localdomain systemd[1]: hibernate.target: Installed new job hibernate.target/start as 1967
Jun 18 15:55:44 localhost.localdomain systemd[1]: systemd-hibernate.service: Installed new job systemd-hibernate.service/start as 1968
Jun 18 15:55:44 localhost.localdomain systemd[1]: hibernate.target: Enqueued job hibernate.target/start as 1967
Jun 18 15:55:44 localhost.localdomain systemd[1]: sleep.target changed dead -> active
Jun 18 15:55:44 localhost.localdomain systemd[1]: sleep.target: Job sleep.target/start finished, result=done
Jun 18 15:55:44 localhost.localdomain systemd[1]: Reached target Sleep.
Jun 18 15:55:44 localhost.localdomain systemd[1]: systemd-hibernate.service: Passing 0 fds to service
Jun 18 15:55:44 localhost.localdomain systemd[1]: systemd-hibernate.service: About to execute: /usr/lib/systemd/systemd-sleep hibernate
Jun 18 15:55:44 localhost.localdomain systemd[1]: systemd-hibernate.service: Forked /usr/lib/systemd/systemd-sleep as 7863
Jun 18 15:55:44 localhost.localdomain systemd[1]: systemd-hibernate.service: Changed dead -> start
Jun 18 15:55:44 localhost.localdomain systemd[1]: Starting Hibernate...
Jun 18 15:55:44 localhost.localdomain systemd[7863]: systemd-hibernate.service: Executing: /usr/lib/systemd/systemd-sleep hibernate
Jun 18 15:55:44 localhost.localdomain systemd[1]: systemd-journald.service: Got notification message from PID 542 (FDSTORE=1)
Jun 18 15:55:44 localhost.localdomain systemd[1]: systemd-journald.service: Added fd 86 (n/a) to fd store.
Jun 18 15:55:44 localhost.localdomain kernel: PM: hibernation entry
Jun 18 15:55:44 localhost.localdomain kernel: PM: Syncing filesystems ...
Jun 18 15:55:44 localhost.localdomain systemd-sleep[7863]: Suspending system...
===============================================================================
[

Comment 1 Justin M. Forbes 2018-07-23 15:12:29 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 27 kernel bugs.

Fedora 27 has now been rebased to 4.17.7-100.fc27.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 28, and are still experiencing this issue, please change the version to Fedora 28.

If you experience different issues, please open a new bug report for those.

Comment 2 Justin M. Forbes 2018-08-29 15:07:38 UTC
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 5 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.


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