Black frozen screen after suspend

Support Graphics & Display
1

I need help, sometimes when I suspend my laptop and then try to resume it’s just black screen with the cursor and frozen I can’t do anything unless I force shutdown, it’s really bothering me. I have been living with this for like 8 months now, I need a solution.

inxi -Fazy:
System:
Kernel: 5.18.5-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.1.0
parameters: BOOT_IMAGE=/boot/vmlinuz-5.18-x86_64
root=UUID=b395b351-d6f7-40f1-88ff-43ee89d7e608 rw quiet acpi_osi=Linux
apparmor=1 security=apparmor udev.log_priority=3
Desktop: KDE Plasma v: 5.24.5 tk: Qt v: 5.15.4 info: latte-dock
wm: kwin_x11 vt: 1 dm: SDDM Distro: Manjaro Linux base: Arch Linux
Machine:
Type: Laptop System: LENOVO product: 82B5 v: Lenovo Legion 5 15ARH05
serial: Chassis: type: 10 v: Lenovo Legion 5 15ARH05
serial:
Mobo: LENOVO model: LNVNB161216 v: SDK0J40709 WIN
serial: UEFI: LENOVO v: EUCN37WW date: 04/14/2022
Battery:
ID-1: BAT0 charge: 9.8 Wh (19.1%) condition: 51.3/60.0 Wh (85.5%)
volts: 15.4 min: 15.4 model: SMP L19M4PC0 type: Li-poly serial:
status: charging cycles: 529
CPU:
Info: model: AMD Ryzen 5 4600H with Radeon Graphics bits: 64 type: MT MCP
arch: Zen 2 gen: 3 built: 2020-22 process: TSMC n7 (7nm) family: 0x17 (23)
model-id: 0x60 (96) stepping: 1 microcode: 0x8600106
Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB L3: 8 MiB
desc: 2x4 MiB
Speed (MHz): avg: 2009 high: 3980 min/max: 1400/3000 boost: enabled
scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 1772 2: 1771
3: 3980 4: 3978 5: 1774 6: 1768 7: 1397 8: 1417 9: 1561 10: 1765 11: 1396
12: 1533 bogomips: 71894
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities:
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data status: Not affected
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW,
STIBP: conditional, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: NVIDIA TU117M [GeForce GTX 1650 Ti Mobile] vendor: Lenovo
driver: N/A alternate: nouveau non-free: 515.xx+
status: current (as of 2022-06) arch: Turing process: TSMC 12nm
built: 2018-22 pcie: gen: 3 speed: 8 GT/s lanes: 8 link-max: lanes: 16
bus-ID: 01:00.0 chip-ID: 10de:1f95 class-ID: 0300
Device-2: AMD Renoir vendor: Lenovo driver: amdgpu v: kernel arch: GCN 5.1
process: TSMC n7 (7nm) built: 2018-21 pcie: gen: 4 speed: 16 GT/s lanes: 16
ports: active: eDP-1 empty: none bus-ID: 05:00.0 chip-ID: 1002:1636
class-ID: 0300
Device-3: Acer Integrated Camera type: USB driver: uvcvideo bus-ID: 1-3:2
chip-ID: 5986:212b class-ID: 0e02
Display: x11 server: [X.Org](http://x.org/) v: 21.1.3 compositor: kwin_x11 driver: X:
loaded: amdgpu unloaded: modesetting alternate: fbdev,vesa gpu: amdgpu
display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
s-diag: 582mm (22.93")
Monitor-1: eDP-1 mapped: eDP model: AU Optronics 0xd1ed built: 2019
res: 1920x1080 hz: 120 dpi: 142 gamma: 1.2 size: 344x193mm (13.54x7.6")
diag: 394mm (15.5") ratio: 16:9 modes: max: 1920x1080 min: 640x480
OpenGL: renderer: AMD RENOIR (LLVM 13.0.1 DRM 3.46 5.18.5-1-MANJARO)
v: 4.6 Mesa 22.1.1 direct render: Yes
Audio:
Device-1: NVIDIA driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s
lanes: 8 link-max: lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:10fa
class-ID: 0403
Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor vendor: Lenovo driver: N/A
alternate: snd_pci_acp3x, snd_rn_pci_acp3x, snd_pci_acp5x, snd_pci_acp6x,
snd_acp_pci, snd_sof_amd_renoir
pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 05:00.5 chip-ID: 1022:15e2
class-ID: 0480
Device-3: AMD Family 17h/19h HD Audio vendor: Lenovo driver: snd_hda_intel
v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 05:00.6
chip-ID: 1022:15e3 class-ID: 0403
Sound Server-1: ALSA v: k5.18.5-1-MANJARO running: yes
Sound Server-2: JACK v: 1.9.21 running: no
Sound Server-3: PulseAudio v: 16.0 running: yes
Sound Server-4: PipeWire v: 0.3.52 running: yes
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Lenovo driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
port: 2000 bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: eno1 state: down mac:
Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: gen: 2
speed: 5 GT/s lanes: 1 bus-ID: 04:00.0 chip-ID: 8086:2723 class-ID: 0280
IF: wlp4s0 state: up mac:
Bluetooth:
Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 3-3:3
chip-ID: 8087:0029 class-ID: e001
Report: rfkill ID: hci0 rfk-id: 3 state: down bt-service: enabled,running
rfk-block: hardware: no software: yes address: see --recommends
Drives:
Local Storage: total: 1.14 TiB used: 794.63 GiB (67.9%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
model: MZVLB256HBHQ-000L2 size: 238.47 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial:
rev: 3L1QEXH7 temp: 62.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Western Digital model: WD10SPSX-08A6W
size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
type: HDD rpm: 7200 serial: rev: 1A01 scheme: GPT
Partition:
ID-1: / raw-size: 51.29 GiB size: 50.31 GiB (98.08%) used: 44.07 GiB (87.6%)
fs: ext4 dev: /dev/nvme0n1p5 maj-min: 259:5
ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%)
used: 46.8 MiB (48.7%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 76.83 GiB size: 75.07 GiB (97.71%)
used: 37.49 GiB (49.9%) fs: ext4 dev: /dev/nvme0n1p7 maj-min: 259:7
Swap:
Kernel: swappiness: 60 (default) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 11.72 GiB used: 3.86 GiB (33.0%)
priority: -2 dev: /dev/nvme0n1p6 maj-min: 259:6
Sensors:
System Temperatures: cpu: N/A mobo: N/A gpu: amdgpu temp: 55.0 C
Fan Speeds (RPM): N/A
Info:
Processes: 385 Uptime: 44m wakeups: 1 Memory: 15 GiB used: 9 GiB (60.0%)
Init: systemd v: 251 default: graphical tool: systemctl Compilers:
gcc: 12.1.0 clang: 13.0.1 Packages: 1591 pacman: 1573 lib: 436 flatpak: 5
snap: 13 Shell: Bash v: 5.1.16 running-in: konsole inxi: 3.3.19

mhwd -l && mhwd -li:

> 0000:03:00.0 (0200:10ec:8168) Network controller Realtek Semiconductor Co., Ltd.:

---


          NAME               VERSION          FREEDRIVER           TYPE


---


 network-r8168            2016.04.20                true            PCI


> 0000:01:00.0 (0300:10de:1f95) Display controller nVidia Corporation:

---


          NAME               VERSION          FREEDRIVER           TYPE


---

video-hybrid-amd-nvidia-prime 2021.12.18 false PCI
video-hybrid-amd-nvidia-470xx-prime 2021.12.18 false PCI
video-nvidia 2021.12.18 false PCI
video-nvidia-470xx 2021.12.18 false PCI
video-linux 2018.05.04 true PCI
video-modesetting 2020.01.13 true PCI
video-vesa 2017.03.12 true PCI

> 0000:05:00.0 (0300:1002:1636) Display controller ATI Technologies Inc:

---


          NAME               VERSION          FREEDRIVER           TYPE


---

video-hybrid-amd-nvidia-prime 2021.12.18 false PCI
video-hybrid-amd-nvidia-470xx-prime 2021.12.18 false PCI
video-linux 2018.05.04 true PCI
video-modesetting 2020.01.13 true PCI
video-vesa 2017.03.12 true PCI

> Installed PCI configs:

---


          NAME               VERSION          FREEDRIVER           TYPE


---

video-hybrid-amd-nvidia-prime 2021.12.18 false PCI
video-linux 2018.05.04 true PCI

Warning: No installed USB configs!
2

provide formatted output from:
inxi -Fazy
mhwd -l && mhwd -li
and try with different kernels, if you have the same issue

5

edit your post, click this icon in the editor: </> and post the output there

6

I have edited the post.

7

no you didnt, click this icon in the editor:
:point_right: </> :point_left:
and put the output of those commands there

8

xD sorry, got it now.

9

so when the black frozen screen happens again and you force rebooted provide logs from the frozen screen boot with this command:
journalctl -b-1 -p4 --no-pager

10

So it happened again today and here is the journalctl

Jul 19 00:34:13 Yamo-Legion5 kwin_x11[1425]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 46876, resource id: 81788934, major code: 18 (ChangeProperty), minor code: 0
Jul 19 00:34:22 Yamo-Legion5 kwin_x11[1425]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 53644, resource id: 81788934, major code: 18 (ChangeProperty), minor code: 0
Jul 19 00:34:27 Yamo-Legion5 kwin_x11[1425]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 61296, resource id: 12614512, major code: 20 (GetProperty), minor code: 0
Jul 19 00:34:27 Yamo-Legion5 kwin_x11[1425]: kwin_core: XCB error: 152 (BadDamage), sequence: 61392, resource id: 12642912, major code: 143 (DAMAGE), minor code: 3 (Subtract)
Jul 19 00:34:41 Yamo-Legion5 tlp[13533]: Warning: systemd-rfkill.service is not masked, radio device switching may not work as configured.
Jul 19 00:34:41 Yamo-Legion5 tlp[13533]: >>> Invoke 'systemctl mask systemd-rfkill.service' to correct this.
Jul 19 00:34:41 Yamo-Legion5 tlp[13534]: Warning: systemd-rfkill.service is not masked, radio device switching may not work as configured.
Jul 19 00:34:41 Yamo-Legion5 tlp[13534]: >>> Invoke 'systemctl mask systemd-rfkill.service' to correct this.
Jul 19 00:34:41 Yamo-Legion5 tlp[13533]: Warning: systemd-rfkill.socket is not masked, radio device switching may not work as configured.
Jul 19 00:34:41 Yamo-Legion5 tlp[13533]: >>> Invoke 'systemctl mask systemd-rfkill.socket' to correct this.
Jul 19 00:34:42 Yamo-Legion5 tlp[13534]: Warning: systemd-rfkill.socket is not masked, radio device switching may not work as configured.
Jul 19 00:34:42 Yamo-Legion5 tlp[13534]: >>> Invoke 'systemctl mask systemd-rfkill.socket' to correct this.
Jul 19 00:34:47 Yamo-Legion5 kwin_x11[1425]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 32915, resource id: 12584004, major code: 3 (GetWindowAttributes), minor code: 0
Jul 19 00:34:47 Yamo-Legion5 kwin_x11[1425]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 32916, resource id: 12584004, major code: 14 (GetGeometry), minor code: 0
Jul 19 00:34:52 Yamo-Legion5 tlp[13796]: Warning: systemd-rfkill.service is not masked, radio device switching may not work as configured.
Jul 19 00:34:52 Yamo-Legion5 tlp[13796]: >>> Invoke 'systemctl mask systemd-rfkill.service' to correct this.
Jul 19 00:34:52 Yamo-Legion5 tlp[13797]: Warning: systemd-rfkill.service is not masked, radio device switching may not work as configured.
Jul 19 00:34:52 Yamo-Legion5 tlp[13797]: >>> Invoke 'systemctl mask systemd-rfkill.service' to correct this.
Jul 19 00:34:52 Yamo-Legion5 tlp[13796]: Warning: systemd-rfkill.socket is not masked, radio device switching may not work as configured.
Jul 19 00:34:52 Yamo-Legion5 tlp[13796]: >>> Invoke 'systemctl mask systemd-rfkill.socket' to correct this.
Jul 19 00:34:52 Yamo-Legion5 tlp[13797]: Warning: systemd-rfkill.socket is not masked, radio device switching may not work as configured.
Jul 19 00:34:52 Yamo-Legion5 tlp[13797]: >>> Invoke 'systemctl mask systemd-rfkill.socket' to correct this.
Jul 19 00:34:52 Yamo-Legion5 tlp[13852]: Warning: systemd-rfkill.service is not masked, radio device switching may not work as configured.
Jul 19 00:34:52 Yamo-Legion5 tlp[13852]: >>> Invoke 'systemctl mask systemd-rfkill.service' to correct this.
Jul 19 00:34:52 Yamo-Legion5 tlp[13852]: Warning: systemd-rfkill.socket is not masked, radio device switching may not work as configured.
Jul 19 00:34:52 Yamo-Legion5 tlp[13852]: >>> Invoke 'systemctl mask systemd-rfkill.socket' to correct this.
Jul 19 00:35:19 Yamo-Legion5 baloo_file[1496]: kf.baloo: Inotify - too many event - Overflowed
Jul 19 00:35:20 Yamo-Legion5 baloo_file[1496]: kf.baloo: Inotify - too many event - Overflowed
Jul 19 00:35:22 Yamo-Legion5 upowerd[1310]: energy 51.790000 bigger than full 51.780000
Jul 19 00:38:16 Yamo-Legion5 org_kde_powerdevil[1488]: org.kde.powerdevil: Unsatisfied policies, the action has been aborted
Jul 19 00:39:15 Yamo-Legion5 kernel: __report_access: 80 callbacks suppressed
Jul 19 00:39:20 Yamo-Legion5 kernel: __report_access: 316 callbacks suppressed
Jul 19 00:39:28 Yamo-Legion5 kernel: __report_access: 366 callbacks suppressed
Jul 19 00:39:31 Yamo-Legion5 org_kde_powerdevil[1488]: org.kde.powerdevil: Unsatisfied policies, the action has been aborted
Jul 19 00:39:33 Yamo-Legion5 kernel: __report_access: 197 callbacks suppressed
Jul 19 00:39:38 Yamo-Legion5 kernel: __report_access: 266 callbacks suppressed
Jul 19 00:39:43 Yamo-Legion5 kernel: __report_access: 144 callbacks suppressed
Jul 19 00:39:48 Yamo-Legion5 kernel: __report_access: 187 callbacks suppressed
Jul 19 00:39:56 Yamo-Legion5 kernel: __report_access: 155 callbacks suppressed
Jul 19 00:40:01 Yamo-Legion5 kernel: __report_access: 218 callbacks suppressed
Jul 19 00:40:46 Yamo-Legion5 org_kde_powerdevil[1488]: org.kde.powerdevil: Unsatisfied policies, the action has been aborted
Jul 19 00:43:45 Yamo-Legion5 kernel: __report_access: 104 callbacks suppressed
Jul 19 00:43:50 Yamo-Legion5 kernel: __report_access: 312 callbacks suppressed
Jul 19 00:43:58 Yamo-Legion5 kernel: __report_access: 370 callbacks suppressed
Jul 19 00:44:03 Yamo-Legion5 kernel: __report_access: 189 callbacks suppressed
Jul 19 00:44:08 Yamo-Legion5 kernel: __report_access: 268 callbacks suppressed
Jul 19 00:44:13 Yamo-Legion5 kernel: __report_access: 140 callbacks suppressed
Jul 19 00:44:18 Yamo-Legion5 kernel: __report_access: 182 callbacks suppressed
Jul 19 00:44:26 Yamo-Legion5 kernel: __report_access: 167 callbacks suppressed
Jul 19 00:44:33 Yamo-Legion5 kernel: __report_access: 245 callbacks suppressed
Jul 19 00:44:38 Yamo-Legion5 kernel: __report_access: 98 callbacks suppressed
Jul 19 00:46:13 Yamo-Legion5 kwin_x11[1425]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 6055, resource id: 12684314, major code: 20 (GetProperty), minor code: 0
Jul 19 00:48:48 Yamo-Legion5 kernel: __report_access: 299 callbacks suppressed
Jul 19 00:48:53 Yamo-Legion5 kernel: __report_access: 355 callbacks suppressed
Jul 19 00:48:59 Yamo-Legion5 kernel: __report_access: 81 callbacks suppressed
Jul 19 00:49:04 Yamo-Legion5 kernel: __report_access: 224 callbacks suppressed
Jul 19 00:49:09 Yamo-Legion5 kernel: __report_access: 203 callbacks suppressed
Jul 19 00:49:14 Yamo-Legion5 kernel: __report_access: 161 callbacks suppressed
Jul 19 00:49:19 Yamo-Legion5 kernel: __report_access: 215 callbacks suppressed
Jul 19 00:49:26 Yamo-Legion5 kernel: __report_access: 86 callbacks suppressed
Jul 19 00:49:33 Yamo-Legion5 kernel: __report_access: 245 callbacks suppressed
Jul 19 00:50:52 Yamo-Legion5 org_kde_powerdevil[1488]: org.kde.powerdevil: Unsatisfied policies, the action has been aborted
Jul 19 00:52:07 Yamo-Legion5 org_kde_powerdevil[1488]: org.kde.powerdevil: Unsatisfied policies, the action has been aborted
Jul 19 00:52:52 Yamo-Legion5 kwin_x11[1425]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 46370, resource id: 12705779, major code: 20 (GetProperty), minor code: 0
Jul 19 00:53:15 Yamo-Legion5 kwin_x11[1425]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 52974, resource id: 62914586, major code: 18 (ChangeProperty), minor code: 0
Jul 19 00:53:33 Yamo-Legion5 kernel: __report_access: 101 callbacks suppressed
Jul 19 00:53:38 Yamo-Legion5 kernel: __report_access: 310 callbacks suppressed
Jul 19 00:53:44 Yamo-Legion5 kernel: __report_access: 174 callbacks suppressed
Jul 19 00:53:49 Yamo-Legion5 kernel: __report_access: 72 callbacks suppressed
Jul 19 00:53:54 Yamo-Legion5 kernel: __report_access: 99 callbacks suppressed
Jul 19 00:53:59 Yamo-Legion5 kernel: __report_access: 216 callbacks suppressed
Jul 19 00:54:04 Yamo-Legion5 kernel: __report_access: 218 callbacks suppressed
Jul 19 00:54:05 Yamo-Legion5 kstart5[16735]: Omitting both --window and --windowclass arguments is not recommended
Jul 19 00:54:05 Yamo-Legion5 kwin_x11[1425]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 29207, resource id: 62914570, major code: 18 (ChangeProperty), minor code: 0
Jul 19 00:54:05 Yamo-Legion5 kwin_x11[1425]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 29211, resource id: 62914571, major code: 18 (ChangeProperty), minor code: 0
Jul 19 00:54:09 Yamo-Legion5 kernel: __report_access: 137 callbacks suppressed
Jul 19 00:54:14 Yamo-Legion5 kernel: __report_access: 146 callbacks suppressed
Jul 19 00:54:23 Yamo-Legion5 kernel: __report_access: 191 callbacks suppressed
Jul 19 00:54:31 Yamo-Legion5 kernel: __report_access: 242 callbacks suppressed
Jul 19 00:54:36 Yamo-Legion5 kernel: __report_access: 98 callbacks suppressed
Jul 19 00:55:09 Yamo-Legion5 kscreenlocker_greet[17047]: Qt: Session management error: networkIdsList argument is NULL
Jul 19 00:55:09 Yamo-Legion5 kded5[1422]: org.kde.plasma.nm.kded: Unhandled active connection state change:  3
Jul 19 00:55:09 Yamo-Legion5 kscreenlocker_greet[17047]: file:///home/yamo/.local/share/plasma/look-and-feel/Sweet/contents/lockscreen/LockScreen.qml:52:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
Jul 19 00:55:30 Yamo-Legion5 kernel: Freezing of tasks failed after 20.002 seconds (1 tasks refusing to freeze, wq_busy=0):
Jul 19 00:55:30 Yamo-Legion5 kernel: 
Jul 19 00:55:30 Yamo-Legion5 rtkit-daemon[1545]: The canary thread is apparently starving. Taking action.
Jul 19 00:55:30 Yamo-Legion5 kscreenlocker_greet[17047]: qt.gui.icc: fromIccProfile: failed minimal tag size sanity
11

here is something:

org.kde.powerdevil: Unsatisfied policies, the action has been aborted

also a lot of those suppressed messages from kernel…
switch to a different kernel: try with these: 5.15 - 5.10

12 
org.kde.powerdevil: Unsatisfied policies, the action has been aborted

what am I looking at here exactly?

13

powerdevil is a power management app, related to suspend …
did you switch kernels? try using different kernels and see if you still have frozen screen after suspend

14

I switched kernels and I will monitor the laptop for the upcoming days and see if there is anything new.