You are not logged in.
I have an X1 Extreme with a 1050ti, running the latest proprietary NVIDIA drivers. For the last week or so, the laptop has stopped waking from suspend on opening the lid. Power button + Thinkpad light is cycling, indicating that the machine is suspended. Pressing the keyboard / power-button does nothing. This results in me needed to force a power-off by holding the power-button for >10sec.
It should be noted that the fan(s) spin up when I open the lid, and at the few occasions where I have put my laptop back into a bag after attempting to wake from suspend, I'll quickly find it extremely hot and fans running at 100%.
At the same time, the system sometimes completely freezes, with the laptop screen being filled with horizontal, colourful lines. At this point, the machine is completely frozen and I need to force a reboot by holding the power button.
I'm not sure how to debug this. I did, however, provide the output of `journalctl` at the point of one of these crashes.
Feb 26 15:23:37 x1-arch wpa_supplicant[1009]: wlp0s20f3: PMKSA-CACHE-ADDED 78:72:5d:50:ba:60 0
Feb 26 15:23:37 x1-arch wpa_supplicant[1009]: wlp0s20f3: PMKSA-CACHE-ADDED bc:26:c7:6c:97:c0 0
Feb 26 15:23:37 x1-arch wpa_supplicant[1009]: wlp0s20f3: PMKSA-CACHE-ADDED 78:72:5d:32:0b:40 0
Feb 26 15:23:37 x1-arch wpa_supplicant[1009]: wlp0s20f3: PMKSA-CACHE-ADDED 78:72:5d:4c:18:cf 0
Feb 26 15:23:37 x1-arch wpa_supplicant[1009]: wlp0s20f3: PMKSA-CACHE-ADDED 78:72:5d:32:06:4f 0
Feb 26 15:28:41 x1-arch wpa_supplicant[1009]: wlp0s20f3: PMKSA-CACHE-ADDED bc:26:c7:6c:8d:a0 0
Feb 26 15:28:41 x1-arch wpa_supplicant[1009]: wlp0s20f3: PMKSA-CACHE-ADDED 78:72:5d:32:0b:e0 0
Feb 26 15:33:44 x1-arch wpa_supplicant[1009]: wlp0s20f3: PMKSA-CACHE-ADDED bc:26:c7:6c:90:ef 0
Feb 26 15:38:00 x1-arch audit[22142]: USER_AUTH pid=22142 uid=1000 auid=1000 ses=1 msg='op=PAM:unix_chkpwd acct="vegarab" exe="/usr/bin/unix_chkpwd" hostname=? addr=? terminal=? res=success'
Feb 26 15:38:00 x1-arch kernel: Rekeying PTK for STA bc:26:c7:6c:97:cf but driver can't safely do that.
Feb 26 15:38:00 x1-arch kernel: audit: type=1100 audit(1582731480.522:150): pid=22142 uid=1000 auid=1000 ses=1 msg='op=PAM:unix_chkpwd acct="vegarab" exe="/usr/bin/unix_chkpwd" hostname=? addr=? terminal=? res=success'
Feb 26 15:40:39 x1-arch rtkit-daemon[1615]: Supervising 2 threads of 2 processes of 1 users.
Feb 26 15:40:39 x1-arch rtkit-daemon[1615]: Supervising 2 threads of 2 processes of 1 users.
-- Reboot --
Feb 26 15:44:04 x1-arch kernel: Linux version 5.5.5-arch1-1 (linux@archlinux) (gcc version 9.2.1 20200130 (Arch Linux 9.2.1+20200130-2)) #1 SMP PREEMPT Thu, 20 Feb 2020 18:23:09 +0000Also added the `journalctl` output of a point where the machine did not wake from suspend:
Feb 25 18:14:58 x1-arch systemd-logind[950]: Lid closed.
Feb 25 18:14:58 x1-arch systemd-logind[950]: Suspending...
Feb 25 18:14:58 x1-arch NetworkManager[944]: <info> [1582654498.0733] manager: sleep: sleep requested (sleeping: no enabled: yes)
Feb 25 18:14:58 x1-arch NetworkManager[944]: <info> [1582654498.0735] device (p2p-dev-wlp0s20f3): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Feb 25 18:14:58 x1-arch NetworkManager[944]: <info> [1582654498.0744] manager: NetworkManager state is now ASLEEP
Feb 25 18:14:58 x1-arch systemd[1]: Reached target Sleep.
Feb 25 18:14:58 x1-arch systemd[1]: Starting autorandr execution hook...
Feb 25 18:14:58 x1-arch systemd[1]: Starting NVIDIA system suspend actions...
Feb 25 18:14:58 x1-arch suspend[8697]: nvidia-suspend.service
Feb 25 18:14:58 x1-arch logger[8697]: <13>Feb 25 18:14:58 suspend: nvidia-suspend.service
Feb 25 18:15:00 x1-arch systemd[1]: nvidia-suspend.service: Succeeded.
Feb 25 18:15:00 x1-arch systemd[1]: Started NVIDIA system suspend actions.
Feb 25 18:15:00 x1-arch audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=nvidia-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 25 18:15:00 x1-arch audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=nvidia-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 25 18:15:00 x1-arch systemd[1]: Starting Suspend...
Feb 25 18:15:00 x1-arch kernel: audit: type=1130 audit(1582654500.745:123): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=nvidia-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 25 18:15:00 x1-arch kernel: audit: type=1131 audit(1582654500.745:124): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=nvidia-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 25 18:15:00 x1-arch autorandr[8702]: autorandr running as user vegarab (started from batch instance)
Feb 25 18:15:00 x1-arch autorandr[8702]: default
Feb 25 18:15:00 x1-arch autorandr[8702]: workstation-16
Feb 25 18:15:00 x1-arch autorandr[8702]: workstation
Feb 25 18:15:00 x1-arch autorandr[8696]: Running autorandr as vegarab for display :0
Feb 25 18:15:00 x1-arch systemd[1]: autorandr.service: Succeeded.
Feb 25 18:15:00 x1-arch systemd[1]: Started autorandr execution hook.
Feb 25 18:15:00 x1-arch audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=autorandr comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 25 18:15:00 x1-arch audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=autorandr comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 25 18:15:00 x1-arch kernel: audit: type=1130 audit(1582654500.768:125): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=autorandr comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 25 18:15:00 x1-arch kernel: audit: type=1131 audit(1582654500.768:126): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=autorandr comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
-- Reboot --
Feb 26 11:02:51 x1-arch kernel: Linux version 5.5.5-arch1-1 (linux@archlinux) (gcc version 9.2.1 20200130 (Arch Linux 9.2.1+20200130-2)) #1 SMP PREEMPT Thu, 20 Feb 2020 18:23:09 +0000The last thing I did before closing the lid was using autorandr to disconnect an external display, remove the USB-C cable to the display and then close the lid. It seems autorandr is still doing something after the close-lid action is evoked. Could this be related to not being able to wake again?
Last edited by vegarab (2020-02-26 16:03:54)
Offline