System suddenly freezes forcing me to reboot, seems to be GPU issue

mactemporal · 2026-01-27 19:04:53

Hello
It happened to me for the second time.
I was just using my PC as normal when suddenly everything freezes : the screen freezes, the system continues to "operate" as I can still hear music for exemple.
I can still see the amount of RAM used at crash time and it's not full so it does no seem to be a memory.
When checking journalctl it prompts at the time of the crash:

janv. 27 19:51:03 user-arch rtkit-daemon[1831]: Successfully made thread 62153 of process 61229 owned by '1000' RT at priority 10.
janv. 27 19:51:03 user-arch /usr/lib/xdg-desktop-portal[1865]: A backend call failed: Inhibiting other than idle not supported
janv. 27 19:51:03 user-arch /usr/lib/xdg-desktop-portal[1865]: A backend call failed: Inhibiting other than idle not supported
janv. 27 19:51:23 user-arch kernel: NVRM: GPU at PCI:0000:01:00: GPU-cba61232-5e90-a071-98c2-d1da72ac91c5
janv. 27 19:51:23 user-arch kernel: NVRM: GPU Board Serial Number: 0
janv. 27 19:51:23 user-arch kernel: NVRM: Xid (PCI:0000:01:00): 62, 32344000 0000b670 00000000 206a7a8a 206a6c4a 206a6db8 206a52ae 206a5aca
janv. 27 19:51:23 user-arch kernel: NVRM: Xid (PCI:0000:01:00): 154, GPU recovery action changed from 0x0 (None) to 0x1 (GPU Reset Required)
janv. 27 19:51:32 user-arch kernel: NVRM: Xid (PCI:0000:01:00): 109, pid=2044, name=electron, channel 0x00000005, errorString CTX SWITCH TIMEOUT, Info 0x54005
janv. 27 19:51:32 user-arch kernel: NVRM: krcWatchdog_IMPL: RC watchdog: GPU is probably locked!  Notify Timeout Seconds: 7

My relevant (?) system specs are :

CPU: AMD Ryzen 7 7700X (16) @ 5.58 GHz
GPU 1: NVIDIA GeForce RTX 5070 [Discrete]
GPU 2: AMD Raphael [Integrated]

My current installed drivers are :

lib32-nvidia-utils 590.48.01-1
libva-nvidia-driver 0.0.14-1
linux-firmware-nvidia 20260110-1
nvidia-open 590.48.01-8
nvidia-utils 590.48.01-2
opencl-nvidia 590.48.01-2
cuda 13.1.1-1
linux-firmware-amdgpu 
amd-ucode

I cannot find any information on "NVRM" or anything and I have failed to identify some kind of element for reproductability of the problem, the errors logged stay the same though.
Thank you very much for yout attention!

EDIT : I have vague memory of the first time it happened when after some time my screen turned completely black and show an error message (can't remember)
EDIT 2 : Added AMD drivers

Last edited by mactemporal (2026-01-27 21:10:39)

KevinCrrl · 2026-01-27 19:30:04

My current installed drivers are :

lib32-nvidia-utils 590.48.01-1
libva-nvidia-driver 0.0.14-1
linux-firmware-nvidia 20260110-1
nvidia-open 590.48.01-8
nvidia-utils 590.48.01-2
opencl-nvidia 590.48.01-2
cuda 13.1.1-1

And the drivers and firmware for AMD? for AMD you need linux-firmware-amdgpu (and probally amd-ucode).

Last edited by KevinCrrl (2026-01-27 19:34:53)

mactemporal · 2026-01-27 21:10:00

Thank you for your answer.
I already got linux-firmware-amdgpu and amd-ucode installed on my system.

seth · 2026-01-27 21:23:30

janv. 27 19:51:23 user-arch kernel: NVRM: Xid (PCI:0000:01:00): 62, 32344000 0000b670 00000000 206a7a8a 206a6c4a 206a6db8 206a52ae 206a5aca

GSP crashes and triggers a reset, RTX 5070 should be a blackwell chip, so you'll have to use nvidia-open and the GSP firmware

You could still try to downgrade to the 580xx nvidia-open driver, https://wiki.archlinux.org/title/Arch_Linux_Archive

Fwwi, NVRM is how nvidia tags most of its kernel messages.

mactemporal · 2026-02-04 17:19:13

Thank you for your answer and sorry for the delay
No luck so far, and a new error has joined :

févr. 04 18:10:51 user-arch kernel: NVRM: krcWatchdog_IMPL: RC watchdog: GPU is probably locked!  Notify Timeout Seconds: 7
févr. 04 18:11:00 user-arch kernel: NVRM: krcWatchdog_IMPL: RC watchdog: GPU is probably locked!  Notify Timeout Seconds: 7
févr. 04 18:11:08 user-arch kernel: NVRM: krcWatchdog_IMPL: RC watchdog: GPU is probably locked!  Notify Timeout Seconds: 7
févr. 04 18:11:16 user-arch kernel: NVRM: krcWatchdog_IMPL: RC watchdog: GPU is probably locked!  Notify Timeout Seconds: 7
févr. 04 18:11:24 user-arch kernel: NVRM: krcWatchdog_IMPL: RC watchdog: GPU is probably locked!  Notify Timeout Seconds: 7
févr. 04 18:11:32 user-arch kernel: NVRM: krcWatchdog_IMPL: RC watchdog: GPU is probably locked!  Notify Timeout Seconds: 7
févr. 04 18:11:40 user-arch kernel: NVRM: krcWatchdog_IMPL: RC watchdog: GPU is probably locked!  Notify Timeout Seconds: 7
févr. 04 18:11:49 user-arch kernel: NVRM: krcWatchdog_IMPL: RC watchdog: GPU is probably locked!  Notify Timeout Seconds: 7
févr. 04 18:11:57 user-arch kernel: NVRM: krcWatchdog_IMPL: RC watchdog: GPU is probably locked!  Notify Timeout Seconds: 7
févr. 04 18:12:05 user-arch kernel: NVRM: krcWatchdog_IMPL: RC watchdog: GPU is probably locked!  Notify Timeout Seconds: 7
févr. 04 18:12:09 user-arch systemd-logind[1031]: New session 'c2' of user 'user' with class 'user' and type 'x11'.
févr. 04 18:12:09 user-arch systemd[1]: Created slice User Slice of UID 1000.
févr. 04 18:12:09 user-arch systemd[1]: Starting User Runtime Directory /run/user/1000...
févr. 04 18:12:09 user-arch systemd[1]: Finished User Runtime Directory /run/user/1000.
févr. 04 18:12:09 user-arch systemd[1]: Starting User Manager for UID 1000...
févr. 04 18:12:09 user-arch (systemd)[9212]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8002 service=[systemd-user] terminal=[] user=[user] ruser=[<unknown>] rhost=[<unknown>]
févr. 04 18:12:09 user-arch (systemd)[9212]: pam_unix(systemd-user:session): session opened for user user(uid=1000) by user(uid=0)
févr. 04 18:12:09 user-arch systemd-logind[1031]: New session '3' of user 'user' with class 'manager' and type 'unspecified'.
févr. 04 18:12:09 user-arch systemd[1]: Started User Manager for UID 1000.
févr. 04 18:12:09 user-arch systemd[1]: Started Session c2 of User user.
févr. 04 18:12:09 user-arch ly-dm[9171]: pam_unix(ly:session): session opened for user user(uid=1000) by user(uid=0)
févr. 04 18:12:09 user-arch kernel: nvidia-modeset: ERROR: GPU:0: The requested configuration of display devices (Samsung C27F398 (HDMI-0)) is not supported on this GPU.
févr. 04 18:12:09 user-arch kernel: nvidia-modeset: ERROR: GPU:0: The requested configuration of display devices (Samsung C27F398 (HDMI-0)) is not supported on this GPU.
févr. 04 18:12:09 user-arch kernel: nvidia-modeset: ERROR: GPU:0: The requested configuration of display devices (Samsung C27F398 (HDMI-0)) is not supported on this GPU.
févr. 04 18:12:09 user-arch kernel: NVRM: GPU0 nvCheckOkFailedNoLog: Check failed: Reset required [NV_ERR_RESET_REQUIRED] (0x00000062) returned from kbusSendBusInfo(pGpu, GPU_GET_KERNEL_BUS(pGpu), &pBusInfos[i]>
févr. 04 18:12:09 user-arch kernel: nvidia-modeset: ERROR: GPU:0: The requested configuration of display devices (Samsung C27F398 (HDMI-0)) is not supported on this GPU.
févr. 04 18:12:09 user-arch kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000ca7d:0:0:0x00000062
févr. 04 18:12:09 user-arch kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000ca7e:0:0:0x00000062
févr. 04 18:12:09 user-arch kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000ca7e:1:0:0x00000062
févr. 04 18:12:09 user-arch kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000ca7e:2:0:0x00000062
févr. 04 18:12:09 user-arch kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000ca7e:3:0:0x00000062
févr. 04 18:12:09 user-arch kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000ca7e:4:0:0x00000062
févr. 04 18:12:09 user-arch kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000ca7e:5:0:0x00000062
févr. 04 18:12:09 user-arch kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000ca7e:6:0:0x00000062
févr. 04 18:12:09 user-arch kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000ca7e:7:0:0x00000062
févr. 04 18:12:09 user-arch kernel: NVRM: GPU0 nvAssertFailedNoLog: Assertion failed: (status == NV_OK) || (status == NV_ERR_GPU_IN_FULLCHIP_RESET) @ rs_client.c:844
févr. 04 18:12:09 user-arch kernel: NVRM: nvAssertFailedNoLog: Assertion failed: (status == NV_OK) || (status == NV_ERR_GPU_IN_FULLCHIP_RESET) @ rs_server.c:259
févr. 04 18:12:09 user-arch kernel: NVRM: GPU0 nvCheckFailedNoLog: Check failed: (status == NV_OK) || (status == NV_ERR_GPU_IN_FULLCHIP_RESET) @ gpu_user_shared_data.c:462
févr. 04 18:12:09 user-arch kernel: NVRM: GPU0 nvCheckOkFailedNoLog: Check failed: Reset required [NV_ERR_RESET_REQUIRED] (0x00000062) returned from _gpushareddataSendDataPollRpc(pGpu, polledDataMask, pollingIn>
févr. 04 18:12:09 user-arch kernel: NVRM: GPU0 nvCheckFailedNoLog: Check failed: _handlePollMaskHelper(pGpu, NV_FALSE, NV_TRUE) == NV_OK @ gpu_user_shared_data.c:152
févr. 04 18:12:09 user-arch kernel: nvidia-modeset: ERROR: GPU:0: The requested configuration of display devices (Samsung C27F398 (HDMI-0)) is not supported on this GPU.
févr. 04 18:12:09 user-arch kernel: nvidia-modeset: ERROR: GPU:0: The requested configuration of display devices (Samsung C27F398 (HDMI-0)) is not supported on this GPU.
févr. 04 18:12:09 user-arch kernel: nvidia-modeset: ERROR: GPU:0: The requested configuration of display devices (Samsung C27F398 (HDMI-0)) is not supported on this GPU.
févr. 04 18:12:13 user-arch kernel: NVRM: krcWatchdog_IMPL: RC watchdog: GPU is probably locked!  Notify Timeout Seconds: 7

seth · 2026-02-04 20:38:18

Please post your complete system journal for the boot:

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

Please post your Xorg log, https://wiki.archlinux.org/title/Xorg#General

févr. 04 18:12:05 user-arch kernel: NVRM: krcWatchdog_IMPL: RC watchdog: GPU is probably locked!  Notify Timeout Seconds: 7
févr. 04 18:12:09 user-arch systemd-logind[1031]: New session 'c2' of user 'user' with class 'user' and type 'x11'.
févr. 04 18:12:09 user-arch kernel: nvidia-modeset: ERROR: GPU:0: The requested configuration of display devices (Samsung C27F398 (HDMI-0)) is not supported on this GPU.

slayerking · 2026-02-05 03:29:39

Getting this on AMD gpu as well, Just locks up can still hear music and then goes back to login screen after going black for a few seconds. Seems to have started with the latest kernel update

Feb 05 14:03:08 hell kernel: amdgpu 0000:03:00.0: amdgpu: Dumping IP State
Feb 05 14:03:08 hell kernel: amdgpu 0000:03:00.0: amdgpu: Dumping IP State Completed
Feb 05 14:03:08 hell kernel: amdgpu 0000:03:00.0: amdgpu: [drm] AMDGPU device coredump file has been created
Feb 05 14:03:08 hell kernel: amdgpu 0000:03:00.0: amdgpu: [drm] Check your /sys/class/drm/card1/device/devcoredump/data
Feb 05 14:03:08 hell kernel: amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 timeout, signaled seq=6763078, emitted seq=6763080
Feb 05 14:03:08 hell kernel: amdgpu 0000:03:00.0: amdgpu:  Process Xorg pid 1138 thread Xorg:cs0 pid 1166
Feb 05 14:03:08 hell kernel: amdgpu 0000:03:00.0: amdgpu: Starting gfx_0.0.0 ring reset
Feb 05 14:03:08 hell kernel: [drm:gfx_v11_0_bad_op_irq [amdgpu]] *ERROR* Illegal opcode in command stream 
Feb 05 14:03:10 hell kernel: amdgpu 0000:03:00.0: amdgpu: MES failed to respond to msg=RESET
Feb 05 14:03:10 hell kernel: amdgpu 0000:03:00.0: amdgpu: failed to reset legacy queue
Feb 05 14:03:10 hell kernel: amdgpu 0000:03:00.0: amdgpu: reset via MES failed and try pipe reset -110
Feb 05 14:03:10 hell kernel: amdgpu 0000:03:00.0: amdgpu: The CPFW hasn't support pipe reset yet.
Feb 05 14:03:10 hell kernel: amdgpu 0000:03:00.0: amdgpu: Ring gfx_0.0.0 reset failed
Feb 05 14:03:10 hell kernel: amdgpu 0000:03:00.0: amdgpu: GPU reset begin!. Source:  1
Feb 05 14:03:12 hell kernel: amdgpu 0000:03:00.0: amdgpu: MES failed to respond to msg=REMOVE_QUEUE
Feb 05 14:03:12 hell kernel: amdgpu 0000:03:00.0: amdgpu: failed to unmap legacy queue
Feb 05 14:03:12 hell kernel: [drm:gfx_v11_0_hw_fini [amdgpu]] *ERROR* failed to halt cp gfx
Feb 05 14:03:12 hell kernel: amdgpu 0000:03:00.0: amdgpu: MODE1 reset
Feb 05 14:03:12 hell kernel: amdgpu 0000:03:00.0: amdgpu: GPU mode1 reset
Feb 05 14:03:12 hell kernel: amdgpu 0000:03:00.0: amdgpu: GPU smu mode1 reset
Feb 05 14:03:13 hell kernel: amdgpu 0000:03:00.0: amdgpu: GPU reset succeeded, trying to resume
Feb 05 14:03:13 hell kernel: [drm] PCIE GART of 512M enabled (table at 0x0000008000F00000).
Feb 05 14:03:13 hell kernel: amdgpu 0000:03:00.0: amdgpu: VRAM is lost due to GPU reset!
Feb 05 14:03:13 hell kernel: amdgpu 0000:03:00.0: amdgpu: PSP is resuming...
Feb 05 14:03:13 hell kernel: amdgpu 0000:03:00.0: amdgpu: reserve 0x1300000 from 0x85fc000000 for PSP TMR
Feb 05 14:03:13 hell kernel: amdgpu 0000:03:00.0: amdgpu: RAP: optional rap ta ucode is not available
Feb 05 14:03:13 hell kernel: amdgpu 0000:03:00.0: amdgpu: SECUREDISPLAY: optional securedisplay ta ucode is not available
Feb 05 14:03:13 hell kernel: amdgpu 0000:03:00.0: amdgpu: SMU is resuming...
Feb 05 14:03:13 hell kernel: amdgpu 0000:03:00.0: amdgpu: smu driver if version = 0x0000003d, smu fw if version = 0x00000040, smu fw program = 0, smu fw version = 0x004e8300 (78.131.0)
Feb 05 14:03:13 hell kernel: amdgpu 0000:03:00.0: amdgpu: SMU driver if version not matched
Feb 05 14:03:13 hell kernel: amdgpu 0000:03:00.0: amdgpu: SMU is resumed successfully!
Feb 05 14:03:13 hell kernel: amdgpu 0000:03:00.0: amdgpu: [drm] DMUB hardware initialized: version=0x07002F00
Feb 05 14:03:13 hell kernel: amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
Feb 05 14:03:13 hell kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Feb 05 14:03:13 hell kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Feb 05 14:03:13 hell kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
Feb 05 14:03:13 hell kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
Feb 05 14:03:13 hell kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
Feb 05 14:03:13 hell kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
Feb 05 14:03:13 hell kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
Feb 05 14:03:13 hell kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
Feb 05 14:03:13 hell kernel: amdgpu 0000:03:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
Feb 05 14:03:13 hell kernel: amdgpu 0000:03:00.0: amdgpu: ring sdma1 uses VM inv eng 13 on hub 0
Feb 05 14:03:13 hell kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 8
Feb 05 14:03:13 hell kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_unified_1 uses VM inv eng 1 on hub 8
Feb 05 14:03:13 hell kernel: amdgpu 0000:03:00.0: amdgpu: ring jpeg_dec uses VM inv eng 4 on hub 8
Feb 05 14:03:13 hell kernel: amdgpu 0000:03:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 14 on hub 0
Feb 05 14:03:13 hell kernel: amdgpu 0000:03:00.0: amdgpu: GPU reset(1) succeeded!
Feb 05 14:03:13 hell kernel: amdgpu 0000:03:00.0: amdgpu: [drm] *ERROR* Failed to initialize parser -125!

seth · 2026-02-05 08:45:26

Probably unrelated, https://bbs.archlinux.org/viewtopic.php?id=311920 ?

slayerking · 2026-02-05 10:55:28

seth wrote:

Probably unrelated, https://bbs.archlinux.org/viewtopic.php?id=311920 ?

Yeah unrelated to that, Mines a desktop, But this did start with 6.18.7. I've downgraded to my last kernel that was 6.18.5 and it hasn't done it yet. It was exact same symptoms screen freezes (usually in a game Diablo 2 resurrected) music still playing then goes black and drops back to log in, Happens anywhere from 30 minutes to a few hours.

mactemporal · 2026-02-05 12:46:47

Please post your complete system journal for the boot

Here you go https://0x0.st/Pcuh.txt

Is it possible to get Xorg log files from a previous boot?

seth · 2026-02-05 15:04:55

@slayerking
what I meant is that your problem is unlikely related to this thread and more likely falls into https://bbs.archlinux.org/viewtopic.php?id=311920

@mactemporal
There's an Xorg.0.log.old - otherwise you'd have to avoid starting X11 again and backup the existing log before.

févr. 04 17:53:33 archlinux kernel: amdgpu 0000:11:00.0: [drm] Cannot find any crtc or sizes

Apparently there're no outputs attached to the AMD GPU, if you don't intend to use it and can, disabling it in the firmware (UEFI/BIOS) will uncomplicate the situation

févr. 04 17:53:35 lucas-arch kernel: nvidia-modeset: Loading NVIDIA UNIX Open Kernel Mode Setting Driver for x86_64  590.48.01  Release Build  (root@)

You're still on 590xx, have you tried whether the problem remains w/ the 580xx nvidia-open driver, https://wiki.archlinux.org/title/Arch_Linux_Archive (you'll need nvidia-open-dkms)

févr. 04 18:09:13 lucas-arch systemd[1]: Starting Cleanup of Temporary Directories...
févr. 04 18:09:13 lucas-arch systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully.
févr. 04 18:09:13 lucas-arch systemd[1]: Finished Cleanup of Temporary Directories.
févr. 04 18:10:02 lucas-arch kernel: NVRM: GPU at PCI:0000:01:00: GPU-cba61232-5e90-a071-98c2-d1da72ac91c5
févr. 04 18:10:02 lucas-arch kernel: NVRM: Xid (PCI:0000:01:00): 62, 32344000 0000b670 00000000 206a7a8a 206a6c4a 206a6db8 206a52ae 206a5aca
févr. 04 18:10:02 lucas-arch kernel: NVRM: Xid (PCI:0000:01:00): 154, GPU recovery action changed from 0x0 (None) to 0x1 (GPU Reset Required)
févr. 04 18:10:10 lucas-arch kernel: NVRM: Xid (PCI:0000:01:00): 109, pid=1794, name=Renderer, channel 0x00000009, errorString CTX SWITCH TIMEOUT, Info 0xd400d
févr. 04 18:10:19 lucas-arch kernel: NVRM: Xid (PCI:0000:01:00): 120, pid=1794, name=CPMMListener, GSP task exception: supervisor timer interrupt (cause:0x8000000000000005) @ pc:0x1a9aa88, partition:4#0, task:3
févr. 04 18:10:22 lucas-arch kernel: NVRM: Xid (PCI:0000:01:00): 109, channel 0x00000009, errorString CTX SWITCH TIMEOUT, Info 0xd400d

If you're looking at older journals, is systemd-tmpfiles-clean.service => NVRM: Xid a fixed pattern?
(systemd might trash some transactional files or sockets from there…)
You could try to "sudo systemctl mask systemd-tmpfiles-clean.service"

mactemporal · 2026-02-08 17:37:27

Thank you for your answer

There's an Xorg.0.log.old - otherwise you'd have to avoid starting X11 again and backup the existing log before.

Willdo!

Apparently there're no outputs attached to the AMD GPU, if you don't intend to use it and can, disabling it in the firmware (UEFI/BIOS) will uncomplicate the situation

That's a good idea, i'll try that.

You're still on 590xx, have you tried whether the problem remains w/ the 580xx nvidia-open driver

I tried indeed, but nothing worked after ahah. But I'll try with a little more effort.

Will keep you updated!

mactemporal · 2026-02-28 18:01:44

It happened again (ring the bells !!)
It's the samer same as the others, nothing relevant happens and pouf my PC has a stroke
journalctl uploaded here : https://0x0.st/P1iR.txt
NOTA : I deactivated the AMD GPU in the BIOS
Thank you for your attention

seth · 2026-02-28 19:52:49

Exactly the same crash, this time in Xorg instead of the "Renderer" process…

févr. 28 18:45:42 user-arch kernel: NVRM: Xid (PCI:0000:01:00): 62, 32344000 0000b670 00000000 206a7a8a 206a6c4a 206a6db8 206a52ae 206a5aca
févr. 28 18:45:42 user-arch kernel: NVRM: Xid (PCI:0000:01:00): 154, GPU recovery action changed from 0x0 (None) to 0x1 (GPU Reset Required)
févr. 28 18:45:51 user-arch kernel: NVRM: Xid (PCI:0000:01:00): 109, pid=1551, name=Xorg, channel 0x00000002, errorString CTX SWITCH TIMEOUT, Info 0x14009
févr. 28 18:45:57 user-arch kernel: NVRM: GPU0 _kgspLogXid119: ********************************* GSP Timeout **********************************

Is this on the 580xx open or still the 590xx driver?
(nb. you *cannot* use the non-open driver w/ the blackwell chip)

mactemporal · 2026-03-01 10:31:58

Hey
I tried downgrading to previous driver versions but literary nothing ever worked so i stuck with nvidia-open 590.48.01-13
and nvidia-utils 590.48.01-4 ...

Last edited by mactemporal (2026-03-01 13:08:00)

seth · 2026-03-01 14:40:30

literary nothing ever worked

https://bbs.archlinux.org/viewtopic.php?id=57855

What did you do *exactly* and how did that not work *exactly*?
https://wiki.archlinux.org/title/Arch_Linux_Archive
You'll need https://archive.archlinux.org/packages/ … kg.tar.zst and read https://wiki.archlinux.org/title/Dynami … le_Support
Edit: and of course downgrade nvidia-utils and possibly the multilib package as well.

Last edited by seth (2026-03-01 14:41:03)

Arch Linux

#1 2026-01-27 19:04:53

System suddenly freezes forcing me to reboot, seems to be GPU issue

#2 2026-01-27 19:30:04

Re: System suddenly freezes forcing me to reboot, seems to be GPU issue

#3 2026-01-27 21:10:00

Re: System suddenly freezes forcing me to reboot, seems to be GPU issue

#4 2026-01-27 21:23:30

Re: System suddenly freezes forcing me to reboot, seems to be GPU issue

#5 2026-02-04 17:19:13

Re: System suddenly freezes forcing me to reboot, seems to be GPU issue

#6 2026-02-04 20:38:18

Re: System suddenly freezes forcing me to reboot, seems to be GPU issue

#7 2026-02-05 03:29:39

Re: System suddenly freezes forcing me to reboot, seems to be GPU issue

#8 2026-02-05 08:45:26

Re: System suddenly freezes forcing me to reboot, seems to be GPU issue

#9 2026-02-05 10:55:28

Re: System suddenly freezes forcing me to reboot, seems to be GPU issue

#10 2026-02-05 12:46:47

Re: System suddenly freezes forcing me to reboot, seems to be GPU issue

#11 2026-02-05 15:04:55

Re: System suddenly freezes forcing me to reboot, seems to be GPU issue

#12 2026-02-08 17:37:27

Re: System suddenly freezes forcing me to reboot, seems to be GPU issue

#13 2026-02-28 18:01:44

Re: System suddenly freezes forcing me to reboot, seems to be GPU issue

#14 2026-02-28 19:52:49

Re: System suddenly freezes forcing me to reboot, seems to be GPU issue

#15 2026-03-01 10:31:58

Re: System suddenly freezes forcing me to reboot, seems to be GPU issue

#16 2026-03-01 14:40:30

Re: System suddenly freezes forcing me to reboot, seems to be GPU issue

Board footer