Hide Forgot
Description of problem: After recent upgrade from kernel-4.3.3-300.fc23.x86_64 to kernel-4.4.2-301.fc23.x86_64 hibernation to disk stopped working. Version-Release number of selected component (if applicable): kernel-4.4.2-301.fc23.x86_64 How reproducible: Open "Shutdown the computer" panel add-on and click the "Hibernate" button. Actual results: The notebook attempts to hibernate but at some point just hangs while still showing the Xorg screen, the mouse/keyboard is unresopnsive. It requires a hard power down (by holding down the power button). Expected results: Hibernation. Additional info: Hibernation worked properly before the update to kernel-4.4.2-301.fc23.x86_64, the notebook is an Acer Aspire 8920G. From what I can tell, the log does not show any errors: Mar 02 00:46:08 469.lan NetworkManager[1623]: <info> sleep requested (sleeping: no enabled: yes) Mar 02 00:46:08 469.lan kernel: IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready Mar 02 00:46:08 469.lan NetworkManager[1623]: <info> sleeping... Mar 02 00:46:08 469.lan NetworkManager[1623]: <info> (wlp4s0): device state change: unavailable -> unmanaged (reason 'sleeping') [20 10 37] Mar 02 00:46:08 469.lan NetworkManager[1623]: <info> (enp2s0): device state change: activated -> unmanaged (reason 'sleeping') [100 10 37] Mar 02 00:46:08 469.lan NetworkManager[1623]: <info> (enp2s0): canceled DHCP transaction, DHCP client pid 25801 Mar 02 00:46:08 469.lan NetworkManager[1623]: <info> (enp2s0): DHCPv4 state changed bound -> done Mar 02 00:46:08 469.lan avahi-daemon[1464]: Withdrawing address record for fe80::2a0:d1ff:fea5:3f43 on enp2s0. Mar 02 00:46:08 469.lan avahi-daemon[1464]: Withdrawing address record for 192.168.2.60 on enp2s0. Mar 02 00:46:08 469.lan avahi-daemon[1464]: Leaving mDNS multicast group on interface enp2s0.IPv4 with address 192.168.2.60. Mar 02 00:46:08 469.lan avahi-daemon[1464]: Interface enp2s0.IPv4 no longer relevant for mDNS. Mar 02 00:46:08 469.lan NetworkManager[1623]: <info> NetworkManager state is now ASLEEP Mar 02 00:46:08 469.lan org.gtk.vfs.Daemon[1923]: ** (process:23176): WARNING **: Couldn't create directory monitor on smb://x-gnome-default-workgroup/. Error: The specified location Mar 02 00:46:08 469.lan audit: NETFILTER_CFG table=nat family=2 entries=52 Mar 02 00:46:08 469.lan audit[26707]: SYSCALL arch=c000003e syscall=54 success=yes exit=0 a0=3 a1=0 a2=40 a3=563b627562b0 items=0 ppid=1460 pid=26707 auid=4294967295 uid=0 gid=0 euid Mar 02 00:46:08 469.lan audit: PROCTITLE proctitle=2F7573722F7362696E2F69707461626C65732D726573746F7265002D6E Mar 02 00:46:08 469.lan audit: NETFILTER_CFG table=mangle family=2 entries=40 Mar 02 00:46:08 469.lan audit[26707]: SYSCALL arch=c000003e syscall=54 success=yes exit=0 a0=3 a1=0 a2=40 a3=563b627562b0 items=0 ppid=1460 pid=26707 auid=4294967295 uid=0 gid=0 euid Mar 02 00:46:08 469.lan audit: PROCTITLE proctitle=2F7573722F7362696E2F69707461626C65732D726573746F7265002D6E Mar 02 00:46:08 469.lan audit: NETFILTER_CFG table=filter family=2 entries=85 Mar 02 00:46:08 469.lan audit[26707]: SYSCALL arch=c000003e syscall=54 success=yes exit=0 a0=3 a1=0 a2=40 a3=563b62759f60 items=0 ppid=1460 pid=26707 auid=4294967295 uid=0 gid=0 euid Mar 02 00:46:08 469.lan audit: PROCTITLE proctitle=2F7573722F7362696E2F69707461626C65732D726573746F7265002D6E Mar 02 00:46:08 469.lan audit: NETFILTER_CFG table=nat family=10 entries=52 Mar 02 00:46:08 469.lan audit[26708]: SYSCALL arch=c000003e syscall=54 success=yes exit=0 a0=3 a1=29 a2=40 a3=5556ecf41250 items=0 ppid=1460 pid=26708 auid=4294967295 uid=0 gid=0 eui Mar 02 00:46:08 469.lan audit: PROCTITLE proctitle=2F7573722F7362696E2F6970367461626C65732D726573746F7265002D6E Mar 02 00:46:08 469.lan audit: NETFILTER_CFG table=mangle family=10 entries=40 Mar 02 00:46:08 469.lan audit[26708]: SYSCALL arch=c000003e syscall=54 success=yes exit=0 a0=3 a1=29 a2=40 a3=5556ecf41250 items=0 ppid=1460 pid=26708 auid=4294967295 uid=0 gid=0 eui Mar 02 00:46:08 469.lan audit: PROCTITLE proctitle=2F7573722F7362696E2F6970367461626C65732D726573746F7265002D6E Mar 02 00:46:08 469.lan audit: NETFILTER_CFG table=filter family=10 entries=86 Mar 02 00:46:08 469.lan audit[26708]: SYSCALL arch=c000003e syscall=54 success=yes exit=0 a0=3 a1=29 a2=40 a3=5556ecf46360 items=0 ppid=1460 pid=26708 auid=4294967295 uid=0 gid=0 eui Mar 02 00:46:08 469.lan audit: PROCTITLE proctitle=2F7573722F7362696E2F6970367461626C65732D726573746F7265002D6E Mar 02 00:46:08 469.lan dbus[1408]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' Mar 02 00:46:08 469.lan NetworkManager[1623]: <info> (enp2s0): link disconnected Mar 02 00:46:08 469.lan systemd[1]: Reached target Sleep. Mar 02 00:46:08 469.lan systemd[1]: Starting Sleep. Mar 02 00:46:08 469.lan systemd[1]: Starting Hibernate... Mar 02 00:46:08 469.lan kernel: PM: Hibernation mode set to 'platform' Mar 02 00:46:08 469.lan systemd-sleep[26709]: Suspending system... Mar 02 00:46:08 469.lan systemd[1]: Starting Network Manager Script Dispatcher Service... Mar 02 00:46:08 469.lan dbus[1408]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Mar 02 00:46:08 469.lan systemd[1]: Started Network Manager Script Dispatcher Service. Mar 02 00:46:08 469.lan audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname= Mar 02 00:46:08 469.lan nm-dispatcher[26711]: Dispatching action 'down' for enp2s0
Same problem here, but with suspend, on a Lenovo ThinkPad T540p. Bug appeared on upgrade from kernel 4.3.5-300.fc23.x86_64 to kernel 4.4.2-301.fc23.x86_64.
Seeing the same for suspend on Thinkpad T430s, everything just freezes. Works if I boot the older 4.3.5-300.fc23.x86_64. Both when closing lid and systemctl suspend.
(In reply to gidi from comment #1) > Same problem here, but with suspend, on a Lenovo ThinkPad T540p. Bug > appeared on upgrade from kernel 4.3.5-300.fc23.x86_64 to kernel > 4.4.2-301.fc23.x86_64. Suspend bug resolved for me with new kernel 4.4.3-300.fc23.x86_64.
4.4.3-300.fc23.x86_64 resolved it for me as well.
It works partially for me, it does not hang anymore, but every other time resume will not really resume but boot normally, losing the hibernation status.
Yesterday I had a hangup again when hibernating, so I guess sometimes it works, sometimes it fails to resume from hibernation and sometimes it will just hang as with 4.4.2-301.fc23.x86_64 If I can provide any additional info to help solve this issue - please let me know.
Updated to 4.4.3-300.fc23.x86_64 and made an interesting observation (probably valid for the earlier version too): when doing "hibernate" it actually does not hang... it just takes ages! I let the notebook in this "hanged up" state for several minutes and at some point it finally hibernated. The problem was NOT present in kernel-4.3.3-300, there hibernation worked reliably without any delays.
So it's been a while and I am still suffering form this problem. However, recently after an update to 4.6.6-200.fc23.x86_64 my system hibernated with a success rate of 100% for about 1.5 weeks. Then I updated to 4.6.7-200.fc23.x86_64 and the problems reappeared. Sometimes it won't hibernate, sometimes it will freeze for several minutes to hibernate after that delay, and sometimes it will hibernate, but won't resume. Sometimes it works, but not that often. Is there anything I can do in order to help to figure this out? Any special logs, tests, whatever? What was the major difference in 4.6.6-200.fc23.x86_64?
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is 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 23 kernel bugs. Fedora 23 has now been rebased to 4.7.4-100.fc23. 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 24 or 25, and are still experiencing this issue, please change the version to Fedora 24 or 25. If you experience different issues, please open a new bug report for those.
I updated to Fedora 24, 4.7.4-200.fc24.x86_64, I have been watching the situation for a couple of days now and so far it seems better. At least when hibernation is initiated, it does not take >5min. However, I yesterday I experienced a situation where the notebook seemed to have hibernated successfully, but failed to resume and did a fresh boot instead. I will keep watching it, but imho it's too early to close this one as hibernation does not seem to work reliably.
Seems, that the problem is no longer present on Fedora 24 anymore. It does fail to resume from hibernation at times, but this would be a different bug.