It cannot do that without a power monitoring ic onboard , it’s a guesstimate.
Igors lab testing
“” NVIDIA is actually known for permanently monitoring every 12V rail via shunts and the voltage drop that occurs there. Thus, a suitable monitoring chip can be used to determine the flowing currents and the firmware can then throttle the power supply so that the maximum power target stored in the firmware is never exceeded. Interestingly, these shunts do not exist on any of the RTX 4060 boards and a suitable monitoring chip is also completely missing .“”
shelter
February 24, 2025, 10:06am
187
Well, is it limited to the 4060 only then?
Because I don’t get any output from my 4070 either:
Attached GPUs : 1
GPU 00000000:01:00.0
Voltage
Graphics : N/A
faz
February 24, 2025, 11:00am
188
Power usage and voltage are different. Voltage SHOULD be available. It WAS available before they moved nvidia-smi to nvml. It’s also missing on my RTX 3070 and will be missing on every card until they expose something in nvml to read voltage. (i think)
1 Like
Voltage has been intentionally deprecated from nvidia-smi per the docs, and will be completely removed.
https://docs.nvidia.com/deploy/nvidia-smi/index.html
Current voltage of the graphics unit. This field is deprecated and always displays "N/A". Voltage will be removed in a future release.
So it is not a bug. Why they are doing this, who knows.
2 Likes
Running Kingdom Come: Deliverance 2 with git master branch of DXVK-NVAPI and everything else from proton-ge 9-25. Trying to use PROTON_ENABLE_NGX_UPDATER=1 to use DLSS override causes a black screen on launch. DLSS indicator does work:
Launch options with PROTON_ENABLE_NGX_UPDATER=1:
PROTON_LOG=1 DXVK_NVAPI_VKREFLEX=1 DXVK_NVAPI_SET_NGX_DEBUG_OPTIONS=DLSSIndicator=1024,DLSSGIndicator=2,Logging=1,LogLevel=1 PROTON_ENABLE_NGX_UPDATER=1 DXVK_NVAPI_DRS_SETTINGS=NGX_DLSS_SR_OVERRIDE=on,NGX_DLSS_RR_OVERRIDE_RENDER_PRESET_SELECTION=render_preset_k %command%
Going PROTON_ENABLE_NGX_UPDATER=0 makes the game launch properly but not do DLSS override. Having NVAPI_VKREFLEX on or off makes no difference.
Log from PROTON_LOG:
7994.046:0120:0124:info:nvapi64:<-NvAPI_DRS_DestroySession: OK
7994.047:0120:0124:fixme:cryptasn:CryptDecodeObjectEx Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4
7994.047:0120:0124:fixme:cryptasn:CryptDecodeObjectEx Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4
7999.177:0120:0124:err:sync:RtlpWaitForCriticalSection section 00006FFFFFFB13A0 "../src-wine/dlls/ntdll/loader.c: loader_section" wait timed out in thread 0124, blocked by 0288, retrying (60 sec)
7999.177:0120:0288:err:sync:RtlpWaitForCriticalSection section 00006FFFEF0BB000 "?" wait timed out in thread 0288, blocked by 0278, retrying (60 sec)
7999.177:0120:0278:err:sync:RtlpWaitForCriticalSection section 00006FFFFFFB13A0 "../src-wine/dlls/ntdll/loader.c: loader_section" wait timed out in thread 0278, blocked by 0288, retrying (60 sec)
7999.177:0120:027c:err:sync:RtlpWaitForCriticalSection section 00006FFFEF0BB000 "?" wait timed out in thread 027c, blocked by 0278, retrying (60 sec)
7999.177:0120:0280:err:sync:RtlpWaitForCriticalSection section 00006FFFEF0BB000 "?" wait timed out in thread 0280, blocked by 0278, retrying (60 sec)
7999.177:0120:0284:err:sync:RtlpWaitForCriticalSection section 00006FFFEF0BB000 "?" wait timed out in thread 0284, blocked by 0278, retrying (60 sec)
8016.809:0120:01b8:info:vkd3d-proton:dxgi_vk_swap_chain_recreate_swapchain_in_present_task: Got 4 swapchain images.
8051.760:0120:0124:warn:seh:dispatch_exception backtrace: --- Exception 0x80000101.
8051.760:0120:0124:trace:seh:dispatch_exception code=80000101 flags=1 addr=00007C00AC51EBAD ip=7c00ac51ebad
8051.760:0120:0124:warn:seh:dispatch_exception EXCEPTION_WINE_ASSERTION exception (code=80000101) raised
8051.760:0120:0124:trace:seh:dispatch_exception rax=fffffffffffffffc rbx=00007c009fe4a240 rcx=00007c00ac51ebad rdx=0000000000000000
8051.760:0120:0124:trace:seh:dispatch_exception rsi=0000000000000080 rdi=00007c009fe4a240 rbp=00000001000ffbf0 rsp=00000001000ffb98
8051.760:0120:0124:trace:seh:dispatch_exception r8=0000000000000000 r9=0000000000000000 r10=00000001000ffbb0 r11=0000000000000246
8051.760:0120:0124:trace:seh:dispatch_exception r12=000000000011d470 r13=0000000000000000 r14=01db86fe0b3a875a r15=00000001000ffbb0
8051.760:0120:0124:trace:seh:call_vectored_handlers calling handler at 00006FFFEF40B1F0 code=80000101 flags=1
8051.760:0120:0124:trace:seh:call_vectored_handlers handler at 00006FFFEF40B1F0 returned 0
8051.760:0120:0124:trace:seh:call_vectored_handlers calling handler at 00006FFFF1140680 code=80000101 flags=1
8051.760:0120:0124:trace:seh:call_vectored_handlers handler at 00006FFFF1140680 returned 0
8051.760:0120:0124:trace:seh:call_vectored_handlers calling handler at 00006FFFF148B1B0 code=80000101 flags=1
8051.760:0120:0124:trace:seh:call_vectored_handlers handler at 00006FFFF148B1B0 returned 0
8051.760:0120:0124:trace:seh:call_vectored_handlers calling handler at 00006FFFFD24C080 code=80000101 flags=1
8051.760:0120:0124:trace:seh:call_vectored_handlers handler at 00006FFFFD24C080 returned 0
8051.760:0120:0124:trace:unwind:dwarf_virtual_unwind function 7c00ac51ebad base 0x7c00ac51eb90 cie 0x7c00ac5cc380 len 14 id 0 version 1 aug 'zR' code_align 1 data_align -8 retaddr %rip
8051.760:0120:0124:warn:seh:dwarf_virtual_unwind backtrace: 0x7c00ac51ebad: /usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/libc.so.6 + 0x11ebad (syscall + 0x1d).
8051.760:0120:0124:trace:unwind:execute_cfa_instructions 7c00ac51eb90: DW_CFA_def_cfa %rsp, 8
8051.760:0120:0124:trace:unwind:execute_cfa_instructions 7c00ac51eb90: DW_CFA_offset %rip, -8
8051.760:0120:0124:trace:unwind:dwarf_virtual_unwind fde 0x7c00ac5e3c90 len 10 personality (nil) lsda (nil) code 7c00ac51eb90-7c00ac51ebc7
8051.760:0120:0124:trace:unwind:dwarf_virtual_unwind next function rip=00007c00a8c42919
8051.760:0120:0124:trace:unwind:dwarf_virtual_unwind rax=fffffffffffffffc rbx=00007c009fe4a240 rcx=00007c00ac51ebad rdx=0000000000000000
8051.760:0120:0124:trace:unwind:dwarf_virtual_unwind rsi=0000000000000080 rdi=00007c009fe4a240 rbp=00000001000ffbf0 rsp=00000001000ffba0
8051.760:0120:0124:trace:unwind:dwarf_virtual_unwind r8=0000000000000000 r9=0000000000000000 r10=00000001000ffbb0 r11=0000000000000246
8051.760:0120:0124:trace:unwind:dwarf_virtual_unwind r12=000000000011d470 r13=0000000000000000 r14=01db86fe0b3a875a r15=00000001000ffbb0
8051.760:0120:0124:err:seh:call_stack_handlers invalid frame 00000001000FFB98 (0000000000022000-0000000000120000)
8051.760:0120:0124:err:seh:NtRaiseException Exception frame is not in stack limits => unable to dispatch exception.
8051.791:00dc:028c:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
8052.271:0030:0290:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
8052.272:0030:0294:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
8052.272:0030:0298:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
8052.272:0030:029c:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
8052.272:0030:02a0:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
pid 409608 != 409607, skipping destruction (fork without exec?)
Nvidia bug report:
nvidia-bug-report.log.gz (440.9 KB)
Replacing DLL file (as this is a single player game) does work:
faz
February 24, 2025, 10:01pm
191
Why have they done this??? This seriously makes 0 sense
1 Like
flat1:
nvidia-smi -q -d VOLTAGE
same here with 1650 ti moblie
uh
it should be not removed
Sure, it is still defined other places like NVCtrl, but that is tied to X11. I don’t believe NV_CTRL_GPU_CURRENT_CORE_VOLTAGE from there is even supported on a newer card, I just tested quickly out of curiosity in an X session and this attribute is not giving me anything on my 50-series. Is that what you are using or is there another source to dig through too? I have seen that you like to be obtuse, so I’m not necessarily expecting a straight answer :)
It is unfortunate for Nvidia to remove it (or not re-implement it) in nvidia-smi either way. Clearly they seem to intend nvidia-smi/nvml to be the intended management tool.
faz
February 25, 2025, 9:22am
196
PROTON_ENABLE_NGX_UPDATER=1
still broken on 570 drivers with some games. Tested Red Dead Redemption 2, the game window opens but nothing ever displays. Removing the env var makes the game launch again.
Seems to work on THE FINALS, so I forced newer DLSS stuff which seemed to work perfectly (preset K, etc)
1 Like
Frame gen locks up the GPU clock to 780 Mhz for the 5080 RTXs. Theres already a couple of people reporting this bug. Best example personally i can give is cyberpunk since i tested it myself. If you activate frame gen at x3 or x4 it will lock up the clock at 780 MHz but if you start cyberpunk with x2 frame gen it kinda works but it looks kinda glitchy and buggy but the clock doesn’t lock up. I hope nvidia fixes this with the new driver update.
Also Monster hunter Wilds has the same bug with frame gen on. everything is laggy and glitchy but when i turn it off its all smooth. basically any games with the frame gen option the GPU clock locks up at 780 MHz.
Ryzen 7 9800x3D | with 5080 RTX | 64 gb ram. I’m on Archlinux based distro if that helps.
birdie
February 26, 2025, 1:38pm
198
For me this is the first driver in years for which resume is completely broken for me:
kernel: NVRM: gpuWaitForGfwBootComplete_TU102: failed to wait for GFW_BOOT: (progress 0x3)
kernel: NVRM: kgspWaitForGfwBootOk_TU102: failed to wait for GFW boot complete: 0x55 VBIOS version 95.04.69.40.36
kernel: NVRM: kgspWaitForGfwBootOk_TU102: (the GPU may be in a bad state and may need to be reset)
kernel: NVRM: _kgspLogXid119: ********************************* GSP Timeout **********************************
kernel: NVRM: _kgspLogXid119: Note: Please also check logs above.
kernel: NVRM: GPU at PCI:0000:09:00: GPU-c3ad889c-6ef1-2ea2-2635-079a8d083975
kernel: NVRM: Xid (PCI:0000:09:00): 119, pid=55768, name=nvidia-sleep.sh, Timeout after 6s of waiting for RPC response from GPU0 GSP! Expected function 76 (GSP_RM_CONTROL) (0x20801117 0x1).
kernel: NVRM: GPU0 GSP RPC buffer contains function 76 (GSP_RM_CONTROL) and data 0x0000000020801117 0x0000000000000001.
kernel: NVRM: GPU0 RPC history (CPU -> GSP):
kernel: NVRM: entry function data0 data1 ts_start ts_end duration actively_polling
kernel: NVRM: 0 76 GSP_RM_CONTROL 0x0000000020801117 0x0000000000000001 0x00062f0b794056b3 0x0000000000000000 y
kernel: NVRM: -1 47 UNLOADING_GUEST_DRIVE 0x0000000000000000 0x0000000000000000 0x00062f09365e4005 0x00062f09365f299e 59801us
kernel: NVRM: -2 10 FREE 0x00000000c1e00b62 0x0000000000000000 0x00062f09365e3ea6 0x00062f09365e3fb6 272us
kernel: NVRM: -3 10 FREE 0x000000000000000a 0x0000000000000000 0x00062f09365e3d3e 0x00062f09365e3ea4 358us
kernel: NVRM: -4 10 FREE 0x000000000000000b 0x0000000000000000 0x00062f09365e3c21 0x00062f09365e3cc8 167us
kernel: NVRM: -5 10 FREE 0x0000000000000006 0x0000000000000000 0x00062f09365e39ec 0x00062f09365e3c1a 558us
kernel: NVRM: -6 10 FREE 0x0000000000000002 0x0000000000000000 0x00062f09365e345e 0x00062f09365e39a1 1347us
kernel: NVRM: -7 10 FREE 0x0000000000000005 0x0000000000000000 0x00062f09365e30b9 0x00062f09365e3459 928us
kernel: NVRM: GPU0 RPC event history (CPU <- GSP):
kernel: NVRM: entry function data0 data1 ts_start ts_end duration during_incomplete_rpc
kernel: NVRM: 0 4108 UCODE_LIBOS_PRINT 0x0000000000000000 0x0000000000000000 0x00062f09365eb072 0x00062f09365eb072
kernel: NVRM: -1 4128 GSP_POST_NOCAT_RECORD 0x0000000000000002 0x0000000000000028 0x00062f09365e5d70 0x00062f09365e5d72 2us
kernel: NVRM: -2 4111 PERF_BRIDGELESS_INFO_ 0x0000000000000000 0x0000000000000000 0x00062f09365c4bd6 0x00062f09365c4bd7 1us
kernel: NVRM: -3 4128 GSP_POST_NOCAT_RECORD 0x0000000000000005 0x00000285017d990c 0x00062f09365c1d34 0x00062f09365c1d35 1us
kernel: NVRM: -4 4099 POST_EVENT 0x0000000000000000 0x0000000000000000 0x00062f09365c08c2 0x00062f09365c08c5 3us
kernel: NVRM: -5 4128 GSP_POST_NOCAT_RECORD 0x0000000000000005 0x00000285017d990c 0x00062f09365bcd2b 0x00062f09365bcd2c 1us
kernel: NVRM: -6 4099 POST_EVENT 0x0000000000000000 0x0000000000000000 0x00062f09365bb964 0x00062f09365bb966 2us
kernel: NVRM: -7 4099 POST_EVENT 0x0000000000000000 0x0000000000000000 0x00062f09365b9e4a 0x00062f09365b9e4c 2us
kernel: CPU: 13 UID: 0 PID: 55768 Comm: nvidia-sleep.sh Tainted: G O 6.13.4-zen3 #2
kernel: Tainted: [O]=OOT_MODULE
kernel: Hardware name: System manufacturer System Product Name/TUF GAMING X570-PLUS (WI-FI), BIOS 5013 03/22/2024
kernel: Call Trace:
kernel: <TASK>
kernel: dump_stack_lvl+0x4c/0x70
kernel: dump_stack+0x10/0x16
kernel: os_dump_stack+0x9/0x10 [nvidia]
kernel: _kgspRpcRecvPoll+0x54c/0x620 [nvidia]
kernel: _issueRpcAndWait+0x71/0x360 [nvidia]
kernel: rpcRmApiControl_GSP+0x67e/0xa10 [nvidia]
kernel: ? os_release_spinlock+0x15/0x20 [nvidia]
kernel: ? _tlsThreadEntryGet+0x82/0x90 [nvidia]
kernel: ? osGetCurrentThread+0x26/0x60 [nvidia]
kernel: rmresControl_Prologue_IMPL+0xd8/0x230 [nvidia]
kernel: resControl_IMPL+0xd9/0x1e0 [nvidia]
kernel: ? _tlsEntryAcquire+0x93/0xe0 [nvidia]
kernel: serverControl+0x48f/0x5c0 [nvidia]
kernel: _rmapiRmControl+0x4f2/0x840 [nvidia]
kernel: rmapiControlWithSecInfo+0x79/0x140 [nvidia]
kernel: rmapiControl+0x24/0x40 [nvidia]
kernel: rm_restart_user_channels+0x6b/0xc0 [nvidia]
kernel: nv_restore_user_channels+0x40/0x1d0 [nvidia]
kernel: nv_set_system_power_state+0xe6/0x490 [nvidia]
kernel: nv_procfs_write_suspend+0xe2/0x150 [nvidia]
kernel: proc_reg_write+0x59/0x90
kernel: vfs_write+0xd4/0x3d0
kernel: ? __x64_sys_fcntl+0x92/0xf0
kernel: ksys_write+0x56/0xd0
kernel: __x64_sys_write+0x14/0x20
kernel: x64_sys_call+0x28a/0x1d70
kernel: do_syscall_64+0x79/0x150
kernel: ? syscall_exit_to_user_mode+0x33/0x170
kernel: ? do_syscall_64+0x85/0x150
kernel: entry_SYSCALL_64_after_hwframe+0x6c/0x74
kernel: RIP: 0033:0x7fdddf751504
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 8b 10 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
kernel: RSP: 002b:00007ffd8f06b418 EFLAGS: 00000202 ORIG_RAX: 0000000000000001
kernel: RAX: ffffffffffffffda RBX: 0000000000000007 RCX: 00007fdddf751504
kernel: RDX: 0000000000000007 RSI: 000056118bba3740 RDI: 0000000000000001
kernel: RBP: 00007ffd8f06b440 R08: 0000000000000410 R09: 0000000000000001
kernel: R10: 0000000000000004 R11: 0000000000000202 R12: 0000000000000007
kernel: R13: 000056118bba3740 R14: 00007fdddf8535c0 R15: 00007fdddf850e80
kernel: </TASK>
kernel: NVRM: _kgspLogXid119: ********************************************************************************
kernel: NVRM: _issueRpcAndWait: rpcRecvPoll timedout for fn 76!
kernel: ------------[ cut here ]------------
kernel: WARNING: CPU: 13 PID: 55768 at nvidia/nv.c:4291 nv_restore_user_channels+0x4e/0x1d0 [nvidia]
kernel: Modules linked in: uinput tun rfcomm snd_hrtimer nvidia_uvm(O) cmac algif_hash algif_skcipher af_alg msr nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nf_log_syslog vboxnetadp(O) vboxnetflt(O) nft_limit nft_ct nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nfnetlink_log nft_log vboxdrv(O) bnep nf_tables libcrc32c nct6775 nct6775_core hwmon_vid input_leds hid_generic usbhid hid btusb btintel btbcm bluetooth ntfs3 nvidia_drm(O) nvidia_modeset(O) snd_hda_codec_realtek snd_hda_codec_generic snd_hda_scodec_component iwlmvm kvm_amd snd_hda_codec_hdmi ptp pps_core kvm nvidia(O) ee1004 mac80211 crct10dif_pclmul libarc4 crc32_pclmul led_class wmi_bmof snd_hda_intel snd_intel_dspcfg crc32c_intel polyval_clmulni polyval_generic sha512_ssse3 snd_hda_codec sha512_generic snd_hwdep snd_hda_core sha256_ssse3 snd_seq sha1_ssse3 snd_seq_device sr_mod backlight aesni_intel snd_pcm cdrom gf128mul crypto_simd ccp drm_client_lib cryptd drm_ttm_helper iwlwifi sha1_generic ttm snd_timer efi_pstore pcspkr snd
kernel: drm_kms_helper k10temp r8169 cfg80211 realtek i2c_piix4 mdio_devres xhci_pci rfkill libphy xhci_hcd 8250 8250_base wmi serial_base tpm_crb tpm_tis tpm_tis_core evdev fuse dm_mod nfnetlink efivarfs tpm libaescfb ecdh_generic ecc rng_core ipv6
kernel: CPU: 13 UID: 0 PID: 55768 Comm: nvidia-sleep.sh Tainted: G O 6.13.4-zen3 #2
kernel: Tainted: [O]=OOT_MODULE
kernel: Hardware name: System manufacturer System Product Name/TUF GAMING X570-PLUS (WI-FI), BIOS 5013 03/22/2024
kernel: RIP: 0010:nv_restore_user_channels+0x4e/0x1d0 [nvidia]
kernel: Code: 30 06 00 00 4c 89 f7 e8 60 94 09 ec f6 43 10 01 74 76 48 89 de 31 ff e8 d0 66 11 00 41 89 c7 85 c0 0f 84 3f 01 00 00 45 31 e4 <0f> 0b 49 81 c5 68 07 00 00 4c 89 ef e8 31 94 09 ec be 01 00 00 00
kernel: RSP: 0018:ffffb92345c27cf8 EFLAGS: 00010246
kernel: RAX: 0000000000000065 RBX: ffff996e02d05000 RCX: ffffb92345c27c78
kernel: RDX: 0000000000000000 RSI: 0000000000000282 RDI: ffffb92345c27c38
kernel: RBP: ffffb92345c27d20 R08: 0000000000000000 R09: ffffb92345c27ae4
kernel: R10: ffffffffc1339d80 R11: 0000000000000002 R12: 0000000000000000
kernel: R13: ffff996e02d05000 R14: ffff996e02d05630 R15: 0000000000000065
kernel: FS: 00007fdddf666740(0000) GS:ffff997cef140000(0000) knlGS:0000000000000000
kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
kernel: CR2: 00007f9e8a72d938 CR3: 000000013dcee000 CR4: 0000000000b50ef0
kernel: Call Trace:
kernel: <TASK>
kernel: ? show_regs.part.0+0x1d/0x30
kernel: ? show_regs.cold+0x8/0xd
kernel: ? __warn.cold+0x95/0xa3
kernel: ? nv_restore_user_channels+0x4e/0x1d0 [nvidia]
kernel: ? report_bug+0x101/0x150
kernel: ? handle_bug+0x5b/0x90
kernel: ? exc_invalid_op+0x18/0x70
kernel: ? asm_exc_invalid_op+0x1b/0x20
kernel: ? nv_restore_user_channels+0x4e/0x1d0 [nvidia]
kernel: ? nv_restore_user_channels+0x40/0x1d0 [nvidia]
kernel: nv_set_system_power_state+0xe6/0x490 [nvidia]
kernel: nv_procfs_write_suspend+0xe2/0x150 [nvidia]
kernel: proc_reg_write+0x59/0x90
kernel: vfs_write+0xd4/0x3d0
kernel: ? __x64_sys_fcntl+0x92/0xf0
kernel: ksys_write+0x56/0xd0
kernel: __x64_sys_write+0x14/0x20
kernel: x64_sys_call+0x28a/0x1d70
kernel: do_syscall_64+0x79/0x150
kernel: ? syscall_exit_to_user_mode+0x33/0x170
kernel: ? do_syscall_64+0x85/0x150
kernel: entry_SYSCALL_64_after_hwframe+0x6c/0x74
kernel: RIP: 0033:0x7fdddf751504
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 8b 10 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
kernel: RSP: 002b:00007ffd8f06b418 EFLAGS: 00000202 ORIG_RAX: 0000000000000001
kernel: RAX: ffffffffffffffda RBX: 0000000000000007 RCX: 00007fdddf751504
kernel: RDX: 0000000000000007 RSI: 000056118bba3740 RDI: 0000000000000001
kernel: RBP: 00007ffd8f06b440 R08: 0000000000000410 R09: 0000000000000001
kernel: R10: 0000000000000004 R11: 0000000000000202 R12: 0000000000000007
kernel: R13: 000056118bba3740 R14: 00007fdddf8535c0 R15: 00007fdddf850e80
kernel: </TASK>
kernel: ---[ end trace 0000000000000000 ]---
kernel: ------------[ cut here ]------------
kernel: WARNING: CPU: 13 PID: 55768 at nvidia/nv.c:4513 nv_set_system_power_state+0x2e7/0x490 [nvidia]
kernel: Modules linked in: uinput tun rfcomm snd_hrtimer nvidia_uvm(O) cmac algif_hash algif_skcipher af_alg msr nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nf_log_syslog vboxnetadp(O) vboxnetflt(O) nft_limit nft_ct nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nfnetlink_log nft_log vboxdrv(O) bnep nf_tables libcrc32c nct6775 nct6775_core hwmon_vid input_leds hid_generic usbhid hid btusb btintel btbcm bluetooth ntfs3 nvidia_drm(O) nvidia_modeset(O) snd_hda_codec_realtek snd_hda_codec_generic
snd_hda_scodec_component iwlmvm kvm_amd snd_hda_codec_hdmi ptp pps_core kvm nvidia(O) ee1004 mac80211 crct10dif_pclmul libarc4 crc32_pclmul led_class wmi_bmof snd_hda_intel snd_intel_dspcfg crc32c_intel polyval_clmulni polyval_generic sha512_ssse3 snd_hda_codec sha512_generic snd_hwdep snd_hda_core sha256_ssse3 snd_seq sha1_ssse3 snd_seq_device sr_mod backlight aesni_intel snd_pcm cdrom gf128mul crypto_simd ccp drm_client_lib cryptd drm_ttm_helper iwlwifi sha1_generic ttm snd_timer efi_pstore pcspkr snd
kernel: drm_kms_helper k10temp r8169 cfg80211 realtek i2c_piix4 mdio_devres xhci_pci rfkill libphy xhci_hcd 8250 8250_base wmi serial_base tpm_crb tpm_tis tpm_tis_core evdev fuse dm_mod nfnetlink efivarfs tpm libaescfb ecdh_generic ecc rng_core ipv6
kernel: CPU: 13 UID: 0 PID: 55768 Comm: nvidia-sleep.sh Tainted: G W O 6.13.4-zen3 #2
kernel: Tainted: [W]=WARN, [O]=OOT_MODULE
kernel: Hardware name: System manufacturer System Product Name/TUF GAMING X570-PLUS (WI-FI), BIOS 5013 03/22/2024
kernel: RIP: 0010:nv_set_system_power_state+0x2e7/0x490 [nvidia]
kernel: Code: 00 00 00 48 8b 70 78 48 8b 78 60 e8 43 cf ff ff 85 c0 0f 85 ea 00 00 00 4d 8b a4 24 58 06 00 00 4d 85 e4 75 d1 e9 c6 fd ff ff <0f> 0b e9 00 fe ff ff 48 8b 3d 83 70 3e 00 4c 89 fe e8 a3 a9 b0 eb
kernel: RSP: 0018:ffffb92345c27d30 EFLAGS: 00010206
kernel: RAX: 0000000000000065 RBX: 0000000000000002 RCX: ffffb92345c27c78
kernel: RDX: ffff996e02d05638 RSI: 0000000000000296 RDI: ffff996e02d05630
kernel: RBP: ffffb92345c27d68 R08: 0000000000000000 R09: ffffb92345c27ae4
kernel: R10: ffffffffc1339d80 R11: 0000000000000002 R12: ffff996e02d05000
kernel: R13: 0000000000000000 R14: ffffb92345c27e60 R15: ffff996e00dd6900
kernel: FS: 00007fdddf666740(0000) GS:ffff997cef140000(0000) knlGS:0000000000000000
kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
kernel: CR2: 00007f9e8a72d938 CR3: 000000013dcee000 CR4: 0000000000b50ef0
kernel: Call Trace:
kernel: <TASK>
kernel: ? show_regs.part.0+0x1d/0x30
kernel: ? show_regs.cold+0x8/0xd
kernel: ? __warn.cold+0x95/0xa3
kernel: ? nv_set_system_power_state+0x2e7/0x490 [nvidia]
kernel: ? report_bug+0x101/0x150
kernel: ? handle_bug+0x5b/0x90
kernel: ? exc_invalid_op+0x18/0x70
kernel: ? asm_exc_invalid_op+0x1b/0x20
kernel: ? nv_set_system_power_state+0x2e7/0x490 [nvidia]
kernel: nv_procfs_write_suspend+0xe2/0x150 [nvidia]
kernel: proc_reg_write+0x59/0x90
kernel: vfs_write+0xd4/0x3d0
kernel: ? __x64_sys_fcntl+0x92/0xf0
kernel: ksys_write+0x56/0xd0
kernel: __x64_sys_write+0x14/0x20
kernel: x64_sys_call+0x28a/0x1d70
kernel: do_syscall_64+0x79/0x150
kernel: ? syscall_exit_to_user_mode+0x33/0x170
kernel: ? do_syscall_64+0x85/0x150
kernel: entry_SYSCALL_64_after_hwframe+0x6c/0x74
kernel: RIP: 0033:0x7fdddf751504
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 8b 10 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
kernel: RSP: 002b:00007ffd8f06b418 EFLAGS: 00000202 ORIG_RAX: 0000000000000001
kernel: RAX: ffffffffffffffda RBX: 0000000000000007 RCX: 00007fdddf751504
kernel: RDX: 0000000000000007 RSI: 000056118bba3740 RDI: 0000000000000001
kernel: RBP: 00007ffd8f06b440 R08: 0000000000000410 R09: 0000000000000001
kernel: R10: 0000000000000004 R11: 0000000000000202 R12: 0000000000000007
kernel: R13: 000056118bba3740 R14: 00007fdddf8535c0 R15: 00007fdddf850e80
kernel: </TASK>
kernel: ---[ end trace 0000000000000000 ]---
OS: Linux 6.13.4 vanilla
GPU: 4070S
CPU: Ryzen 7 5800X
MB: ASUS TUF GAMING X570-PLUS (WI-FI)
I’m using an open source kernel module.
5070 TI support is broken with driver 570.86.16.
Archlinux kernel 6.13.4 / nvidia-open 570.86.16. Intel 14600k, 32 GB RAM, Monitor 1080p
Gaming with proton gives framerates about 10 fps.
Unigine Heaven benchmark around 32 fps.
5070 TI support is broken…shows “NVIDIA Graphics Device” as output of nvidia-smi
1 Like
Disabling VRR with nvidia_drm.disable_vrr=1
kernel parameters made DisplayPort MST and both displays work again.
Go figure as I don’t have monitors that support VRR.
kernel: NVRM: GPU at PCI:0000:01:00: GPU-bd6ea9c2-9aa6-cae8-5848-1dc19cdfa850
kernel: NVRM: Xid (PCI:0000:01:00): 109, pid=287585, name=WoW.exe, Ch 00000067, errorString CTX SWITCH TIMEOUT, Info 0x13c086
Vesktop-1.5.5_e11009d19549f2e4d4bb7241c6c2ae2e.AppImage[7367]: [7367:0226/220735.285575:ERROR:command_buffer_proxy_impl.cc(131)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
kwin_wayland[4249]: kwin_wayland_drm: The main thread was hanging temporarily!
Had another freeze up while playing World of Warcraft. RTX 3090, 570 driver version. Game locks up and I need to terminate it. Same issue I’ve been seeing since at least 535.
cho
February 27, 2025, 5:49am
204
The GeForce RTX 5070 Ti model name is not recognized correctly.:
nvidia-smi
Thu Feb 27 13:45:10 2025
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 570.86.16 Driver Version: 570.86.16 CUDA Version: 12.8 |
|-----------------------------------------+------------------------+----------------------+
| 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 Graphics Device Off | 00000000:01:00.0 Off | N/A |
| 30% 32C P1 53W / 300W | 229MiB / 16303MiB | 0% Default |
| | | N/A |
+-----------------------------------------+------------------------+----------------------+
+-----------------------------------------------------------------------------------------+
| Processes: |
| GPU GI CI PID Type Process name GPU Memory |
| ID ID Usage |
|=========================================================================================|
| 0 N/A N/A 3061 C python3 220MiB |
+-----------------------------------------------------------------------------------------+
570.86.16 does not include PCIe ID for 5070Ti . You can try adding it manually and recompiling, but no idea if it will work.