Wake after Blank Screen does not work

falstaff_ch · 2016-10-07 01:37:51

Hi,

On a Lenovo T440s with a integrated Intel graphics (i7-4600U) I recently can't wake the system after the screen goes blank. I can wake it changing the Virtual Terminal (or hotplugging an external Monitor). But normal keystroke or mouse movements do not wake the system. I haven't had the issue until around 3 months ago... I did a rather big update, so I could not pinpoint the issue to a package, however, I am pretty sure that it is not the kernel since I tested an older LTS which I am sure worked at one point in time...

Any hints welcome!

Thanks,
Stefan

jethronsun7 · 2016-10-11 21:05:04

Could you be a little more specific? Does the DE/WM affect it? What do you mean by the "screen goes black"?

Last edited by jethronsun7 (2016-10-11 21:05:13)

falstaff_ch · 2016-10-19 16:07:58

I use Gnome 3, I have the issue actually on two laptops (the second is a T431s, also with Intel graphics,same Software setup otherwise).

With "screen goes black" I mean the regular screen turn-off functionality when a system is idle. Specifically, in Gnome Power you can configure "Blank Screen". So if I set this to 1 Minute, wait this one Minute the screen starts to dimm and then goes off. When I move the mouse while dimming, it stops dimming and I can continue working. However, once the screen is completely off, I can move my mouse however I want, it does not turn on again.

This happens when I use a external monitor (via DP) or only use the Laptop screen.

I can wake-up the screen by switching VT (Ctrl+Alt+Fsomething and then back to wherever the X server is running). So I have a working work-around... But its ugly! And I wonder that nobody else has this, since I have it on two systems...

falstaff_ch · 2016-10-19 16:31:14

Regarding wake-up: normally this should work with either mouse movement or keyboard. In this case, nothing works: Internal Keyboard, external keyboard, internal touchpad and external mouse, I can press/click/move whatever I wan't the system does not wake up. The only thing which helps is VT change. I also checked Xorg.0.log and journalctl, both show nothing until I do the VT change:

-- At this point the screen is blank and I try to wake it up...
-- Using Ctrl+Alt+F3 to wake the system
Okt 19 09:29:09 trochilidae /usr/lib/gdm/gdm-x-session[983]: (II) AIGLX: Suspending AIGLX clients for VT switch
Okt 19 09:29:10 trochilidae root[26454]: ACPI group/action undefined: jack/lineout / LINEOUT
Okt 19 09:29:10 trochilidae root[26456]: ACPI group/action undefined: jack/videoout / VIDEOOUT
Okt 19 09:29:10 trochilidae /usr/lib/gdm/gdm-x-session[983]: (II) systemd-logind: got pause for 13:82
Okt 19 09:29:10 trochilidae /usr/lib/gdm/gdm-x-session[983]: (II) systemd-logind: got pause for 13:79
Okt 19 09:29:10 trochilidae /usr/lib/gdm/gdm-x-session[983]: (II) systemd-logind: got pause for 13:68
Okt 19 09:29:10 trochilidae /usr/lib/gdm/gdm-x-session[983]: (II) systemd-logind: got pause for 13:81
Okt 19 09:29:10 trochilidae /usr/lib/gdm/gdm-x-session[983]: (II) systemd-logind: got pause for 13:67
Okt 19 09:29:10 trochilidae /usr/lib/gdm/gdm-x-session[983]: (II) systemd-logind: got pause for 226:0
Okt 19 09:29:10 trochilidae /usr/lib/gdm/gdm-x-session[983]: (II) systemd-logind: got pause for 13:65
Okt 19 09:29:10 trochilidae /usr/lib/gdm/gdm-x-session[983]: (II) systemd-logind: got pause for 13:66
Okt 19 09:29:10 trochilidae /usr/lib/gdm/gdm-x-session[983]: (II) systemd-logind: got pause for 13:80
Okt 19 09:29:10 trochilidae /usr/lib/gdm/gdm-x-session[983]: (II) systemd-logind: got pause for 13:78
Okt 19 09:29:11 trochilidae acpid[389]: client 985[1000:1000] has disconnected
Okt 19 09:29:11 trochilidae /usr/lib/gdm/gdm-x-session[983]: (II) systemd-logind: got resume for 13:82
Okt 19 09:29:11 trochilidae /usr/lib/gdm/gdm-x-session[983]: (II) systemd-logind: got resume for 13:79
Okt 19 09:29:11 trochilidae /usr/lib/gdm/gdm-x-session[983]: (II) systemd-logind: got resume for 13:68
Okt 19 09:29:11 trochilidae /usr/lib/gdm/gdm-x-session[983]: (II) systemd-logind: got resume for 13:81
Okt 19 09:29:11 trochilidae /usr/lib/gdm/gdm-x-session[983]: (II) systemd-logind: got resume for 13:67
Okt 19 09:29:11 trochilidae /usr/lib/gdm/gdm-x-session[983]: (II) systemd-logind: got resume for 226:0
Okt 19 09:29:11 trochilidae /usr/lib/gdm/gdm-x-session[983]: (II) Open ACPI successful (/var/run/acpid.socket)
Okt 19 09:29:11 trochilidae /usr/lib/gdm/gdm-x-session[983]: (II) AIGLX: Resuming AIGLX clients after VT switch
Okt 19 09:29:11 trochilidae acpid[389]: client connected from 985[1000:1000]
Okt 19 09:29:11 trochilidae acpid[389]: 1 client rule loaded
Okt 19 09:29:12 trochilidae root[26461]: ACPI group/action undefined: jack/lineout / LINEOUT
Okt 19 09:29:12 trochilidae root[26463]: ACPI group/action undefined: jack/videoout / VIDEOOUT
Okt 19 09:29:12 trochilidae root[26465]: ACPI group/action undefined: jack/lineout / LINEOUT
Okt 19 09:29:12 trochilidae root[26467]: ACPI group/action undefined: jack/videoout / VIDEOOUT
Okt 19 09:29:13 trochilidae /usr/lib/gdm/gdm-x-session[983]: (II) intel(0): EDID vendor "CMN", prod id 5250
Okt 19 09:29:13 trochilidae /usr/lib/gdm/gdm-x-session[983]: (II) intel(0): Printing DDC gathered Modelines:
Okt 19 09:29:13 trochilidae /usr/lib/gdm/gdm-x-session[983]: (II) intel(0): Modeline "1600x900"x0.0  107.80  1600 1648 1680 1940  900 903 908 926 -hsync -vsync (55.6 kHz eP)
Okt 19 09:29:13 trochilidae /usr/lib/gdm/gdm-x-session[983]: (II) systemd-logind: got resume for 13:65
Okt 19 09:29:13 trochilidae /usr/lib/gdm/gdm-x-session[983]: (II) systemd-logind: got resume for 13:66
Okt 19 09:29:13 trochilidae /usr/lib/gdm/gdm-x-session[983]: (II) systemd-logind: got resume for 13:80
Okt 19 09:29:13 trochilidae /usr/lib/gdm/gdm-x-session[983]: (II) systemd-logind: got resume for 13:78
Okt 19 09:29:13 trochilidae /usr/lib/gdm/gdm-x-session[983]: (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found

richcocoa · 2016-10-22 07:30:26

I have the same issue. My journalctl output does not hint at any culprits. Mine is a Dell Inspiron 15 5558, with an Intel Core i5 5250U and Intel HD6000 on board graphics. The dedicated graphics card is disabled. I also started facing the issue only recently, though not really sure when. And I simply switch VTs like you do

$ journalctl -x --no-hostname --since <just before suspend>

-- Logs begin at Sat 2016-09-24 07:42:06 IST, end at Sat 2016-10-22 12:03:16 IST. --
Oct 22 12:00:41 systemd-logind[338]: Lid closed.
Oct 22 12:00:41 systemd-logind[338]: Suspending...
Oct 22 12:00:41 NetworkManager[343]: <info>  [1477117841.9511] manager: sleep requested (sleeping: no  enabled: yes)
Oct 22 12:00:41 dbus[341]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Oct 22 12:00:41 NetworkManager[343]: <info>  [1477117841.9511] manager: sleeping...
Oct 22 12:00:41 NetworkManager[343]: <info>  [1477117841.9513] manager: NetworkManager state is now ASLEEP
Oct 22 12:00:41 NetworkManager[343]: <info>  [1477117841.9517] device (wlp6s0): state change: activated -> deactivating (reason 'sleeping') [100 110 37]
Oct 22 12:00:41 systemd[1]: Starting Network Manager Script Dispatcher Service...
Oct 22 12:00:41 dbus[341]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Oct 22 12:00:41 systemd[1]: Started Network Manager Script Dispatcher Service.
Oct 22 12:00:41 nm-dispatcher[30330]: req:1 'connectivity-change': new request (0 scripts)
Oct 22 12:00:41 nm-dispatcher[30330]: req:1 'connectivity-change': completed: no scripts
Oct 22 12:00:42 NetworkManager[343]: <info>  [1477117842.0350] device (wlp6s0): state change: deactivating -> disconnected (reason 'sleeping') [110 30 37]
Oct 22 12:00:42 vmnet-natd[16251]: RTM_NEWLINK: name:wlp6s0 index:3 flags:0x00011043
Oct 22 12:00:42 vmnetBridge[16221]: RTM_NEWLINK: name:wlp6s0 index:3 flags:0x00011043
Oct 22 12:00:42 NetworkManager[343]: <info>  [1477117842.0519] dhcp4 (wlp6s0): canceled DHCP transaction, DHCP client pid 28987
Oct 22 12:00:42 NetworkManager[343]: <info>  [1477117842.0519] dhcp4 (wlp6s0): state changed bound -> done
Oct 22 12:00:42 vmnet-natd[16251]: RTM_DELADDR: index:3, addr:192.168.1.103
Oct 22 12:00:42 kernel: wlp6s0: deauthenticating from 00:0b:04:11:37:4a by local choice (Reason: 3=DEAUTH_LEAVING)
Oct 22 12:00:42 wpa_supplicant[426]: wlp6s0: CTRL-EVENT-DISCONNECTED bssid=00:0b:04:11:37:4a reason=3 locally_generated=1
Oct 22 12:00:42 vmnet-natd[16251]: RTM_NEWLINK: name:wlp6s0 index:3 flags:0x00001003
Oct 22 12:00:42 vmnetBridge[16221]: RTM_NEWLINK: name:wlp6s0 index:3 flags:0x00001003
Oct 22 12:00:42 vmnetBridge[16221]: Removing interface wlp6s0 index:3
Oct 22 12:00:42 kernel: bridge-wlp6s0: disabling the bridge
Oct 22 12:00:42 vmnet-natd[16251]: RTM_NEWLINK: name:wlp6s0 index:3 flags:0x00001002
Oct 22 12:00:42 NetworkManager[343]: <info>  [1477117842.0619] device (wlp6s0): set-hw-addr: set MAC address to BA:4F:0E:2B:6A:75 (scanning)
Oct 22 12:00:42 vmnet-natd[16251]: RTM_NEWLINK: name:wlp6s0 index:3 flags:0x00001002
Oct 22 12:00:42 vmnet-natd[16251]: RTM_NEWLINK: name:wlp6s0 index:3 flags:0x00001003
Oct 22 12:00:42 NetworkManager[343]: <info>  [1477117842.0644] dns-mgr: Removing DNS information from /usr/bin/resolvconf
Oct 22 12:00:42 kernel: IPv6: ADDRCONF(NETDEV_UP): wlp6s0: link is not ready
Oct 22 12:00:42 vmnetBridge[16221]: Stopped bridge wlp6s0 to virtual network 0.
Oct 22 12:00:42 vmnetBridge[16221]: RTM_NEWLINK: name:wlp6s0 index:3 flags:0x00001002
Oct 22 12:00:42 vmnetBridge[16221]: RTM_NEWLINK: name:wlp6s0 index:3 flags:0x00001002
Oct 22 12:00:42 vmnetBridge[16221]: RTM_NEWLINK: name:wlp6s0 index:3 flags:0x00001003
Oct 22 12:00:42 kernel: bridge-wlp6s0: down
Oct 22 12:00:42 kernel: bridge-wlp6s0: detached
Oct 22 12:00:42 NetworkManager[343]: <warn>  [1477117842.1036] sup-iface[0x156fee0,wlp6s0]: connection disconnected (reason -3)
Oct 22 12:00:42 NetworkManager[343]: <info>  [1477117842.1037] device (wlp6s0): supplicant interface state: completed -> disconnected
Oct 22 12:00:42 nm-dispatcher[30330]: req:2 'down' [wlp6s0]: new request (0 scripts)
Oct 22 12:00:42 nm-dispatcher[30330]: req:2 'down' [wlp6s0]: completed: no scripts
Oct 22 12:00:42 NetworkManager[343]: <info>  [1477117842.1110] device (wlp6s0): state change: disconnected -> unmanaged (reason 'sleeping') [30 10 37]
Oct 22 12:00:42 vmnet-natd[16251]: RTM_NEWLINK: name:wlp6s0 index:3 flags:0x00001002
Oct 22 12:00:42 vmnetBridge[16221]: RTM_NEWLINK: name:wlp6s0 index:3 flags:0x00001002
Oct 22 12:00:42 vmnetBridge[16221]: RTM_NEWLINK: name:wlp6s0 index:3 flags:0x00001002
Oct 22 12:00:42 NetworkManager[343]: <info>  [1477117842.1136] device (wlp6s0): set-hw-addr: reset MAC address to E4:F8:9C:BC:7A:0A (unmanage)
Oct 22 12:00:42 vmnet-natd[16251]: RTM_NEWLINK: name:wlp6s0 index:3 flags:0x00001002
Oct 22 12:00:42 wpa_supplicant[426]: nl80211: deinit ifname=p2p-dev-wlp6s0 disabled_11b_rates=0
Oct 22 12:00:42 wpa_supplicant[426]: nl80211: deinit ifname=wlp6s0 disabled_11b_rates=0
Oct 22 12:00:42 kernel: userif-3: sent link down event.
Oct 22 12:00:42 kernel: userif-3: sent link up event.
Oct 22 12:00:43 systemd[1]: Reached target Sleep.
Oct 22 12:00:43 systemd[1]: Starting Suspend...
Oct 22 12:00:43 systemd-sleep[30386]: Suspending system...
Oct 22 12:01:05 kernel: PM: Syncing filesystems ... done.
Oct 22 12:01:05 kernel: PM: Preparing system for sleep (mem)
Oct 22 12:01:05 kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
Oct 22 12:01:05 kernel: Double checking all user space processes after OOM killer disable... (elapsed 0.000 seconds) 
Oct 22 12:01:05 kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Oct 22 12:01:05 kernel: PM: Suspending system (mem)
Oct 22 12:01:05 kernel: Suspending console(s) (use no_console_suspend to debug)
Oct 22 12:01:05 kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Oct 22 12:01:05 kernel: sd 0:0:0:0: [sda] Stopping disk
Oct 22 12:01:05 kernel: PM: suspend of devices complete after 1114.001 msecs
Oct 22 12:01:05 kernel: PM: late suspend of devices complete after 17.774 msecs
Oct 22 12:01:05 kernel: r8169 0000:07:00.0: System wakeup enabled by ACPI
Oct 22 12:01:05 kernel: xhci_hcd 0000:00:14.0: System wakeup enabled by ACPI
Oct 22 12:01:05 kernel: ehci-pci 0000:00:1d.0: System wakeup enabled by ACPI
Oct 22 12:01:05 kernel: PM: noirq suspend of devices complete after 13.772 msecs
Oct 22 12:01:05 kernel: ACPI: Preparing to enter system sleep state S3
Oct 22 12:01:05 kernel: ACPI : EC: EC stopped
Oct 22 12:01:05 kernel: PM: Saving platform NVS memory
Oct 22 12:01:05 kernel: Disabling non-boot CPUs ...
Oct 22 12:01:05 kernel: smpboot: CPU 1 is now offline
Oct 22 12:01:05 kernel: smpboot: CPU 2 is now offline
Oct 22 12:01:05 kernel: smpboot: CPU 3 is now offline
Oct 22 12:01:05 kernel: ACPI: Low-level resume complete
Oct 22 12:01:05 kernel: ACPI : EC: EC started
Oct 22 12:01:05 kernel: PM: Restoring platform NVS memory
Oct 22 12:01:05 kernel: Enabling non-boot CPUs ...
Oct 22 12:01:05 kernel: x86: Booting SMP configuration:
Oct 22 12:01:05 kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
Oct 22 12:01:05 kernel:  cache: parent cpu1 should not be sleeping
Oct 22 12:01:05 kernel: CPU1 is up
Oct 22 12:01:05 kernel: smpboot: Booting Node 0 Processor 2 APIC 0x1
Oct 22 12:01:05 kernel:  cache: parent cpu2 should not be sleeping
Oct 22 12:01:05 kernel: CPU2 is up
Oct 22 12:01:05 kernel: smpboot: Booting Node 0 Processor 3 APIC 0x3
Oct 22 12:01:05 kernel: /dev/vmmon[30386]: HostIFReadUptimeWork: detected settimeofday: fixed uptimeBase old 18445266969041813981 new 18445266969022939125 attempts 1
Oct 22 12:01:05 kernel:  cache: parent cpu3 should not be sleeping
Oct 22 12:01:05 kernel: CPU3 is up
Oct 22 12:01:05 kernel: ACPI: Waking up from system sleep state S3
Oct 22 12:01:05 kernel: ehci-pci 0000:00:1d.0: System wakeup disabled by ACPI
Oct 22 12:01:05 kernel: xhci_hcd 0000:00:14.0: System wakeup disabled by ACPI
Oct 22 12:01:05 kernel: PM: noirq resume of devices complete after 40.166 msecs
Oct 22 12:01:05 kernel: PM: early resume of devices complete after 26.169 msecs
Oct 22 12:01:05 kernel: sd 0:0:0:0: [sda] Starting disk
Oct 22 12:01:05 kernel: r8169 0000:07:00.0: System wakeup disabled by ACPI
Oct 22 12:01:05 kernel: rtc_cmos 00:01: System wakeup disabled by ACPI
Oct 22 12:01:05 kernel: xhci_hcd 0000:00:14.0: port 7 resume PLC timeout
Oct 22 12:01:05 kernel: xhci_hcd 0000:00:14.0: port 5 resume PLC timeout
Oct 22 12:01:05 kernel: r8169 0000:07:00.0 enp7s0: link down
Oct 22 12:01:05 kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Oct 22 12:01:05 kernel: ata2.00: configured for UDMA/133
Oct 22 12:01:05 kernel: usb 2-5: reset high-speed USB device number 2 using xhci_hcd
Oct 22 12:01:05 kernel: usb 2-6: reset full-speed USB device number 3 using xhci_hcd
Oct 22 12:01:05 kernel: usb 2-8: reset high-speed USB device number 4 using xhci_hcd
Oct 22 12:01:05 kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Oct 22 12:01:05 kernel: ata1.00: configured for UDMA/133
Oct 22 12:01:05 kernel: PM: resume of devices complete after 1171.969 msecs
Oct 22 12:01:05 kernel: usb 2-6:1.0: rebind failed: -517
Oct 22 12:01:05 kernel: usb 2-6:1.1: rebind failed: -517
Oct 22 12:01:05 kernel: PM: Finishing wakeup.
Oct 22 12:01:05 kernel: Restarting tasks ... 
Oct 22 12:01:05 kernel: pci_bus 0000:04: Allocating resources
Oct 22 12:01:05 kernel: pci_bus 0000:06: Allocating resources
Oct 22 12:01:05 kernel: pci_bus 0000:07: Allocating resources
Oct 22 12:01:05 kernel: pci_bus 0000:08: Allocating resources
Oct 22 12:01:05 kernel: pci_bus 0000:04: Allocating resources
Oct 22 12:01:05 kernel: pci_bus 0000:06: Allocating resources
Oct 22 12:01:05 kernel: pci_bus 0000:07: Allocating resources
Oct 22 12:01:05 kernel: pci_bus 0000:08: Allocating resources
Oct 22 12:01:05 kernel: pci_bus 0000:04: Allocating resources
Oct 22 12:01:05 kernel: pci_bus 0000:06: Allocating resources
Oct 22 12:01:05 kernel: pci_bus 0000:07: Allocating resources
Oct 22 12:01:05 kernel: pci_bus 0000:08: Allocating resources
Oct 22 12:01:05 kernel: done.
Oct 22 12:01:05 systemd[1]: Time has been changed
Oct 22 12:01:05 systemd-logind[338]: Lid opened.
Oct 22 12:01:05 systemd[1]: Starting Load/Save RF Kill Switch Status...
Oct 22 12:01:05 systemd[747]: Time has been changed
Oct 22 12:01:05 systemd[1]: bluetooth.target: Unit not needed anymore. Stopping.
Oct 22 12:01:05 systemd[1]: Stopped target Bluetooth.
Oct 22 12:01:05 systemd[1]: Reached target Bluetooth.
Oct 22 12:01:05 systemd[1]: Started Load/Save RF Kill Switch Status.
Oct 22 12:01:05 kernel: Bluetooth: hci0: read Intel version: 3707100100012d0d00
Oct 22 12:01:05 kernel: Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.0.1.2d.d.bseq
Oct 22 12:01:05 kernel: Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated
Oct 22 12:01:05 systemd-sleep[30386]: System resumed.
Oct 22 12:01:05 systemd[1]: Started Suspend.
Oct 22 12:01:05 systemd[1]: sleep.target: Unit not needed anymore. Stopping.
Oct 22 12:01:05 systemd[1]: Stopped target Sleep.
Oct 22 12:01:05 systemd[1]: Reached target Suspend.
Oct 22 12:01:05 systemd-logind[338]: Operation 'sleep' finished.
Oct 22 12:01:05 systemd[1]: suspend.target: Unit is bound to inactive unit systemd-suspend.service. Stopping, too.
Oct 22 12:01:05 systemd[1]: Stopped target Suspend.
Oct 22 12:01:05 NetworkManager[343]: <info>  [1477117865.8422] manager: wake requested (sleeping: yes  enabled: yes)
Oct 22 12:01:05 NetworkManager[343]: <info>  [1477117865.8423] manager: waking up...
Oct 22 12:01:05 NetworkManager[343]: <info>  [1477117865.8423] device (enp7s0): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 37]
Oct 22 12:01:05 bluetoothd[340]: Failed to obtain handles for "Service Changed" characteristic
Oct 22 12:01:05 bluetoothd[340]: Sap driver initialization failed.
Oct 22 12:01:05 bluetoothd[340]: sap-server: Operation not permitted (1)
Oct 22 12:01:05 vmnet-natd[16251]: RTM_NEWLINK: name:enp7s0 index:2 flags:0x00001002
Oct 22 12:01:05 NetworkManager[343]: <info>  [1477117865.8600] device (enp7s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Oct 22 12:01:05 vmnetBridge[16221]: RTM_NEWLINK: name:enp7s0 index:2 flags:0x00001002
Oct 22 12:01:05 kernel: IPv6: ADDRCONF(NETDEV_UP): enp7s0: link is not ready
Oct 22 12:01:06 vmnetBridge[16221]: RTM_NEWLINK: name:enp7s0 index:2 flags:0x00001003
Oct 22 12:01:06 vmnet-natd[16251]: RTM_NEWLINK: name:enp7s0 index:2 flags:0x00001003
Oct 22 12:01:06 NetworkManager[343]: <info>  [1477117866.0372] device (wlp6s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Oct 22 12:01:06 kernel: r8169 0000:07:00.0 enp7s0: link down
Oct 22 12:01:06 kernel: IPv6: ADDRCONF(NETDEV_UP): enp7s0: link is not ready
Oct 22 12:01:06 kernel: IPv6: ADDRCONF(NETDEV_UP): wlp6s0: link is not ready
Oct 22 12:01:06 kernel: iwlwifi 0000:06:00.0: L1 Enabled - LTR Enabled
Oct 22 12:01:06 kernel: iwlwifi 0000:06:00.0: L1 Enabled - LTR Enabled
Oct 22 12:01:06 bluetoothd[340]: Failed to set mode: Blocked through rfkill (0x12)
Oct 22 12:01:06 kernel: iwlwifi 0000:06:00.0: L1 Enabled - LTR Enabled
Oct 22 12:01:06 kernel: iwlwifi 0000:06:00.0: L1 Enabled - LTR Enabled
Oct 22 12:01:06 vmnet-natd[16251]: RTM_NEWLINK: name:wlp6s0 index:3 flags:0x00001003
Oct 22 12:01:06 vmnetBridge[16221]: RTM_NEWLINK: name:wlp6s0 index:3 flags:0x00001003
Oct 22 12:01:06 kernel: IPv6: ADDRCONF(NETDEV_UP): wlp6s0: link is not ready
Oct 22 12:01:06 vmnetBridge[16221]: RTM_NEWLINK: name:wlp6s0 index:3 flags:0x00001002
Oct 22 12:01:06 vmnet-natd[16251]: RTM_NEWLINK: name:wlp6s0 index:3 flags:0x00001002
Oct 22 12:01:06 vmnet-natd[16251]: RTM_NEWLINK: name:wlp6s0 index:3 flags:0x00001002
Oct 22 12:01:06 NetworkManager[343]: <info>  [1477117866.1672] device (wlp6s0): set-hw-addr: set MAC address to BA:4F:0E:2B:6A:75 (scanning)
Oct 22 12:01:06 vmnetBridge[16221]: RTM_NEWLINK: name:wlp6s0 index:3 flags:0x00001002
Oct 22 12:01:06 kernel: iwlwifi 0000:06:00.0: L1 Enabled - LTR Enabled
Oct 22 12:01:06 kernel: iwlwifi 0000:06:00.0: L1 Enabled - LTR Enabled
Oct 22 12:01:06 kernel: iwlwifi 0000:06:00.0: L1 Enabled - LTR Enabled
Oct 22 12:01:06 kernel: iwlwifi 0000:06:00.0: L1 Enabled - LTR Enabled
Oct 22 12:01:06 vmnetBridge[16221]: RTM_NEWLINK: name:wlp6s0 index:3 flags:0x00001003
Oct 22 12:01:06 vmnet-natd[16251]: RTM_NEWLINK: name:wlp6s0 index:3 flags:0x00001003
Oct 22 12:01:06 NetworkManager[343]: <info>  [1477117866.2913] manager: NetworkManager state is now DISCONNECTED
Oct 22 12:01:06 kernel: IPv6: ADDRCONF(NETDEV_UP): wlp6s0: link is not ready
Oct 22 12:01:06 vmnet-natd[16251]: RTM_NEWLINK: name:wlp6s0 index:3 flags:0x00001003
Oct 22 12:01:06 vmnetBridge[16221]: RTM_NEWLINK: name:wlp6s0 index:3 flags:0x00001003
Oct 22 12:01:06 wpa_supplicant[426]: Could not read interface p2p-dev-wlp6s0 flags: No such device
Oct 22 12:01:06 NetworkManager[343]: <info>  [1477117866.3402] sup-iface[0x14c52b0,wlp6s0]: supports 5 scan SSIDs
Oct 22 12:01:06 NetworkManager[343]: <info>  [1477117866.3410] device (wlp6s0): supplicant interface state: starting -> ready
Oct 22 12:01:06 NetworkManager[343]: <info>  [1477117866.3411] device (wlp6s0): state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Oct 22 12:01:06 vmnet-natd[16251]: RTM_NEWLINK: name:wlp6s0 index:3 flags:0x00001003
Oct 22 12:01:06 kernel: IPv6: ADDRCONF(NETDEV_UP): wlp6s0: link is not ready
Oct 22 12:01:06 vmnetBridge[16221]: RTM_NEWLINK: name:wlp6s0 index:3 flags:0x00001003
Oct 22 12:01:09 wpa_supplicant[426]: wlp6s0: Reject scan trigger since one is already pending
Oct 22 12:01:09 NetworkManager[343]: <info>  [1477117869.7113] device (wlp6s0): supplicant interface state: ready -> inactive
Oct 22 12:01:09 NetworkManager[343]: <info>  [1477117869.7126] policy: auto-activating connection 'BEAM311512'
Oct 22 12:01:09 NetworkManager[343]: <info>  [1477117869.7137] device (wlp6s0): Activation: starting connection 'BEAM311512' (591d9d08-1594-4e0f-92a5-b1a4986ae12b)
Oct 22 12:01:09 NetworkManager[343]: <info>  [1477117869.7138] device (wlp6s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Oct 22 12:01:09 NetworkManager[343]: <info>  [1477117869.7139] manager: NetworkManager state is now CONNECTING
Oct 22 12:01:09 vmnetBridge[16221]: RTM_NEWLINK: name:wlp6s0 index:3 flags:0x00001002
Oct 22 12:01:09 vmnet-natd[16251]: RTM_NEWLINK: name:wlp6s0 index:3 flags:0x00001002
Oct 22 12:01:09 vmnet-natd[16251]: RTM_NEWLINK: name:wlp6s0 index:3 flags:0x00001002
Oct 22 12:01:09 NetworkManager[343]: <info>  [1477117869.7202] device (wlp6s0): set-hw-addr: set-cloned MAC address to E4:F8:9C:BC:7A:0A (permanent)
Oct 22 12:01:09 vmnetBridge[16221]: RTM_NEWLINK: name:wlp6s0 index:3 flags:0x00001002
Oct 22 12:01:09 vmnet-natd[16251]: RTM_NEWLINK: name:wlp6s0 index:3 flags:0x00001003
Oct 22 12:01:09 vmnetBridge[16221]: RTM_NEWLINK: name:wlp6s0 index:3 flags:0x00001003
Oct 22 12:01:09 kernel: IPv6: ADDRCONF(NETDEV_UP): wlp6s0: link is not ready
Oct 22 12:01:09 NetworkManager[343]: <info>  [1477117869.7319] device (wlp6s0): state change: prepare -> config (reason 'none') [40 50 0]
Oct 22 12:01:09 NetworkManager[343]: <info>  [1477117869.7322] device (wlp6s0): Activation: (wifi) access point 'BEAM311512' has security, but secrets are required.
Oct 22 12:01:09 NetworkManager[343]: <info>  [1477117869.7322] device (wlp6s0): state change: config -> need-auth (reason 'none') [50 60 0]
Oct 22 12:01:09 NetworkManager[343]: <info>  [1477117869.7353] device (wlp6s0): state change: need-auth -> prepare (reason 'none') [60 40 0]
Oct 22 12:01:09 NetworkManager[343]: <info>  [1477117869.7356] device (wlp6s0): state change: prepare -> config (reason 'none') [40 50 0]
Oct 22 12:01:09 NetworkManager[343]: <info>  [1477117869.7358] device (wlp6s0): Activation: (wifi) connection 'BEAM311512' has security, and secrets exist.  No new secrets needed.
Oct 22 12:01:09 NetworkManager[343]: <info>  [1477117869.7359] Config: added 'ssid' value 'BEAM311512'
Oct 22 12:01:09 NetworkManager[343]: <info>  [1477117869.7359] Config: added 'scan_ssid' value '1'
Oct 22 12:01:09 NetworkManager[343]: <info>  [1477117869.7359] Config: added 'key_mgmt' value 'WPA-PSK'
Oct 22 12:01:09 NetworkManager[343]: <info>  [1477117869.7359] Config: added 'psk' value '<omitted>'
Oct 22 12:01:09 NetworkManager[343]: <info>  [1477117869.7625] device (wlp6s0): supplicant interface state: inactive -> disconnected
Oct 22 12:01:09 NetworkManager[343]: <info>  [1477117869.7626] sup-iface[0x14c52b0,wlp6s0]: config: set interface ap_scan to 1
Oct 22 12:01:09 NetworkManager[343]: <info>  [1477117869.7707] device (wlp6s0): supplicant interface state: disconnected -> inactive
Oct 22 12:01:09 wpa_supplicant[426]: wlp6s0: SME: Trying to authenticate with 00:0b:04:11:37:4a (SSID='BEAM311512' freq=2437 MHz)
Oct 22 12:01:09 kernel: wlp6s0: authenticate with 00:0b:04:11:37:4a
Oct 22 12:01:09 kernel: wlp6s0: send auth to 00:0b:04:11:37:4a (try 1/3)
Oct 22 12:01:09 wpa_supplicant[426]: wlp6s0: Trying to associate with 00:0b:04:11:37:4a (SSID='BEAM311512' freq=2437 MHz)
Oct 22 12:01:09 NetworkManager[343]: <info>  [1477117869.7765] device (wlp6s0): supplicant interface state: inactive -> associating
Oct 22 12:01:09 kernel: wlp6s0: authenticated
Oct 22 12:01:09 kernel: wlp6s0: associate with 00:0b:04:11:37:4a (try 1/3)
Oct 22 12:01:09 kernel: wlp6s0: RX AssocResp from 00:0b:04:11:37:4a (capab=0x411 status=0 aid=9)
Oct 22 12:01:09 vmnet-natd[16251]: RTM_NEWLINK: name:wlp6s0 index:3 flags:0x00011003
Oct 22 12:01:09 vmnetBridge[16221]: RTM_NEWLINK: name:wlp6s0 index:3 flags:0x00011003
Oct 22 12:01:09 wpa_supplicant[426]: wlp6s0: Associated with 00:0b:04:11:37:4a
Oct 22 12:01:09 kernel: wlp6s0: associated
Oct 22 12:01:09 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp6s0: link becomes ready
Oct 22 12:01:09 NetworkManager[343]: <info>  [1477117869.7920] device (wlp6s0): supplicant interface state: associating -> 4-way handshake
Oct 22 12:01:09 NetworkManager[343]: <info>  [1477117869.8027] device (wlp6s0): supplicant interface state: 4-way handshake -> group handshake
Oct 22 12:01:10 wpa_supplicant[426]: wlp6s0: WPA: Key negotiation completed with 00:0b:04:11:37:4a [PTK=CCMP GTK=CCMP]
Oct 22 12:01:10 wpa_supplicant[426]: wlp6s0: CTRL-EVENT-CONNECTED - Connection to 00:0b:04:11:37:4a completed [id=0 id_str=]
Oct 22 12:01:10 vmnet-natd[16251]: RTM_NEWLINK: name:wlp6s0 index:3 flags:0x00011043
Oct 22 12:01:10 vmnetBridge[16221]: RTM_NEWLINK: name:wlp6s0 index:3 flags:0x00011043
Oct 22 12:01:10 vmnetBridge[16221]: Adding interface wlp6s0 index:3
Oct 22 12:01:10 vmnetBridge[16221]: Started bridge wlp6s0 to virtual network 0.
Oct 22 12:01:10 kernel: /dev/vmnet: open called by PID 16221 (vmnet-bridge)
Oct 22 12:01:10 kernel: /dev/vmnet: hub 0 does not exist, allocating memory.
Oct 22 12:01:10 kernel: /dev/vmnet: port on hub 0 successfully opened
Oct 22 12:01:10 kernel: bridge-wlp6s0: device is wireless, enabling SMAC
Oct 22 12:01:10 kernel: bridge-wlp6s0: up
Oct 22 12:01:10 kernel: bridge-wlp6s0: attached
Oct 22 12:01:10 NetworkManager[343]: <info>  [1477117870.8056] device (wlp6s0): supplicant interface state: group handshake -> completed
Oct 22 12:01:10 NetworkManager[343]: <info>  [1477117870.8057] device (wlp6s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'BEAM311512'.
Oct 22 12:01:10 NetworkManager[343]: <info>  [1477117870.8058] device (wlp6s0): state change: config -> ip-config (reason 'none') [50 70 0]
Oct 22 12:01:10 NetworkManager[343]: <info>  [1477117870.8062] dhcp4 (wlp6s0): activation: beginning transaction (timeout in 45 seconds)
Oct 22 12:01:10 NetworkManager[343]: <info>  [1477117870.8079] dhcp4 (wlp6s0): dhclient started with pid 30490
Oct 22 12:01:10 vmnet-natd[16251]: RTM_NEWLINK: name:wlp6s0 index:3 flags:0x00011043
Oct 22 12:01:10 vmnetBridge[16221]: RTM_NEWLINK: name:wlp6s0 index:3 flags:0x00011043
Oct 22 12:01:10 dhclient[30490]: DHCPREQUEST on wlp6s0 to 255.255.255.255 port 67
Oct 22 12:01:10 dhclient[30490]: DHCPACK from 192.168.1.254
Oct 22 12:01:10 NetworkManager[343]: <info>  [1477117870.8446] dhcp4 (wlp6s0):   address 192.168.1.103
Oct 22 12:01:10 NetworkManager[343]: <info>  [1477117870.8447] dhcp4 (wlp6s0):   plen 24 (255.255.255.0)
Oct 22 12:01:10 NetworkManager[343]: <info>  [1477117870.8447] dhcp4 (wlp6s0):   gateway 192.168.1.254
Oct 22 12:01:10 vmnet-natd[16251]: RTM_NEWADDR: index:3, addr:192.168.1.103
Oct 22 12:01:10 NetworkManager[343]: <info>  [1477117870.8447] dhcp4 (wlp6s0):   server identifier 192.168.1.254
Oct 22 12:01:10 vmnetBridge[16221]: RTM_NEWROUTE: index:3
Oct 22 12:01:10 NetworkManager[343]: <info>  [1477117870.8447] dhcp4 (wlp6s0):   lease time 864000
Oct 22 12:01:10 vmnet-natd[16251]: RTM_NEWROUTE: index:3
Oct 22 12:01:10 NetworkManager[343]: <info>  [1477117870.8447] dhcp4 (wlp6s0):   nameserver '192.168.1.254'
Oct 22 12:01:10 nm-dispatcher[30330]: req:3 'connectivity-change': new request (0 scripts)
Oct 22 12:01:10 NetworkManager[343]: <info>  [1477117870.8447] dhcp4 (wlp6s0): state changed unknown -> bound
Oct 22 12:01:10 nm-dispatcher[30330]: req:3 'connectivity-change': completed: no scripts
Oct 22 12:01:10 NetworkManager[343]: <info>  [1477117870.8463] device (wlp6s0): state change: ip-config -> ip-check (reason 'none') [70 80 0]
Oct 22 12:01:10 NetworkManager[343]: <info>  [1477117870.8466] device (wlp6s0): state change: ip-check -> secondaries (reason 'none') [80 90 0]
Oct 22 12:01:10 NetworkManager[343]: <info>  [1477117870.8469] device (wlp6s0): state change: secondaries -> activated (reason 'none') [90 100 0]
Oct 22 12:01:10 NetworkManager[343]: <info>  [1477117870.8471] manager: NetworkManager state is now CONNECTED_LOCAL
Oct 22 12:01:11 kernel: userif-3: sent link down event.
Oct 22 12:01:11 kernel: userif-3: sent link up event.
Oct 22 12:01:11 dhclient[30490]: bound to 192.168.1.103 -- renewal in 393182 seconds.
Oct 22 12:01:11 NetworkManager[343]: <info>  [1477117871.0719] manager: NetworkManager state is now CONNECTED_GLOBAL
Oct 22 12:01:11 NetworkManager[343]: <info>  [1477117871.0720] policy: set 'BEAM311512' (wlp6s0) as default for IPv4 routing and DNS
Oct 22 12:01:11 NetworkManager[343]: <info>  [1477117871.0726] dns-mgr: Writing DNS information to /usr/bin/resolvconf
Oct 22 12:01:11 NetworkManager[343]: <info>  [1477117871.1131] device (wlp6s0): Activation: successful, device activated.
Oct 22 12:01:11 nm-dispatcher[30330]: req:4 'up' [wlp6s0]: new request (0 scripts)
Oct 22 12:01:11 nm-dispatcher[30330]: req:4 'up' [wlp6s0]: completed: no scripts
Oct 22 12:01:29 cinnamon-screensaver-dialog[30469]: gkr-pam: unlocked login keyring
Oct 22 12:02:11 systemd[1]: Time has been changed
Oct 22 12:02:11 systemd[747]: Time has been changed
Oct 22 12:02:11 systemd-timesyncd[335]: Synchronized to time server 128.199.84.169:123 (0.arch.pool.ntp.org).
Oct 22 12:02:11 kernel: /dev/vmmon[0]: HostIFReadUptimeWork: detected settimeofday: fixed uptimeBase old 18445266969022939125 new 18445266969021640495 attempts 1

umaru · 2016-10-27 13:03:35

I have the exact same problem. I dont know how, but i found it is related some how to the intel video driver. The last sane drivrer package for me is the xf86-video-intel-1_2.99.917+676+g26f8ab5-1-x86_64. Downgrading to that package solved the problem for me. I know that downgrade it is not the best way but i have little or no time to do best. Hope this can help.

bryan.paradis · 2016-12-03 07:20:21

Having exactly the same problem. It just started happening though. I have had had many versions installed since your last stable version of the intel driver umaru.

bryan.paradis · 2016-12-03 08:30:09

After further googling I found this thread here: https://bbs.archlinux.org/viewtopic.php?id=215930 where a user kindly suggested that this is a problem with DRI 3. Another user and myself have confirmed that switching to DRI 2 fixes the issue.

/usr/share/X11/xorg.conf.d/20-intel.conf

Section "Device"
        Identifier  "Intel Graphics"
        Driver      "intel"
        Option      "DRI"              "2"
EndSection

tommyturbine · 2017-01-08 12:56:29

I tried the above on my 1st generation Thinkpad X1 Carbon but unfortunately using DRI 2 led to instability and occasional lockups. So, I tried using the modesetting driver instead by removing xf86-video-intel and deleting 20-intel.conf. So far everything seems to be working great, the blank screen on wake issue has gone, plus temperatures don't get quite as high when using graphically intensive software.

Arch Linux

#1 2016-10-07 01:37:51

Wake after Blank Screen does not work

#2 2016-10-11 21:05:04

Re: Wake after Blank Screen does not work

#3 2016-10-19 16:07:58

Re: Wake after Blank Screen does not work

#4 2016-10-19 16:31:14

Re: Wake after Blank Screen does not work

#5 2016-10-22 07:30:26

Re: Wake after Blank Screen does not work

#6 2016-10-27 13:03:35

Re: Wake after Blank Screen does not work

#7 2016-12-03 07:20:21

Re: Wake after Blank Screen does not work

#8 2016-12-03 08:30:09

Re: Wake after Blank Screen does not work

#9 2017-01-08 12:56:29

Re: Wake after Blank Screen does not work

Board footer