Dear developer, it seems that the latest nvidia-470 (470.63.01) driver has a minor glitch, that after every wake-up from suspend (especially when there are active CUDA processes either running or at breakpoint), I need to manually rmmod and modprobe the nvidia-uvm kernel driver in order to run PyTor…

this bug happens on multi-gpu machines with cuda 12 and v525 or 528. I solved it by sudo rmmod nvidia_uvm from the host. Looks like if 2 processes access this file at the same time, 1st one blocks it and 2nd one hangs and after that any call to cuda gives an error for everybody. I thought it was rel…

The bug still exists on the latest versions of Nvidia drivers up to today. Did you suspend while CUDA process is running or at breakpoint? If I terminate all CUDA processes before suspend, there is no such issue.

I can confirm this happens to me on driver 525.125 on AMD64 Debian Sid kernel 6.5.0-2 with a GTX-1070, exactly as described after suspend.

nothing’s gonna happen if none of you provide the nvidia-bug-report

I have filed a bug 4343535 internally for tracking purpose. Would request to share nvidia bug report from repro state so that I can match configuration as close as possible.

Hi, Can someone please share nvidia bug report from repro state so that I can match configuration as close as possible.

Hi @amrits , I was having the exact same issue on two machines (one laptop, one PC). I tested the state with the following code: #include <stdio.h> #include <cuda.h> int main() { CUresult ret = cuInit(0); if (ret != CUDA_SUCCESS) { fprintf(stderr, "cuInit failed! Error code: %d\n"…

I was able to repro issue locally but wanted to check if anyone knows the last passing driver. root@oemqa-Alienware-m17:~/cuda-samples/Samples/1_Utilities/bandwidthTest# ./bandwidthTest [CUDA Bandwidth Test] - Starting… Running on… cudaGetDeviceProperties returned 999 → unknown error CUDA err…

No clue when this last worked, I remember this being an issue for a long long time (years?). Update from my side: since last post I haven’t needed to reload nvidia_uvm after suspending. Seems to work as intended. Hope it helps finding the root cause.

Update after multiple months, I still don’t see this issue anymore. I haven’t tried reverting the changes I made, but something seems to work ;)

BUG: nvidia_uvm needs to be removed and re-inserted in order to work after wakeup from suspend

Graphics / Linux Linux

amrits May 23, 2025, 7:51am 24

Please enable PreserveVideoMemoryAllocations as per below steps and share test results.

#rmmod nvidia-uvm nvidia-drm nvidia-modeset nvidia
#modprobe nvidia “NVreg_PreserveVideoMemoryAllocations=1”

Topic		Replies	Views
/dev/nvidia-uvm IO error on Ubuntu 22.04, 520 to 535 driver versions Linux cuda , opencl , linux-driver	2	3678	August 27, 2023
Nvidia-uvm module bug on suspend Linux	14	2258	December 7, 2023
CUDA Error when starting machine post suspension Linux	7	3926	April 16, 2021
_raw_q_flush NULL deref in nvidia_uvm during suspend on GM108M / 580.159.03 (kernel 7.0.x) Linux	0	215	May 3, 2026
Suspend not working on Ubuntu 26.04 /black screen on resume with Nvidia driver version 595 Linux	13	933	September 5, 2026
Periodically resume to black screen using kernel 6.10.4 with nvidia driver 555.58.02-15 on GTX 970 Linux	1	538	September 23, 2024
cuda (375.66) is failing with uknown error 30 after suspending Ubuntu 16.04 Linux	3	1764	September 5, 2017
Problem with resume from suspend (Ubuntu 16.04, GT 940MX) Linux	171	63185	August 2, 2021
565.57.01 won't resume from "suspend to RAM" Linux	35	5325	May 18, 2025
Sometimes unable to suspend OS: Failed to map NvKmsKapiMemory Linux	14	1193	September 3, 2026

BUG: nvidia_uvm needs to be removed and re-inserted in order to work after wakeup from suspend

Related topics