Black Screen or no signal on resume

Azuredas · 2025-08-29 01:29:02

I've been having this issue for what seems like forever and it's been a real hair puller. Whenever I resume/wake my computer, the monitor has a chance to just not wake up at all. The behavior when it fails is I wiggle the mouse or press a key the monitor will light up the button to indicate that it's getting a signal, it will show on the OSD that it's scanning, then it will either tell me that it recognizes the resolution and refresh rate but show a black screen or go back to sleep. On the black screen no mouse is visible either. The only way to wake is really just to reboot at that point. I'm pretty sure the computer isn't crashing cause I can still ssh into it and do things. Here's some info about my system:

Kernel: Linux 6.16.3-arch1-1
Display Dell AW3225QF: 3840x2160 @ 120 Hz in 32" [External]
DE: GNOME 48.4
WM: Mutter (Wayland)
MOBO: Asus Strix B550 gaming
CPU: AMD Ryzen 7 5800X (16) @ 4.85 GHz
GPU: NVIDIA GeForce RTX 3080 [Discrete]

nvidia packages:

nvidia 580.76.05-6
nvidia-utils-580.76.05-4

I've added these entries to my modprobe.d as some have recommended:

options nvidia NVreg_PreserveVideoMemoryAllocations=1 NVreg_TemporaryFilePath=/var/tmp
options nvidia_drm modeset=1
options nvidia_drm fbdev=1
options nvidia NVreg_EnableGpuFirmware=0

I read that the problems might be gnome related, so I'm thinking about switching to KDE plasma and see if the issues persist. I can supply whatever logs you like just let me know how to get them, cause I'm still pretty noobish.

seth · 2025-08-29 07:32:51

When this happens, can you switch the VT and get an output (ctrl+alt+f3)?
Please post your complete system journal for the boot after the failure

sudo journalctl -b | curl -F 'file=@-' 0x0.st

Azuredas · 2025-08-30 01:11:41

Thanks for taking the time to reply! Here's the link: https://0x0.st/KHq4.txt

So for this time, the monitor didn't even attempt to wake for me wiggling the mouse or pressing keys on the keyboard. Also a little extra info just in case it's useful I'm on a 70' AOC hdmi 2.1 cable. Says it's rated for 4k 120hz. I am also using an icron 3104 raven to connect my usb devices. I was however having these issues before moving to this setup with regularly attached usb devices and a displayport 1.4 cable.

Edit: since the monitor didn't wake up the key combination didn't seem to do anything

Last edited by Azuredas (2025-08-30 01:12:44)

seth · 2025-08-30 20:43:38

There's no attempt to suspend the system covered by that journal?

Only one nvidia GPU, gnome-shell runs on it (card1)

Aug 29 20:01:48 serenity gnome-shell[1308]: setup_framebuffers: assertion 'width > 0' failed
Aug 29 20:01:48 serenity gnome-shell[1308]: setup_framebuffers: assertion 'width > 0' failed
Aug 29 20:01:48 serenity gnome-shell[1308]: setup_framebuffers: assertion 'width > 0' failed
Aug 29 20:01:48 serenity systemd[1216]: Started Application launched by gnome-shell.
Aug 29 20:01:48 serenity gnome-shell[1308]: setup_framebuffers: assertion 'width > 0' failed
Aug 29 20:01:48 serenity gnome-shell[1308]: setup_framebuffers: assertion 'width > 0' failed
Aug 29 20:01:48 serenity gnome-shell[1308]: setup_framebuffers: assertion 'width > 0' failed
Aug 29 20:01:48 serenity gnome-shell[1308]: setup_framebuffers: assertion 'width > 0' failed
Aug 29 20:01:48 serenity gnome-shell[1308]: setup_framebuffers: assertion 'width > 0' failed
Aug 29 20:01:48 serenity gnome-shell[1308]: setup_framebuffers: assertion 'width > 0' failed
Aug 29 20:01:48 serenity gnome-shell[1308]: setup_framebuffers: assertion 'width > 0' failed
Aug 29 20:01:48 serenity gnome-shell[1308]: setup_framebuffers: assertion 'width > 0' failed
Aug 29 20:01:48 serenity gnome-shell[1308]: setup_framebuffers: assertion 'width > 0' failed
Aug 29 20:01:48 serenity gnome-shell[1308]: setup_framebuffers: assertion 'width > 0' failed
Aug 29 20:01:48 serenity gnome-shell[1308]: setup_framebuffers: assertion 'width > 0' failed
Aug 29 20:01:48 serenity gnome-shell[1308]: setup_framebuffers: assertion 'width > 0' failed

looks mildly concerning.

I'm on a 70' AOC hdmi 2.1 cable

70' as in 21.3 meter or 70 subway footlongs?
And probably w/ an active repeater?
It'd probably be helpful to eliminate that variable for testing is possible.

Azuredas · 2025-08-30 23:44:09

I'm not super familiar with journalctl but wouldn't the

-b

just show since the boot after I already had to restart? If I understood right I took a look at the logs from the time before the boot with

journalctl -b -1

and I did some digging and found that there's an issue with something called simpledrm. I blacklisted it and switched some stuff around so I got rid of what was in my modprobe.d folder. From what I could tell from the wiki most of those options I entered where already defaults on current nvidia drivers. I switched to nvidia-open-dkms and I added

nvidia NVreg_PreserveVideoMemoryAllocations=1 modprobe.blacklist=simpledrm

to my cmdline file. So far things have been somewhat stable. Wake ups from screen off have been consistently working. I did have one GUI invoked suspend that seemed like it wasn't gonna wake up but I used the ctrl+alt+f3 combination and shut off the monitor then turned it back on and saw that I was in the text based login. I then pressed ctrl+alt+f2 and I was back to my normal login.

Oh yeah sorry the cable is 70 feet. It's not easy to switch out at the moment cause my computer is rack mounted a ways away. Yeah it's an active fiber cable, though the issue has preceded the cable. I can try it after if this starts to get unstable again. This should be a journal snippet from one of the crashes before I made any changes, but I grep'd for suspend|resume|error|drm|gpu|display.

Aug 30 09:18:41 serenity kernel: ACPI: bus type _connector registered
Aug 30 09:18:41 serenity kernel: simple-framebuffer simple-framebuffer.0: [drm] Registered 1 planes with drm panic
Aug 30 09:18:41 serenity kernel: [drm] Initialized simpledrm 1.0.0 for simple-framebuffer.0 on minor 0
Aug 30 09:18:41 serenity kernel: simple-framebuffer simple-framebuffer.0: [drm] fb0: simpledrmdrmfb frame buffer device
Aug 30 09:18:41 serenity kernel: RAS: Correctable Errors collector initialized.
Aug 30 09:18:41 serenity systemd[1]: Starting Load Kernel Module drm...
Aug 30 09:18:41 serenity systemd[1]: modprobe@drm.service: Deactivated successfully.
Aug 30 09:18:41 serenity systemd[1]: Finished Load Kernel Module drm.
Aug 30 09:18:42 serenity kernel: [drm] [nvidia-drm] [GPU ID 0x00000800] Loading driver
Aug 30 09:18:44 serenity kernel: [drm] Initialized nvidia-drm 0.0.0 for 0000:08:00.0 on minor 1
Aug 30 09:18:44 serenity kernel: fbcon: nvidia-drmdrmfb (fb0) is primary device
Aug 30 09:18:44 serenity kernel: nvidia 0000:08:00.0: [drm] fb0: nvidia-drmdrmfb frame buffer device
Aug 30 09:18:45 serenity systemd[1]: Starting GNOME Display Manager...
Aug 30 09:18:45 serenity systemd[1]: Started GNOME Display Manager.
Aug 30 09:18:45 serenity polkitd[739]: Error opening rules directory: Error opening directory “/run/polkit-1/rules.d”: No such file or directory (g-file-error-quark, 4)
Aug 30 09:18:45 serenity polkitd[739]: Error opening rules directory: Error opening directory “/usr/local/share/polkit-1/rules.d”: No such file or directory (g-file-error-quark, 4)
Aug 30 09:18:45 serenity gnome-session[785]: gnome-session-binary[785]: WARNING: Could not check if unit gnome-session-wayland@gnome-login.target is active: Error calling StartServiceByName for org.freedesktop.systemd1: Process org.freedesktop.systemd1 exited with status 1
Aug 30 09:18:45 serenity gnome-session-binary[785]: WARNING: Could not check if unit gnome-session-wayland@gnome-login.target is active: Error calling StartServiceByName for org.freedesktop.systemd1: Process org.freedesktop.systemd1 exited with status 1
Aug 30 09:18:45 serenity gnome-shell[797]: Running GNOME Shell (using mutter 48.4) as a Wayland display server
Aug 30 09:18:46 serenity gnome-shell[797]: Added device '/dev/dri/card1' (nvidia-drm) using atomic mode setting.
Aug 30 09:18:46 serenity gnome-shell[797]: Boot VGA GPU /dev/dri/card1 selected as primary
Aug 30 09:18:46 serenity gnome-shell[797]: Using public X11 display :1024, (using :1025 for managed services)
Aug 30 09:18:46 serenity gnome-shell[797]: Using Wayland display name 'wayland-0'
Aug 30 09:18:46 serenity gsd-sharing[907]: Failed to handle service change: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
Aug 30 09:18:46 serenity gsd-sharing[907]: Failed to handle service change: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
Aug 30 09:18:46 serenity gnome-shell[797]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
Aug 30 09:18:46 serenity org.gnome.Shell.desktop[1105]: Errors from xkbcomp are not fatal to the X server
Aug 30 09:18:46 serenity org.gnome.Shell.desktop[1148]: Errors from xkbcomp are not fatal to the X server
Aug 30 09:18:50 serenity gsd-sharing[907]: Failed to handle service change: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
Aug 30 09:18:50 serenity gsd-sharing[907]: Failed to handle service change: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
Aug 30 09:18:57 serenity /usr/lib/gdm-wayland-session[1287]: /usr/bin/xrdb: Can't open display ''
Aug 30 09:18:57 serenity udisksd[1310]: Error probing device: Error sending ATA command IDENTIFY DEVICE to '/dev/sda': Unexpected sense data returned:
                                         (g-io-error-quark, 0)
Aug 30 09:18:57 serenity kwin_wayland[1300]: No backend specified, automatically choosing drm
Aug 30 09:18:58 serenity kwin_wayland_wrapper[1383]: Errors from xkbcomp are not fatal to the X server
Aug 30 09:18:58 serenity kwin_wayland_wrapper[1390]: Errors from xkbcomp are not fatal to the X server
Aug 30 09:19:00 serenity org_kde_powerdevil[1457]: [  1457] Watching for display connection changes, resolved watch mode = Watch_Mode_Xevent, poll loop interval = 100 millisec
Aug 30 09:19:00 serenity org_kde_powerdevil[1457]: [  1570] (dw_recheck_displays_func) Recheck interval: Sleeping for 200 milliseconds
Aug 30 09:19:00 serenity systemd[1]: Created slice Slice /system/dbus-:1.2-org.kde.powerdevil.discretegpuhelper.
Aug 30 09:19:00 serenity systemd[1]: Started dbus-:1.2-org.kde.powerdevil.discretegpuhelper@0.service.
Aug 30 09:19:01 serenity kded6[1418]: kf.modemmanagerqt: Failed enumerating MM objects: "org.freedesktop.DBus.Error.NameHasNoOwner" 
Aug 30 09:19:06 serenity systemd[1250]: Started Display Configuration.
Aug 30 09:19:07 serenity gnome-shell[797]: JS ERROR: Gio.IOErrorEnum: Xwayland exited unexpectedly
Aug 30 09:19:07 serenity xdg-document-po[1164]: Error releasing name org.freedesktop.portal.Documents: The connection is closed
Aug 30 09:19:09 serenity systemd[1]: dbus-:1.2-org.kde.powerdevil.discretegpuhelper@0.service: Deactivated successfully.
Aug 30 09:20:29 serenity plasmashell[1428]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml:131: TypeError: Cannot read property 'screenGeometry' of null
Aug 30 09:20:29 serenity plasmashell[1428]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml:261: TypeError: Cannot read property 'plasmoid' of undefined
Aug 30 09:21:58 serenity nautilus[2085]: Failed to initialize display server connection: Cannot invoke method; proxy is for the well-known name org.gnome.Mutter.ServiceChannel without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
Aug 30 09:23:37 serenity systemsettings[1857]: file:///usr/lib/qt6/qml/org/kde/kirigami/private/globaltoolbar/ToolBarPageHeader.qml:40: TypeError: Cannot read property 'Kirigami' of null
Aug 30 09:23:38 serenity systemsettings[1857]: file:///usr/share/kcm_recentFiles/workspace/settings//qml/recentFiles/ExcludedApplicationView.qml:20: TypeError: Cannot read property 'enabled' of null
Aug 30 09:24:08 serenity systemsettings[1857]: file:///usr/lib/qt6/qml/org/kde/kirigami/private/globaltoolbar/ToolBarPageHeader.qml:121: TypeError: Cannot read property 'globalToolBar' of null
Aug 30 09:24:08 serenity systemsettings[1857]: file:///usr/lib/qt6/qml/org/kde/kirigami/private/globaltoolbar/ToolBarPageHeader.qml:40: TypeError: Cannot read property 'Kirigami' of null
                                                 #15 0x00007ffbf00b06f3 wl_display_dispatch_queue_pending (libwayland-client.so.0 + 0x56f3)
                                                 #16 0x00007ffbee56e266 _ZN15QtWaylandClient15QWaylandDisplay13flushRequestsEv (libQt6WaylandClient.so.6 + 0x6e266)
Aug 30 09:24:47 serenity drkonqi-coredump-launcher[2506]:                 #15 0x00007ffbf00b06f3 wl_display_dispatch_queue_pending (libwayland-client.so.0 + 0x56f3)
Aug 30 09:24:47 serenity drkonqi-coredump-launcher[2506]:                 #16 0x00007ffbee56e266 _ZN15QtWaylandClient15QWaylandDisplay13flushRequestsEv (libQt6WaylandClient.so.6 + 0x6e266)
Aug 30 09:24:47 serenity drkonqi-coredump-launcher[2507]:                 #15 0x00007ffbf00b06f3 wl_display_dispatch_queue_pending (libwayland-client.so.0 + 0x56f3)
Aug 30 09:24:47 serenity drkonqi-coredump-launcher[2507]:                 #16 0x00007ffbee56e266 _ZN15QtWaylandClient15QWaylandDisplay13flushRequestsEv (libQt6WaylandClient.so.6 + 0x6e266)
Aug 30 09:26:47 serenity plasma-discover[2753]: org.kde.plasma.libdiscover: error loading "fwupd-backend" "Cannot load library /usr/lib/qt6/plugins/discover/fwupd-backend.so: libfwupd.so.3: cannot open shared object file: No such file or directory" QJsonObject({"IID":"org.kde.discover.6.4.4.AbstractResourcesBackendFactory","archlevel":1,"className":"FwupdBackendFactory","debug":false,"version":395520})
Aug 30 09:26:47 serenity plasma-discover[2753]: org.kde.plasma.libdiscover: error loading "packagekit-backend" "Cannot load library /usr/lib/qt6/plugins/discover/packagekit-backend.so: libpackagekitqt6.so.1: cannot open shared object file: No such file or directory" QJsonObject({"IID":"org.kde.discover.6.4.4.AbstractResourcesBackendFactory","archlevel":1,"className":"PackageKitBackendFactory","debug":false,"version":395520})
Aug 30 09:26:47 serenity plasmashell[2492]: error creating screencast "Could not find window id {3122ede3-3ece-4fc9-bccd-710611fbc70d}"
Aug 30 09:27:58 serenity kwalletd6[3051]: kf.wallet.kwalletd: Error reading label: QDBusError("org.freedesktop.DBus.Error.UnknownInterface", "Interface 'org.freedesktop.Secret.Collection' was not found")
Aug 30 09:28:14 serenity brave[3000]: [3000:3000:0830/092814.165953:ERROR:content/browser/network_service_instance_impl.cc:597] Network service crashed, restarting service.
Aug 30 09:28:14 serenity brave[3000]: [3000:3000:0830/092814.296705:ERROR:extensions/browser/service_worker/service_worker_task_queue.cc:449] DidStartWorkerFail nngceckbapebfimnlniiiahkandclblb: 3
Aug 30 09:28:20 serenity brave[3000]: [3000:3000:0830/092820.168534:ERROR:components/dbus/xdg/request.cc:165] Request cancelled by user.
Aug 30 09:28:20 serenity brave[3000]: [3000:3000:0830/092820.168549:ERROR:ui/base/accelerators/global_accelerator_listener/global_accelerator_listener_linux.cc:285] Failed to call BindShortcuts (error code 4).
Aug 30 09:28:28 serenity brave[3000]: [3000:3036:0830/092828.555871:ERROR:../src/content/browser/browser_main_loop.cc:285] GLib: g_main_context_pop_thread_default: assertion 'stack != NULL' failed
Aug 30 09:28:28 serenity brave[3000]: [3000:3034:0830/092828.555868:ERROR:../src/content/browser/browser_main_loop.cc:285] GLib: g_main_context_pop_thread_default: assertion 'stack != NULL' failed
Aug 30 09:28:28 serenity brave[3000]: [3000:3035:0830/092828.555868:ERROR:../src/content/browser/browser_main_loop.cc:285] GLib: g_main_context_pop_thread_default: assertion 'stack != NULL' failed
Aug 30 09:28:28 serenity brave[3002]: [0830/092828.564424:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64] tag not found
Aug 30 09:28:28 serenity brave[3002]: [0830/092828.565348:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64] tag not found
Aug 30 09:28:28 serenity brave[3002]: [0830/092828.565477:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64] tag not found
Aug 30 09:28:28 serenity brave[3002]: [0830/092828.565560:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64] tag not found
Aug 30 09:28:28 serenity brave[3002]: [0830/092828.569395:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64] tag not found
Aug 30 09:28:28 serenity brave[3002]: [0830/092828.570777:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64] tag not found
Aug 30 09:28:28 serenity brave[3002]: [0830/092828.570917:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64] tag not found
Aug 30 09:28:28 serenity brave[3002]: [0830/092828.570959:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64] tag not found
Aug 30 09:28:28 serenity brave[3002]: [0830/092828.571198:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64] tag not found
Aug 30 09:28:28 serenity brave[3002]: [0830/092828.571524:ERROR:third_party/crashpad/crashpad/util/process/process_memory_range.cc:75] read out of range
Aug 30 09:28:28 serenity brave[3002]: [0830/092828.571532:ERROR:third_party/crashpad/crashpad/util/process/process_memory_range.cc:75] read out of range
Aug 30 09:28:28 serenity brave[3002]: [0830/092828.575673:ERROR:third_party/crashpad/crashpad/util/process/process_memory_range.cc:75] read out of range
Aug 30 09:28:28 serenity brave[3002]: [0830/092828.575681:ERROR:third_party/crashpad/crashpad/util/process/process_memory_range.cc:75] read out of range
Aug 30 09:28:28 serenity brave[3002]: [0830/092828.575691:ERROR:third_party/crashpad/crashpad/util/process/process_memory_range.cc:75] read out of range
Aug 30 09:28:28 serenity brave[3002]: [0830/092828.575695:ERROR:third_party/crashpad/crashpad/util/process/process_memory_range.cc:75] read out of range
Aug 30 09:28:28 serenity brave[3002]: [0830/092828.581202:ERROR:third_party/crashpad/crashpad/util/file/directory_reader_posix.cc:43] opendir /home/dashts/.config/BraveSoftware/Brave-Browser/Crash Reports/attachments/9ba01843-7ebe-40d8-b403-b5a352517019: No such file or directory (2)
Aug 30 09:28:31 serenity kwalletd6[3051]: kf.wallet.kwalletd: Error reading label: QDBusError("org.freedesktop.DBus.Error.UnknownInterface", "Interface 'org.freedesktop.Secret.Collection' was not found")
Aug 30 09:28:42 serenity brave[3440]: [3440:3440:0830/092842.833896:ERROR:components/dbus/xdg/request.cc:165] Request cancelled by user.
Aug 30 09:28:42 serenity brave[3440]: [3440:3440:0830/092842.833921:ERROR:ui/base/accelerators/global_accelerator_listener/global_accelerator_listener_linux.cc:285] Failed to call BindShortcuts (error code 4).
Aug 30 09:29:01 serenity brave[3440]: [3440:3476:0830/092901.471496:ERROR:../src/content/browser/browser_main_loop.cc:285] GLib: g_main_context_pop_thread_default: assertion 'stack != NULL' failed
Aug 30 09:29:01 serenity brave[3440]: [3440:3475:0830/092901.471495:ERROR:../src/content/browser/browser_main_loop.cc:285] GLib: g_main_context_pop_thread_default: assertion 'stack != NULL' failed
Aug 30 09:29:01 serenity brave[3440]: [3440:3474:0830/092901.471502:ERROR:../src/content/browser/browser_main_loop.cc:285] GLib: g_main_context_pop_thread_default: assertion 'stack != NULL' failed
Aug 30 09:29:21 serenity brave[3440]: [3440:3440:0830/092921.481501:ERROR:ui/events/platform/wayland/wayland_event_watcher.cc:47] libwayland: warning: queue 0x2f6c0016ce00 destroyed while proxies still attached:
Aug 30 09:29:21 serenity brave[3440]: [3440:3440:0830/092921.481566:ERROR:ui/events/platform/wayland/wayland_event_watcher.cc:47] libwayland:   wl_shm_pool#48 still attached
Aug 30 09:29:21 serenity plasmashell[2492]: kf.runner: Error requesting matches; calling "org.kde.plasma.browser_integration"  : "org.freedesktop.DBus.Error.NoReply" "Remote peer disconnected"
Aug 30 09:29:21 serenity brave[3440]: [3440:3470:0830/092921.571044:ERROR:../src/content/browser/browser_main_loop.cc:285] GLib: g_main_context_pop_thread_default: assertion 'stack != NULL' failed
Aug 30 09:30:02 serenity plasmashell[2492]: error creating screencast "Could not find window id {072de3e6-6c30-4087-b259-3bf50b29c378}"
Aug 30 09:30:22 serenity brave[3858]: [3858:3878:0830/093022.169609:ERROR:../src/net/socket/ssl_client_socket_impl.cc:914] handshake failed; returned -1, SSL error code 1, net_error -101
Aug 30 09:30:32 serenity brave[3808]: [3808:3844:0830/093032.017935:ERROR:../src/content/browser/browser_main_loop.cc:285] GLib: g_main_context_pop_thread_default: assertion 'stack != NULL' failed
Aug 30 09:30:32 serenity brave[3808]: [3808:3843:0830/093032.017930:ERROR:../src/content/browser/browser_main_loop.cc:285] GLib: g_main_context_pop_thread_default: assertion 'stack != NULL' failed
Aug 30 09:30:32 serenity brave[3808]: [3808:3842:0830/093032.017947:ERROR:../src/content/browser/browser_main_loop.cc:285] GLib: g_main_context_pop_thread_default: assertion 'stack != NULL' failed
Aug 30 09:30:49 serenity kioworker[4201]: kf.kio.core.connection: Socket not connected QLocalSocket::PeerClosedError
Aug 30 09:30:49 serenity kioworker[4201]: kf.kio.core: An error occurred during write. The worker terminates now.
Aug 30 09:31:34 serenity brave[3808]: [3808:3808:0830/093134.529096:ERROR:CONSOLE:4001] "[Settings] Appearance Page cannot find use default theme button template", source: chrome://settings/settings.js (4001)
Aug 30 09:31:34 serenity brave[3808]: [3808:3808:0830/093134.529201:ERROR:CONSOLE:4001] "[Settings] Appearance Page cannot find use default theme button template", source: chrome://settings/settings.js (4001)
Aug 30 09:31:52 serenity xdg-desktop-por[1308]: Realtime error: Could not get pidns for pid 5662: Could not fstatat ns/pid: Not a directory
Aug 30 09:31:52 serenity xdg-desktop-por[1308]: Realtime error: Could not get pidns for pid 5662: Could not fstatat ns/pid: Not a directory
Aug 30 09:32:26 serenity brave[3808]: [3808:3808:0830/093226.773601:ERROR:components/sharing_message/sharing_service.cc:297] Device registration failed with fatal error
Aug 30 09:33:08 serenity systemsettings[5949]: qrc:/kcm/kcm_clock/main.qml:12: TypeError: Cannot read property 'selectedTimeZone' of null
Aug 30 09:33:52 serenity systemsettings[5949]: file:///usr/lib/qt6/qml/org/kde/kirigami/private/globaltoolbar/ToolBarPageHeader.qml:121: TypeError: Cannot read property 'globalToolBar' of null
Aug 30 09:33:52 serenity systemsettings[5949]: file:///usr/lib/qt6/qml/org/kde/kirigami/private/globaltoolbar/ToolBarPageHeader.qml:40: TypeError: Cannot read property 'Kirigami' of null
Aug 30 09:36:52 serenity brave[3808]: [3808:3808:0830/093652.350980:ERROR:ui/events/platform/wayland/wayland_event_watcher.cc:47] libwayland: warning: queue 0x105400178d80 destroyed while proxies still attached:
Aug 30 09:36:52 serenity brave[3808]: [3808:3808:0830/093652.351057:ERROR:ui/events/platform/wayland/wayland_event_watcher.cc:47] libwayland:   wl_shm_pool#48 still attached
Aug 30 09:36:52 serenity brave[3808]: [3808:3838:0830/093652.516942:ERROR:../src/content/browser/browser_main_loop.cc:285] GLib: g_main_context_pop_thread_default: assertion 'stack != NULL' failed
Aug 30 09:38:42 serenity plasmashell[2492]: error creating screencast "Could not find window id {88e1fba6-f6a2-4c11-95ec-ef3570de73f0}"
Aug 30 09:38:42 serenity brave[7286]: [7286:7286:0830/093842.928959:ERROR:components/sharing_message/sharing_service.cc:297] Device registration failed with fatal error
Aug 30 09:38:43 serenity brave[7334]: [7334:7575:0830/093843.387760:ERROR:components/viz/service/display/display.cc:246] Frame latency is negative: -1.052 ms
Aug 30 09:38:55 serenity brave[7334]: [7334:7334:0830/093855.830217:ERROR:gpu/command_buffer/service/shared_image/shared_image_manager.cc:389] SharedImageManager::ProduceSkia: Trying to Produce a Skia representation from a non-existent mailbox.
Aug 30 09:39:12 serenity brave[7286]: [7286:7323:0830/093912.479790:ERROR:../src/content/browser/browser_main_loop.cc:285] GLib: g_main_context_pop_thread_default: assertion 'stack != NULL' failed
Aug 30 09:39:12 serenity brave[7286]: [7286:7322:0830/093912.479790:ERROR:../src/content/browser/browser_main_loop.cc:285] GLib: g_main_context_pop_thread_default: assertion 'stack != NULL' failed
Aug 30 09:39:12 serenity brave[7286]: [7286:7321:0830/093912.479808:ERROR:../src/content/browser/browser_main_loop.cc:285] GLib: g_main_context_pop_thread_default: assertion 'stack != NULL' failed
Aug 30 09:47:31 serenity brave[7336]: [7336:7342:0830/094731.327527:ERROR:../src/net/socket/ssl_client_socket_impl.cc:914] handshake failed; returned -1, SSL error code 1, net_error -101
Aug 30 09:48:54 serenity kwin_wayland_wrapper[16020]: Errors from xkbcomp are not fatal to the X server
Aug 30 09:51:55 serenity brave[7286]: [7286:7286:0830/095155.281236:ERROR:ui/events/platform/wayland/wayland_event_watcher.cc:47] libwayland: warning: queue 0x1f5c0016cd80 destroyed while proxies still attached:
Aug 30 09:51:55 serenity brave[7286]: [7286:7286:0830/095155.281302:ERROR:ui/events/platform/wayland/wayland_event_watcher.cc:47] libwayland:   wl_shm_pool#48 still attached
Aug 30 09:51:55 serenity brave[7286]: [7286:7316:0830/095155.418072:ERROR:../src/content/browser/browser_main_loop.cc:285] GLib: g_main_context_pop_thread_default: assertion 'stack != NULL' failed
Aug 30 09:52:05 serenity plasmashell[2492]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemtray/contents/ui/items/PlasmoidItem.qml:208: TypeError: Cannot read property 'fullRepresentationItem' of null
Aug 30 09:52:05 serenity plasmashell[2492]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemtray/contents/ui/items/PlasmoidItem.qml:201: TypeError: Cannot read property 'compactRepresentationItem' of null
Aug 30 09:52:05 serenity plasmashell[2492]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemtray/contents/ui/items/PlasmoidItem.qml:24: TypeError: Cannot read property 'toolTipMainText' of null
Aug 30 09:52:05 serenity plasmashell[2492]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml:131: TypeError: Cannot read property 'screenGeometry' of null
Aug 30 09:52:05 serenity plasmashell[2492]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml:261: TypeError: Cannot read property 'plasmoid' of undefined
Aug 30 09:52:06 serenity gnome-session[18385]: gnome-session-binary[18385]: WARNING: Could not check if unit gnome-session-wayland@gnome-login.target is active: Error calling StartServiceByName for org.freedesktop.systemd1: Process org.freedesktop.systemd1 exited with status 1
Aug 30 09:52:06 serenity gnome-session-binary[18385]: WARNING: Could not check if unit gnome-session-wayland@gnome-login.target is active: Error calling StartServiceByName for org.freedesktop.systemd1: Process org.freedesktop.systemd1 exited with status 1
Aug 30 09:52:06 serenity gnome-shell[18397]: Running GNOME Shell (using mutter 48.4) as a Wayland display server
Aug 30 09:52:06 serenity gnome-shell[18397]: Added device '/dev/dri/card1' (nvidia-drm) using atomic mode setting.
Aug 30 09:52:06 serenity gnome-shell[18397]: Boot VGA GPU /dev/dri/card1 selected as primary
Aug 30 09:52:06 serenity gnome-shell[18397]: Using public X11 display :1024, (using :1025 for managed services)
Aug 30 09:52:06 serenity gnome-shell[18397]: Using Wayland display name 'wayland-0'
Aug 30 09:52:07 serenity gnome-shell[18397]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
Aug 30 09:52:07 serenity gsd-sharing[18475]: Failed to handle service change: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
Aug 30 09:52:07 serenity gsd-sharing[18475]: Failed to handle service change: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
Aug 30 09:52:07 serenity org.gnome.Shell.desktop[18678]: Errors from xkbcomp are not fatal to the X server
Aug 30 09:52:07 serenity org.gnome.Shell.desktop[18722]: Errors from xkbcomp are not fatal to the X server
Aug 30 09:52:18 serenity gnome-shell[18923]: Running GNOME Shell (using mutter 48.4) as a Wayland display server
Aug 30 09:52:18 serenity gnome-shell[18923]: Added device '/dev/dri/card1' (nvidia-drm) using atomic mode setting.
Aug 30 09:52:18 serenity gnome-shell[18923]: Boot VGA GPU /dev/dri/card1 selected as primary
Aug 30 09:52:18 serenity gnome-shell[18923]: Using public X11 display :0, (using :1 for managed services)
Aug 30 09:52:18 serenity gnome-shell[18923]: Using Wayland display name 'wayland-0'
Aug 30 09:52:19 serenity gnome-session[18905]: gnome-session-binary[18905]: GnomeDesktop-WARNING: Could not create transient scope for PID 19043: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Failed to set unit properties: No such process
Aug 30 09:52:19 serenity gnome-session-binary[18905]: GnomeDesktop-WARNING: Could not create transient scope for PID 19043: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Failed to set unit properties: No such process
Aug 30 09:52:19 serenity gnome-shell[18923]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
Aug 30 09:52:19 serenity gsd-usb-protect[19063]: Failed to fetch USBGuard parameters: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
Aug 30 09:53:00 serenity systemd[18831]: app-gnome-gnome\x2ddisplay\x2dpanel-19609.scope: Consumed 45.033s CPU time, 1.1G memory peak.
Aug 30 09:53:02 serenity gnome-shell[20250]: Errors from xkbcomp are not fatal to the X server
Aug 30 09:53:02 serenity gnome-shell[20256]: Errors from xkbcomp are not fatal to the X server
Aug 30 09:53:02 serenity gsd-xsettings[20254]: Failed to get current UI scaling factor: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Destination does not exist
Aug 30 09:53:03 serenity vesktop.desktop[20288]: (node:20288) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, open '/home/dashts/.config/vesktop/settings/quickCss.css'
Aug 30 09:53:03 serenity vesktop.desktop[20288]: (node:20288) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag

Deuchnord · 2025-08-31 08:30:21

Hello, I have the same issue since kernel 6.16.2, problem seems to disappear if I downgrade to 6.16.1.

I could have a minimal journal after upgrading to 6.16.4, rebooting, suspending and trying to resume: https://0x0.st/KHOJ.txt
I'm not sure it's related to Nvidia drivers, because I'm on an AMD GPU.

AMD packages:

amd-ucode 20250808-1
lib32-amdvlk 2025.Q2.1-1
linux-firmware-amdgpu 20250808-1
xf86-video-amdgpu 25.0.0-1

seth · 2025-08-31 12:39:59

-b is the running boot - what would be valid when ssh'ing into the broken system.
The simpledrm device is supposed to get replaced by the nvidia_drm driver because of nvidia_drm.fbdev=1 - does it actually show up around the sleep?
(Ideally post a boot w/ a broken resume and one w/ a resume on a system where simpledrm is blacklisted)

@Deuchnord, https://bbs.archlinux.org/viewtopic.php … 9#p2259029

Azuredas · 2025-08-31 15:15:25

That makes a lot more sense. Here is a power save recovery failure without the kernel param
https://0x0.st/KH4f.txt
And here is a working power save recovery with the kernel param
https://0x0.st/KH4v.txt
For the failure I got it on the first try, for the recovery it was also first try.

I'm trying manually suspending without the param and it just keeps waking up correctly atm. I'll keep trying and see if I can get more logs.

seth · 2025-08-31 19:09:01

Aug 31 09:32:05 serenity kernel: Linux version 6.16.4-arch1-1 (linux@archlinux) (gcc (GCC) 15.2.1 20250813, GNU ld (GNU Binutils) 2.45.0) #1 SMP PREEMPT_DYNAMIC Thu, 28 Aug 2025 19:49:53 +0000
Aug 31 09:32:06 serenity kernel: simple-framebuffer simple-framebuffer.0: [drm] Registered 1 planes with drm panic
Aug 31 09:32:06 serenity kernel: [drm] Initialized simpledrm 1.0.0 for simple-framebuffer.0 on minor 0
Aug 31 09:32:06 serenity kernel: simple-framebuffer simple-framebuffer.0: [drm] fb0: simpledrmdrmfb frame buffer device

Aug 31 09:55:53 serenity kernel: Linux version 6.16.4-arch1-1 (linux@archlinux) (gcc (GCC) 15.2.1 20250813, GNU ld (GNU Binutils) 2.45.0) #1 SMP PREEMPT_DYNAMIC Thu, 28 Aug 2025 19:49:53 +0000
Aug 31 09:55:53 serenity kernel: Command line: root=PARTUUID=66cf897e-4dd6-431e-b485-b3c3e0e39056 zswap.enabled=0 rootflags=subvol=@ rw rootfstype=btrfs nvidia.NVreg_PreserveVideoMemoryAllocations=1 modprobe.blacklist=simpledrm
Aug 31 09:55:53 serenity kernel: Kernel command line: root=PARTUUID=66cf897e-4dd6-431e-b485-b3c3e0e39056 zswap.enabled=0 rootflags=subvol=@ rw rootfstype=btrfs nvidia.NVreg_PreserveVideoMemoryAllocations=1 modprobe.blacklist=simpledrm
Aug 31 09:55:53 serenity kernel: simple-framebuffer simple-framebuffer.0: [drm] Registered 1 planes with drm panic
Aug 31 09:55:53 serenity kernel: [drm] Initialized simpledrm 1.0.0 for simple-framebuffer.0 on minor 0
Aug 31 09:55:53 serenity kernel: simple-framebuffer simple-framebuffer.0: [drm] fb0: simpledrmdrmfb frame buffer device

There're not signs of a sleep cycle in either - are we maybe only talking about DPMS (ie. the monitor gets shut off, but the system remains very much awake all the time)?
The only thing that really changes is

Aug 31 09:32:06 serenity kernel: input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:03.1/0000:08:00.1/sound/card0/input8
Aug 31 09:32:06 serenity kernel: input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:03.1/0000:08:00.1/sound/card0/input9
Aug 31 09:32:06 serenity kernel: input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:03.1/0000:08:00.1/sound/card0/input10
Aug 31 09:32:06 serenity kernel: input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:03.1/0000:08:00.1/sound/card0/input11
-----
Aug 31 09:55:54 serenity kernel: input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:03.1/0000:08:00.1/sound/card1/input8
Aug 31 09:55:54 serenity kernel: input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:03.1/0000:08:00.1/sound/card1/input9
Aug 31 09:55:54 serenity kernel: input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:03.1/0000:08:00.1/sound/card1/input10
Aug 31 09:55:54 serenity kernel: input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:03.1/0000:08:00.1/sound/card1/input11
…
Aug 31 09:57:23 serenity gnome-shell[1434]: Invalid sequence for VSYNC frame info

Both actually have

Aug 31 09:32:54 serenity kernel: nvidia-modeset: WARNING: GPU:0: HDMI FRL link training failed.
…
Aug 31 09:57:59 serenity kernel: nvidia-modeset: WARNING: GPU:0: HDMI FRL link training failed.

Do you get the same problem w/ not-gnome, but eg. an X11/openbox session started w/ startx?
(You can force DPMS w/ "xset dpms force off" on X11)

Azuredas · 2025-08-31 20:27:21

Yeah it might be a separate issue. So the monitor/screen won't come back in two scenarios:

1. Screen saver (black screen)
2. Resume from sleep (if it ever even got to sleep)

Here's a log with no modprobe.blacklist and it didn't wakeup (go to sleep even?):

https://0x0.st/KHt4.txt

I did what you asked and set my resolution and refresh rate to max so I was being consistent there and it didn't respond on the second or third attempt. I was able to get back to gnome with ctrl+alt+f2 but now I'm locked to 30hz refresh rate.

https://0x0.st/KHtR.txt

seth · 2025-09-01 07:19:28

Aug 31 14:13:14 serenity kernel: PM: suspend entry (deep)
…
Aug 31 14:13:24 serenity kernel: NVRM: nvCheckFailedNoLog: Check failed: put < size @ crashcat_queue_v1.c:66
…
Aug 31 14:13:26 serenity kernel: nvidia-modeset: WARNING: GPU:0: HDMI FRL link training failed.
…
Aug 31 14:13:27 serenity systemd[1]: Stopped target Sleep.
Aug 31 14:13:27 serenity systemd[1]: Reached target Suspend.
Aug 31 14:13:27 serenity systemd[1]: Starting NVIDIA system resume actions...
Aug 31 14:13:27 serenity systemd[1]: Stopped target Suspend.
…
Aug 31 14:20:50 serenity kernel: nvidia-modeset: WARNING: GPU:0: HDMI FRL link training failed.
Aug 31 14:21:07 serenity kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000800] Flip event timeout on head 0
Aug 31 14:21:11 serenity kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000800] Failed to apply atomic modeset.  Error code: -22
Aug 31 14:21:29 serenity kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000800] Flip event timeout on head 0
Aug 31 14:21:32 serenity kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000800] Flip event timeout on head 0
Aug 31 14:22:35 serenity kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000800] Failed to apply atomic modeset.  Error code: -22
Aug 31 14:22:48 serenity kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000800] Failed to apply atomic modeset.  Error code: -22
Aug 31 14:22:51 serenity kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000800] Flip event timeout on head 0
Aug 31 14:22:54 serenity kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000800] Flip event timeout on head 0
…
Aug 31 14:34:56 serenity kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c67e:6 2:0:2636:2628
Aug 31 14:35:01 serenity kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c67e:6 2:0:2636:2628
Aug 31 14:35:06 serenity kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c67e:6 2:0:2636:2628
Aug 31 14:35:11 serenity kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c67e:6 2:0:2636:2628

Aug 31 14:36:27 serenity kernel: INFO: task nvidia-modeset/:554 blocked for more than 122 seconds.
Aug 31 14:36:27 serenity kernel:       Tainted: G           OE       6.16.4-arch1-1 #1
Aug 31 14:36:27 serenity kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Aug 31 14:36:27 serenity kernel: task:nvidia-modeset/ state:D stack:0     pid:554   tgid:554   ppid:2      task_flags:0x208040 flags:0x00004000
Aug 31 14:36:27 serenity kernel: Call Trace:
Aug 31 14:36:27 serenity kernel:  <TASK>
Aug 31 14:36:27 serenity kernel:  __schedule+0x409/0x1330
Aug 31 14:36:27 serenity kernel:  ? try_to_wake_up+0x309/0x740
Aug 31 14:36:27 serenity kernel:  schedule+0x27/0xd0
Aug 31 14:36:27 serenity kernel:  schedule_timeout+0xbd/0x100
Aug 31 14:36:27 serenity kernel:  __down_common+0x137/0x2d0
Aug 31 14:36:27 serenity kernel:  ? __pfx__main_loop+0x10/0x10 [nvidia_modeset bd33c041e571115a574ac1b8306ecd5f1924565d]
Aug 31 14:36:27 serenity kernel:  down+0x53/0x70
Aug 31 14:36:27 serenity kernel:  nvkms_kthread_q_callback+0xb1/0x170 [nvidia_modeset bd33c041e571115a574ac1b8306ecd5f1924565d]
Aug 31 14:36:27 serenity kernel:  _main_loop+0x93/0x150 [nvidia_modeset bd33c041e571115a574ac1b8306ecd5f1924565d]
Aug 31 14:36:27 serenity kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Aug 31 14:36:27 serenity kernel:  ? __pfx__main_loop+0x10/0x10 [nvidia_modeset bd33c041e571115a574ac1b8306ecd5f1924565d]
Aug 31 14:36:27 serenity kernel:  kthread+0xfc/0x240
Aug 31 14:36:27 serenity kernel:  ? __pfx_kthread+0x10/0x10
Aug 31 14:36:27 serenity kernel:  ret_from_fork+0x19a/0x1d0
Aug 31 14:36:27 serenity kernel:  ? __pfx_kthread+0x10/0x10
Aug 31 14:36:27 serenity kernel:  ret_from_fork_asm+0x1a/0x30
Aug 31 14:36:27 serenity kernel:  </TASK>
Aug 31 14:36:27 serenity kernel: INFO: task nvidia-modeset/:554 blocked on a semaphore likely last held by task KMS thread:1334
Aug 31 14:36:27 serenity kernel: task:KMS thread      state:R  running task     stack:0     pid:1334  tgid:1303  ppid:1211   task_flags:0x400040 flags:0x00004002
Aug 31 14:36:27 serenity kernel: Call Trace:
Aug 31 14:36:27 serenity kernel:  <TASK>
Aug 31 14:36:27 serenity kernel:  ? __pick_next_task+0x3e/0x1b0
Aug 31 14:36:27 serenity kernel:  ? __schedule+0xe08/0x1330
Aug 31 14:36:27 serenity kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Aug 31 14:36:27 serenity kernel:  ? asm_sysvec_apic_timer_interrupt+0x1a/0x20
Aug 31 14:36:27 serenity kernel:  ? schedule+0x27/0xd0
Aug 31 14:36:27 serenity kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Aug 31 14:36:27 serenity kernel:  ? nvEvoMakeRoom+0x11b/0x260 [nvidia_modeset bd33c041e571115a574ac1b8306ecd5f1924565d]
Aug 31 14:36:27 serenity kernel:  ? nvEvoFlipC6+0x33e/0x3a0 [nvidia_modeset bd33c041e571115a574ac1b8306ecd5f1924565d]
Aug 31 14:36:27 serenity kernel:  ? EvoForceIdleSatelliteChannelsWithAccel+0x238/0x5b0 [nvidia_modeset bd33c041e571115a574ac1b8306ecd5f1924565d]
Aug 31 14:36:27 serenity kernel:  ? ktime_get_raw_ts64+0x37/0x100
Aug 31 14:36:27 serenity kernel:  ? nvRMIdleBaseChannel+0xd3/0x100 [nvidia_modeset bd33c041e571115a574ac1b8306ecd5f1924565d]
Aug 31 14:36:27 serenity kernel:  ? nvSetDispModeEvo+0x1e11/0x43e0 [nvidia_modeset bd33c041e571115a574ac1b8306ecd5f1924565d]
Aug 31 14:36:27 serenity kernel:  ? nvKmsIoctl+0x103/0x2c0 [nvidia_modeset bd33c041e571115a574ac1b8306ecd5f1924565d]
Aug 31 14:36:27 serenity kernel:  ? nvkms_ioctl_from_kapi_try_pmlock+0x60/0xa0 [nvidia_modeset bd33c041e571115a574ac1b8306ecd5f1924565d]
Aug 31 14:36:27 serenity kernel:  ? ApplyModeSetConfig+0x14e/0xe40 [nvidia_modeset bd33c041e571115a574ac1b8306ecd5f1924565d]
Aug 31 14:36:27 serenity kernel:  ? ApplyModeSetConfig+0x755/0xe40 [nvidia_modeset bd33c041e571115a574ac1b8306ecd5f1924565d]
Aug 31 14:36:27 serenity kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Aug 31 14:36:27 serenity kernel:  ? nv_drm_atomic_apply_modeset_config+0x473/0x7f0 [nvidia_drm 2e36c0439e41d5eafbe4be4d3d946fd70ae4dc23]
Aug 31 14:36:27 serenity kernel:  ? nv_drm_atomic_apply_modeset_config+0x6fa/0x7f0 [nvidia_drm 2e36c0439e41d5eafbe4be4d3d946fd70ae4dc23]
Aug 31 14:36:27 serenity kernel:  ? drm_atomic_add_affected_connectors+0x111/0x120
Aug 31 14:36:27 serenity kernel:  ? nv_drm_atomic_commit+0x234/0x560 [nvidia_drm 2e36c0439e41d5eafbe4be4d3d946fd70ae4dc23]
Aug 31 14:36:27 serenity kernel:  ? drm_atomic_commit+0xb1/0xe0
Aug 31 14:36:27 serenity kernel:  ? __pfx___drm_printfn_info+0x10/0x10
Aug 31 14:36:27 serenity kernel:  ? drm_mode_atomic_ioctl+0xa82/0xcf0
Aug 31 14:36:27 serenity kernel:  ? __pfx_drm_mode_atomic_ioctl+0x10/0x10
Aug 31 14:36:27 serenity kernel:  ? drm_ioctl_kernel+0xae/0x100
Aug 31 14:36:27 serenity kernel:  ? drm_ioctl+0x29b/0x530
Aug 31 14:36:27 serenity kernel:  ? __pfx_drm_mode_atomic_ioctl+0x10/0x10
Aug 31 14:36:27 serenity kernel:  ? __x64_sys_ioctl+0x97/0xe0
Aug 31 14:36:27 serenity kernel:  ? do_syscall_64+0x81/0x970
Aug 31 14:36:27 serenity kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Aug 31 14:36:27 serenity kernel:  ? switch_fpu_return+0x4e/0xd0
Aug 31 14:36:27 serenity kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Aug 31 14:36:27 serenity kernel:  ? do_syscall_64+0x214/0x970
Aug 31 14:36:27 serenity kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Aug 31 14:36:27 serenity kernel:  ? __rseq_handle_notify_resume+0xa6/0x4b0
Aug 31 14:36:27 serenity kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Aug 31 14:36:27 serenity kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Aug 31 14:36:27 serenity kernel:  ? __x64_sys_ppoll+0xf3/0x180
Aug 31 14:36:27 serenity kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Aug 31 14:36:27 serenity kernel:  ? exit_to_user_mode_loop+0xcf/0x150
Aug 31 14:36:27 serenity kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Aug 31 14:36:27 serenity kernel:  ? do_syscall_64+0x214/0x970
Aug 31 14:36:27 serenity kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Aug 31 14:36:27 serenity kernel:  ? do_syscall_64+0x214/0x970
Aug 31 14:36:27 serenity kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Aug 31 14:36:27 serenity kernel:  ? exit_to_user_mode_loop+0xcf/0x150
Aug 31 14:36:27 serenity kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Aug 31 14:36:27 serenity kernel:  ? do_syscall_64+0x214/0x970
Aug 31 14:36:27 serenity kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Aug 31 14:36:27 serenity kernel:  ? do_syscall_64+0x214/0x970
Aug 31 14:36:27 serenity kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Aug 31 14:36:27 serenity kernel:  ? entry_SYSCALL_64_after_hwframe+0x76/0x7e
Aug 31 14:36:27 serenity kernel:  </TASK>

There's clearly an issue w/

Aug 31 15:18:07 serenity kernel: NVRM: loading NVIDIA UNIX Open Kernel Module for x86_64  580.76.05  Release Build  (root@)

Do you also get this w/ the binary nvidia module and in doubt disabling https://wiki.archlinux.org/title/NVIDIA … P_firmware ?

I did what you asked and … was able to get back to gnome with ctrl+alt+f2

The idea was to have no gnome or GDM running at all, just boot the multi-user.target (2nd link below) and startx from there.
Then please post your Xorg log, https://wiki.archlinux.org/title/Xorg#General if you encounter the same issue in this setup.
(I want to rule out the DPMS issue just being down to the gnome screenlocking)

Azuredas · 2025-09-01 22:40:18

I switched to the binary and added that param to my kernel. Issues persist. Here's a log of me doing the no-gnome boot, hopefully, correctly. It still crashes my display :(

https://0x0.st/KHdK.txt

seth · 2025-09-02 15:07:54

I switched to the binary and added that param to my kernel.

Nope:

Sep 01 17:23:20 serenity kernel: NVRM: loading NVIDIA UNIX Open Kernel Module for x86_64  580.76.05  Release Build  (root@)

Azuredas · 2025-09-03 13:51:35

I didn't realize the binary module means the proprietary one? I'm running on the proprietary one now, and it's been good so far. Will report back with some more rigorous testing later.

Azuredas · 2025-09-04 03:18:19

Okay I tested a little more. The issues continue. I tried the no-gnome setup again and it still dropped my monitor's session, but I could still wake it up by switching to tty2 or tty3. The logs don't seem to report anything when it stops either. Do I need more verbose logs or logs from a different place?

https://0x0.st/KXeC.txt

seth · 2025-09-04 13:08:55

Sep 03 22:08:34 serenity kernel: nvidia-modeset: WARNING: GPU:0: HDMI FRL link training failed.

https://forums.developer.nvidia.com/t/s … and/314590
https://forums.developer.nvidia.com/t/n … off/158456

Pattern there seems the necessity to physically turn off the monitor (though depending on the monitor model it might implicitly do that w/ the DPMS signal) and the use of VRR /240Hz
Does any of that apply to your situation? Do very brief DPMS stints trigger this?

Azuredas · 2025-09-06 01:02:01

That first one sounds incredibly similar to what I'm experiencing, though VRR was something I enabled recently. I dropped vrr and my refresh down to 120Hz to do some testing with this, and yeah brief dpms will trigger it, it doesn't have to be very long at all.

seth · 2025-09-06 07:51:57

it doesn't have to be very long at all

I mean like "one second" (the plan is to prevent the monitor from responding to the DPMS by powering down, though that won't lead to a solution, because that's the whole point of DPMS)
Do you btw. have a different monitor you could test?

no-gnome setup again and it still dropped my monitor's session, but I could still wake it up by switching to tty2 or tty3

The main problem would be to trigger a new handshake despite gnome.

Can you ssh into the compromised system?
https://man.archlinux.org/man/gdctl.1 - check the condition and try to change the mode (eg. from 240Hz to 120Hz or 60Hz or whatever is available)

Azuredas · 2025-09-10 16:15:35

I can ssh into it. I've switched to KDE Plasma and while gnome may not have been the problem KDE seems to have been a solution. It's been working really well, with no resume issues for several days. I did have issues with gnome on even the "one second" scenario. Usually it would be resumable with turning the monitor off and on again. I can try to install gnome again and give that a shot.

seth · 2025-09-10 19:53:15

Ftr, is this currently kwin_wayland or kwin_x11 ?
Does it work on both? Does it work w/ gnome on X11?

pswiatki · 2025-09-13 17:57:04

I have a similar issue. Not sure if different enough to create a separate post, so please advise if I should post separately @seth. Upon resume from sleep (it is s2idle) my system usually initialises all 3 external monitors correctly at first, but after several seconds, some of them (sometimes one, sometimes 2, I have yet to see all 3) go "no signal". Switching to VT and back usually restores things to normal, but on occasion, the displays remain "stubborn" and it takes several switches between VT and X to get stable video output.
My setup: DELL 3561 , Dell Thunderbolt TB16 docking station connected via Thunderbolt 3 cable. 2 identical HP LP2475w monitors and one AOC CQ27G2U/BK. Most of the time HP monitors experience loss of signal (only occasionally AOC). Xorg in use, no Wayland. The only thing I see in the log (/var/log/Xorg.0.log) is:

[ 17859.647] (II) AIGLX: Suspending AIGLX clients for VT switch
[ 17866.340] (II) AIGLX: Resuming AIGLX clients after VT switch
[ 17866.465] (II) modeset(0): EDID vendor "LGD", prod id 1668
[ 17866.465] (II) modeset(0): Printing DDC gathered Modelines:
[ 17866.465] (II) modeset(0): Modeline "1920x1080"x0.0  138.65  1920 1968 2000 2080  1080 1083 1088 1111 +hsync -vsync (66.7 kHz eP)
[ 17866.465] (II) modeset(0): Modeline "1920x1080"x0.0  110.95  1920 1968 2000 2080  1080 1083 1088 1111 +hsync -vsync (53.3 kHz e)
[ 17868.217] (II) modeset(0): EDID vendor "LGD", prod id 1668
[ 17868.217] (II) modeset(0): Printing DDC gathered Modelines:
[ 17868.217] (II) modeset(0): Modeline "1920x1080"x0.0  138.65  1920 1968 2000 2080  1080 1083 1088 1111 +hsync -vsync (66.7 kHz eP)
[ 17868.217] (II) modeset(0): Modeline "1920x1080"x0.0  110.95  1920 1968 2000 2080  1080 1083 1088 1111 +hsync -vsync (53.3 kHz e)
[ 17868.376] (II) event5  - Video Bus: is tagged by udev as: Keyboard

Video cards:

[root@sdr-aptv log]# lshw -class video
  *-display                 
       description: 3D controller
       product: TU117GLM [T600 Mobile]
       vendor: NVIDIA Corporation
       physical id: 0
       bus info: pci@0000:01:00.0
       logical name: /dev/fb0
       version: a1
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list rom fb
       configuration: depth=32 driver=nvidia latency=0 mode=1920x1080 visual=truecolor xres=1920 yres=1080
       resources: iomemory:600-5ff iomemory:600-5ff irq:16 memory:a3000000-a3ffffff memory:6000000000-600fffffff memory:6010000000-6011ffffff ioport:3000(size=128)
  *-display
       description: VGA compatible controller
       product: TigerLake-H GT1 [UHD Graphics]
       vendor: Intel Corporation
       physical id: 2
       bus info: pci@0000:00:02.0
       logical name: /dev/fb0
       version: 01
       width: 64 bits
       clock: 33MHz
       capabilities: pciexpress msi pm vga_controller bus_master cap_list rom fb
       configuration: depth=32 driver=i915 latency=0 resolution=1920,1080
       resources: iomemory:600-5ff iomemory:400-3ff irq:183 memory:6072000000-6072ffffff memory:4000000000-400fffffff ioport:4000(size=64) memory:c0000-dffff memory:4010000000-4016ffffff memory:4020000000-40ffffffff

This switching off happens only in Arch (Linux in general, I guess). Never seen it while in Windows.

If journal from the current boot (with suspend/resume events) is OK - here is the log.

pswiatki · 2025-09-13 18:00:25

pswiatki wrote:

Most of the time HP monitors experience loss of signal (only occasionally AOC).

Just to be perfectly clear: once fixed the video outputs (on all displays, including the laptop's internal LCD) remain stable (no issues with video) until the next suspend / resume.

seth · 2025-09-13 20:30:30

Are all of them attached to the dock?
Can you attach one of the HP ones directly to the notebook and does it then still show this behavior?
(iow: do we blame the dock?)

Edit: ps, sidebar: you want to disable systemd-networkd

Last edited by seth (2025-09-13 20:33:12)

pswiatki · 2025-09-13 23:07:55

seth wrote:

Are all of them attached to the dock?
Can you attach one of the HP ones directly to the notebook and does it then still show this behavior?
(iow: do we blame the dock?)
Edit: ps, sidebar: you want to disable systemd-networkd

Yes, all of them are attached to the dock. HPs are DP (1 normal, 1 mini-DP), while AOC is HDMI. I could potentially hook up one of the HPs directly, but I only have HDMI on the notebook itself, so such configuration would be slightly different from the current one.
Oh, oh.... and I forgot to mention in my original post: there is a 3x3 KVM switch between the PCs and those three monitors. But even before I hooked up that KVM, the issue was visible.
Also, as already mentioned, Windows has no such oddity at all.

seth wrote:

Do we blame the dock?

I don't think so - the same dock works perfectly OK in Windows (the only issue I had with it was a funky operation of the Ethernet controller, but that's completely separate).

sidebar: Would you be so kind as to point me in the proper direction so that I could learn why systemd-networkd shall be disabled? Thank you so much!

Last edited by pswiatki (2025-09-13 23:09:42)

pswiatki · 2025-09-13 23:18:00

Things have just gotten weirder: I had to quickly leave the office, so I just locked the desktop. Did not return to the PC for several hours. What I saw puzzled me a little. Both HPs running fine, AOC sleeping (no signal). Switching to VT and back fixed it. Here is what I see in the Xorg.0.log:

[ 19864.093] (II) event8  - PS/2 Generic Mouse: device is a pointer
[ 19864.139] (II) modeset(0): EDID vendor "LGD", prod id 1668
[ 19864.139] (II) modeset(0): Printing DDC gathered Modelines:
[ 19864.139] (II) modeset(0): Modeline "1920x1080"x0.0  138.65  1920 1968 2000 2080  1080 1083 1088 1111 +hsync -vsync (66.7 kHz eP)
[ 19864.139] (II) modeset(0): Modeline "1920x1080"x0.0  110.95  1920 1968 2000 2080  1080 1083 1088 1111 +hsync -vsync (53.3 kHz e)
[ 19921.064] (II) modeset(0): EDID vendor "LGD", prod id 1668
[ 19921.064] (II) modeset(0): Printing DDC gathered Modelines:
[ 19921.064] (II) modeset(0): Modeline "1920x1080"x0.0  138.65  1920 1968 2000 2080  1080 1083 1088 1111 +hsync -vsync (66.7 kHz eP)
[ 19921.064] (II) modeset(0): Modeline "1920x1080"x0.0  110.95  1920 1968 2000 2080  1080 1083 1088 1111 +hsync -vsync (53.3 kHz e)
[ 20254.844] (II) modeset(0): EDID vendor "LGD", prod id 1668
[ 20254.844] (II) modeset(0): Printing DDC gathered Modelines:
[ 20254.844] (II) modeset(0): Modeline "1920x1080"x0.0  138.65  1920 1968 2000 2080  1080 1083 1088 1111 +hsync -vsync (66.7 kHz eP)
[ 20254.844] (II) modeset(0): Modeline "1920x1080"x0.0  110.95  1920 1968 2000 2080  1080 1083 1088 1111 +hsync -vsync (53.3 kHz e)
[ 20375.294] (II) modeset(0): Allocate new frame buffer 6080x2520 stride
[ 20396.008] (II) modeset(0): Allocate new frame buffer 6400x2520 stride
[ 23039.898] (II) modeset(0): EDID vendor "LGD", prod id 1668
[ 23039.898] (II) modeset(0): Printing DDC gathered Modelines:
[ 23039.898] (II) modeset(0): Modeline "1920x1080"x0.0  138.65  1920 1968 2000 2080  1080 1083 1088 1111 +hsync -vsync (66.7 kHz eP)
[ 23039.898] (II) modeset(0): Modeline "1920x1080"x0.0  110.95  1920 1968 2000 2080  1080 1083 1088 1111 +hsync -vsync (53.3 kHz e)
[ 23040.028] (II) modeset(0): EDID vendor "LGD", prod id 1668
[ 23040.028] (II) modeset(0): Printing DDC gathered Modelines:
[ 23040.028] (II) modeset(0): Modeline "1920x1080"x0.0  138.65  1920 1968 2000 2080  1080 1083 1088 1111 +hsync -vsync (66.7 kHz eP)
[ 23040.028] (II) modeset(0): Modeline "1920x1080"x0.0  110.95  1920 1968 2000 2080  1080 1083 1088 1111 +hsync -vsync (53.3 kHz e)
[ 23046.202] (II) modeset(0): EDID vendor "LGD", prod id 1668
[ 23046.202] (II) modeset(0): Printing DDC gathered Modelines:
[ 23046.202] (II) modeset(0): Modeline "1920x1080"x0.0  138.65  1920 1968 2000 2080  1080 1083 1088 1111 +hsync -vsync (66.7 kHz eP)
[ 23046.202] (II) modeset(0): Modeline "1920x1080"x0.0  110.95  1920 1968 2000 2080  1080 1083 1088 1111 +hsync -vsync (53.3 kHz e)
[ 25162.689] (II) modeset(0): EDID vendor "LGD", prod id 1668
[ 25162.689] (II) modeset(0): Printing DDC gathered Modelines:
[ 25162.689] (II) modeset(0): Modeline "1920x1080"x0.0  138.65  1920 1968 2000 2080  1080 1083 1088 1111 +hsync -vsync (66.7 kHz eP)
[ 25162.689] (II) modeset(0): Modeline "1920x1080"x0.0  110.95  1920 1968 2000 2080  1080 1083 1088 1111 +hsync -vsync (53.3 kHz e)
[ 41868.418] (II) modeset(0): EDID vendor "LGD", prod id 1668
[ 41868.418] (II) modeset(0): Printing DDC gathered Modelines:
[ 41868.418] (II) modeset(0): Modeline "1920x1080"x0.0  138.65  1920 1968 2000 2080  1080 1083 1088 1111 +hsync -vsync (66.7 kHz eP)
[ 41868.418] (II) modeset(0): Modeline "1920x1080"x0.0  110.95  1920 1968 2000 2080  1080 1083 1088 1111 +hsync -vsync (53.3 kHz e)
[ 41897.677] (II) event5  - Video Bus: device removed
[ 41897.686] (II) event4  - Video Bus: device removed
[ 41897.694] (II) event1  - Power Button: device removed
[ 41897.701] (II) event2  - Sleep Button: device removed

None of the ModeLines has anything that would match the AOC (which is 2560x1440). Not sure what to think of that.....

Just checked, it is the internal LCD:

[pswiatki@sdr-aptv OBS]$ edid-decode LCD 
edid-decode (hex):

00 ff ff ff ff ff ff 00 30 e4 84 06 00 00 00 00
00 1e 01 04 95 22 13 78 ea 38 d5 97 5e 59 8e 27
1c 50 54 00 00 00 01 01 01 01 01 01 01 01 01 01
01 01 01 01 01 01 29 36 80 a0 70 38 1f 40 30 20
35 00 58 c2 10 00 00 1a 57 2b 80 a0 70 38 1f 40
30 20 35 00 58 c2 10 00 00 1a 00 00 00 fe 00 35
35 39 44 31 80 31 35 36 57 46 44 0a 00 00 00 00
00 00 41 31 99 00 10 00 00 0a 01 0a 20 20 00 eb

----------------

Block 0, Base EDID:
  EDID Structure Version & Revision: 1.4
  Vendor & Product Identification:
    Manufacturer: LGD
    Model: 1668
    Made in: 2020
  Basic Display Parameters & Features:
    Digital display
    Bits per primary color channel: 6
    DisplayPort interface
    Maximum image size: 34 cm x 19 cm
    Gamma: 2.20
    DPMS levels: Standby Suspend Off
    Supported color formats: RGB 4:4:4, YCrCb 4:4:4
    First detailed timing includes the native pixel format and preferred refresh rate
  Color Characteristics:
    Red  : 0.5898, 0.3701
    Green: 0.3496, 0.5546
    Blue : 0.1552, 0.1103
    White: 0.3134, 0.3291
  Established Timings I & II: none
  Standard Timings: none
  Detailed Timing Descriptors:
    DTD 1:  1920x1080   59.998788 Hz  16:9     66.659 kHz    138.650000 MHz (344 mm x 194 mm)
                 Hfront   48 Hsync  32 Hback   80 Hpol P
                 Vfront    3 Vsync   5 Vback   23 Vpol N
    DTD 2:  1920x1080   48.012013 Hz  16:9     53.341 kHz    110.950000 MHz (344 mm x 194 mm)
                 Hfront   48 Hsync  32 Hback   80 Hpol P
                 Vfront    3 Vsync   5 Vback   23 Vpol N
    Alphanumeric Data String: '559D1.156WFD'
    Manufacturer-Specified Display Descriptor (0x00): 00 00 00 00 41 31 99 00 10 00 00 0a 01 0a 20 20 '....A1........  '
Checksum: 0xeb

Last edited by pswiatki (2025-09-13 23:30:41)

Arch Linux

#1 2025-08-29 01:29:02

Black Screen or no signal on resume

#2 2025-08-29 07:32:51

Re: Black Screen or no signal on resume

#3 2025-08-30 01:11:41

Re: Black Screen or no signal on resume

#4 2025-08-30 20:43:38

Re: Black Screen or no signal on resume

#5 2025-08-30 23:44:09

Re: Black Screen or no signal on resume

#6 2025-08-31 08:30:21

Re: Black Screen or no signal on resume

#7 2025-08-31 12:39:59

Re: Black Screen or no signal on resume

#8 2025-08-31 15:15:25

Re: Black Screen or no signal on resume

#9 2025-08-31 19:09:01

Re: Black Screen or no signal on resume

#10 2025-08-31 20:27:21

Re: Black Screen or no signal on resume

#11 2025-09-01 07:19:28

Re: Black Screen or no signal on resume

#12 2025-09-01 22:40:18

Re: Black Screen or no signal on resume

#13 2025-09-02 15:07:54

Re: Black Screen or no signal on resume

#14 2025-09-03 13:51:35

Re: Black Screen or no signal on resume

#15 2025-09-04 03:18:19

Re: Black Screen or no signal on resume

#16 2025-09-04 13:08:55

Re: Black Screen or no signal on resume

#17 2025-09-06 01:02:01

Re: Black Screen or no signal on resume

#18 2025-09-06 07:51:57

Re: Black Screen or no signal on resume

#19 2025-09-10 16:15:35

Re: Black Screen or no signal on resume

#20 2025-09-10 19:53:15

Re: Black Screen or no signal on resume

#21 2025-09-13 17:57:04

Re: Black Screen or no signal on resume

#22 2025-09-13 18:00:25

Re: Black Screen or no signal on resume

#23 2025-09-13 20:30:30

Re: Black Screen or no signal on resume

#24 2025-09-13 23:07:55

Re: Black Screen or no signal on resume

#25 2025-09-13 23:18:00

Re: Black Screen or no signal on resume

Board footer