You are not logged in.
I can't find any mention of this issue anywhere online so maybe I'm just the only unlucky one here, but for the last 7 months or so my TP T430 has failed to resume after suspending. The machine will come back on and be usable for about 5 seconds before becoming mostly unresponsive. The mouse cursor still moves, open terminals might echo keypresses, maybe the nm-applet connecting animation keeps going, but the rest of the machine is dead and I have to turn it off, switching to a VT, the reboot command, etc stop working. The kernel log usually contains all sorts of errors, but they never seem to survive after rebooting, so the only way to see them is during my 5 second window of usability.
Looking back at my logs it seems to have started when I upgraded from kernel 4.2.5-1 to 4.3.3-2, although a bunch of other packages were upgraded as well. Can't imagine they'd cause any issues, I looked through them and nothing that could affect suspend was upgraded.
Anyone else running into this problem? I've started using hibernate now, which works just fine, but it would be nice to have my suspend back...
Offline
Can you post a screenshot of the kernel log errors? Are they available using journalctl? My guess would be a kernel module of sorts which crashes upon resume... perhaps a network driver.
Even if you can't snag the logs at the time of the crash, the boot log (journalctl -b) can still provide insight into the issue, so please post that as well!
Offline
I tried grabbing logs immediately after resume, but no luck, dmesg/journalctl/etc pretty much hang. Here's the very first log from when it first started happening:
Jan 01 09:20:33 novo systemd-logind[993]: Suspend key pressed.
Jan 01 09:20:33 novo root[10677]: SleepButton pressed
Jan 01 09:20:33 novo NetworkManager[1104]: <info> sleep requested (sleeping: no enabled: yes)
Jan 01 09:20:33 novo NetworkManager[1104]: <info> sleeping...
Jan 01 09:20:33 novo NetworkManager[1104]: <info> (wlp3s0): device state change: activated -> unmanaged (reason 'sleeping') [100 10 37]
Jan 01 09:20:33 novo NetworkManager[1104]: <info> (wlp3s0): canceled DHCP transaction, DHCP client pid 5830
Jan 01 09:20:33 novo NetworkManager[1104]: <info> (wlp3s0): DHCPv4 state changed bound -> done
Jan 01 09:20:33 novo kernel: wlp3s0: deauthenticating from 34:7a:60:8d:62:e3 by local choice (Reason: 3=DEAUTH_LEAVING)
Jan 01 09:20:33 novo wpa_supplicant[1781]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=34:7a:60:8d:62:e3 reason=3 locally_generated=1
Jan 01 09:20:33 novo NetworkManager[1104]: <info> Removing DNS information from /usr/bin/resolvconf
Jan 01 09:20:33 novo NetworkManager[1104]: <info> NetworkManager state is now ASLEEP
Jan 01 09:20:33 novo NetworkManager[1104]: <info> (enp0s25): device state change: unavailable -> unmanaged (reason 'sleeping') [20 10 37]
Jan 01 09:20:33 novo dbus[1000]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Jan 01 09:20:33 novo systemd[1]: Starting Network Manager Script Dispatcher Service...
Jan 01 09:20:33 novo dbus[1000]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jan 01 09:20:33 novo systemd[1]: Started Network Manager Script Dispatcher Service.
Jan 01 09:20:33 novo wpa_supplicant[1781]: nl80211: deinit ifname=wlp3s0 disabled_11b_rates=0
Jan 01 09:20:34 novo NetworkManager[1104]: <warn> Failed to GDBus.Error:fi.w1.wpa_supplicant1.NotConnected: This interface is not connected: disconnect.
Jan 01 09:20:34 novo systemd[1]: Reached target Sleep.
Jan 01 09:20:34 novo kernel: e1000e: enp0s25 NIC Link is Down
Jan 01 09:20:34 novo systemd[1]: Starting Suspend...
Jan 01 09:20:34 novo systemd-sleep[10760]: Suspending system...
-- Reboot --
Jan 01 09:55:53 novo systemd-journald[165]: Runtime journal (/run/log/journal/) is currently using 8.0M.
Maximum allowed usage is set to 383.2M.
Leaving at least 574.9M free (of currently available 3.7G of space).
Enforced usage limit is thus 383.2M, of which 375.2M are still available.
Jan 01 09:55:53 novo systemd-journald[165]: System journal (/var/log/journal/) is currently using 2.1G.
Maximum allowed usage is set to 4.0G.
Leaving at least 4.0G free (of currently available 31.2G of space).
Enforced usage limit is thus 4.0G, of which 1.8G are still available.
Jan 01 09:55:53 novo systemd-journald[165]: Time spent on flushing to /var is 1.242ms for 2 entries.
Jan 01 09:55:53 novo kernel: Initializing cgroup subsys cpuset
Jan 01 09:55:53 novo kernel: Initializing cgroup subsys cpu
Jan 01 09:55:53 novo kernel: Initializing cgroup subsys cpuacct
Jan 01 09:55:53 novo kernel: Linux version 4.3.3-2-ARCH (builduser@tobias) (gcc version 5.3.0 (GCC) ) #1 SMP PREEMPT Wed Dec 23 20:09:18 CET 2015
Jan 01 09:55:53 novo kernel: Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=c7dbaae1-b6ee-4610-adb0-2efddd99fd5f rw
Jan 01 09:55:53 novo kernel: x86/fpu: xstate_offset[2]: 0240, xstate_sizes[2]: 0100
Jan 01 09:55:53 novo kernel: x86/fpu: Supporting XSAVE feature 0x01: 'x87 floating point registers'
Jan 01 09:55:53 novo kernel: x86/fpu: Supporting XSAVE feature 0x02: 'SSE registers'
Jan 01 09:55:53 novo kernel: x86/fpu: Supporting XSAVE feature 0x04: 'AVX registers'
Jan 01 09:55:53 novo kernel: x86/fpu: Enabled xstate features 0x7, context size is 0x340 bytes, using 'standard' format.
Jan 01 09:55:53 novo kernel: x86/fpu: Using 'eager' FPU context switches.
Jan 01 09:55:53 novo kernel: e820: BIOS-provided physical RAM map:
Jan 01 09:55:53 novo kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009d7ff] usable
Jan 01 09:55:53 novo kernel: BIOS-e820: [mem 0x000000000009d800-0x000000000009ffff] reserved
Jan 01 09:55:53 novo kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jan 01 09:55:53 novo kernel: BIOS-e820: [mem 0x0000000000100000-0x000000001fffffff] usable
Jan 01 09:55:53 novo kernel: BIOS-e820: [mem 0x0000000020000000-0x00000000201fffff] reserved
Jan 01 09:55:53 novo kernel: BIOS-e820: [mem 0x0000000020200000-0x0000000040003fff] usable
Jan 01 09:55:53 novo kernel: BIOS-e820: [mem 0x0000000040004000-0x0000000040004fff] reserved
Jan 01 09:55:53 novo kernel: BIOS-e820: [mem 0x0000000040005000-0x00000000ad573fff] usable
Jan 01 09:55:53 novo kernel: BIOS-e820: [mem 0x00000000ad574000-0x00000000bae9efff] reserved
Jan 01 09:55:53 novo kernel: BIOS-e820: [mem 0x00000000bae9f000-0x00000000baf9efff] ACPI NVS
Jan 01 09:55:53 novo kernel: BIOS-e820: [mem 0x00000000baf9f000-0x00000000baffefff] ACPI data
Jan 01 09:55:53 novo kernel: BIOS-e820: [mem 0x00000000bafff000-0x00000000bf9fffff] reservedAs you can see, everything logged after resume is never saved to disk, it just continues after reboot. I'm tempted to rebuild the last working kernel myself and boot that to see if it's really a kernel issue...
Offline