KDE issues after waking up from S3 (sleep) on Wayland

Skeleton2323 · 2024-11-09 11:49:22

Hey there, I'm running into a couple of issues whenever I put my system to sleep and wake it up after a bit of time.
Whenever I wake the system up from sleep, I get ghosty-like flickering windows, especially upon minimizing and maximizing, requiring me to log out and in again. Also, a lot of text boxes flat out disappear, showing blank spaces where the text on e.g. the start menu should be.
This issue has been going on since I've initially installed KDE and Arch, in July.
Is there any way to fix this? I'm aware NVidia on Wayland is finicky but is there any way around this?

Operating System: Arch Linux
KDE Plasma Version: 6.2.3
KDE Frameworks Version: 6.8.0
Qt Version: 6.8.0
Kernel Version: 6.11.6-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz
Memory: 15,6 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2
Manufacturer: ASUS
Product Name: All Series

journalctl since waking from sleep

 ...skipping...
Nov 09 13:39:14 ymarchlinuxrog kded6[875]: org.kde.pulseaudio: No object for name "@DEFAULT_SINK@"
Nov 09 13:39:14 ymarchlinuxrog kded6[875]: org.kde.pulseaudio: No object for name "@DEFAULT_SOURCE@"
Nov 09 13:39:14 ymarchlinuxrog kded6[875]: org.kde.pulseaudio: No object for name "alsa_input.pci-0000_00_1b.0.analog-stereo"
Nov 09 13:39:14 ymarchlinuxrog plasmashell[902]: org.kde.pulseaudio: No object for name "@DEFAULT_SINK@"
Nov 09 13:39:14 ymarchlinuxrog plasmashell[902]: org.kde.pulseaudio: No object for name "@DEFAULT_SOURCE@"
Nov 09 13:39:14 ymarchlinuxrog plasmashell[902]: org.kde.pulseaudio: No object for name "alsa_input.pci-0000_00_1b.0.analog-stereo"
Nov 09 13:39:14 ymarchlinuxrog kded6[875]: org.kde.pulseaudio: No object for name "alsa_input.pci-0000_00_1b.0.analog-stereo"
Nov 09 13:39:14 ymarchlinuxrog kded6[875]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1b.0.analog-stereo"
Nov 09 13:39:14 ymarchlinuxrog kded6[875]: org.kde.pulseaudio: No object for name "alsa_input.pci-0000_00_1b.0.analog-stereo"
Nov 09 13:39:14 ymarchlinuxrog kded6[875]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_01_00.1.hdmi-stereo.monitor"
Nov 09 13:39:14 ymarchlinuxrog kded6[875]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_01_00.1.hdmi-stereo.monitor"
Nov 09 13:39:14 ymarchlinuxrog kded6[875]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1b.0.analog-stereo.monitor"
Nov 09 13:39:14 ymarchlinuxrog plasmashell[902]: org.kde.pulseaudio: No object for name "alsa_input.pci-0000_00_1b.0.analog-stereo"
Nov 09 13:39:14 ymarchlinuxrog plasmashell[902]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1b.0.analog-stereo"
Nov 09 13:39:14 ymarchlinuxrog plasmashell[902]: org.kde.pulseaudio: No object for name "alsa_input.pci-0000_00_1b.0.analog-stereo"
Nov 09 13:39:14 ymarchlinuxrog plasmashell[902]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1b.0.analog-stereo"
Nov 09 13:39:14 ymarchlinuxrog plasmashell[902]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1b.0.analog-stereo.monitor"
Nov 09 13:39:14 ymarchlinuxrog plasmashell[902]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1b.0.analog-stereo.monitor"
Nov 09 13:39:14 ymarchlinuxrog plasmashell[902]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1b.0.analog-stereo.monitor"
Nov 09 13:39:15 ymarchlinuxrog kscreenlocker_greet[3173]: pam_systemd_home(kde:auth): New sd-bus connection (system-bus-pam-systemd-home-3173) opened.
Nov 09 13:39:18 ymarchlinuxrog google-chrome-stable[1178]: [1290:1290:1109/133918.947844:ERROR:shared_context_state.cc(1255)] SharedContextState context lost via ARB/EXT_robustness. Reset status = GL_GUILTY_CONTEXT_RESET_KHR
Nov 09 13:39:18 ymarchlinuxrog google-chrome-stable[1178]: [1290:1290:1109/133918.947970:ERROR:gpu_service_impl.cc(1159)] Exiting GPU process because some drivers can't recover from errors. GPU process will restart shortly.
Nov 09 13:39:18 ymarchlinuxrog google-chrome-stable[1178]: [1504:1:1109/133918.954096:ERROR:command_buffer_proxy_impl.cc(131)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
Nov 09 13:39:18 ymarchlinuxrog google-chrome-stable[1178]: [1169:1169:1109/133918.955798:ERROR:gpu_process_host.cc(980)] GPU process exited unexpectedly: exit_code=8704
Nov 09 13:39:19 ymarchlinuxrog kwin_wayland[720]: kwin_scene_opengl: A graphics reset attributable to the current GL context occurred.
Nov 09 13:39:19 ymarchlinuxrog google-chrome-stable[1178]: src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000
Nov 09 13:39:19 ymarchlinuxrog google-chrome-stable[1178]: src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000
Nov 09 13:39:19 ymarchlinuxrog google-chrome-stable[1178]: src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000
Nov 09 13:39:19 ymarchlinuxrog google-chrome-stable[1178]: src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000
Nov 09 13:39:19 ymarchlinuxrog google-chrome-stable[1178]: src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000
Nov 09 13:39:19 ymarchlinuxrog google-chrome-stable[1178]: src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000
Nov 09 13:39:19 ymarchlinuxrog google-chrome-stable[1178]: src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000
Nov 09 13:39:19 ymarchlinuxrog google-chrome-stable[1178]: src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000
Nov 09 13:39:19 ymarchlinuxrog google-chrome-stable[1178]: src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000
Nov 09 13:39:19 ymarchlinuxrog google-chrome-stable[1178]: src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000
Nov 09 13:39:19 ymarchlinuxrog kwin_wayland[720]: BlurConfig::instance called after the first use - ignoring
Nov 09 13:39:19 ymarchlinuxrog kwin_wayland[720]: KscreenConfig::instance called after the first use - ignoring
Nov 09 13:39:19 ymarchlinuxrog kwin_wayland[720]: OverviewConfig::instance called after the first use - ignoring
Nov 09 13:39:19 ymarchlinuxrog kwin_wayland[720]: ShakeCursorConfig::instance called after the first use - ignoring
Nov 09 13:39:19 ymarchlinuxrog kwin_wayland[720]: SlideConfig::instance called after the first use - ignoring
Nov 09 13:39:19 ymarchlinuxrog kwin_wayland[720]: SlidingPopupsConfig::instance called after the first use - ignoring
Nov 09 13:39:19 ymarchlinuxrog kwin_wayland[720]: WindowViewConfig::instance called after the first use - ignoring
Nov 09 13:39:19 ymarchlinuxrog kwin_wayland[720]: ZoomConfig::instance called after the first use - ignoring
Nov 09 13:39:21 ymarchlinuxrog kscreenlocker_greet[3173]: Failed to write to the pipe: Bad file descriptor.
Nov 09 13:39:27 ymarchlinuxrog kwin_wayland[720]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated.
Nov 09 13:39:27 ymarchlinuxrog kwin_wayland[720]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated.
Nov 09 13:39:27 ymarchlinuxrog kwin_wayland[720]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated.
Nov 09 13:39:27 ymarchlinuxrog kwin_wayland[720]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated.
Nov 09 13:39:27 ymarchlinuxrog kwin_wayland[720]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated.
Nov 09 13:39:27 ymarchlinuxrog kwin_wayland[720]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated.
Nov 09 13:39:27 ymarchlinuxrog kwin_wayland[720]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated.
Nov 09 13:39:27 ymarchlinuxrog kwin_wayland[720]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated.
Nov 09 13:39:40 ymarchlinuxrog google-chrome-stable[1178]: [1169:1169:1109/133940.326627:ERROR:atom_cache.cc(229)] Add WM_CHANGE_STATE to kAtomsToCache
Nov 09 13:39:41 ymarchlinuxrog kioworker[2990]: The following paths were searched for Qt WebEngine dictionaries:
                                                     /usr/lib/kf6/qtwebengine_dictionaries
                                                     /usr/share/qt6/qtwebengine_dictionaries
                                                   but could not find it.
                                                   You may override the default search path by using QTWEBENGINE_DICTIONARIES_PATH environment variable.
                                                   Spellchecking can not be enabled.
Nov 09 13:39:41 ymarchlinuxrog kioworker[2990]: kf.kio.core: Connection::send() called with connection not inited
Nov 09 13:39:41 ymarchlinuxrog kioworker[2990]: kf.kio.core: An error occurred during write. The worker terminates now.
Nov 09 13:39:44 ymarchlinuxrog kioworker[3461]: The following paths were searched for Qt WebEngine dictionaries:
                                                     /usr/lib/kf6/qtwebengine_dictionaries
                                                     /usr/share/qt6/qtwebengine_dictionaries
                                                   but could not find it.
                                                   You may override the default search path by using QTWEBENGINE_DICTIONARIES_PATH environment variable.
                                                   Spellchecking can not be enabled.
Nov 09 13:39:45 ymarchlinuxrog kioworker[3461]: kf.kio.core: Connection::send() called with connection not inited
Nov 09 13:39:45 ymarchlinuxrog kioworker[3461]: kf.kio.core: An error occurred during write. The worker terminates now.
Nov 09 13:39:47 ymarchlinuxrog plasmashell[902]: kf.windowsystem.wayland: Failed to recreate shadow for PlasmaQuick::AppletPopup_QML_158(0x62ac60534e70, name="popupWindow")
Nov 09 13:39:50 ymarchlinuxrog systemsettings[1172]: The cached device pixel ratio value was stale on window expose.  Please file a QTBUG which explains how to reproduce.
Nov 09 13:39:50 ymarchlinuxrog systemd[669]: app-systemsettings@e09defad33b34504adee81babe6f4c23.service: Consumed 1.610s CPU time, 119.8M memory peak.
Nov 09 13:39:50 ymarchlinuxrog pipewire[799]: pw.node: (alsa_output.pci-0000_00_1b.0.analog-stereo-59) graph xrun not-triggered (0 suppressed)
Nov 09 13:39:50 ymarchlinuxrog pipewire[799]: pw.node: (alsa_output.pci-0000_00_1b.0.analog-stereo-59) xrun state:0x7802b821c008 pending:1/1 s:0 a:0 f:0 waiting:0 process:0 status:triggered
Nov 09 13:40:33 ymarchlinuxrog kwin_wayland[720]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated.
Nov 09 13:40:33 ymarchlinuxrog kwin_wayland[720]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated.
Nov 09 13:40:33 ymarchlinuxrog kwin_wayland[720]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated.
Nov 09 13:40:33 ymarchlinuxrog kwin_wayland[720]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated.
Nov 09 13:40:33 ymarchlinuxrog kwin_wayland[720]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated.
Nov 09 13:40:33 ymarchlinuxrog kwin_wayland[720]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated.
Nov 09 13:40:33 ymarchlinuxrog kwin_wayland[720]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated.
Nov 09 13:40:33 ymarchlinuxrog kwin_wayland[720]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated.
lines 672917-672997/672997 (END)

Last edited by Skeleton2323 (2024-11-09 11:56:21)

seth · 2024-11-09 18:08:00

The system journal (and including before the sleep) would tell use more.

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

Skeleton2323 · 2024-11-09 22:26:01

http://0x0.st/XD0Z.txt

seth · 2024-11-10 08:09:06

That's a 30s boot and there's no sleep cycle (or even attempt).

Skeleton2323 · 2024-11-10 11:57:28

apologies for not including a sleep cycle, here's one where I put the system to sleep for quite a while. a new issue that I faced this time was that the KDE lock screen's "accept password" button did nothing, requiring me to click "switch user" to log in from SDDM and also, this time, the text boxes seemed to not have disappeared completely.
http://0x0.st/XDnN.txt

Last edited by Skeleton2323 (2024-11-10 11:58:39)

seth · 2024-11-10 14:56:49

Topic-adjacent, check

nomodeset nvidia-drm.modeset=1 nvidia_drm.fbdev=1

nvidia-drm.modeset=1 nvidia_drm.fbdev=0

whether disabling fbdev helps and remove the nomodeset parameter.

Then there's a redonkulous amount of

Νοε 10 13:47:12 ymarchlinuxrog kernel: ------------[ cut here ]------------
Νοε 10 13:47:12 ymarchlinuxrog kernel: WARNING: CPU: 6 PID: 1469 at include/linux/rwsem.h:80 follow_pte+0x1de/0x200
Νοε 10 13:47:12 ymarchlinuxrog kernel: Modules linked in: snd_seq_dummy snd_hrtimer snd_seq snd_seq_device vfat fat mousedev joydev hid_generic intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm eeepc_wmi crct10dif_pclmul asus_wmi crc32_pclmul platform_profile snd_hda_codec_realtek polyval_clmulni polyval_generic snd_hda_codec_generic usbhid ghash_clmulni_intel snd_hda_scodec_component sha512_ssse3 snd_hda_codec_hdmi sha256_ssse3 sha1_ssse3 aesni_intel snd_hda_intel ucsi_ccg gf128mul snd_intel_dspcfg crypto_simd typec_ucsi snd_intel_sdw_acpi cryptd typec snd_hda_codec iTCO_wdt at24 roles intel_pmc_bxt rapl mei_hdcp mei_pxp snd_hda_core i8042 iTCO_vendor_support intel_cstate i2c_i801 sparse_keymap serio snd_hwdep i2c_smbus intel_uncore rfkill wmi_bmof razermouse(OE) razerkbd(OE) mxm_wmi pcspkr i2c_mux snd_pcm i2c_nvidia_gpu lpc_ich e1000e snd_timer mei_me snd soundcore ptp mei pps_core acpi_pad mac_hid ip6t_REJECT nf_reject_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 xt_LOG nf_log_syslog xt_multiport
Νοε 10 13:47:12 ymarchlinuxrog kernel:  xt_limit xt_addrtype xt_tcpudp xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c ip6table_filter ip6_tables iptable_filter i2c_dev sg crypto_user dm_mod loop nfnetlink ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 nvme sr_mod crc32c_intel nvme_core cdrom xhci_pci nvme_auth xhci_pci_renesas nvidia_drm(OE) drm_ttm_helper ttm nvidia_uvm(OE) nvidia_modeset(OE) video wmi nvidia(OE)
Νοε 10 13:47:12 ymarchlinuxrog kernel: CPU: 6 UID: 0 PID: 1469 Comm: nvidia-sleep.sh Tainted: G        W  OE      6.11.6-arch1-1 #1 1400000003000000474e5500ffbb7565590de2b9
Νοε 10 13:47:12 ymarchlinuxrog kernel: Tainted: [W]=WARN, [O]=OOT_MODULE, [E]=UNSIGNED_MODULE
Νοε 10 13:47:12 ymarchlinuxrog kernel: Hardware name: ASUS All Series/MAXIMUS VII HERO, BIOS 3103 03/09/2016
Νοε 10 13:47:12 ymarchlinuxrog kernel: RIP: 0010:follow_pte+0x1de/0x200
Νοε 10 13:47:12 ymarchlinuxrog kernel: Code: cc cc cc 48 81 e2 00 00 00 c0 48 09 c2 48 f7 d2 48 85 fa 75 20 e8 42 f1 ff ff 48 8b 35 5b b3 5c 01 48 81 e6 00 00 00 c0 eb 8d <0f> 0b 48 3b 1f 0f 83 50 fe ff ff bd ea ff ff ff eb b6 49 8b 3c 24
Νοε 10 13:47:12 ymarchlinuxrog kernel: RSP: 0018:ffffb2c4cd22b898 EFLAGS: 00010246
Νοε 10 13:47:12 ymarchlinuxrog kernel: RAX: 0000000000000000 RBX: 00007f898581b000 RCX: ffffb2c4cd22b8d8
Νοε 10 13:47:12 ymarchlinuxrog kernel: RDX: ffffb2c4cd22b8d0 RSI: 00007f898581b000 RDI: ffff956858785730
Νοε 10 13:47:12 ymarchlinuxrog kernel: RBP: ffffb2c4cd22b918 R08: ffffb2c4cd22ba70 R09: 0000000000000000
Νοε 10 13:47:12 ymarchlinuxrog kernel: R10: 000000000040003b R11: 0000000000000000 R12: ffffb2c4cd22b8d8
Νοε 10 13:47:12 ymarchlinuxrog kernel: R13: ffffb2c4cd22b8d0 R14: ffff95684c83ac00 R15: 0000000000000000
Νοε 10 13:47:12 ymarchlinuxrog kernel: FS:  000070b373227b80(0000) GS:ffff956b4ed00000(0000) knlGS:0000000000000000
Νοε 10 13:47:12 ymarchlinuxrog kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Νοε 10 13:47:12 ymarchlinuxrog kernel: CR2: 000062ff60b81148 CR3: 000000011735e005 CR4: 00000000001706f0
Νοε 10 13:47:12 ymarchlinuxrog kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Νοε 10 13:47:12 ymarchlinuxrog kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Νοε 10 13:47:12 ymarchlinuxrog kernel: Call Trace:
Νοε 10 13:47:12 ymarchlinuxrog kernel:  <TASK>
Νοε 10 13:47:12 ymarchlinuxrog kernel:  ? follow_pte+0x1de/0x200
Νοε 10 13:47:12 ymarchlinuxrog kernel:  ? __warn.cold+0x8e/0xe8
Νοε 10 13:47:12 ymarchlinuxrog kernel:  ? follow_pte+0x1de/0x200
Νοε 10 13:47:12 ymarchlinuxrog kernel:  ? report_bug+0xff/0x140
Νοε 10 13:47:12 ymarchlinuxrog kernel:  ? handle_bug+0x3c/0x80
Νοε 10 13:47:12 ymarchlinuxrog kernel:  ? exc_invalid_op+0x17/0x70
Νοε 10 13:47:12 ymarchlinuxrog kernel:  ? asm_exc_invalid_op+0x1a/0x20
Νοε 10 13:47:12 ymarchlinuxrog kernel:  ? follow_pte+0x1de/0x200
Νοε 10 13:47:12 ymarchlinuxrog kernel:  ? unmap_page_range+0x1568/0x1600
Νοε 10 13:47:12 ymarchlinuxrog kernel:  follow_phys+0x49/0x110
Νοε 10 13:47:12 ymarchlinuxrog kernel:  untrack_pfn+0x55/0x120
Νοε 10 13:47:12 ymarchlinuxrog kernel:  unmap_single_vma+0xa6/0xe0
Νοε 10 13:47:12 ymarchlinuxrog kernel:  zap_page_range_single+0x122/0x1d0
Νοε 10 13:47:12 ymarchlinuxrog kernel:  unmap_mapping_range+0x116/0x140
Νοε 10 13:47:12 ymarchlinuxrog kernel:  nv_revoke_gpu_mappings_locked+0x47/0x70 [nvidia 1400000003000000474e550098469cc57c81fdc0]
Νοε 10 13:47:12 ymarchlinuxrog kernel:  nv_set_system_power_state+0x1cd/0x480 [nvidia 1400000003000000474e550098469cc57c81fdc0]
Νοε 10 13:47:12 ymarchlinuxrog kernel:  nv_procfs_write_suspend+0xef/0x170 [nvidia 1400000003000000474e550098469cc57c81fdc0]
Νοε 10 13:47:12 ymarchlinuxrog kernel:  proc_reg_write+0x5d/0xa0
Νοε 10 13:47:12 ymarchlinuxrog kernel:  vfs_write+0xfe/0x460
Νοε 10 13:47:12 ymarchlinuxrog kernel:  ksys_write+0x6d/0xf0
Νοε 10 13:47:12 ymarchlinuxrog kernel:  do_syscall_64+0x82/0x190
Νοε 10 13:47:12 ymarchlinuxrog kernel:  ? __alloc_pages_noprof+0x184/0x350
Νοε 10 13:47:12 ymarchlinuxrog kernel:  ? __mod_memcg_lruvec_state+0xa0/0x150
Νοε 10 13:47:12 ymarchlinuxrog kernel:  ? __lruvec_stat_mod_folio+0x83/0xd0
Νοε 10 13:47:12 ymarchlinuxrog kernel:  ? set_ptes.isra.0+0x41/0x90
Νοε 10 13:47:12 ymarchlinuxrog kernel:  ? do_anonymous_page+0xfe/0x870
Νοε 10 13:47:12 ymarchlinuxrog kernel:  ? __pte_offset_map+0x1b/0x180
Νοε 10 13:47:12 ymarchlinuxrog kernel:  ? __handle_mm_fault+0xbe7/0x1030
Νοε 10 13:47:12 ymarchlinuxrog kernel:  ? syscall_exit_to_user_mode+0x10/0x200
Νοε 10 13:47:12 ymarchlinuxrog kernel:  ? __count_memcg_events+0x58/0xf0
Νοε 10 13:47:12 ymarchlinuxrog kernel:  ? count_memcg_events.constprop.0+0x1a/0x30
Νοε 10 13:47:12 ymarchlinuxrog kernel:  ? handle_mm_fault+0x1bb/0x2c0
Νοε 10 13:47:12 ymarchlinuxrog kernel:  ? do_user_addr_fault+0x36c/0x620
Νοε 10 13:47:12 ymarchlinuxrog kernel:  ? exc_page_fault+0x81/0x190
Νοε 10 13:47:12 ymarchlinuxrog kernel:  entry_SYSCALL_64_after_hwframe+0x76/0x7e
Νοε 10 13:47:12 ymarchlinuxrog kernel: RIP: 0033:0x70b3733a47a4
Νοε 10 13:47:12 ymarchlinuxrog kernel: Code: c7 00 16 00 00 00 b8 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 80 3d c5 28 0e 00 00 74 13 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 54 c3 0f 1f 00 55 48 89 e5 48 83 ec 20 48 89
Νοε 10 13:47:12 ymarchlinuxrog kernel: RSP: 002b:00007ffc59af0a58 EFLAGS: 00000202 ORIG_RAX: 0000000000000001
Νοε 10 13:47:12 ymarchlinuxrog kernel: RAX: ffffffffffffffda RBX: 0000000000000008 RCX: 000070b3733a47a4
Νοε 10 13:47:12 ymarchlinuxrog kernel: RDX: 0000000000000008 RSI: 000062ff60b80d40 RDI: 0000000000000001
Νοε 10 13:47:12 ymarchlinuxrog kernel: RBP: 00007ffc59af0a80 R08: 0000000000000410 R09: 0000000000000001
Νοε 10 13:47:12 ymarchlinuxrog kernel: R10: 0000000000000004 R11: 0000000000000202 R12: 0000000000000008
Νοε 10 13:47:12 ymarchlinuxrog kernel: R13: 000062ff60b80d40 R14: 000070b3734805c0 R15: 000070b37347dea0
Νοε 10 13:47:12 ymarchlinuxrog kernel:  </TASK>
Νοε 10 13:47:12 ymarchlinuxrog kernel: ---[ end trace 0000000000000000 ]---

and ultimately

Νοε 10 13:50:29 ymarchlinuxrog systemd[1]: nvidia-resume.service: Deactivated successfully.
Νοε 10 13:50:29 ymarchlinuxrog systemd[1]: Finished NVIDIA system resume actions.
Νοε 10 13:50:29 ymarchlinuxrog kernel: NVRM: GPU at PCI:0000:01:00: GPU-4f85e9fb-2e29-bd4f-df26-c083657e6d18
Νοε 10 13:50:29 ymarchlinuxrog kernel: NVRM: Xid (PCI:0000:01:00): 13, pid='<unknown>', name=<unknown>, Graphics Exception: Shader Program Header 18 Error
Νοε 10 13:50:29 ymarchlinuxrog kernel: NVRM: Xid (PCI:0000:01:00): 13, pid='<unknown>', name=<unknown>, Graphics Exception: ESR 0x405840=0x82040000
Νοε 10 13:50:29 ymarchlinuxrog kernel: NVRM: Xid (PCI:0000:01:00): 13, pid='<unknown>', name=<unknown>, Graphics Exception: ESR 0x405848=0x80000000
Νοε 10 13:50:29 ymarchlinuxrog kernel: NVRM: Xid (PCI:0000:01:00): 13, pid=791, name=kwin_wayland, Graphics Exception: ChID 0009, Class 0000c597, Offset 00000000, Data 00000000
Νοε 10 13:50:29 ymarchlinuxrog kernel: NVRM: Xid (PCI:0000:01:00): 13, pid='<unknown>', name=<unknown>, Graphics Exception: Shader Program Header 11 Error
Νοε 10 13:50:29 ymarchlinuxrog kernel: NVRM: Xid (PCI:0000:01:00): 13, pid='<unknown>', name=<unknown>, Graphics Exception: Shader Program Header 18 Error
Νοε 10 13:50:29 ymarchlinuxrog kernel: NVRM: Xid (PCI:0000:01:00): 13, pid='<unknown>', name=<unknown>, Graphics Exception: ESR 0x405840=0xa2040800
Νοε 10 13:50:29 ymarchlinuxrog kernel: NVRM: Xid (PCI:0000:01:00): 13, pid='<unknown>', name=<unknown>, Graphics Exception: ESR 0x405848=0x80000000
Νοε 10 13:50:29 ymarchlinuxrog kernel: NVRM: Xid (PCI:0000:01:00): 13, pid='<unknown>', name=<unknown>, Graphics Exception: ChID 006c, Class 0000c597, Offset 00000000, Data 00000000

https://wiki.archlinux.org/title/NVIDIA … er_suspend
Add "nvidia.NVreg_PreserveVideoMemoryAllocations=0" to the kernel parameters and DISable all of nvidia-suspend.service, nvidia-hibernate.service, and nvidia-resume.service and see whether that makes the situation better or worse.
These are supposed to mitigate VRAM decay (which would typically lead to this) but there's certainly some problem with them, https://github.com/NVIDIA/open-gpu-kern … issues/719

You could also try to use "nvidia.NVreg_TemporaryFilePath=/tmp", though might run OOM w/ that

Skeleton2323 · 2024-11-10 20:02:15

I tried changing the parameters (and disabling all the hibernate/sleep systemd modules) and apparently going to sleep without anything open doesn't seem to cause any issues, whereas if I have any programs maximized and then go to sleep, that's when chaos ensues.

journalctl -b from going to sleep freshly after boot without opening any programs. The KDE lockscreen issue still persisted but there were no graphical glitches.
http://0x0.st/XDFz.txt

Last edited by Skeleton2323 (2024-11-10 20:27:22)

seth · 2024-11-10 21:12:41

The nvidia-sleep induced kernel warnings are (usurprisingly) gone but there's still

Νοε 10 21:45:56 ymarchlinuxrog kernel: NVRM: GPU at PCI:0000:01:00: GPU-4f85e9fb-2e29-bd4f-df26-c083657e6d18
Νοε 10 21:45:56 ymarchlinuxrog kernel: NVRM: Xid (PCI:0000:01:00): 13, pid='<unknown>', name=<unknown>, Graphics Exception: Shader Program Header 18 Error
Νοε 10 21:45:56 ymarchlinuxrog kernel: NVRM: Xid (PCI:0000:01:00): 13, pid='<unknown>', name=<unknown>, Graphics Exception: ESR 0x405840=0x82040000
Νοε 10 21:45:56 ymarchlinuxrog kernel: NVRM: Xid (PCI:0000:01:00): 13, pid='<unknown>', name=<unknown>, Graphics Exception: ESR 0x405848=0x80000000
Νοε 10 21:45:56 ymarchlinuxrog kernel: NVRM: Xid (PCI:0000:01:00): 13, pid=779, name=kwin_wayland, Graphics Exception: ChID 0009, Class 0000c597, Offset 00000000, Data 00000000
Νοε 10 21:45:57 ymarchlinuxrog kernel: NVRM: Xid (PCI:0000:01:00): 13, pid='<unknown>', name=<unknown>, Graphics Exception: Shader Program Header 11 Error
Νοε 10 21:45:57 ymarchlinuxrog kernel: NVRM: Xid (PCI:0000:01:00): 13, pid='<unknown>', name=<unknown>, Graphics Exception: Shader Program Header 18 Error
Νοε 10 21:45:57 ymarchlinuxrog kernel: NVRM: Xid (PCI:0000:01:00): 13, pid='<unknown>', name=<unknown>, Graphics Exception: ESR 0x405840=0xa2040800
Νοε 10 21:45:57 ymarchlinuxrog kernel: NVRM: Xid (PCI:0000:01:00): 13, pid='<unknown>', name=<unknown>, Graphics Exception: ESR 0x405848=0x80000000
Νοε 10 21:45:57 ymarchlinuxrog kernel: NVRM: Xid (PCI:0000:01:00): 13, pid='<unknown>', name=<unknown>, Graphics Exception: ChID 006c, Class 0000c597, Offset 00000000, Data 00000000

https://bugs.kde.org/show_bug.cgi?id=473393
https://forums.developer.nvidia.com/t/g … top/309259

What if you re-enable the VRAM preservation services except for the resume.service and also try https://aur.archlinux.org/packages/nvidia-535xx-dkms instead of the 565xx drivers?

The lockscreen is essentially a fullscreen window. Does that condition also hold w/ the sleep services enabled?

Arch Linux

#1 2024-11-09 11:49:22

KDE issues after waking up from S3 (sleep) on Wayland

#2 2024-11-09 18:08:00

Re: KDE issues after waking up from S3 (sleep) on Wayland

#3 2024-11-09 22:26:01

Re: KDE issues after waking up from S3 (sleep) on Wayland

#4 2024-11-10 08:09:06

Re: KDE issues after waking up from S3 (sleep) on Wayland

#5 2024-11-10 11:57:28

Re: KDE issues after waking up from S3 (sleep) on Wayland

#6 2024-11-10 14:56:49

Re: KDE issues after waking up from S3 (sleep) on Wayland

#7 2024-11-10 20:02:15

Re: KDE issues after waking up from S3 (sleep) on Wayland

#8 2024-11-10 21:12:41

Re: KDE issues after waking up from S3 (sleep) on Wayland

Board footer