[SOLVED]Why my archlinux gets freezed after waking up from suspend?

logicipher · 2021-09-27 06:31:10

Recently I got a weird problem with my laptop. Here is what happens: I installed archlinux on my laptop and use **dwm** as my windows manager. I use no display manager or desktop environment. I also have **Nvidia driver** installed. But, sometimes when I use

systemctl suspend

to put the laptop into sleep and after several hours open the lid to wake up it, the laptop just gets freezed. The screen only shows something like

[23413.53525] done

at the upper-left corner. The remaining area got nothing but black screen. I can't open another tty or anything else. I have to push the power button to reboot.
Here is some informatin about my laptop:

kernel version: linux 5.14.6.arch1-1
memory: 16G
swap: 8G
00:02.0 VGA compatible controller: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (rev 01)
	Subsystem: Lenovo Device 3f92
	Kernel driver in use: i915
--
2c:00.0 3D controller: NVIDIA Corporation TU117M [GeForce MX450] (rev a1)
	Subsystem: Lenovo Device 3f92
	Kernel driver in use: nvidia

And here is some journalctl shows:

Sep 26 23:17:44 moon systemd-sleep[6904]: Entering sleep state 'suspend'...
Sep 26 23:17:44 moon kernel: PM: suspend entry (s2idle)
Sep 26 23:17:44 moon kernel: Filesystems sync: 0.038 seconds
Sep 27 09:14:22 moon kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
Sep 27 09:14:22 moon kernel: OOM killer disabled.
Sep 27 09:14:22 moon kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Sep 27 09:14:22 moon kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Sep 27 09:14:22 moon kernel: wlan0: deauthenticating from d4:ee:07:66:b9:56 by local choice (Reason: 3=DEAUTH_LEAVING)
Sep 27 09:14:22 moon kernel: ACPI: EC: interrupt blocked
Sep 27 09:14:22 moon kernel: ideapad_acpi VPC2004:00: Unknown event: 12
Sep 27 09:14:22 moon kernel: ACPI: EC: interrupt unblocked
Sep 27 09:14:22 moon kernel: nvme nvme0: 8/0/0 default/read/poll queues
Sep 27 09:14:22 moon kernel: r8169 0000:2d:00.0 enp45s0: Link is Down
Sep 27 09:14:22 moon kernel: ata1: SATA link down (SStatus 4 SControl 300)
Sep 27 09:14:22 moon kernel: OOM killer enabled.
Sep 27 09:14:22 moon kernel: Restarting tasks ... 
Sep 27 09:14:22 moon kernel: usb 3-1: USB disconnect, device number 2
Sep 27 09:14:22 moon kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
Sep 27 09:14:22 moon kernel: done.
Sep 27 09:14:22 moon systemd-logind[1744]: Lid closed.
Sep 27 09:14:22 moon iwd[1741]: Received Deauthentication event, reason: 3, from_ap: false
Sep 27 09:14:22 moon dhcpcd[1745]: wlan0: carrier lost
Sep 27 09:14:22 moon systemd-logind[1744]: Lid opened.
Sep 27 09:14:22 moon systemd[1]: Condition check resulted in Daily man-db regeneration being skipped.
Sep 27 09:14:22 moon dhcpcd[1745]: wlan0: deleting address fe80::a64e:704:92ce:7891
Sep 27 09:14:22 moon dhcpcd[1745]: wlan0: deleting route to 192.168.199.0/24
Sep 27 09:14:22 moon dhcpcd[1745]: wlan0: deleting default route via 192.168.199.1
Sep 27 09:14:22 moon systemd[1]: Started Verify integrity of password and group files.
Sep 27 09:14:22 moon audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=shadow comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Sep 27 09:14:22 moon kernel: audit: type=1130 audit(1632705262.370:115): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=shadow comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Sep 27 09:14:22 moon systemd[1]: shadow.service: Deactivated successfully.
Sep 27 09:14:22 moon audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=shadow comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Sep 27 09:14:22 moon kernel: audit: type=1131 audit(1632705262.406:116): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=shadow comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Sep 27 09:14:22 moon systemd-sleep[6904]: System returned from sleep state.
Sep 27 09:14:22 moon kernel: PM: suspend exit
Sep 27 09:14:22 moon kernel: wlan0: authenticate with d4:b7:09:a7:f2:92
Sep 27 09:14:22 moon kernel: wlan0: send auth to d4:b7:09:a7:f2:92 (try 1/3)
Sep 27 09:14:22 moon systemd[1]: systemd-suspend.service: Deactivated successfully.
Sep 27 09:14:22 moon systemd[1]: Finished System Suspend.
Sep 27 09:14:22 moon audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Sep 27 09:14:22 moon audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Sep 27 09:14:22 moon kernel: audit: type=1130 audit(1632705262.466:117): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Sep 27 09:14:22 moon systemd[1]: Stopped target Sleep.
Sep 27 09:14:22 moon systemd[1]: Reached target Suspend.
Sep 27 09:14:22 moon systemd[1]: Stopped target Suspend.
Sep 27 09:14:22 moon kernel: wlan0: authenticated
Sep 27 09:14:22 moon kernel: wlan0: associate with d4:b7:09:a7:f2:92 (try 1/3)
Sep 27 09:14:22 moon kernel: wlan0: RX AssocResp from d4:b7:09:a7:f2:92 (capab=0x1c31 status=0 aid=5)
Sep 27 09:14:22 moon kernel: wlan0: associated
Sep 27 09:14:22 moon kernel: wlan0: Limiting TX power to 27 (27 - 0) dBm as advertised by d4:b7:09:a7:f2:92
Sep 27 09:14:22 moon dhcpcd[1745]: wlan0: carrier acquired
Sep 27 09:14:22 moon dhcpcd[1745]: wlan0: connected to Access Point: hx-da
Sep 27 09:14:22 moon dhcpcd[1745]: wlan0: IAID 57:1f:ef:69
Sep 27 09:14:22 moon dhcpcd[1745]: wlan0: adding address fe80::dc41:224c:136:18cc
Sep 27 09:14:22 moon systemd-logind[1744]: Operation 'sleep' finished.
Sep 27 09:14:22 moon dhcpcd[1745]: wlan0: soliciting an IPv6 router
Sep 27 09:14:23 moon dhcpcd[1745]: wlan0: rebinding lease of 192.168.2.170
Sep 27 09:14:23 moon dhcpcd[1745]: wlan0: probing address 192.168.2.170/24
Sep 27 09:14:23 moon dhcpcd[1745]: wlan0: Router Advertisement from fe80::5
Sep 27 09:14:23 moon dhcpcd[1745]: wlan0: soliciting a DHCPv6 lease
Sep 27 09:14:25 moon dhcpcd[1745]: wlan0: DHCPv6 REPLY: No Addresses Available
Sep 27 09:14:26 moon dhcpcd[1745]: wlan0: DHCPv6 REPLY: No Addresses Available
Sep 27 09:14:29 moon dhcpcd[1745]: wlan0: leased 192.168.2.170 for 86400 seconds
Sep 27 09:14:29 moon dhcpcd[1745]: wlan0: adding route to 192.168.2.0/24
Sep 27 09:14:29 moon dhcpcd[1745]: wlan0: adding default route via 192.168.2.1
Sep 27 09:14:32 moon dhcpcd[1745]: wlan0: DHCPv6 REPLY: No Addresses Available
Sep 27 09:14:37 moon upowerd[4354]: treating change event as add on /sys/devices/pci0000:00/0000:00:14.0/usb3/3-1
Sep 27 09:14:41 moon dhcpcd[1745]: wlan0: DHCPv6 REPLY: No Addresses Available
Sep 27 09:14:56 moon dhcpcd[1745]: wlan0: DHCPv6 REPLY: No Addresses Available
Sep 27 09:15:24 moon dhcpcd[1745]: wlan0: DHCPv6 REPLY: No Addresses Available
Sep 27 09:15:38 moon kernel: ucsi_acpi USBC000:00: UCSI_GET_PDOS returned 0 bytes
Sep 27 09:15:41 moon kernel: ucsi_acpi USBC000:00: UCSI_GET_PDOS returned 0 bytes
Sep 27 09:16:27 moon dhcpcd[1745]: wlan0: DHCPv6 REPLY: No Addresses Available
Sep 27 09:18:39 moon dhcpcd[1745]: wlan0: DHCPv6 REPLY: No Addresses Available
Sep 27 09:21:03 moon systemd-logind[1744]: Power key pressed.
Sep 27 09:21:03 moon systemd-logind[1744]: Powering Off...

By the way, if I just suspend the laptop for a little while, I can wake up it normally.
Also, I notice every time when this happens, the dhcpcd and iwctl seem to report errors. But when it wakes up normally, they don't.

Please help and thank you so much.

Last edited by logicipher (2021-09-28 01:34:25)

seth · 2021-09-27 07:17:29

Interesting pattern, https://bbs.archlinux.org/viewtopic.php?id=269945
Are you running on the intel or the nvidia chip? Xorg log?
Does it happen w/ eg. openbox?

logicipher · 2021-09-27 07:41:58

glxinfo shows:

OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) Xe Graphics (TGL GT2)

so I guess I'm using Intel card. And the Xorg log seems to be normal.
The system seems to be running normally, but I just got a black screen and I can do nothing but reboot by pressing power button.
It seems like I can't go back to my session after waking up. Do I need a display manager?
Maybe I should try other DMs and check whether this happens.

seth · 2021-09-27 15:16:56

I don't think this is related to a DM. The common elements are
* you're using dwm
* you've an nvidia chip in the box

=> Try openbox to ensure it's not a dwm issue.
Do you have more than one outputs (and is one of them wired to the nvidia chip? xorg log, https://wiki.archlinux.org/title/Xorg#General )

logicipher · 2021-09-28 01:24:38

Thank you dude, I think I know what the issue is. I installed xfce4-power-manager and configured to lock my laptop when it gets sleeping.
But it seems that I got no way to unlock the laptop since I don't have a display manager or lock screen application.
I have remove the manager and everything seems going well.
Still, thanks for your help.

Arch Linux

#1 2021-09-27 06:31:10

[SOLVED]Why my archlinux gets freezed after waking up from suspend?

#2 2021-09-27 07:17:29

Re: [SOLVED]Why my archlinux gets freezed after waking up from suspend?

#3 2021-09-27 07:41:58

Re: [SOLVED]Why my archlinux gets freezed after waking up from suspend?

#4 2021-09-27 15:16:56

Re: [SOLVED]Why my archlinux gets freezed after waking up from suspend?

#5 2021-09-28 01:24:38

Re: [SOLVED]Why my archlinux gets freezed after waking up from suspend?

Board footer