-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Critical Dr.Jit compiler failure: cuda_check(): API error 0718 (CUDA_ERROR_INVALID_PC): "invalid program counter" in D:\a\drjit\drjit\ext\drjit-core\src\eval.cpp:395 #296
Comments
Hi @aantg What OS and GPU model are you using? In my personal experience these type of errors are often related to a faulty driver installation. |
Can confirm this on Manjaro Linux, NVIDIA driver 565.57.01, cuda 12.6.2 (but downgrading cuda did not help). This error occurs with drjit 0.4.6 and Mitsuba 3.5.2, but also with drjit 1.0.0 in the current development version Mitsuba 3.6 when compiled in Release mode (clang 18.1.8 ). "llmv_ad_rgb" always works. Somewhat surprisingly, the error does not occur if the program is compiled in Debug mode. In the latter case (Mitsuba 3.6) the scene from the tutorial "editing_a_scene" notebook works with "cuda_ad_rgb", but fails, for example, when the "diffuse" material is replaced with "roughplastic". This may be a driver problem (as far as I know, this is a beta driver), but the dependence of the error on the compilation mode and the dependence on scene parameters suggest a problem with drjit. ===================================
|
I have also encountered this problem:
Env: Platform: Windows 11
|
Hello. I also have the issue. I tried rolling back to a previous version of Nvidia driver but that did not fix the issue. I am on Fedora 41 I used pip install mitsuba to install the mitsuba renderer. I also tried to compile it, but I end up with the same error message (even though I must say that it has not been easy to compile Mitsuba on the last Fedora release, and I do not know how well I can rely on my installation) . Would it be relevant to try Mitsuba 3.5 and if so could you let me know if I need to roll back to drjit 0.4.6 and how to do so. Everything seems to work well when I use the 'llvm_ad_rgb' variant or any other variant in general. Best, |
This problem is related to the NVIDIA driver version 565, not to the mitsuba 3.x version, cuda version, compiler, linux kernel etc. For me, only downgrading this driver (in my case to 550.135) helped. Version 560 does probably also work. Maybe simply a bug in the beta driver, but maybe also an incompatibility of drjit with new procedure implemented in newer driver. |
Hello, It indeed seems to work now (even if I did not test many tutorials, the one that did not run correctly before downgrading are now working as expected). Thank you very much. I for sure did not downgrade the driver correctly before and probably introduce issues when trying to build Mitsuba. The Nvidia driver version I am currently using is 560.35.03. Thank you again for your help. Best wishes |
This is a critical issue, yet nobody talks about it. Downgrading drivers isn't always an option. |
Dear all -- this is a serious problem indeed. But I don't think this is our fault—a change made between NVIDIA driver version 561 and 565.9 causes a miscompilation of very simple programs. I filed a reproducer with NVIDIA. But even if this is fixed in an upcoming release, I don't think that we will be able to work around it for the existing drivers. If so, we will likely push out a new release of Dr.Jit that just errors out with an error message telling the user to install a newer or older driver. |
Hello. Got this error after updating NVIDIA driver to latest version 565.90 even with "Hello World" example from Mitsuba3 documentation (using 'cuda_ad_rgb' variant of course). Rolling back to previous driver version (561.09) make this error disappear.
Looks like there's some incompatibility?
DrJit 0.4.6 + mitsuba 3.5.2
The text was updated successfully, but these errors were encountered: