Created attachment 788008 [details] Output of pm-utils-bugreport-info.sh Description of problem: hibernate does not work Version-Release number of selected component (if applicable): Fedora 19 with all updates How reproducible: systemctl hibernate or pm-hibernate Steps to Reproduce: 1.Terminal with KDE:"systemctl hibernate" or "pm-hibernate" 2. 3. Actual results: Display ist going to get black for 3 seconds, then hibernate was interrupted Errors (files as an attachment) Expected results: Laptop is going to sleep Additional info:
Created attachment 788009 [details] Output of journatctl -xn
hi hibernate is a java library you filled this bug to a wrong component please, find the right one regards
(In reply to gil cattaneo from comment #2) > hi > hibernate is a java library > you filled this bug to a wrong component > please, find the right one > regards No, I mean Hibernate Modus Andreas
(In reply to Andreas Reschke from comment #3) > (In reply to gil cattaneo from comment #2) > > hi > > hibernate is a java library > > you filled this bug to a wrong component > > please, find the right one > > regards > > No, I mean Hibernate Modus > Andreas More Information: [root@hp635 ~]# systemctl hibernate A dependency job for hibernate.target failed. See 'journalctl -xn' for details. [root@hp635 ~]# journalctl -xn -- Logs begin at Sa 2013-06-29 12:13:59 CEST, end at Mi 2013-08-21 12:48:44 CEST. -- Aug 21 12:48:44 hp635.reschke.lan kernel: ata2.00: configured for UDMA/100 Aug 21 12:48:44 hp635.reschke.lan kernel: PM: thaw of devices complete after 1638.111 msecs Aug 21 12:48:44 hp635.reschke.lan kernel: PM: writing image. Aug 21 12:48:44 hp635.reschke.lan kernel: PM: Cannot find swap device, try swapon -a. Aug 21 12:48:44 hp635.reschke.lan kernel: PM: Cannot get swap writer Aug 21 12:48:44 hp635.reschke.lan kernel: Restarting tasks ... done. Aug 21 12:48:44 hp635.reschke.lan kernel: PM: Basic memory bitmaps freed Aug 21 12:48:44 hp635.reschke.lan kernel: video LNXVIDEO:00: Restoring backlight state Aug 21 12:48:44 hp635.reschke.lan NetworkManager[747]: <info> (eno1): carrier now ON (device state 100) Aug 21 12:48:44 hp635.reschke.lan kernel: r8169 0000:06:00.0 eno1: link up [root@hp635 ~]# swapon -s Filename Type Size Used Priority /dev/dm-5 partition 9205756 0 -1 [root@hp635 ~]#
Hibernation is no longer handled by pm-utils but by systemd (i.e. the systemctl). But in this case it seems to be kernel where it fails, reassigning.
(In reply to Jaroslav Škarvada from comment #5) > Hibernation is no longer handled by pm-utils but by systemd (i.e. the > systemctl). But in this case it seems to be kernel where it fails, > reassigning. With the newest kernel (3.10.9-200.fc19.x86_64) same failure. Same on two different Laptops.
*********** 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 19 kernel bugs. Fedora 19 has now been rebased to 3.11.1-200.fc19. Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those.
(In reply to Josh Boyer from comment #7) > *********** 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 19 kernel bugs. > > Fedora 19 has now been rebased to 3.11.1-200.fc19. Please test this kernel > update and let us know if you issue has been resolved or if it is still > present with the newer kernel. > > If you experience different issues, please open a new bug report for those. Sorry for delay (Vacation) Next test with kernel 3.11.1-200.fc19 and Fedora up2date: screen goes black for 2-3 seconds and prompt returns [andreas@hp635 ~]$ su - Passwort: [root@hp635 ~]# systemctl hibernate A dependency job for hibernate.target failed. See 'journalctl -xn' for details. [root@hp635 ~]# journalctl -xn -- Logs begin at Sa 2013-06-29 12:13:59 CEST, end at Di 2013-09-24 08:02:43 CEST. -- Sep 24 08:02:43 hp635.reschke.lan kernel: ath9k 0000:07:00.0 wlo1: disabling VHT as WMM/QoS is not supported by the AP Sep 24 08:02:43 hp635.reschke.lan kernel: wlo1: associate with a0:f3:c1:27:7c:cf (try 1/3) Sep 24 08:02:43 hp635.reschke.lan NetworkManager[766]: <info> (wlo1): supplicant interface state: authenticating -> associating Sep 24 08:02:43 hp635.reschke.lan kernel: wlo1: associate with a0:f3:c1:27:7c:cf (try 2/3) Sep 24 08:02:43 hp635.reschke.lan kernel: wlo1: associate with a0:f3:c1:27:7c:cf (try 3/3) Sep 24 08:02:43 hp635.reschke.lan kernel: wlo1: RX AssocResp from a0:f3:c1:27:7c:cf (capab=0x411 status=0 aid=1) Sep 24 08:02:43 hp635.reschke.lan kernel: wlo1: associated Sep 24 08:02:43 hp635.reschke.lan NetworkManager[766]: <info> (wlo1): supplicant interface state: associating -> 4-way handshake Sep 24 08:02:43 hp635.reschke.lan NetworkManager[766]: <info> (wlo1): supplicant interface state: 4-way handshake -> completed Sep 24 08:02:43 hp635.reschke.lan NetworkManager[766]: <info> (wlo1): roamed from BSSID (none) ((none)) to A0:F3:C1:27:7C:CF (Tux-Network2) [root@hp635 ~]#
I have a similar or identical problem. I previously had fc18 x86 installed and fc17 before that on my acer laptop, and hibernate worked fine (clicked from the MATE desktop 'System->Shut down' menu option). After recent clean install of fc19 x86 the system crashes after I click 'Hibernate.' The screen goes black for a few seconds, then comes back on (without being responsive) then the system crashes a few seconds later. This happens every time I hibernate; sleep works fine. Kernel is 3.11.3-201.fc19.x86_64 For three such crashes, /var/log/messages says- Sep 26 10:39:15 localhost NetworkManager[986]: <info> sleep requested (sleeping: no enabled: yes) Sep 26 10:39:15 localhost NetworkManager[986]: <info> sleeping or disabling... Sep 26 10:39:15 localhost NetworkManager[986]: <info> (wlp13s0): device state change: unavailable -> unmanaged (reason 'sleeping') [20 10 37] Sep 26 10:39:15 localhost NetworkManager[986]: <info> (p5p1): device state change: activated -> unmanaged (reason 'sleeping') [100 10 37] Sep 26 10:39:15 localhost NetworkManager[986]: <info> (p5p1): deactivating device (reason 'sleeping') [37] Sep 26 10:39:15 localhost NetworkManager[986]: <info> (p5p1): canceled DHCP transaction, DHCP client pid 6234 Sep 26 10:39:16 localhost NetworkManager[986]: <info> (p5p1): cleaning up... Sep 26 10:39:16 localhost NetworkManager[986]: <info> (p5p1): taking down device. Sep 26 10:39:16 localhost dbus-daemon[933]: dbus[933]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.s$ Sep 26 10:39:16 localhost dbus-daemon[933]: dbus[933]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.nm-dispatcher.service': Unit dbus-org.freedesktop.$ Sep 26 10:39:16 localhost dbus[933]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' Sep 26 10:39:16 localhost dbus[933]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.nm-dispatcher.service': Unit dbus-org.freedesktop.nm-dispatcher.serv$ Sep 26 10:39:16 localhost NetworkManager[986]: <warn> Dispatcher failed: (32) Unit dbus-org.freedesktop.nm-dispatcher.service failed to load: No such file or directory. See sy$ Sep 26 12:14:30 localhost rsyslogd: [origin software="rsyslogd" swVersion="7.2.6" x-pid="934" x-info="http://www.rsyslog.com"] start Oct 3 14:13:56 localhost udisksd[2022]: Cleaning up LUKS device /dev/dm-7 (backing device 8:17 no longer exist) Oct 3 14:14:26 localhost NetworkManager[953]: <info> sleep requested (sleeping: no enabled: yes) Oct 3 14:14:26 localhost NetworkManager[953]: <info> sleeping or disabling... Oct 3 14:14:26 localhost NetworkManager[953]: <info> (wlp13s0): device state change: unavailable -> unmanaged (reason 'sleeping') [20 10 37] Oct 3 14:14:26 localhost NetworkManager[953]: <info> (p5p1): device state change: activated -> unmanaged (reason 'sleeping') [100 10 37] Oct 3 14:14:26 localhost NetworkManager[953]: <info> (p5p1): deactivating device (reason 'sleeping') [37] Oct 3 14:14:26 localhost NetworkManager[953]: <info> (p5p1): canceled DHCP transaction, DHCP client pid 6231 Oct 3 14:14:26 localhost NetworkManager[953]: <info> (p5p1): cleaning up... Oct 3 14:14:26 localhost NetworkManager[953]: <info> (p5p1): taking down device. ^@^@^@^@^@^@^@^@^@^@^@^@^@Oct 3 15:11:20 localhost rsyslogd: [origin software="rsyslogd" swVersion="7.2.6" x-pid="926" x-info="http://www.rsyslog.com"] start Oct 8 07:57:51 localhost NetworkManager[963]: <info> Activation (p5p1) Stage 4 of 5 (IPv6 Configure Timeout) complete. Oct 8 07:58:00 localhost systemd[1]: Starting Stop Read-Ahead Data Collection... Oct 8 07:58:01 localhost systemd[1]: Started Stop Read-Ahead Data Collection. Oct 8 07:58:01 localhost fprintd[1772]: ** Message: No devices in use, exit Oct 8 07:58:07 localhost systemd-logind[906]: Removed session c1. Oct 8 07:58:08 localhost NetworkManager[963]: <info> disable requested (sleeping: no enabled: yes) Oct 8 07:58:08 localhost NetworkManager[963]: <info> sleeping or disabling... Oct 8 07:58:08 localhost NetworkManager[963]: <info> (wlp13s0): device state change: unavailable -> unmanaged (reason 'sleeping') [20 10 37] Oct 8 07:58:08 localhost NetworkManager[963]: <info> (p5p1): device state change: activated -> unmanaged (reason 'sleeping') [100 10 37] Oct 8 07:58:08 localhost NetworkManager[963]: <info> (p5p1): deactivating device (reason 'sleeping') [37] Oct 8 07:58:08 localhost NetworkManager[963]: <info> (p5p1): canceled DHCP transaction, DHCP client pid 1677 Oct 8 07:58:08 localhost NetworkManager[963]: <info> (p5p1): cleaning up... Oct 8 07:58:08 localhost NetworkManager[963]: <info> (p5p1): taking down device. Oct 8 07:58:08 localhost dbus-daemon[917]: dbus[917]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.s$ Oct 8 07:58:08 localhost dbus[917]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' Oct 8 07:58:08 localhost systemd[1]: Starting Network Manager Script Dispatcher Service... Oct 8 07:58:08 localhost dbus-daemon[917]: dbus[917]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Oct 8 07:58:08 localhost dbus[917]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Oct 8 07:58:08 localhost systemd[1]: Started Network Manager Script Dispatcher Service. Oct 8 07:58:09 localhost systemd[1]: Stopping Sendmail Mail Transport Client... Oct 8 07:58:09 localhost systemd[1]: Stopping Sendmail Mail Transport Agent... Oct 8 07:58:09 localhost systemd[1]: Starting Sendmail Mail Transport Agent... Oct 8 07:58:09 localhost systemd[1]: PID file /run/sendmail.pid not readable (yet?) after start. Oct 8 07:58:09 localhost systemd[1]: Started Sendmail Mail Transport Agent. Oct 8 07:58:09 localhost systemd[1]: Starting Sendmail Mail Transport Client... Oct 8 07:58:09 localhost systemd[1]: Started Sendmail Mail Transport Client. Oct 8 07:58:16 localhost NetworkManager[963]: <info> sleep requested (sleeping: no enabled: no) Oct 8 07:58:16 localhost NetworkManager[963]: <info> sleeping or disabling... Oct 8 07:59:30 localhost rsyslogd: [origin software="rsyslogd" swVersion="7.2.6" x-pid="913" x-info="http://www.rsyslog.com"] start
Hi there, with kernel 3.11.4-201.fc19.x86_64 hibernate is working, so we can close this bug. Thanks Andreas
When calling hibernate, I still see the same crash after upgrading the kernel to 3.11.4-201.fc19.x86_64 - Oct 16 11:05:13 localhost NetworkManager[936]: <info> sleep requested (sleeping: no enabled: yes) Oct 16 11:05:13 localhost NetworkManager[936]: <info> sleeping or disabling... Oct 16 11:05:13 localhost NetworkManager[936]: <info> (wlp13s0): device state change: unavailable -> unmanaged (reason 'sleeping') [20 10 37] Oct 16 11:05:13 localhost NetworkManager[936]: <info> (p5p1): device state change: activated -> unmanaged (reason 'sleeping') [100 10 37] Oct 16 11:05:13 localhost NetworkManager[936]: <info> (p5p1): deactivating device (reason 'sleeping') [37] Oct 16 11:05:13 localhost NetworkManager[936]: <info> (p5p1): canceled DHCP transaction, DHCP client pid 1662 Oct 16 11:05:13 localhost NetworkManager[936]: <info> (p5p1): cleaning up... Oct 16 11:05:13 localhost NetworkManager[936]: <info> (p5p1): taking down device. Oct 16 11:05:14 localhost dbus-daemon[871]: dbus[871]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.s$ Oct 16 11:05:14 localhost dbus-daemon[871]: dbus[871]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Oct 16 11:05:14 localhost dbus[871]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' Oct 16 11:05:14 localhost dbus[871]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Oct 16 11:05:14 localhost systemd[1]: Starting Network Manager Script Dispatcher Service... Oct 16 11:05:14 localhost systemd[1]: Started Network Manager Script Dispatcher Service. Oct 16 11:05:14 localhost systemd[1]: Stopping Sendmail Mail Transport Client... Oct 16 11:05:14 localhost systemd[1]: Stopping Sendmail Mail Transport Agent... Oct 16 11:05:14 localhost systemd[1]: Starting Sendmail Mail Transport Agent... Oct 16 11:05:14 localhost systemd[1]: PID file /run/sendmail.pid not readable (yet?) after start. Oct 16 11:05:14 localhost systemd[1]: Started Sendmail Mail Transport Agent. Oct 16 11:05:14 localhost systemd[1]: Starting Sendmail Mail Transport Client... Oct 16 11:05:14 localhost systemd[1]: Started Sendmail Mail Transport Client. Oct 16 16:34:26 localhost rsyslogd: [origin software="rsyslogd" swVersion="7.2.6" x-pid="875" x-info="http://www.rsyslog.com"] start