ThinkPad P15v Gen 3 AMD black screen with blinking cursor on suspend

endlessrevision · 2025-12-25 02:32:39

I have a ThinkPad P15V Gen 3 AMD with a Nvidia RTX A2000 running the most recent version of the linux kernel which has been having issues with suspend. After installing the required Nvidia modules, I've been stuck at this current state where the system appears to suspend properly (as I don't see any glaring errors when looking at journalctl, but I'm greeted with a black screen with a blinking cursor, similar to after booting into Arch and unlocking my LUKS drives without the drive unlock prompts.

I've tried looking at various forum posts and wiki pages, and it seems like I've sort of narrowed it down to either Nvidia, the NVME drives (everything is on a SK Hynix SSD), or the ath11k_pci module which are most of the errors I see on journalctl, but I'm not too sure how to proceed. I've tried the following:

Nvidia related: I installed the nvidia-utils package and the appropriate drivers, and that got me from the screen freezing, which was how it was after installing, to the black screen/current state we are in now.
network/ath11k related: a solution listed in the wiki here for P16s AMD which was sort of similar as a shot in the dark but that wasn't the solution. Similar attempts to disable wifi/bluetooth through e.g. rfkill have also not been useful.
SSD/NVMe related: I tried the kernel parameter iommu=soft which just gets us to the blinking cursor black screen earlier. Previously it just blanks completely before showing the black screen if I press the keyboard.

I'm at my wit's end on what else I can do. Are there any other things to try?

Here's a recent journalctl log related to suspend:

Dec 23 19:09:12 nightfall systemd-logind[1710]: The system will suspend now!
Dec 23 19:09:12 nightfall rtkit-daemon[2509]: Demoting known real-time threads.
Dec 23 19:09:12 nightfall rtkit-daemon[2509]: Successfully demoted thread 3094 of process 2921.
Dec 23 19:09:12 nightfall NetworkManager[1706]: <info>  [1766545752.4883] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Dec 23 19:09:12 nightfall rtkit-daemon[2509]: Successfully demoted thread 2508 of process 2501.
Dec 23 19:09:12 nightfall rtkit-daemon[2509]: Successfully demoted thread 2501 of process 2501.
Dec 23 19:09:12 nightfall rtkit-daemon[2509]: Successfully demoted thread 2516 of process 2503.
Dec 23 19:09:12 nightfall rtkit-daemon[2509]: Successfully demoted thread 2503 of process 2503.
Dec 23 19:09:12 nightfall rtkit-daemon[2509]: Successfully demoted thread 2528 of process 2502.
Dec 23 19:09:12 nightfall rtkit-daemon[2509]: Successfully demoted thread 2502 of process 2502.
Dec 23 19:09:12 nightfall rtkit-daemon[2509]: Demoted 7 threads.
Dec 23 19:09:12 nightfall NetworkManager[1706]: <info>  [1766545752.6108] device (enp4s0f0): state change: unavailable -> unmanaged (reason 'unmanaged-nm-disabled', managed-type: 'full')
Dec 23 19:09:12 nightfall kernel: r8169 0000:04:00.0 enp4s0f0: Link is Down
Dec 23 19:09:12 nightfall NetworkManager[1706]: <info>  [1766545752.6183] device (p2p-dev-wlp2s0): state change: disconnected -> unmanaged (reason 'unmanaged-nm-disabled', managed-type: 'full')
Dec 23 19:09:12 nightfall NetworkManager[1706]: <info>  [1766545752.6187] manager: NetworkManager state is now DISABLED (ASLEEP)
Dec 23 19:09:12 nightfall NetworkManager[1706]: <info>  [1766545752.6191] device (wlp2s0): state change: activated -> deactivating (reason 'sleeping', managed-type: 'full')
Dec 23 19:09:12 nightfall systemd[1]: Starting Network Manager Script Dispatcher Service...
░░ Subject: A start job for unit NetworkManager-dispatcher.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit NetworkManager-dispatcher.service has begun execution.
░░ 
░░ The job identifier is 1769.
Dec 23 19:09:12 nightfall systemd[1]: Started Network Manager Script Dispatcher Service.
░░ Subject: A start job for unit NetworkManager-dispatcher.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit NetworkManager-dispatcher.service has finished successfully.
░░ 
░░ The job identifier is 1769.
Dec 23 19:09:12 nightfall dhcpcd[1722]: wlp2s0: carrier lost
Dec 23 19:09:12 nightfall kernel: wlp2s0: deauthenticating from 9c:4f:5f:92:26:31 by local choice (Reason: 3=DEAUTH_LEAVING)
Dec 23 19:09:12 nightfall dhcpcd[1722]: wlp2s0: deleting address fe80::a92:9c6a:19f1:5d3b
Dec 23 19:09:12 nightfall avahi-daemon[1707]: Withdrawing address record for fe80::a92:9c6a:19f1:5d3b on wlp2s0.
Dec 23 19:09:12 nightfall avahi-daemon[1707]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::a92:9c6a:19f1:5d3b.
Dec 23 19:09:12 nightfall avahi-daemon[1707]: Joining mDNS multicast group on interface wlp2s0.IPv6 with address fe80::77de:703f:1aa1:6983.
Dec 23 19:09:12 nightfall avahi-daemon[1707]: Withdrawing address record for 192.168.84.174 on wlp2s0.
Dec 23 19:09:12 nightfall wpa_supplicant[1902]: nl80211: send_event_marker failed: Source based routing not supported
Dec 23 19:09:12 nightfall wpa_supplicant[1902]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=9c:4f:5f:92:26:31 reason=3 locally_generated=1
Dec 23 19:09:12 nightfall dhcpcd[1722]: wlp2s0: deleting route to 192.168.84.0/24
Dec 23 19:09:12 nightfall dhcpcd[1722]: wlp2s0: deleting default route via 192.168.84.1
Dec 23 19:09:12 nightfall wpa_supplicant[1902]: wlp2s0: CTRL-EVENT-DSCP-POLICY clear_all
Dec 23 19:09:12 nightfall NetworkManager[1706]: <info>  [1766545752.7323] device (wlp2s0): supplicant interface state: completed -> disconnected
Dec 23 19:09:12 nightfall NetworkManager[1706]: <info>  [1766545752.7324] device (wlp2s0): state change: deactivating -> disconnected (reason 'sleeping', managed-type: 'full')
Dec 23 19:09:12 nightfall avahi-daemon[1707]: Withdrawing address record for fe80::77de:703f:1aa1:6983 on wlp2s0.
Dec 23 19:09:12 nightfall avahi-daemon[1707]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::77de:703f:1aa1:6983.
Dec 23 19:09:12 nightfall NetworkManager[1706]: <info>  [1766545752.7329] dhcp4 (wlp2s0): canceled DHCP transaction
Dec 23 19:09:12 nightfall avahi-daemon[1707]: Interface wlp2s0.IPv6 no longer relevant for mDNS.
Dec 23 19:09:12 nightfall NetworkManager[1706]: <info>  [1766545752.7329] dhcp4 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)
Dec 23 19:09:12 nightfall NetworkManager[1706]: <info>  [1766545752.7329] dhcp4 (wlp2s0): state changed no lease
Dec 23 19:09:12 nightfall avahi-daemon[1707]: Interface wlp2s0.IPv4 no longer relevant for mDNS.
Dec 23 19:09:12 nightfall avahi-daemon[1707]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 192.168.84.175.
Dec 23 19:09:12 nightfall avahi-daemon[1707]: Withdrawing address record for 192.168.84.175 on wlp2s0.
Dec 23 19:09:12 nightfall dhcpcd[1722]: wlp2s0: old hardware address: 8c:3b:4a:44:ec:1e
Dec 23 19:09:12 nightfall dhcpcd[1722]: wlp2s0: new hardware address: f2:c0:ed:aa:b1:a8
Dec 23 19:09:12 nightfall NetworkManager[1706]: <info>  [1766545752.7629] device (wlp2s0): set-hw-addr: set MAC address to F2:C0:ED:AA:B1:A8 (scanning)
Dec 23 19:09:12 nightfall avahi-daemon[1707]: Joining mDNS multicast group on interface wlp2s0.IPv4 with address 192.168.84.175.
Dec 23 19:09:12 nightfall avahi-daemon[1707]: New relevant interface wlp2s0.IPv4 for mDNS.
Dec 23 19:09:12 nightfall avahi-daemon[1707]: Registering new address record for 192.168.84.175 on wlp2s0.IPv4.
Dec 23 19:09:12 nightfall avahi-daemon[1707]: Withdrawing address record for 192.168.84.175 on wlp2s0.
Dec 23 19:09:12 nightfall avahi-daemon[1707]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 192.168.84.175.
Dec 23 19:09:12 nightfall wpa_supplicant[1902]: wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=US
Dec 23 19:09:12 nightfall avahi-daemon[1707]: Interface wlp2s0.IPv4 no longer relevant for mDNS.
Dec 23 19:09:12 nightfall wpa_supplicant[1902]: wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=US
Dec 23 19:09:12 nightfall NetworkManager[1706]: <info>  [1766545752.8398] device (wlp2s0): supplicant interface state: disconnected -> interface_disabled
Dec 23 19:09:12 nightfall NetworkManager[1706]: <info>  [1766545752.8399] device (wlp2s0): supplicant interface state: interface_disabled -> disconnected
Dec 23 19:09:12 nightfall NetworkManager[1706]: <info>  [1766545752.8403] device (wlp2s0): state change: disconnected -> unmanaged (reason 'unmanaged-nm-disabled', managed-type: 'full')
Dec 23 19:09:12 nightfall dhcpcd[1722]: wlp2s0: old hardware address: f2:c0:ed:aa:b1:a8
Dec 23 19:09:12 nightfall dhcpcd[1722]: wlp2s0: new hardware address: 8c:3b:4a:44:ec:1e
Dec 23 19:09:12 nightfall NetworkManager[1706]: <info>  [1766545752.9253] device (wlp2s0): set-hw-addr: reset MAC address to 8C:3B:4A:44:EC:1E (unmanage)
Dec 23 19:09:12 nightfall wpa_supplicant[1902]: wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=US
Dec 23 19:09:12 nightfall systemd[1]: Reached target Sleep.
░░ Subject: A start job for unit sleep.target has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit sleep.target has finished successfully.
░░ 
░░ The job identifier is 1893.
Dec 23 19:09:12 nightfall wpa_supplicant[1902]: wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=US
Dec 23 19:09:12 nightfall systemd[1]: Starting NVIDIA system suspend actions...
░░ Subject: A start job for unit nvidia-suspend.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit nvidia-suspend.service has begun execution.
░░ 
░░ The job identifier is 1894.
Dec 23 19:09:12 nightfall wpa_supplicant[1902]: p2p-dev-wlp2s0: CTRL-EVENT-DSCP-POLICY clear_all
Dec 23 19:09:12 nightfall wpa_supplicant[1902]: p2p-dev-wlp2s0: CTRL-EVENT-DSCP-POLICY clear_all
Dec 23 19:09:12 nightfall wpa_supplicant[1902]: nl80211: deinit ifname=p2p-dev-wlp2s0 disabled_11b_rates=0
Dec 23 19:09:12 nightfall suspend[7759]: nvidia-suspend.service
Dec 23 19:09:12 nightfall logger[7759]: <13>Dec 23 19:09:12 suspend: nvidia-suspend.service
Dec 23 19:09:13 nightfall wpa_supplicant[1902]: wlp2s0: CTRL-EVENT-DSCP-POLICY clear_all
Dec 23 19:09:13 nightfall wpa_supplicant[1902]: wlp2s0: CTRL-EVENT-DSCP-POLICY clear_all
Dec 23 19:09:13 nightfall wpa_supplicant[1902]: nl80211: deinit ifname=wlp2s0 disabled_11b_rates=0
Dec 23 19:09:13 nightfall systemd[2485]: Reached target Smart Card.
░░ Subject: A start job for unit UNIT has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit UNIT has finished successfully.
░░ 
░░ The job identifier is 265.
Dec 23 19:09:13 nightfall systemd[2485]: Reached target Sound Card.
░░ Subject: A start job for unit UNIT has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit UNIT has finished successfully.
░░ 
░░ The job identifier is 250.
Dec 23 19:09:15 nightfall systemd[1]: nvidia-suspend.service: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit nvidia-suspend.service has successfully entered the 'dead' state.
Dec 23 19:09:15 nightfall systemd[1]: Finished NVIDIA system suspend actions.
░░ Subject: A start job for unit nvidia-suspend.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit nvidia-suspend.service has finished successfully.
░░ 
░░ The job identifier is 1894.
Dec 23 19:09:15 nightfall systemd[1]: nvidia-suspend.service: Consumed 1.355s CPU time over 2.357s wall clock time, 55.5M memory peak.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit nvidia-suspend.service completed and consumed the indicated resources.
Dec 23 19:09:15 nightfall systemd[1]: Starting System Suspend...
░░ Subject: A start job for unit systemd-suspend.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit systemd-suspend.service has begun execution.
░░ 
░░ The job identifier is 1890.
Dec 23 19:09:15 nightfall systemd-sleep[7821]: User sessions remain unfrozen on explicit request ($SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=0).
Dec 23 19:09:15 nightfall systemd-sleep[7821]: This is not recommended, and might result in unexpected behavior, particularly
Dec 23 19:09:15 nightfall systemd-sleep[7821]: in suspend-then-hibernate operations or setups with encrypted home directories.
Dec 23 19:09:15 nightfall systemd-sleep[7821]: Performing sleep operation 'suspend'...
░░ Subject: System sleep state suspend entered
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The system has now entered the suspend sleep state.
Dec 23 19:09:15 nightfall kernel: PM: suspend entry (s2idle)
Dec 23 19:09:15 nightfall kernel: Filesystems sync: 0.023 seconds

Last edited by endlessrevision (2025-12-25 04:14:02)

seth · 2025-12-27 00:23:36

Please never use "-x" w/ journalctl, it's effectively just spam.
The journal stops at the suspend entry and I assume you move a way from the wakeup failure by pushing the power button: avoid that at all costs.
See whether you can switch the VT (ctrl+alt+f3) or ssh into the system or reboot by frenetically pressing ctrl+alt+del (iirc systemd interprets 7 consecutive invocations as reboot desire) or the https://wiki.archlinux.org/title/Keyboa … el_(SysRq) (nb. you'll have to explicitly enable that *before* the suspend)

From the journal fragment you're running NM and dhcpcd and I can't tell whether you've configured dhcpcd as NM dhcp backend, but make sure to not enable multiple network managing services.
Because I'm not sure why NM thinks

Dec 23 19:09:12 nightfall NetworkManager[1706]: <info>  [1766545752.7629] device (wlp2s0): set-hw-addr: set MAC address to F2:C0:ED:AA:B1:A8 (scanning)

now is a good time to scan the network…
In doubt please post the output of

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

Ceterum censeo, in case there's a parallel windows installation see the 3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

endlessrevision · 2025-12-27 04:27:30

I tried switching to a different TTY a few times and I noticed it basically freezes at some point and stops accepting keyboard input - on one occasion I was able to log in, another I changed tty a few times and got stuck before doing anything more, and a third time I was too late and any attempts to switch were unsuccessful. I also could not SSH into the system after suspend. It also rebooted a few times on keyboard input (which wasn't what I was trying to do and doesn't seem like expected behavior). Regardless I still end up with the same journalctl output where it ends at the suspend entry.

I didn't end up setting dhcpcd as my NM backend; I think I just copied what I did from an old install so I just removed it for simplicity.

Also disabled Windows fast start/hibernation and I noticed I'm no longer getting issues where it's telling me filesystem corrupt and need to run fsck, so that at least seems to be something good.

seth · 2025-12-27 09:40:38

seth wrote:

reboot windows and linux twice for voodo reasons

Only half of that is a joke (it's based on anecdotal evidence and probably relates to the inner state of the firmware but ultimately not sufficiently explained - hence "voodoo")

Then enable the sysrq because it's gonna be your best shot at maybe getting a clean reboot (which requires the entire REISUB dance, no, not for voodoo reasons ) to preserve a journal maybe shedding some light on this.
Then keep us posted on the status quo.

endlessrevision · 2026-04-29 23:16:26

Extremely long time no reply - ended up getting way too busy to take a look at this laptop. Updated the kernel and everything to the latest and fixed any issues that came up. I enabled SysRq and I can get it to successfully reboot after the black screen but it doesn't seem like it has much new journal information as the journalctl logs still end with suspend entry (s2idle). New thought is if this could be related to LUKS as I have an encrypted root and swap partition? I noticed this which seems to be new:

Apr 29 16:03:57 nightfall systemd[1]: Starting System Suspend...
Apr 29 16:03:57 nightfall wpa_supplicant[1930]: wlp2s0: CTRL-EVENT-DSCP-POLICY clear_all
Apr 29 16:03:57 nightfall systemd-sleep[2822]: User sessions remain unfrozen on explicit request ($SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=0).
Apr 29 16:03:57 nightfall systemd-sleep[2822]: This is not recommended, and might result in unexpected behavior, particularly
Apr 29 16:03:57 nightfall systemd-sleep[2822]: in suspend-then-hibernate operations or setups with encrypted home directories.

Full logs from the recent suspend:

Apr 29 16:03:57 nightfall systemd-logind[1719]: The system will suspend now!
Apr 29 16:03:57 nightfall rtkit-daemon[2003]: Demoting known real-time threads.
Apr 29 16:03:57 nightfall rtkit-daemon[2003]: Successfully demoted thread 2002 of process 1991.
Apr 29 16:03:57 nightfall NetworkManager[1714]: <info>  [1777503837.1335] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Apr 29 16:03:57 nightfall rtkit-daemon[2003]: Successfully demoted thread 1991 of process 1991.
Apr 29 16:03:57 nightfall NetworkManager[1714]: <info>  [1777503837.1337] device (enp4s0f0): state change: unavailable -> unmanaged (reason 'unmanaged-nm-disabled', managed-type: 'full')
Apr 29 16:03:57 nightfall rtkit-daemon[2003]: Successfully demoted thread 2012 of process 1992.
Apr 29 16:03:57 nightfall rtkit-daemon[2003]: Successfully demoted thread 1992 of process 1992.
Apr 29 16:03:57 nightfall rtkit-daemon[2003]: Successfully demoted thread 2004 of process 1993.
Apr 29 16:03:57 nightfall rtkit-daemon[2003]: Successfully demoted thread 1993 of process 1993.
Apr 29 16:03:57 nightfall rtkit-daemon[2003]: Demoted 6 threads.
Apr 29 16:03:57 nightfall NetworkManager[1714]: <info>  [1777503837.1411] device (p2p-dev-wlp2s0): state change: disconnected -> unmanaged (reason 'unmanaged-nm-disabled', managed-type: 'full')
Apr 29 16:03:57 nightfall NetworkManager[1714]: <info>  [1777503837.1414] manager: NetworkManager state is now DISABLED (ASLEEP)
Apr 29 16:03:57 nightfall NetworkManager[1714]: <info>  [1777503837.1416] device (wlp2s0): state change: activated -> deactivating (reason 'sleeping', managed-type: 'full')
Apr 29 16:03:57 nightfall kernel: wlp2s0: deauthenticating from 3c:64:cf:94:be:e2 by local choice (Reason: 3=DEAUTH_LEAVING)
Apr 29 16:03:57 nightfall wpa_supplicant[1930]: nl80211: send_event_marker failed: Source based routing not supported
Apr 29 16:03:57 nightfall wpa_supplicant[1930]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=3c:64:cf:94:be:e2 reason=3 locally_generated=1
Apr 29 16:03:57 nightfall wpa_supplicant[1930]: wlp2s0: CTRL-EVENT-DSCP-POLICY clear_all
Apr 29 16:03:57 nightfall NetworkManager[1714]: <info>  [1777503837.2493] device (wlp2s0): supplicant interface state: completed -> disconnected
Apr 29 16:03:57 nightfall NetworkManager[1714]: <info>  [1777503837.2495] device (wlp2s0): state change: deactivating -> disconnected (reason 'sleeping', managed-type: 'full')
Apr 29 16:03:57 nightfall avahi-daemon[1715]: Withdrawing address record for fe80::c921:e0d4:d490:e4e0 on wlp2s0.
Apr 29 16:03:57 nightfall avahi-daemon[1715]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::c921:e0d4:d490:e4e0.
Apr 29 16:03:57 nightfall avahi-daemon[1715]: Interface wlp2s0.IPv6 no longer relevant for mDNS.
Apr 29 16:03:57 nightfall NetworkManager[1714]: <info>  [1777503837.2607] dhcp4 (wlp2s0): canceled DHCP transaction
Apr 29 16:03:57 nightfall NetworkManager[1714]: <info>  [1777503837.2607] dhcp4 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)
Apr 29 16:03:57 nightfall NetworkManager[1714]: <info>  [1777503837.2608] dhcp4 (wlp2s0): state changed no lease
Apr 29 16:03:57 nightfall avahi-daemon[1715]: Interface wlp2s0.IPv4 no longer relevant for mDNS.
Apr 29 16:03:57 nightfall avahi-daemon[1715]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 192.168.0.13.
Apr 29 16:03:57 nightfall avahi-daemon[1715]: Withdrawing address record for 192.168.0.13 on wlp2s0.
Apr 29 16:03:57 nightfall NetworkManager[1714]: <info>  [1777503837.2981] device (wlp2s0): set-hw-addr: set MAC address to 3E:23:28:14:F4:93 (scanning)
Apr 29 16:03:57 nightfall avahi-daemon[1715]: Joining mDNS multicast group on interface wlp2s0.IPv4 with address 192.168.0.13.
Apr 29 16:03:57 nightfall avahi-daemon[1715]: New relevant interface wlp2s0.IPv4 for mDNS.
Apr 29 16:03:57 nightfall avahi-daemon[1715]: Registering new address record for 192.168.0.13 on wlp2s0.IPv4.
Apr 29 16:03:57 nightfall avahi-daemon[1715]: Withdrawing address record for 192.168.0.13 on wlp2s0.
Apr 29 16:03:57 nightfall avahi-daemon[1715]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 192.168.0.13.
Apr 29 16:03:57 nightfall wpa_supplicant[1930]: wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=US
Apr 29 16:03:57 nightfall avahi-daemon[1715]: Interface wlp2s0.IPv4 no longer relevant for mDNS.
Apr 29 16:03:57 nightfall wpa_supplicant[1930]: wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=US
Apr 29 16:03:57 nightfall systemd-resolved[1282]: wlp2s0: Bus client set default route setting: no
Apr 29 16:03:57 nightfall systemd-resolved[1282]: wlp2s0: Bus client reset DNS server list.
Apr 29 16:03:57 nightfall NetworkManager[1714]: <info>  [1777503837.3814] device (wlp2s0): supplicant interface state: disconnected -> interface_disabled
Apr 29 16:03:57 nightfall NetworkManager[1714]: <info>  [1777503837.3815] device (wlp2s0): supplicant interface state: interface_disabled -> disconnected
Apr 29 16:03:57 nightfall NetworkManager[1714]: <info>  [1777503837.3818] device (wlp2s0): state change: disconnected -> unmanaged (reason 'unmanaged-nm-disabled', managed-type: 'full')
Apr 29 16:03:57 nightfall NetworkManager[1714]: <info>  [1777503837.4589] device (wlp2s0): set-hw-addr: reset MAC address to 8C:3B:4A:44:EC:1E (unmanage)
Apr 29 16:03:57 nightfall systemd[1]: Reached target Sleep.
Apr 29 16:03:57 nightfall systemd[1]: Starting NVIDIA system suspend actions...
Apr 29 16:03:57 nightfall wpa_supplicant[1930]: p2p-dev-wlp2s0: CTRL-EVENT-DSCP-POLICY clear_all
Apr 29 16:03:57 nightfall suspend[2817]: nvidia-suspend.service
Apr 29 16:03:57 nightfall logger[2817]: <13>Apr 29 16:03:57 suspend: nvidia-suspend.service
Apr 29 16:03:57 nightfall wpa_supplicant[1930]: p2p-dev-wlp2s0: CTRL-EVENT-DSCP-POLICY clear_all
Apr 29 16:03:57 nightfall wpa_supplicant[1930]: nl80211: deinit ifname=p2p-dev-wlp2s0 disabled_11b_rates=0
Apr 29 16:03:57 nightfall systemd[1]: nvidia-suspend.service: Deactivated successfully.
Apr 29 16:03:57 nightfall systemd[1]: Finished NVIDIA system suspend actions.
Apr 29 16:03:57 nightfall systemd[1]: Starting System Suspend...
Apr 29 16:03:57 nightfall wpa_supplicant[1930]: wlp2s0: CTRL-EVENT-DSCP-POLICY clear_all
Apr 29 16:03:57 nightfall systemd-sleep[2822]: User sessions remain unfrozen on explicit request ($SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=0).
Apr 29 16:03:57 nightfall systemd-sleep[2822]: This is not recommended, and might result in unexpected behavior, particularly
Apr 29 16:03:57 nightfall systemd-sleep[2822]: in suspend-then-hibernate operations or setups with encrypted home directories.
Apr 29 16:03:57 nightfall systemd[1]: NetworkManager-wait-online.service: Deactivated successfully.
Apr 29 16:03:57 nightfall systemd[1]: Stopped Network Manager Wait Online.
Apr 29 16:03:57 nightfall systemd[1]: Stopping Network Manager...
Apr 29 16:03:57 nightfall NetworkManager[1714]: <info>  [1777503837.6030] caught SIGTERM, shutting down normally.
Apr 29 16:03:57 nightfall wpa_supplicant[1930]: wlp2s0: CTRL-EVENT-DSCP-POLICY clear_all
Apr 29 16:03:57 nightfall wpa_supplicant[1930]: nl80211: deinit ifname=wlp2s0 disabled_11b_rates=0
Apr 29 16:03:57 nightfall NetworkManager[1714]: <info>  [1777503837.6328] exiting (success)
Apr 29 16:03:57 nightfall systemd[1]: NetworkManager.service: Deactivated successfully.
Apr 29 16:03:57 nightfall systemd[1]: Stopped Network Manager.
Apr 29 16:03:57 nightfall avahi-daemon[1715]: Withdrawing workstation service for wlp2s0.
Apr 29 16:03:57 nightfall systemd[1]: Starting Load/Save RF Kill Switch Status...
Apr 29 16:03:57 nightfall systemd[1]: Started Load/Save RF Kill Switch Status.
Apr 29 16:03:58 nightfall systemd-sleep[2822]: Performing sleep operation 'suspend'...
Apr 29 16:03:58 nightfall kernel: PM: suspend entry (s2idle)

seth · 2026-04-30 07:28:16

I can get it to successfully reboot after the black screen but it doesn't seem like it has much new journal information as the journalctl logs still end with suspend entry (s2idle).

Did you do the entire sysrq+REISUB dance (and wait like 3 seconds between each step)?

New thought is if this could be related to LUKS as I have an encrypted root and swap partition?

x-ref, https://bbs.archlinux.org/viewtopic.php?id=311852 but no LUKS

endlessrevision · 2026-05-01 04:37:24

Did you do the entire sysrq+REISUB dance (and wait like 3 seconds between each step)?

Not while you replied, just Alt+SysRq+B to reboot the first time, but I am fairly certain I did it twice today and the journalctl logs yield marginally more information than before, there's a tiny bit about my Yubikey. Makes me think I either didn't run the sequence properly but I feel like there's no way to verify any of the other actions in the REISUB dance like you said.

Apr 30 21:26:51 nightfall systemd-sleep[3776]: Performing sleep operation 'suspend'...
Apr 30 21:26:51 nightfall kernel: PM: suspend entry (s2idle)
Apr 30 21:26:51 nightfall kernel: Filesystems sync: 0.009 seconds
Apr 30 21:26:51 nightfall systemd[1983]: Reached target Smart Card.
Apr 30 21:26:51 nightfall systemd[1983]: Reached target Sound Card.
Apr 30 21:26:52 nightfall systemd-logind[1729]: Watching system buttons on /dev/input/event9 (Yubico YubiKey OTP+FIDO+CCID)

Might as well read the other thread to see if there's any food for thought there, but glad it rules out one thing?

After reading the other thread and some more browsing I'm more convinced it could either be SSD/NVMe related (strange, since I run the same SSD on my P52 and it is fine, pending if that will be the same case for my P53 which I've yet to set up) or laptop specific based on this page for a similar ThinkPad that is a generation after mine and has similar issues. The thing is that none of those workarounds seemed to have worked which worries me that it might be some issue that is relatively unheard of.

Last edited by endlessrevision (2026-05-01 07:12:18)

seth · 2026-05-01 10:51:11

The usual cause for nvme related problems is APST, https://wiki.archlinux.org/title/Solid_ … leshooting
"nvme_core.default_ps_max_latency_us=0 pcie_aspm=off iommu=soft", https://wiki.archlinux.org/title/Kernel_parameters

Arch Linux

#1 2025-12-25 02:32:39

ThinkPad P15v Gen 3 AMD black screen with blinking cursor on suspend

#2 2025-12-27 00:23:36

Re: ThinkPad P15v Gen 3 AMD black screen with blinking cursor on suspend

#3 2025-12-27 04:27:30

Re: ThinkPad P15v Gen 3 AMD black screen with blinking cursor on suspend

#4 2025-12-27 09:40:38

Re: ThinkPad P15v Gen 3 AMD black screen with blinking cursor on suspend

#5 2026-04-29 23:16:26

Re: ThinkPad P15v Gen 3 AMD black screen with blinking cursor on suspend

#6 2026-04-30 07:28:16

Re: ThinkPad P15v Gen 3 AMD black screen with blinking cursor on suspend

#7 2026-05-01 04:37:24

Re: ThinkPad P15v Gen 3 AMD black screen with blinking cursor on suspend

#8 2026-05-01 10:51:11

Re: ThinkPad P15v Gen 3 AMD black screen with blinking cursor on suspend

Board footer