Description of problem: My HP dv6t freezes when resuming from suspend. The screen comes on and shows what was on it when it was suspended, but the system is completely hung. I can't even press Ctrl+Alt+F2 to get to a secondary console. Version-Release number of selected component (if applicable): xorg-x11-drv-intel-2.21.8-1.fc19.x86_64 How reproducible: Always Steps to Reproduce: 1. Close lid, wait for system to suspend 2. Open lid Actual results: Everything comes back, but the computer is frozen Expected results: Everything comes back, the computer starts working again Additional info: Downgrading to xorg-x11-drv-intel-2.21.6-1.fc19.x86_64 fixes the problem, so this seems to be a regression. The last thing that's shown in the logs is the system suspending; there are no logs for the resuming.
I confirm this problem. My laptop is a Thinkpad X301. Ctrl+Alt+Delete does not work either: all you can do is switch off the laptop and reboot. The behviour is exactly as described in Jonatahn first post. Log messages do not give any useful information I can see. See below /var/log/message the suspend message is followed by the booting message obtained after switching off the laptop: no message about resuming. Graphic Controller: 000:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device 20e4 Flags: bus master, fast devsel, latency 0, IRQ 44 Memory at f0000000 (64-bit, non-prefetchable) [size=4M] Memory at d0000000 (64-bit, prefetchable) [size=256M] I/O ports at 1800 [size=8] Expansion ROM at <unassigned> [disabled] Capabilities: <access denied> Kernel driver in use: i915 00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) Subsystem: Lenovo Device 20e4 Flags: bus master, fast devsel, latency 0 Memory at f0400000 (64-bit, non-prefetchable) [size=1M] Capabilities: <access denied> /var/log/messages of right before suspend Aug 9 15:45:56 mirto systemd[1]: Starting Cleanup of Temporary Directories... Aug 9 15:45:56 mirto systemd-tmpfiles[3493]: stat(/run/user/1000/gvfs) failed: Permission denied Aug 9 15:45:56 mirto systemd[1]: Started Cleanup of Temporary Directories. Aug 9 15:49:46 mirto NetworkManager[561]: <info> sleep requested (sleeping: no enabled: yes) Aug 9 15:49:46 mirto NetworkManager[561]: <info> sleeping or disabling... Aug 9 15:49:46 mirto NetworkManager[561]: <info> (enp0s25): device state change: unavailable -> unmanaged (reason 'sleeping') [20 10 37] Aug 9 15:49:46 mirto NetworkManager[561]: <info> (enp0s25): cleaning up... Aug 9 15:49:46 mirto NetworkManager[561]: <info> (enp0s25): taking down device. Aug 9 15:49:46 mirto NetworkManager[561]: <info> (wls1): device state change: activated -> unmanaged (reason 'sleeping') [100 10 37] Aug 9 15:49:46 mirto NetworkManager[561]: <info> (wls1): deactivating device (reason 'sleeping') [37] Aug 9 15:49:46 mirto NetworkManager[561]: <info> (wls1): canceled DHCP transaction, DHCP client pid 1248 Aug 9 15:49:46 mirto avahi-daemon[497]: Withdrawing address record for 192.168.1.102 on wls1. Aug 9 15:49:46 mirto avahi-daemon[497]: Leaving mDNS multicast group on interface wls1.IPv4 with address 192.168.1.102. Aug 9 15:49:46 mirto kernel: [ 1130.024629] wls1: deauthenticating from 00:13:10:1f:62:7d by local choice (reason=3) Aug 9 15:49:46 mirto NetworkManager[561]: <info> (wls1): cleaning up... Aug 9 15:49:46 mirto kernel: [ 1130.032070] cfg80211: Calling CRDA to update world regulatory domain Aug 9 15:49:46 mirto avahi-daemon[497]: Interface wls1.IPv4 no longer relevant for mDNS. Aug 9 15:49:46 mirto NetworkManager[561]: <info> (wls1): taking down device. Aug 9 15:49:46 mirto kernel: [ 1130.058689] cfg80211: World regulatory domain updated: Aug 9 15:49:46 mirto kernel: [ 1130.058695] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) Aug 9 15:49:46 mirto kernel: [ 1130.058698] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Aug 9 15:49:46 mirto kernel: [ 1130.058701] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Aug 9 15:49:46 mirto kernel: [ 1130.058703] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) Aug 9 15:49:46 mirto kernel: [ 1130.058705] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Aug 9 15:49:46 mirto kernel: [ 1130.058708] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Aug 9 15:49:46 mirto kernel: [ 1130.058732] cfg80211: Calling CRDA for country: FR Aug 9 15:49:46 mirto avahi-daemon[497]: Withdrawing address record for fe80::221:6aff:fe8c:c45e on wls1. Aug 9 15:49:46 mirto kernel: [ 1130.075512] cfg80211: Regulatory domain changed to country: FR Aug 9 15:49:46 mirto kernel: [ 1130.075517] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) Aug 9 15:49:46 mirto kernel: [ 1130.075520] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm) Aug 9 15:49:46 mirto kernel: [ 1130.075522] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm) Aug 9 15:49:46 mirto kernel: [ 1130.075524] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm) Aug 9 15:49:46 mirto kernel: [ 1130.075527] cfg80211: (5490000 KHz - 5710000 KHz @ 40000 KHz), (N/A, 2700 mBm) Aug 9 15:49:46 mirto kernel: [ 1130.075529] cfg80211: (57240000 KHz - 65880000 KHz @ 2160000 KHz), (N/A, 4000 mBm) Aug 9 15:49:46 mirto NetworkManager[561]: <info> (wwp0s29f7u4i7): device state change: disconnected -> unmanaged (reason 'sleeping') [30 10 37] Aug 9 15:49:46 mirto NetworkManager[561]: <info> (wwp0s29f7u4i7): cleaning up... Aug 9 15:49:46 mirto dbus[499]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' Aug 9 15:49:46 mirto dbus-daemon[499]: dbus[499]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' Aug 9 15:49:46 mirto systemd[1]: Starting Network Manager Script Dispatcher Service... Aug 9 15:49:46 mirto dbus-daemon[499]: dbus[499]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Aug 9 15:49:46 mirto dbus[499]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Aug 9 15:49:46 mirto systemd[1]: Starting Sleep. Aug 9 15:49:46 mirto systemd[1]: Reached target Sleep. Aug 9 15:49:46 mirto systemd[1]: Starting Suspend... Aug 9 15:49:46 mirto systemd[1]: Started Network Manager Script Dispatcher Service. Aug 9 15:49:46 mirto systemd-sleep[3570]: Suspending system... Aug 9 15:50:55 mirto kernel: [ 0.000000] Initializing cgroup subsys cpuset Aug 9 15:50:55 mirto kernel: [ 0.000000] Initializing cgroup subsys cpu Aug 9 15:50:55 mirto kernel: [ 0.000000] Initializing cgroup subsys cpuacct Aug 9 15:50:55 mirto kernel: [ 0.000000] Linux version 3.10.4-300.fc19.x86_64 (mockbuild@bkernel02) (gcc version 4.8.1 20130603 (Red Hat 4.8.1-1) (GCC) ) #1 SMP Tue Jul 30 11:29:05 UTC 2013 Aug 9 15:50:55 mirto kernel: [ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.10.4-300.fc19.x86_64 root=/dev/mapper/vg_mirto-lv_root ro rd.md=0 rd.dm=0 vconsole.keymap=us rd.lvm.lv=vg_mirto/lv_swap rd.luks=0 vconsole.font=latarcyrheb-sun16 rd.lvm.lv=vg_mirto/lv_root rhgb quiet Aug 9 15:50:55 mirto kernel: [ 0.000000] Disabled fast string operations Aug 9 15:50:55 mirto kernel: [ 0.000000] e820: BIOS-provided physical RAM map:
the bug is present both in xorg-x11-drv-intel-2.21.12-2.fc19.x86_64 and in xorg-x11-drv-intel-2.21.8-1.fc19.x86_64 Contrary to Jonathan case, downgrading to xorg-x11-drv-intel-2.21.6-1.fc19.x86_64 does NOT fix the problem in my case. Suspend and resume worked flawlessly in Fedora 18.
Seems to be fixed for me with some of the latest update. The driver version is still xorg-x11-drv-intel.x86_64 (2.21.12-2.fc19). I don't know what exactly fixed it.
I confirm. It is fixed, for me too.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.