This generally means an issue with your driver, and not CUDA.jl. Unless of course you say it didn’t occur with CUDA.jl 3.5, but does with CUDA.jl 3.6 or higher. Can you confirm that, and/or try to narrow down which exact version introduced the failure?
Can you bisect even further? If you clone the CUDA.jl repository, you can do a git bisect and run julia --project -e 'using Pkg; Pkg.test()' at every step.
You start by cloning CUDA.jl from GitHub and working from that directory:
git clone https://github.com/JuliaGPU/CUDA.jl/
cd CUDA.jl
git bisect start
git checkout v3.7.0
git bisect bad
git checkout v3.6.0
git bisect good
(spelling out the commands here for clarity, I know there’s shortcuts)
At that point, git will drop you at specific points in the repository’s history. You then run julia --project -e 'using Pkg; Pkg.test()', and depending on whether that fails or succeeds you execute git bisect bad or git bisect good. After 4 steps, git will tell you which commit is to blame.
HEAD is now at 92f0dce6 Bump version.
gpus@gpus-ESC700-159:~/Downloads/CUDA.jl$ git bisect bad
gpus@gpus-ESC700-159:~/Downloads/CUDA.jl$ git checkout v3.6.0
Previous HEAD position was 92f0dce6 Bump version.
HEAD is now at 2a6bfa6c Merge pull request #1288 from JuliaGPU/tb/shared_isbits
gpus@gpus-ESC700-159:~/Downloads/CUDA.jl$ git bisect good
Bisecting: 20 revisions left to test after this (roughly 4 steps)
[db6170c4d8388f01088b5fe49c6ab3df567a8cfe] Try running CI with the package server enabled.