I finally managed to produce the freeze again and captured a bug report during it. Still happens with the new driver randomly on GNOME when using multiple displays. While one was frozen I could execute the tool on the other one.
nvidia-bug-report.log.gz (1.2 MB)
With my new RTX 5060 this is my driver status:
575.181 until 580.82.09 all 95% of all the game were not playable ( most of them were Windows + Proton, and some native ported games in Linux):
low FPS (between 4 and 15 and High GPU utilization)
broken audio ( screeching, out of sync)
After installed the 580.95.05 the situation changed and the games were finally playable even for hours ( played Control and Cyberpunk 2077 for almost all Saturday afternoon) with the following issue:
Now with the installation of the new 580.105.08 the audio situation its better, no more broken audio ( screeching, out of sync) but issue the low FPS is still there.
Browsers HW acceleration is not working, and Smplayer have artifacts but works okyes, in all the versions above. ( more info here Lenovo ThinkStation P520 + RTX 5060Ti 16 GB - Games going in a "Bad state")
nvidia-bug-report.log.gz (525.0 KB)
We are tracking this under bug id 5667666, Can you please generate Linux bug report and share here to proceed further on this bug?
Version 580.105.08 fixed the external monitor freezing the system but not the one using an external TV. It breaks both when already connected at boot and when connected afterwards (hdmi)
modinfo nvidia
filename: /lib/modules/6.17.8-arch1-1/updates/dkms/nvidia.ko.zst
alias: char-major-195-*
version: 580.105.08
supported: external
license: NVIDIA
firmware: nvidia/580.105.08/gsp_tu10x.bin
firmware: nvidia/580.105.08/gsp_ga10x.bin
srcversion: 29E07DAF85D9F5330CC1C83
alias: pci:v000010DEd*sv*sd*bc06sc80i00*
alias: pci:v000010DEd*sv*sd*bc03sc02i00*
alias: pci:v000010DEd*sv*sd*bc03sc00i00*
alias: of:N*T*Cnvidia,tegra264-displayC*
alias: of:N*T*Cnvidia,tegra264-display
alias: of:N*T*Cnvidia,tegra234-displayC*
alias: of:N*T*Cnvidia,tegra234-display
depends:
name: nvidia
retpoline: Y
vermagic: 6.17.8-arch1-1 SMP preempt mod_unload
sig_id: PKCS#7
signer: DKMS module signing key
parm: NvSwitchRegDwords:NvSwitch regkey (charp)
parm: NvSwitchBlacklist:NvSwitchBlacklist=uuid[,uuid...] (charp)
parm: NVreg_ResmanDebugLevel:int
parm: NVreg_RmLogonRC:int
parm: NVreg_ModifyDeviceFiles:int
parm: NVreg_DeviceFileUID:int
parm: NVreg_DeviceFileGID:int
parm: NVreg_DeviceFileMode:int
parm: NVreg_InitializeSystemMemoryAllocations:int
parm: NVreg_UsePageAttributeTable:int
parm: NVreg_EnablePCIeGen3:int
parm: NVreg_EnableMSI:int
parm: NVreg_EnableStreamMemOPs:int
parm: NVreg_RestrictProfilingToAdminUsers:int
parm: NVreg_PreserveVideoMemoryAllocations:int
parm: NVreg_EnableS0ixPowerManagement:int
parm: NVreg_S0ixPowerManagementVideoMemoryThreshold:int
parm: NVreg_DynamicPowerManagement:int
parm: NVreg_DynamicPowerManagementVideoMemoryThreshold:int
parm: NVreg_EnableGpuFirmware:int
parm: NVreg_EnableGpuFirmwareLogs:int
parm: NVreg_OpenRmEnableUnsupportedGpus:int
parm: NVreg_EnableUserNUMAManagement:int
parm: NVreg_MemoryPoolSize:int
parm: NVreg_KMallocHeapMaxSize:int
parm: NVreg_VMallocHeapMaxSize:int
parm: NVreg_IgnoreMMIOCheck:int
parm: NVreg_NvLinkDisable:int
parm: NVreg_EnablePCIERelaxedOrderingMode:int
parm: NVreg_RegisterPCIDriver:int
parm: NVreg_RegisterPlatformDeviceDriver:int
parm: NVreg_EnableResizableBar:int
parm: NVreg_EnableDbgBreakpoint:int
parm: NVreg_EnableNonblockingOpen:int
parm: NVreg_CoherentGPUMemoryMode:charp
parm: NVreg_RegistryDwords:charp
parm: NVreg_RegistryDwordsPerDevice:charp
parm: NVreg_RmMsg:charp
parm: NVreg_GpuBlacklist:charp
parm: NVreg_TemporaryFilePath:charp
parm: NVreg_ExcludedGpus:charp
parm: NVreg_DmaRemapPeerMmio:int
parm: NVreg_RmNvlinkBandwidth:charp
parm: NVreg_RmNvlinkBandwidthLinkCount:int
parm: NVreg_ImexChannelCount:int
parm: NVreg_CreateImexChannel0:int
parm: NVreg_GrdmaPciTopoCheckOverride:int
parm: rm_firmware_active:charp
dmesg log
NVRM: GPU at PCI:0000:01:00: GPU-b39367ca-0644-d089-2313-8af63b63e85d
NVRM: Xid (PCI:0000:01:00): 120, pid=1294, name=kwin_wayland, GSP task exception: load access page fault (cause:0xd) @ pc:0x12b125c, partition:2#0, task:3
NVRM: Reported by libos partition:2#4 kernel v3.1 [0] @ ts:1763584118
NVRM: RISC-V CSR State:
NVRM: sstatus:0x0000000200000020 sscratch:0xffffffffa30134d0 sie:0x0000000000000220 sip:0x0000000000000000
NVRM: sepc:0x00000000012b125c stval:0x0000000000000009 scause:0x000000000000000d
NVRM: RISC-V GPR State:
NVRM: ra:0x00000000012b11fe sp:0x0000000400a0c4b0 gp:0x0000000000000000 tp:0x0000000000000000
NVRM: a0:0x0000000000000000 a1:0x0000000000000004 a2:0x0000000400a0c560 a3:0x0000000900000000
NVRM: a4:0x0000000000001000 a5:0x0000000000000000 a6:0x0000000029292929 a7:0x0000000000000006
NVRM: s0:0x0000000400a0c630 s1:0x00000003fa01c010 s2:0x00000003fa1a2500 s3:0x00000003fa116ed0
NVRM: s4:0x0000000004160fd8 s5:0x0000000000000000 s6:0x00000003fa1a24f0 s7:0x00000003fa01c010
NVRM: s8:0x00000003fa013f50 s9:0x00000003fa01b8d0 s10:0x00000003fa1a34f0 s11:0x00000003fa01b710
NVRM: t0:0x0000000000000001 t1:0x0000000000000002 t2:0x000000000ba014c8 t3:0x0000000000000000
NVRM: t4:0x00000003fa01b010 t5:0x0000000020000000 t6:0x000000000419b570
NVRM: Stack Trace:
NVRM: 0x00000000012b125c
NVRM: 0x00000000012aea3a
NVRM: 0x000000000121e3f2
NVRM: 0x00000000018e69ce
NVRM: 0x00000000011ccb20
NVRM: 0x0000000001aded78
NVRM: 0x00000000010552ec
NVRM: 0x0000000001055c5a
NVRM: 0x0000000001a4c096
NVRM: 0x0000000001a5a89c
NVRM: 0x0000000001b8e6da
NVRM: 0x0000000001a8ac22
NVRM: 0x0000000001bf01ca
NVRM: 0x0000000001a87336
NVRM: PC Trace:
NVRM: 0x00000000012b125c 0x0000000001b23d2a 0x00000000012b11fa 0x00000000012aacb8 0x0000000001a8785c
NVRM: 0xffffffff93002e4c 0x0000000001a87880 0x00000000012aac88 0x000000000143d6ac 0x0000000001b40a28
NVRM: 0xffffffff93002e4c 0x0000000001b409da 0x000000000143d6e4 0x000000000143002c 0xffffffff93002e4c
NVRM: 0x0000000001430002 0x000000000143d6b4 0xffffffff93002e4c 0x000000000143d6c6 0x00000000012aac62
NVRM: 0x00000000017d4782 0x00000000017c84d0 0x000000000146b23e 0x0000000001700172 0x00000000017335c4
NVRM: 0x000000000170012c 0x000000000146b1b0 0x00000000017c8484 0x00000000017bd32e 0x00000000017c328c
NVRM: 0x00000000017bd33a 0x00000000017c8694 0x00000000018de790 0x00000000017c8450 0x00000000017335c4
NVRM: 0x00000000017c8a90 0x0000000001a03e1e 0x00000000017c8a72 0x00000000017335c4 0x00000000017c8a62
NVRM: 0x0000000001a03e1e 0x00000000017c842e 0x0000000001b94a76 0x00000000017c840c 0x00000000017335c4
NVRM: 0x00000000017c8a4c 0x0000000001a03e1e 0x00000000017c83f2 0x000000000182134e 0x0000000001b468ba
NVRM: 0x000000000182131c 0xffffffff93002e4c 0x00000000018212fc 0x00000000013e9ae4
NVRM: Local I/O Register State:
NVRM: 0x01281500:0x00000000 0x01281504:0xbadf5620 0x01281508:0x00849970 0x01281510:0x00000000
NVRM: 0x01281528:0x01049042 0x0128152c:0x01000040 0x01281530:0x00000000 0x01280008:0x00000000
NVRM: ------------[ end crash report ]------------
NVRM: GPU0 GSP RPC buffer contains function 76 (GSP_RM_CONTROL) sequence 4087 and data 0x000000000073029a 0x0000000000000010.
NVRM: GPU0 RPC history (CPU -> GSP):
NVRM: entry function sequence data0 data1 ts_start ts_end duration actively_polling
NVRM: 0 76 GSP_RM_CONTROL 4087 0x000000000073029a 0x0000000000000010 0x000643f86ceb2bfb 0x0000000000000000 y
NVRM: -1 76 GSP_RM_CONTROL 4086 0x00000000007302a2 0x0000000000000008 0x000643f86ceb2a02 0x000643f86ceb2bf1 495us
NVRM: -2 76 GSP_RM_CONTROL 4085 0x0000000000731152 0x0000000000000050 0x000643f86ceb2530 0x000643f86ceb29f4 1220us
NVRM: -3 76 GSP_RM_CONTROL 4084 0x000000000073028a 0x0000000000000014 0x000643f86ceb2177 0x000643f86ceb2526 943us
NVRM: -4 76 GSP_RM_CONTROL 4083 0x0000000000730293 0x000000000000000c 0x000643f86ceb1991 0x000643f86ceb216d 2012us
NVRM: -5 76 GSP_RM_CONTROL 4082 0x00000000007302ae 0x0000000000000006 0x000643f86ceb14ca 0x000643f86ceb1987 1213us
NVRM: -6 76 GSP_RM_CONTROL 4081 0x0000000000730245 0x0000000000000810 0x000643f86cea5b62 0x000643f86ceb1442 47328us
NVRM: -7 76 GSP_RM_CONTROL 4080 0x0000000000730246 0x000000000000080c 0x000643f86cea597c 0x000643f86cea5b58 476us
NVRM: GPU0 RPC event history (CPU <- GSP):
NVRM: entry function sequence data0 data1 ts_start ts_end duration during_incomplete_rpc
NVRM: 0 4099 POST_EVENT 0 0x0000000000000001 0x0000000000000000 0x000643f86cea1fba 0x000643f86cea1fd5 27us
NVRM: -1 4108 UCODE_LIBOS_PRINT 0 0x0000000000000000 0x0000000000000000 0x000643f86a769634 0x000643f86a769635 1us
NVRM: -2 4108 UCODE_LIBOS_PRINT 0 0x0000000000000000 0x0000000000000000 0x000643f86a76951d 0x000643f86a76951d
NVRM: -3 4098 GSP_RUN_CPU_SEQUENCER 0 0x000000000000061c 0x0000000000003fe2 0x000643f86a75bfb7 0x000643f86a75d42a 5235us
nvidia-modeset: ERROR: GPU:0: Failure reading DP dongle info for display device Tech Concepts Beyond TV (HDMI-0).
nvidia-modeset: ERROR: GPU:0: Failed to query VR headset for Tech Concepts Beyond TV (HDMI-0)
NVRM: Xid (PCI:0000:01:00): 154, GPU recovery action changed from 0x0 (None) to 0x1 (GPU Reset Required)
nvidia-modeset: WARNING: GPU:0: Failure processing EDID for display device BOE Technology Group Co., Ltd (DP-4).
nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device BOE Technology Group Co., Ltd (DP-4)
nvidia-modeset: ERROR: GPU:0: Failure reading maximum pixel clock value for display device DP-4.
nvidia-modeset: ERROR: GPU:0: Failed detecting connected display devices
nvidia-modeset: ERROR: GPU:0: Failed detecting connected display devices
nvidia-modeset: ERROR: GPU:0: Failed detecting connected display devices
nvidia-modeset: ERROR: GPU:0: Failure reading maximum pixel clock value for display device HDMI-0.
nvidia-modeset: WARNING: GPU:0: Failure processing EDID for display device DP-4.
nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DP-4
nvidia-modeset: ERROR: GPU:0: Failed detecting connected display devices
nvidia-modeset: ERROR: GPU:0: Failed detecting connected display devices
nvidia-modeset: ERROR: GPU:0: Failed detecting connected display devices
nvidia-modeset: WARNING: GPU:0: Failure processing EDID for display device DP-4.
nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DP-4
kwin_wayland[1294]: segfault at 0 ip 00007fe6e67717b2 sp 00007ffd2f6a7178 error 6 in libnvidia-eglcore.so.580.105.08[b717b2,7fe6e5e42000+cc3000] likely on CPU 14 (core 7, socket 0)
Code: 00 74 19 48 8b 07 48 8b 80 d8 8d 02 00 0f b6 90 2e 6f 02 00 d0 ea 83 f2 01 83 e2 01 48 8b 87 08 ac 04 00 48 8b 80 80 00 00 00 <c7> 00 a2 05 01 20 48 83 c0 08 89 50 fc 48 8b 97 08 ac 04 00 48 89
nvidia-modeset: ERROR: GPU:0: Failed detecting connected display devices
nvidia-modeset: ERROR: GPU:0: Failed detecting connected display devices
nvidia-modeset: ERROR: GPU:0: Failed detecting connected display devices
nvidia-modeset: WARNING: GPU:0: Failure processing EDID for display device DP-4.
nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DP-4
nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c67e:0:0:0x00000062
nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c67e:2:0:0x00000062
nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c67e:4:0:0x00000062
nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c67e:6:0:0x00000062
nvidia-modeset: WARNING: GPU:0: Lost display notification (0:0x00000000); continuing.
nvidia-modeset: WARNING: GPU:0: Lost display notification (0:0x00000000); continuing.
[drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 0
nvidia-modeset: ERROR: GPU:0: Failed detecting connected display devices
nvidia-modeset: ERROR: GPU:0: Failed detecting connected display devices
nvidia-modeset: ERROR: GPU:0: Failed detecting connected display devices
nvidia-modeset: WARNING: GPU:0: Failure processing EDID for display device DP-4.
nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DP-4
nvidia-smi
nvidia-smi
Fri Nov 21 09:11:14 2025
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 580.105.08 Driver Version: 580.105.08 CUDA Version: 13.0 |
+-----------------------------------------+------------------------+----------------------+
| GPU Name Persistence-M | Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util Compute M. |
| | | MIG M. |
|=========================================+========================+======================|
| 0 NVIDIA GeForce RTX 3070 ... Off | 00000000:01:00.0 On | N/A |
| N/A 35C P3 22W / 115W | 1344MiB / 8192MiB | 0% Default |
| | | N/A |
+-----------------------------------------+------------------------+----------------------+
I experience similar issues with 580.105.08 playing Elite Dangerous while sitting in a hanger on a space port:
kernel: [drm:nv_drm_gem_alloc_nvkms_memory_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to allocate NVKMS memory for GEM object
kernel: [drm:nv_drm_gem_alloc_nvkms_memory_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to allocate NVKMS memory for GEM object
Which causes my entire desktop to lag periodically. I even get Libinput errors due to this and audio crackling:
kwin_wayland[1662]: Libinput: event3 - Razer Razer Viper Ultimate Dongle: client bug: event processing lagging behind by 43ms, your system is too slow
kwin_wayland[1662]: Libinput: event3 - Razer Razer Viper Ultimate Dongle: client bug: event processing lagging behind by 28ms, your system is too slow
kwin_wayland[1662]: Libinput: event3 - Razer Razer Viper Ultimate Dongle: client bug: event processing lagging behind by 30ms, your system is too slow
kwin_wayland[1662]: Libinput: event3 - Razer Razer Viper Ultimate Dongle: client bug: event processing lagging behind by 22ms, your system is too slow
kwin_wayland[1662]: Libinput: event3 - Razer Razer Viper Ultimate Dongle: WARNING: log rate limit exceeded (5 msgs per 60min). Discarding future messages.
After quitting the game everything went back to normal.
nvidia-bug-report.log.gz (552.5 KB)
Iâve experienced audio crackling too but thought it was just Linuxâs audio code sucking. It seems to happen most when the GPU is under high stress. Or maybe itâs when VRAM is being freed/allocated.
Not sure if itâs related, but I get these sometimes in dmesg:
perf: interrupt took too long (4994 > 4925), lowering kernel.perf_event_max_sample_rate to 40000
Thanks.
Currently, I have peace and quiet - on X11 with an HDMI cable with 580.95.05.
I recently had almost 112 hours of uptime, and now I have 62 hours of uptime again without any screen freezes or black screens.
There are already several updates waiting to be installed again.
Iâll probably test Wayland again, but first Iâll try X11 with a DP cable and see what changes.
hi, still nothing new to report? was someone from NVIDIA able to reproduce it?
donât have high hopes regarding 585 and future releases :|
Is HDR supposed to be functional now with the Vulkan developer drivers? Enabling it on Gnome reduces the brightness and causes the night light value to be visually higher. Enabling it in Far Cry 5 causes washed out colors. Enabling HDR scRGB causes funny colors. Nothing seems to have improved.
Please help to share bug report from repro state.
Also please share reliable repro steps, if any, that will help me to run similar experiment for in house repro.
I posted a new topic with my problems with the new Vulkan Beta, but didnât realize I was probably supposed to be replying to this megathread instead.
Toggling the rendering to PQ at runtime, or running a game such as Borderlands 4 which toggles PQ on post-startup, hangs the game. Reliably reproduced by turning rendering to SDR and back to HDR again. Or switching from PQ to scRGB and back to PQ again. And if rendering is scRGB on startup, it seems to work fine in scRGB mode. It looks like deep fried garbage if switching from PQ to scRGB, then freezes on switching back to PQ.
Cyberpunk 2077 also reliably freezes if alt-tabbing out of the benchmark results screen to a Discord client and back again. It seems to work fine tabbing to Spectacle to capture a screen shot, since Proton GE Wayland/HDR doesnât support the Steam overlay, which I recall doesnât support HDR screen shots either.
Dumb workaround if this still happens: Toggle the refresh rate for the affected monitor, apply, then revert. Happens to me on dual DP setup, even just DPMS suspending the monitors without the system going to sleep.
This, plus flickering and sync loss on the second monitor were why I switched it to an HDMI cable.
Thanks for the tip but I donât think my monitor offers changing the refresh if no signal is detected. I have very few options available in the OSD. when it is like that. I was able to get it to see the monitor a second time, so I guess that was a fluke before.
Try this dxvk.conf:
# if you have 12 GB, use around 2-4 GB less here:
dxgi.maxDeviceMemory = 8192
The game notoriously goes over the VRAM budget and relies on Windows driver behavior to put everything back into fast video memory. The Linux driver doesnât seem to be able to do that, or at least it cannot to this with the way DXVK allocates memoryâŠ
I keep one copy of this file in the main installation directory, and symlink it per product (e.g. where the Odyssey executable lives):
ln -s ../../dxvk.conf Products/elite-dangerous-odyssey-64/dxvk.conf
ln -s ../../dxvk.conf Products/elite-dangerous-64/dxvk.conf
This mostly prevents the issue. The only downside is that you may be seeing textures loading more slowly.
Thanks for the update, Please let us now your findings.
Hello Vrachatte,
Can you please let me know if the logs that I submitted, were checked to see the problem that I am experiencing?
Please let me know,
Thanks
(580 release feedback & discussion - #854 by rebelyouth.hacklab)
Hello world :-)
After recent update to nvidia-kmod-devel-580.105.08.1403000 my secondary screen can handle only 2048x1152 resolution instead 2560x1440 (dell monitor). Primary screen is 4K and works fine. Things are huge and hard to work with.
14.3-RELEASE-p5 AMD64 RTX5070.
2560x1440 is not on the list of WM (Enlightenment) nor nvidia-settings.
Previous nvidia devel driver was working fine. Please fix. Thanks :-)
FreeBSD bug report: Making sure you're not a bot!
Tomek
Not sure if this is actually the âcauseâ because it worked all the years since Elite Dangerous release on Linux just fine.
I feel like the driver just doesnât seem to properly garbage collect stuff here and fills up the VRAM. Then the driver starts to swap and causes the allocation errors.
Even with the dxvk.conf I can see my VRAM being filled up way above 8 GiB. I placed it in âŠ/steamapps/common/Elite Dangerous/Products/elite-dangerous-odyssey-64/ next to EliteDangerous64.exe and it doesnât help at all. I have 10 GB VRAM and hence limiting in to 8 should work according to your observations?
The only partial solution I found is using GE-Proton10-25 the game still occasional lags but the driver does not throw these errors and after a short while the game recovers from the issue and goes back to normal. However there are sometimes render artifacts afterwards.
Memory is allocated at the nanosecond time frame. Itâs entirely possible the game or another app is doing small allocations and going above the VRAM limit without you knowing.
Iâve noticed this to be a real issue when alt tabbing in and out of a game when VRAM is near full.
laptop or desktop?