System crash/frozen ~5min after gaming (related to Flatpak nvidia driver)

[Kobold]

Hello,
After i had a gaming session (native linux game "beyond all reason) and had only open my Firefox and Terminal, after i was done with gaming.

My mouse cursor vanished from one second to another and my keyboard also didn’t make any response to my input… as i said nothing else was open and i was done with gaming.

I try to use some Reisub Combos, first i pressed alt+print+f and alt+print+i but nothing happens (visually):

I also pressed crtl+alt+f3 for TTY but nothing, then i press alt+print+b and my system was restarting (Probably the worst way to use Reisub ).

I realise now that alt+print+o should be the better option, anyways after i was back in Linux to find the error’s i saw that alt+print+f (free memory) was working but just not visual, related to my error logs:

$ journalctl -b -1 -p3 --no-pager
Aug 25 00:51:54 koboldx-z170 kernel: x86/cpu: SGX disabled by BIOS.
Aug 25 00:51:55 koboldx-z170 kernel: 
Aug 25 00:52:02 koboldx-z170 kernel: [drm:drm_new_set_master] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
Aug 25 00:52:02 koboldx-z170 kernel: [drm:drm_new_set_master] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
Aug 25 00:52:04 koboldx-z170 pulseaudio[1415]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer 'org.bluez': unit failed
Aug 25 01:49:21 koboldx-z170 systemd-coredump[5572]: [🡕] Process 5563 (gpu-driver) of user 1000 dumped core.
                                                     
                                                     Stack trace of thread 183:
                                                     #0  0x000055ae3822bcc7 n/a (spring + 0x8b5cc7)
                                                     #1  0x000055ae38243a25 n/a (spring + 0x8cda25)
                                                     #2  0x000055ae38491fe2 n/a (spring + 0xb1bfe2)
                                                     #3  0x000055ae38480811 n/a (spring + 0xb0a811)
                                                     #4  0x000055ae3824c98c n/a (spring + 0x8d698c)
                                                     #5  0x000055ae3824cbdf n/a (spring + 0x8d6bdf)
                                                     #6  0x000055ae38492190 n/a (spring + 0xb1c190)
                                                     #7  0x000055ae384967e8 n/a (spring + 0xb207e8)
                                                     #8  0x000055ae38497460 n/a (spring + 0xb21460)
                                                     #9  0x000055ae3846e7f5 n/a (spring + 0xaf87f5)
                                                     #10 0x00007fbc20f9008a n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x2808a)
                                                     #11 0x00007fbc20f9014b n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x2814b)
                                                     #12 0x000055ae37cfc5fa _start (spring + 0x3865fa)
                                                     
                                                     Stack trace of thread 185:
                                                     #0  0x00007fbc21041f63 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0xd9f63)
                                                     #1  0x00007fbc21054e27 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0xece27)
                                                     #2  0x000055ae38488a08 n/a (spring + 0xb12a08)
                                                     #3  0x000055ae38f8645f n/a (spring + 0x161045f)
                                                     #4  0x00007fbc20ff6e39 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x8ee39)
                                                     #5  0x00007fbc2107e9c4 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x1169c4)
                                                     ELF object binary architecture: AMD x86-64
Aug 25 01:49:34 koboldx-z170 systemd-coredump[5820]: [🡕] Process 5814 (gpu-driver) of user 1000 dumped core.
                                                     
                                                     Stack trace of thread 172:
                                                     #0  0x0000557420ea9cc7 n/a (spring + 0x8b5cc7)
                                                     #1  0x0000557420ec1a25 n/a (spring + 0x8cda25)
                                                     #2  0x000055742110ffe2 n/a (spring + 0xb1bfe2)
                                                     #3  0x00005574210fe811 n/a (spring + 0xb0a811)
                                                     #4  0x0000557420eca98c n/a (spring + 0x8d698c)
                                                     #5  0x0000557420ecabdf n/a (spring + 0x8d6bdf)
                                                     #6  0x0000557421110190 n/a (spring + 0xb1c190)
                                                     #7  0x00005574211147e8 n/a (spring + 0xb207e8)
                                                     #8  0x0000557421115460 n/a (spring + 0xb21460)
                                                     #9  0x00005574210ec7f5 n/a (spring + 0xaf87f5)
                                                     #10 0x00007f94aca6e08a n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x2808a)
                                                     #11 0x00007f94aca6e14b n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x2814b)
                                                     #12 0x000055742097a5fa _start (spring + 0x3865fa)
                                                     
                                                     Stack trace of thread 176:
                                                     #0  0x00007f94acb1ff63 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0xd9f63)
                                                     #1  0x00007f94acb32e27 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0xece27)
                                                     #2  0x00005574210fe610 n/a (spring + 0xb0a610)
                                                     #3  0x00005574210fe66e n/a (spring + 0xb0a66e)
                                                     #4  0x0000557421c0445f n/a (spring + 0x161045f)
                                                     #5  0x00007f94acad4e39 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x8ee39)
                                                     #6  0x00007f94acb5c9c4 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x1169c4)
                                                     ELF object binary architecture: AMD x86-64
Aug 25 04:04:13 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Aug 25 04:04:13 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Aug 25 04:04:13 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Aug 25 04:04:13 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Aug 25 04:04:13 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Aug 25 04:04:13 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Aug 25 04:04:13 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Aug 25 04:04:13 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Aug 25 04:04:13 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Aug 25 04:04:13 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Aug 25 04:04:13 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Aug 25 04:04:13 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Aug 25 04:04:13 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Aug 25 04:04:13 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Aug 25 04:04:13 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Aug 25 04:04:23 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Aug 25 04:04:33 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Aug 25 04:04:43 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Aug 25 04:04:53 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Aug 25 04:05:03 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Aug 25 04:05:03 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Aug 25 04:05:03 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Aug 25 04:05:08 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Aug 25 04:05:08 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Aug 25 04:07:50 koboldx-z170 kernel: Out of memory: Killed process 5226 (Web Content) total-vm:2455432kB, anon-rss:14608kB, file-rss:41876kB, shmem-rss:516kB, UID:1000 pgtables:476kB oom_score_adj:233
Aug 25 04:07:53 koboldx-z170 kernel: Out of memory: Killed process 1275 (plasmashell) total-vm:2653796kB, anon-rss:301196kB, file-rss:212464kB, shmem-rss:36kB, UID:1000 pgtables:1372kB oom_score_adj:200
Aug 25 04:07:54 koboldx-z170 kernel: Out of memory: Killed process 1265 (kwin_x11) total-vm:1623976kB, anon-rss:341476kB, file-rss:127148kB, shmem-rss:0kB, UID:1000 pgtables:1352kB oom_score_adj:200
Aug 25 04:07:54 koboldx-z170 kernel: Out of memory: Killed process 5836 (konsole) total-vm:864688kB, anon-rss:25536kB, file-rss:119396kB, shmem-rss:3328kB, UID:1000 pgtables:440kB oom_score_adj:200
Aug 25 04:07:55 koboldx-z170 kernel: Out of memory: Killed process 1264 (kded6) total-vm:857076kB, anon-rss:25628kB, file-rss:77096kB, shmem-rss:0kB, UID:1000 pgtables:396kB oom_score_adj:200
Aug 25 04:07:55 koboldx-z170 kernel: Out of memory: Killed process 1310 (polkit-kde-auth) total-vm:611328kB, anon-rss:18600kB, file-rss:64028kB, shmem-rss:0kB, UID:1000 pgtables:344kB oom_score_adj:200
Aug 25 04:07:55 koboldx-z170 kernel: Out of memory: Killed process 1311 (org_kde_powerde) total-vm:609280kB, anon-rss:19888kB, file-rss:63984kB, shmem-rss:0kB, UID:1000 pgtables:324kB oom_score_adj:200
Aug 25 04:07:56 koboldx-z170 kernel: Out of memory: Killed process 1312 (xdg-desktop-por) total-vm:391648kB, anon-rss:18516kB, file-rss:64732kB, shmem-rss:0kB, UID:1000 pgtables:312kB oom_score_adj:200
Aug 25 04:08:33 koboldx-z170 systemd[1183]: Failed to start KDE Plasma Workspace.
Aug 25 04:09:14 koboldx-z170 systemd[1183]: Failed to start KDE Plasma Workspace.
Aug 25 04:09:24 koboldx-z170 systemd[1183]: Failed to start KDE Window Manager.
Aug 25 04:09:25 koboldx-z170 systemd[1183]: Failed to start KDE PolicyKit Authentication Agent.
Aug 25 04:09:26 koboldx-z170 systemd[1183]: Failed to start Powerdevil.
Aug 25 04:12:39 koboldx-z170 dbus-broker-launch[920]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
Aug 25 04:12:40 koboldx-z170 systemd[1]: Failed unmounting /tmp.
Aug 25 04:12:40 koboldx-z170 kernel: watchdog: watchdog0: watchdog did not stop!

Was there a better option to restore my system?

I remember that the game forced me to update my Flatpak Nvidia GPU driver before i could load into the game (This why i had this 2 core dumps in the logs from the native Linux game crash), but i did this flatpak GPU Updates so many times already in the last few year’s and i never had a frozen desktop after my gaming session.

Im pretty sure that this nvidia error was the main reason, why my desktop crashed:

nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f

But why?

[Keruskerfuerst]

Can you some more information: inxi -Fza ?

[Kobold]

System:
  Kernel: 6.6.46-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/vmlinuz-6.6-x86_64
    root=UUID=eb235aa7-d461-413d-800e-ea57385703fb rw sysrq_always_enabled=1
    nvidia_drm.modeset=1 retbleed=off
    resume=UUID=717b267e-7322-4bf9-a840-f1210d422d1a udev.log_priority=3
  Desktop: KDE Plasma v: 6.0.5 tk: Qt v: N/A info: frameworks v: 6.5.0
    wm: kwin_x11 vt: 2 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop System: Gigabyte product: Z170X-UD3 v: N/A
    serial: <superuser required>
  Mobo: Gigabyte model: Z170X-UD3-CF v: x.x serial: <superuser required>
    uuid: <superuser required> UEFI-[Legacy]: American Megatrends v: F23d
    date: 12/01/2017
Memory:
  System RAM: total: 16 GiB available: 15.58 GiB used: 3.15 GiB (20.2%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 64 GiB slots: 4 modules: 2 EC: None
    max-module-size: 16 GiB note: est.
  Device-1: ChannelA-DIMM0 type: no module installed
  Device-2: ChannelA-DIMM1 type: DDR4 detail: synchronous size: 8 GiB
    speed: 2800 MT/s volts: note: check curr: 1 min: 1 max: 1 width (bits):
    data: 64 total: 64 manufacturer: G.Skill part-no: F4-2800C16-8GRR
    serial: N/A
  Device-3: ChannelB-DIMM0 type: no module installed
  Device-4: ChannelB-DIMM1 type: DDR4 detail: synchronous size: 8 GiB
    speed: 2800 MT/s volts: note: check curr: 1 min: 1 max: 1 width (bits):
    data: 64 total: 64 manufacturer: G.Skill part-no: F4-2800C16-8GRR
    serial: N/A
CPU:
  Info: model: Intel Core i7-6700K bits: 64 type: MT MCP arch: Skylake-S
    gen: core 6 level: v3 note: check built: 2015 process: Intel 14nm family: 6
    model-id: 0x5E (94) stepping: 3 microcode: 0xF0
  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: 8 MiB desc: 1x8 MiB
  Speed (MHz): avg: 4500 min/max: 800/4700 scaling: driver: intel_pstate
    governor: performance cores: 1: 4500 2: 4500 3: 4500 4: 4500 5: 4500 6: 4500
    7: 4500 8: 4500 bogomips: 64026
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Vulnerable: No 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 status: Vulnerable
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; IBRS_FW;
    STIBP: conditional; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not
    affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort mitigation: TSX disabled
Graphics:
  Device-1: NVIDIA TU102 [GeForce RTX 2080 Ti Rev. A] vendor: Micro-Star MSI
    driver: nvidia v: 550.107.02 alternate: nouveau,nvidia_drm non-free: 550.xx+
    status: current (as of 2024-06; EOL~2026-12-xx) arch: Turing code: TUxxx
    process: TSMC 12nm FF built: 2018-2022 pcie: gen: 3 speed: 8 GT/s lanes: 16
    ports: active: none off: DP-3 empty: DP-1, DP-2, HDMI-A-1, Unknown-1
    bus-ID: 01:00.0 chip-ID: 10de:1e07 class-ID: 0300
  Display: x11 server: X.Org v: 21.1.13 with: Xwayland v: 24.1.2
    compositor: kwin_x11 driver: X: loaded: nvidia gpu: nvidia,nvidia-nvswitch
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 2560x1440 s-dpi: 122 s-size: 532x302mm (20.94x11.89")
    s-diag: 612mm (24.08")
  Monitor-1: DP-3 mapped: DP-4 note: disabled model: Dell S2417DG
    serial: <filter> built: 2018 res: 2560x1440 dpi: 123 gamma: 1.2
    size: 527x296mm (20.75x11.65") diag: 604mm (23.8") ratio: 16:9 modes:
    max: 2560x1440 min: 640x480
  API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
    drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia x11: drv: nvidia
    inactive: wayland,device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 550.107.02
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2
    memory: 10.74 GiB
  API: Vulkan v: 1.3.279 layers: 5 device: 0 type: discrete-gpu name: NVIDIA
    GeForce RTX 2080 Ti driver: nvidia v: 550.107.02 device-ID: 10de:1e07
    surfaces: xcb,xlib
Audio:
  Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: Gigabyte
    driver: snd_hda_intel v: kernel alternate: snd_soc_avs bus-ID: 00:1f.3
    chip-ID: 8086:a170 class-ID: 0403
  Device-2: NVIDIA TU102 High Definition Audio vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    bus-ID: 01:00.1 chip-ID: 10de:10f7 class-ID: 0403
  Device-3: Creative Labs CA0132 Sound Core3D [Sound Blaster Recon3D /
    Z-Series BlasterX AE-5 Plus] driver: snd_hda_intel v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 bus-ID: 0b:00.0 chip-ID: 1102:0012 class-ID: 0403
  API: ALSA v: k6.6.46-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 1.2.2 status: off with: pipewire-media-session
    status: active tools: pw-cli
  Server-3: PulseAudio v: 17.0 status: active with: 1: pulseaudio-alsa
    type: plugin 2: pulseaudio-jack type: module tools: pacat,pactl
Network:
  Device-1: Intel Ethernet I219-V vendor: Gigabyte driver: e1000e v: kernel
    port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15b8 class-ID: 0200
  IF: enp0s31f6 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Info: services: NetworkManager
Drives:
  Local Storage: total: 5.93 TiB used: 413.81 GiB (6.8%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Corsair model: MP600 PRO LPX
    size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: EIFM31.6 temp: 34.9 C
    scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 PRO 1TB
    size: 953.87 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 2B6Q scheme: MBR
  ID-3: /dev/sdb maj-min: 8:16 vendor: HGST (Hitachi) model: HDN724030ALE640
    size: 2.73 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: HDD rpm: 7200 serial: <filter> fw-rev: A5E0 scheme: GPT
  ID-4: /dev/sdc maj-min: 8:32 vendor: Samsung model: Portable SSD T5
    size: 465.76 GiB block-size: physical: 512 B logical: 512 B type: USB
    rev: 3.1 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: SSD serial: <filter>
    scheme: MBR
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 88.61 GiB size: 86.66 GiB (97.80%) used: 23.46 GiB (27.1%)
    fs: ext4 dev: /dev/sdc1 maj-min: 8:33 label: N/A
    uuid: eb235aa7-d461-413d-800e-ea57385703fb
  ID-2: /boot raw-size: 2.93 GiB size: 2.82 GiB (96.15%) used: 121 MiB (4.2%)
    fs: ext3 dev: /dev/sdc3 maj-min: 8:35 label: N/A
    uuid: cbfeca98-b99d-4383-9ded-fe66cd598006
  ID-3: /home raw-size: 332.03 GiB size: 325.75 GiB (98.11%)
    used: 16.72 GiB (5.1%) fs: ext4 dev: /dev/sdc4 maj-min: 8:36 label: N/A
    uuid: ada4a6a2-bd0a-4652-b386-7c637bba7ee9
Swap:
  Kernel: swappiness: 10 (default 60) cache-pressure: 100 (default) zswap: yes
    compressor: zstd max-pool: 20%
  ID-1: swap-1 type: partition size: 7.81 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/sdc2 maj-min: 8:34 label: N/A
    uuid: 717b267e-7322-4bf9-a840-f1210d422d1a
Sensors:
  System Temperatures: cpu: 33.0 C mobo: N/A gpu: nvidia temp: 35 C
  Fan Speeds (rpm): N/A gpu: nvidia fan: 25%
Info:
  Processes: 261 Power: uptime: 5h 5m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 6.22 GiB services: org_kde_powerdevil,upowerd
    Init: systemd v: 256 default: graphical tool: systemctl
  Packages: 1603 pm: pacman pkgs: 1597 libs: 458 tools: pamac pm: flatpak
    pkgs: 6 Compilers: clang: 18.1.8 gcc: 14.2.1 Shell: Bash v: 5.2.32
    running-in: konsole inxi: 3.3.35

[Keruskerfuerst]

Can you check the temperatures of the mainboard and graphics card ?

[Kobold]

GPU temps is shown in the inxi,
Mainboard temps must be around 36-37° since i have in Bios settings a very high RPM Curve for my Casefans defined, i can hear the difference when my MB Temps going little higher.

So normaly it takes 2-3 mins after my gaming is done, that the Case Fans chilling around 400-600RPM again, when my Motherboard sensors going back to 35-36° again (or below).

I have a pretty good Fractal Case with optimal airflow.

Edit:
I was just playing the same game again 15min ago and still no freeze on my desktop… i was expecting the freeze again, but nothing at this moment.

Not sure if this is good or bad… i never had a system freeze when my PC was idling.

Journals looking fine right now:

$ journalctl -p 3 -xb
Aug 25 04:13:25 koboldx-z170 kernel: x86/cpu: SGX disabled by BIOS.
Aug 25 04:13:26 koboldx-z170 kernel: 
Aug 25 04:13:33 koboldx-z170 kernel: [drm:drm_new_set_master] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
Aug 25 04:13:33 koboldx-z170 kernel: [drm:drm_new_set_master] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
Aug 25 04:13:35 koboldx-z170 pulseaudio[1396]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer 'org.bluez': unit failed
Aug 25 09:18:52 koboldx-z170 kernel: [drm:drm_new_set_master] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership

[dmt]

@Kobold

I try to use some Reisub Combos, first i pressed alt+print+f and alt+print+i but nothing happens (visually):

I also pressed crtl+alt+f3 for TTY but nothing, then i press alt+print+b and my system was restarting (Probably the worst way to use Reisub ).

What you’re calling reisub is the magic sys req key.

You seem to have forgotten the r, e, s, u from reisub, which is a mnemonic to help you remember the keys and order you should use to safely restart your computer.

[Kobold]

To be honest i never really understood the Reisub feature and how to actually
get this command active.

And the magic sys keys was working for me.

Could you explain to me with your own words, how do i use this Reisub feature?

I try to hold alt+print and was writing reisub… but it wasn’t working in the past, so i gave up and use since all this year’s only the magic sys keys list.

[dmt]

@Kobold

I try to hold alt+print and was writing reisub

That’s pretty much it.

Hold the Magic sys req key combo (for me Ctrl + Alt + PrtSc), then press the letters REISUB one at a time, waiting for at least 1 second in between. If the computer sounds like it’s doing something in response, particularly after S (sync filesystems, that’s the important one), then wait longer.

Sometimes once you get to I, it’ll restart the DE (like Ctrl + Alt + Backspace) and that may be enough.

[Kobold]

@dmt

Ctrl + Alt + Backspace

You mean crlt+alt+del key right? Or what is backspace?

@Fabby

Once you’ve located your SysRq key, please keep the Alt key pressed and then release the SysRq.

Now lightly tap these keys waiting between 1 second (fast, new machines) and 6 seconds (older or resource-starved machines¹) in-between keypresses : R E I S U B

After looking into the guide again, i see that Fabby said here just press alt+print… release the keys and then writing reisub but this never worked for me.

So i really have to press and hold alt+print+r then alt+print+e and so on? Just with delay between each combo, because there is no visual output… besides my HDD/SSD LED on my PC Case.

[dmt]

Backspace is the key above the return key, looks a bit like this <—.

Backspace deletes the character to the left of the cursor, Delete deletes the character to the right of the cursor.

@Kobold

So i really have to press and hold alt+print+r then alt+print+e and so on?

It depends on the system, but usually yes.

[Kobold]

@dmt

Backspace is the key above the return key, looks a bit like this <—.

Yeah im fully aware about the Backspace key. But i always pressed in my 30 year’s PC Time crlt+alt+del in germany it called entfernen =entf which means delete = del and was the short combo for a Warm restart/resetting a PC.

So i never heared about alt+crtl+backspace, is this a special linux combo?

[dmt]

@Kobold

But i always pressed in my 30 year’s PC Time crlt+alt+del in germany it called entfernen =entf which means delete = del and was the short for resetting a PC.

For me it’s always backspace, however now I have to enable it in my keyboard settings.

It’s under “Key sequence to kill the X server” and it’s the only option. Perhaps German layouts are different.

@Kobold

is this a special linux combo?

I think it’s from X. I’m still using mate, so no wayland.

[Kobold]

@dmt

For me it’s always backspace, however now I have to enable it in my keyboard settings.

The key which i enter the bios is del (entf), its located on my QWERT Keyboard above the arrow keys… anyways i think this is going offtopic

So i try this reisub feature again (next time) and i guess Fabby did a little mistake (if i don’t miss understand him) in his guide, because he said there to release alt+print and type reisub.

@dmt

I think it’s from X. I’m still using mate, so no wayland.

I think this explains our misunderstanding… because crtl+alt+del is a Universal Shortcut that replaced the reset button on your PC case and this has nothing to do with a OS feature (shortcut combo).

Edit:
Im still confused about the system lock up. Hopefully this was a one time thing… but is this possible that a flatpak GPU driver for a game, crashed the Desktop?

[dmt]

@Kobold

i guess Fabby did a little mistake (if i don’t miss understand him) in his guide, because he said there to release alt+print and type reisub.

Actually he said to keep Alt pressed and release SysReq.

@Fabby

Once you’ve located your SysRq key, please keep the Alt key pressed and then release the SysRq.

AFAIK it can vary, use whatever works for you. I keep Ctrl + Alt + PrtSc pressed.

@Kobold

because crtl+alt+del is a Universal Shortcut that replaced the reset button on your PC case and this has nothing to do with a OS feature (shortcut combo).

Ah yes, it definitely works before you’ve booted up properly. I can’t remember the last time I tried it after logging in, probably quite a few years ago, but I’m pretty sure it didn’t act like that then.

I’ll have to remember to try it some time when I have less stuff open.

@Kobold

Im still confused about the system lock up. Hopefully this was a one time thing… but is this possible that a flatpak GPU driver for a game, crashed the Desktop?

I suppose, but I don’t use flatpaks.

My first thought was running out of ram, however I’m not sure it’s likely given your RAM and swap. Though it is possible.

[Kobold]

@dmt

My first thought was running out of ram, however I’m not sure it’s likely given your RAM and swap. Though it is possible.

My system was frozen again, just few minutes after i closed the game:

$ journalctl -b -1 -p3 --no-pager
Aug 31 20:26:44 koboldx-z170 kernel: x86/cpu: SGX disabled by BIOS.
Aug 31 20:26:45 koboldx-z170 kernel: 
Aug 31 20:26:52 koboldx-z170 kernel: [drm:drm_new_set_master] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
Aug 31 20:26:52 koboldx-z170 kernel: [drm:drm_new_set_master] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
Aug 31 20:26:54 koboldx-z170 pulseaudio[1403]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer 'org.bluez': unit failed
Aug 31 21:20:02 koboldx-z170 sudo[3368]:  koboldx : a password is required ; PWD=/home/koboldx ; USER=root ; COMMAND=/usr/bin/uptime
Sep 01 08:14:45 koboldx-z170 kernel: irq 16: nobody cared (try booting with the "irqpoll" option)
Sep 01 08:14:45 koboldx-z170 kernel: handlers:
Sep 01 08:14:45 koboldx-z170 kernel: [<00000000265ddaaf>] i801_isr [i2c_i801]
Sep 01 08:14:45 koboldx-z170 kernel: [<00000000b2bd5f28>] azx_interrupt [snd_hda_codec]
Sep 01 08:14:45 koboldx-z170 kernel: Disabling IRQ #16
Sep 01 08:14:55 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Sep 01 08:15:00 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Sep 01 08:15:00 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Sep 01 08:15:00 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Sep 01 08:15:00 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Sep 01 08:15:00 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Sep 01 08:15:00 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Sep 01 08:15:00 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Sep 01 08:15:00 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Sep 01 08:15:00 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Sep 01 08:15:00 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Sep 01 08:15:00 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Sep 01 08:15:00 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Sep 01 08:15:00 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Sep 01 08:15:00 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Sep 01 08:15:00 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Sep 01 08:15:00 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Sep 01 08:15:00 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Sep 01 08:15:00 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Sep 01 08:15:00 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Sep 01 08:15:00 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Sep 01 08:15:10 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Sep 01 08:15:20 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Sep 01 08:15:30 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Sep 01 08:15:40 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Sep 01 08:15:50 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Sep 01 08:15:50 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Sep 01 08:15:50 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Sep 01 08:15:50 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Sep 01 08:15:50 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Sep 01 08:16:36 koboldx-z170 pulseaudio[1403]: Error opening PCM device front:2: No such file or directory
Sep 01 08:16:36 koboldx-z170 pulseaudio[1403]: Error opening PCM device front:2: No such file or directory
Sep 01 08:16:36 koboldx-z170 pulseaudio[1403]: Error opening PCM device hdmi:1: No such file or directory

This time i used/pressed R.E.I.S.U.B but not sure if everything shutdown correct or not.

The nvidia flatpak driver also wasn’t updated since last time.
Having that said, i had started and closed this game for 7 days now, around 20 times and not had a problem since then. I thought it was a one time thing… sadly i was wrong.

Edit:
I just download a new Flatpak driver, i hope this changed anything

$ flatpak update --system
Looking for updates…


        ID                                                    Branch         Op         Remote          Download
 1. [✓] org.freedesktop.Platform.GL.nvidia-550-107-02         1.4            u          flathub         307,3 MB / 308,2 MB

Updates complete.

[Kobold]

I had another freeze, this time while loading a level in the game… but the music was keep playing from the game and but my mouse cursor stuck.

I try to kill the process with free memory, alt+print+f but this lead to a full system freeze.

$ journalctl -b -1 -p3 --no-pager
Sep 01 08:18:49 koboldx-z170 kernel: x86/cpu: SGX disabled by BIOS.
Sep 01 08:18:50 koboldx-z170 kernel: 
Sep 01 08:18:56 koboldx-z170 kernel: [drm:drm_new_set_master] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
Sep 01 08:18:56 koboldx-z170 kernel: [drm:drm_new_set_master] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
Sep 01 08:18:59 koboldx-z170 pulseaudio[1404]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer 'org.bluez': unit failed
Sep 01 10:32:20 koboldx-z170 kernel: irq 16: nobody cared (try booting with the "irqpoll" option)
Sep 01 10:32:20 koboldx-z170 kernel: handlers:
Sep 01 10:32:20 koboldx-z170 kernel: [<000000004471708e>] i801_isr [i2c_i801]
Sep 01 10:32:20 koboldx-z170 kernel: [<00000000017419f9>] azx_interrupt [snd_hda_codec]
Sep 01 10:32:20 koboldx-z170 kernel: Disabling IRQ #16
Sep 01 10:33:42 koboldx-z170 kernel: Out of memory: Killed process 4181 (spring-main) total-vm:8342812kB, anon-rss:6542024kB, file-rss:96788kB, shmem-rss:0kB, UID:1000 pgtables:13700kB oom_score_adj:200
Sep 01 10:33:51 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Sep 01 10:33:56 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Sep 01 10:33:56 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Sep 01 10:33:56 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Sep 01 10:33:56 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Sep 01 10:33:56 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Sep 01 10:33:56 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Sep 01 10:34:17 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Sep 01 10:34:17 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Sep 01 10:34:17 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Sep 01 10:34:17 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Sep 01 10:34:17 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Sep 01 10:34:17 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Sep 01 10:34:27 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Sep 01 10:34:37 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Sep 01 10:34:47 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Sep 01 10:34:47 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Sep 01 10:34:47 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Sep 01 10:34:55 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57d:0:0:0x0000000f
Sep 01 10:34:55 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:0:0:0x0000000f
Sep 01 10:34:55 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:1:0:0x0000000f
Sep 01 10:34:55 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:2:0:0x0000000f
Sep 01 10:34:55 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:3:0:0x0000000f
Sep 01 10:34:55 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:4:0:0x0000000f
Sep 01 10:34:55 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:5:0:0x0000000f
Sep 01 10:34:55 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Sep 01 10:34:55 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:7:0:0x0000000f
Sep 01 10:36:21 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57e:6 2:0:4048:4040
Sep 01 10:36:26 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57e:6 2:0:4048:4040
Sep 01 10:36:31 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57e:6 2:0:4048:4040
Sep 01 10:36:36 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57e:6 2:0:4048:4040
Sep 01 10:36:41 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57e:6 2:0:4048:4040
Sep 01 10:36:46 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57e:6 2:0:4048:4040
Sep 01 10:36:51 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57e:6 2:0:4048:4040
Sep 01 10:36:56 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57e:6 2:0:4048:4040
Sep 01 10:37:01 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57e:6 2:0:4048:4040
Sep 01 10:37:06 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57e:6 2:0:4048:4040
Sep 01 10:37:11 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57e:6 2:0:4048:4040
Sep 01 10:37:16 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57e:6 2:0:4048:4040
Sep 01 10:37:21 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57e:6 2:0:4048:4040
Sep 01 10:37:26 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57e:6 2:0:4048:4040
Sep 01 10:37:31 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57e:6 2:0:4048:4040
Sep 01 10:37:36 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57e:6 2:0:4048:4040
Sep 01 10:37:41 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57e:6 2:0:4048:4040
Sep 01 10:37:46 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57e:6 2:0:4048:4040
Sep 01 10:37:51 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57e:6 2:0:4048:4040
Sep 01 10:37:56 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57e:6 2:0:4048:4040
Sep 01 10:38:01 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57e:6 2:0:4048:4040
Sep 01 10:38:06 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57e:6 2:0:4048:4040
Sep 01 10:38:11 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57e:6 2:0:4048:4040
Sep 01 10:38:16 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57e:6 2:0:4048:4040
Sep 01 10:38:21 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57e:6 2:0:4048:4040
Sep 01 10:38:26 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57e:6 2:0:4048:4040
Sep 01 10:38:31 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57e:6 2:0:4048:4040
Sep 01 10:38:36 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57e:6 2:0:4048:4040
Sep 01 10:38:41 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57e:6 2:0:4048:4040
Sep 01 10:38:46 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57e:6 2:0:4048:4040
Sep 01 10:38:51 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57e:6 2:0:4048:4040
Sep 01 10:38:56 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57e:6 2:0:4048:4040
Sep 01 10:39:01 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57e:6 2:0:4048:4040
Sep 01 10:39:06 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57e:6 2:0:4048:4040
Sep 01 10:39:06 koboldx-z170 systemd[1]: Failed to start CUPS Scheduler.
Sep 01 10:39:11 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57e:6 2:0:4048:4040
Sep 01 10:39:16 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57e:6 2:0:4048:4040

But what can i do? Should i report this problem at the nvidia Forum?

[linux-aarhus]

@Kobold

Sep 01 08:18:56 koboldx-z170 kernel: [drm:drm_new_set_master] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership

A search for the error message, it seems to be the combination of Wayland and Nvidia

unable to grab modeset ownership

[Kobold]

This first 5 lines are the default error’s i get since a long time. My system was stable with them. The error’s below are important.

Do you have a idea how i can do a reinstall from this Flatpak GPU Driver?

[linux-aarhus]

@Kobold

I try to kill the process with free memory, alt+print+f but this lead to a full system freeze

So the full freeze is this point where the oom killing process kicked something ?

@Kobold

Sep 01 10:39:16 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57e:6 2:0:4048:4040

Continue with

@Kobold

Sep 01 10:33:42 koboldx-z170 kernel: Out of memory: Killed process 4181 (spring-main) total-vm:8342812kB, anon-rss:6542024kB, file-rss:96788kB, shmem-rss:0kB, UID:1000 pgtables:13700kB oom_score_adj:200

Which end with this ?

@Kobold

Sep 01 10:33:51 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f

I have on several occasions created system conditions which inevitable result in memorylock.

It is a situation where you keep asking the computer to do the same thing without ever exiting the loop.

I cannot say this is the case but i looks loke the kernel is repeatedly asking for a status using nvidia-modeset and those requests is the first half - give or take - and the answers it other half - give or take. So you assumption that the first 5 lines is insignificant - I am not sure you are correct - but the system continues without - which then would assume a working state - but when a response is actually required - there is nothing.

There is 26 or so requests - given how fast a computer work - it is often sending repeated requests to the same address

@Kobold

kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: : 0x0000c57e:7:0:0x0000000f

And the message log - the kernel gives up the threads - after 35 attempts to retrieve the status - what it is expecting is not coming.

@Kobold

nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57e:6 2:0:4048:4040

The driver is the kernel’s interface to the GPU processing - if that process doesn’t exist or doesn’t reply in timely manner - there is nothing left for the system to other than … what systems do when they are bored.

DRM !== DRM - while the sound the same it it not.

One could think - if I recall correct modeseting is about writing directly to the GPU (Direct Rendering Manager as opposed to Digital rights management) - and it seems the GPU is not ready to supply the state business asked by the kernel

@Kobold

kernel: [drm:drm_new_set_master] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership

Which in turn causes an error to cascade up through the system.

And I have no idea on how to fix it - when I see the jungle of kernel code - I see a pulsating green color - how it does that - I have no idea.

[Kobold]

Thank you for taking your time to help me.

@linux-aarhus

So the full freeze is this point where the oom killing process kicked something ?

At this state, the crash already happen and i was just trying to revive the system with free memory hotkey. But with no success.

You can see the difference, when you look at my first crash journal from today (i posted 2 today).

@linux-aarhus

Which end with this ?

Sep 01 10:33:51 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f

Yeah exactly, but after the newest Flatpak driver, the last error changed a little (maybe because it freezed my system while i was ingame? )

@Kobold

Sep 01 10:39:16 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57e:6 2:0:4048:4040

@linux-aarhus

So you assumption that the first 5 lines is insignificant

I think so because, i saw this error since february around 7 month ago…
where i have reported this:

I got a new nvidia error in journal after the update

I got a new nvidia error in journal after the update: kernel: [drm:drm_new_set_master] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership Should im worry about the error? I’m still using nvidia_drm.modeset=1 in Grub, not sure if this both are related now, after the update

But since my system was still fine… on the otherside, i may could remove this grub command in Grub nvidia_drm.modeset=1 and hopefully something changed after that.

Since im not in need for Firefox H/W Acceleration anyways.

I will report back if removing the Grub command works.