Freezes when interrupted from sleep

When my laptop starts to sleep and the screen goes black often times I will move my mouse to try to interrupt it from going to sleep. This worked fine up until about 2 months ago. Now something has changed in the process, and almost always when I do this it results in an unrecoverable black screen.

I don’t know if it’s actually “crashing” per se. I can switch to another virtual terminal and reboot etc. But this isn’t super helpful because the graphical session is unrecoverable, so I end up losing work and application state.

Here’s my inxi information. I’m not sure what other information would help troubleshoot. Open to suggestions.

inxi -Fazy

System:
Kernel: 5.10.223-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.1.1
clocksource: tsc avail: acpi_pm
parameters: BOOT_IMAGE=/boot/vmlinuz-5.10-x86_64
root=UUID=da1e4ec0-2e46-4890-bd92-48f659d4f309 ro udev.log_priority=3
nvidia-drm.modeset=1
Desktop: KDE Plasma v: 6.0.5 tk: Qt v: N/A info: frameworks v: 6.4.0
wm: kwin_x11 vt: 2 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
Type: Laptop System: ASUSTeK product: UX550VE v: 1.0
serial:
Mobo: ASUSTeK model: UX550VE v: 1.0 serial:
uuid: UEFI: American Megatrends v: UX550VE.304
date: 11/08/2017
CPU:
Info: model: Intel Core i7-7700HQ bits: 64 type: MT MCP arch: Kaby Lake
gen: core 7 level: v3 note: check built: 2018 process: Intel 14nm family: 6
model-id: 0x9E (158) stepping: 9 microcode: 0xF8
Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache:
L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB
L3: 6 MiB desc: 1x6 MiB
Speed (MHz): avg: 1948 high: 2106 min/max: 800/3800 scaling:
driver: intel_pstate governor: powersave cores: 1: 1916 2: 1749 3: 2106
4: 1974 5: 2008 6: 1982 7: 2031 8: 1823 bogomips: 44817
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: gather_data_sampling mitigation: Microcode
Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
vulnerable
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
Type: reg_file_data_sampling status: Not affected
Type: retbleed mitigation: IBRS
Type: spec_rstack_overflow status: Not affected
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
prctl and seccomp
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
sanitization
Type: spectre_v2 mitigation: IBRS, IBPB: conditional, STIBP: conditional,
RSB filling, PBRSB-eIBRS: Not affected
Type: srbds mitigation: Microcode
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Intel HD Graphics 630 vendor: ASUSTeK driver: i915 v: kernel
arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports:
active: DP-3,DP-4,eDP-1 empty: DP-1, DP-2, DP-5, HDMI-A-1 bus-ID: 00:02.0
chip-ID: 8086:591b class-ID: 0300
Device-2: NVIDIA GP107M [GeForce GTX 1050 Ti Mobile] vendor: ASUSTeK
driver: nvidia v: 550.107.02 alternate: nouveau,nvidia_drm non-free: 545.xx+
status: current (as of 2024-06; EOL~2026-12-xx) arch: Pascal code: GP10x
process: TSMC 16nm built: 2016-2021 pcie: gen: 1 speed: 2.5 GT/s lanes: 8
link-max: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 01:00.0 chip-ID: 10de:1c8c
class-ID: 0302
Device-3: IMC Networks USB2.0 VGA UVC WebCam driver: uvcvideo type: USB
rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-4:2 chip-ID: 13d3:5755
class-ID: 0e02 serial:
Device-4: Logitech BRIO Ultra HD Webcam
driver: hid-generic,snd-usb-audio,usbhid,uvcvideo type: USB rev: 3.1
speed: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 bus-ID: 2-5.1:3 chip-ID: 046d:085e
class-ID: 0300 serial:
Display: x11 server: X.Org v: 21.1.13 with: Xwayland v: 24.1.1
compositor: kwin_x11 driver: X: loaded: modesetting unloaded: nvidia
alternate: fbdev,nouveau,nv,vesa dri: iris gpu: i915 display-ID: :0
screens: 1
Screen-1: 0 s-res: 5760x1080 s-dpi: 96 s-size: 1524x285mm (60.00x11.22")
s-diag: 1550mm (61.04")
Monitor-1: not-matched mapped: DP-1-1 pos: left res: 1920x1080 hz: 60
dpi: 102 size: 476x268mm (18.74x10.55") diag: 546mm (21.51") modes: N/A
Monitor-2: not-matched mapped: DP-1-2 pos: right res: 1920x1080 hz: 60
dpi: 103 size: 475x267mm (18.7x10.51") diag: 545mm (21.45") modes: N/A
Monitor-3: eDP-1 pos: primary,center model: ChiMei InnoLux 0x15e8
built: 2016 res: 1920x1080 hz: 60 dpi: 142 gamma: 1.2
size: 344x193mm (13.54x7.6") diag: 394mm (15.5") ratio: 16:9
modes: 1920x1080
API: EGL v: 1.5 hw: drv: intel iris drv: nvidia platforms: device: 0
drv: nvidia device: 2 drv: iris device: 3 drv: swrast gbm: drv: nvidia
surfaceless: drv: nvidia x11: drv: iris inactive: wayland,device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: intel mesa v: 24.1.5-manjaro1.1
glx-v: 1.4 direct-render: yes renderer: Mesa Intel HD Graphics 630 (KBL GT2)
device-ID: 8086:591b memory: 7.58 GiB unified: yes
API: Vulkan v: 1.3.279 layers: 5 device: 0 type: discrete-gpu name: NVIDIA
GeForce GTX 1050 Ti driver: nvidia v: 550.107.02 device-ID: 10de:1c8c
surfaces: xcb,xlib
Info:
Memory: total: 16 GiB available: 15.51 GiB used: 5.07 GiB (32.7%)
Processes: 321 Power: uptime: 16m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 6.2 GiB services: org_kde_powerdevil,upowerd
Init: systemd v: 256 default: graphical tool: systemctl
Packages: pm: pacman pkgs: 1884 libs: 468 tools: pamac,yay Compilers:
clang: 18.1.8 gcc: 14.1.1 Shell: Bash v: 5.2.26 running-in: konsole
inxi: 3.3.35

Since interrupting sleep is likely causing processes to be also “partially” interrupted and maybe left in a non-functional state, I’m surprised this hasn’t happened before.

All I can suggest is to set the screen to dim or go off shortly before the machine is set to suspend.

This might also be down to nvidia drivers; if nvidia is active (in use) during suspend, this can also be a factor. Have you updated or otherwise changed those?

1 Like

You maybe want to try newer Kernels, like LTS 6.1 or LTS 6.6

If this is not helping, i would also try to switch from X11 to Wayland… if this changes anything :man_shrugging:

Additional maybe you can evade the unrecoverable system with TTY?
Crtl+alt+F Keys

or reset your desktop with
crtl+shift+F12

1 Like