-
Notifications
You must be signed in to change notification settings - Fork 503
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
CUDA platform error: CUDA_ERROR_INVALID_PTX #2251
Comments
Sorry, not much idea. That's the sort of error that mostly just shouldn't happen. It could be an error in the CUDA compiler, or a corrupted file on disk, or perhaps trying to load an out of date file, or perhaps linking against one CUDA toolkit but using the compiler from a different version, or various other things. For what it's worth, here's where that error message gets generated: https://github.com/pandegroup/openmm/blob/master/platforms/cuda/src/CudaContext.cpp#L675 Perhaps you can figure out what's wrong with the PTX it's trying to load. |
Haven't dug into the code yet, but I have compiled OpenMM 7.3 against CUDA 8.0 on my Fedora 25 machine (seems I'll have to update to Fedora 27 if I want CUDA 9.2) and installed into the ChimeraX environment. That works fine. On the other hand, running from an installation of OpenMM 7.3 in a fresh Anaconda virtualenv on my CentOS 7 machine (with the CUDA9.2 library and bin dirs first in LD_LIBRARY_PATH and PATH respectively) gives the same CUDA_ERROR_INVALID_PTX. So it's an environment problem, nothing to do with ChimeraX. I guess the question now is, is this a problem with CentOS 7 in general, or just my machine? Will try some debugging and see. |
Edited |
At the end of all that, it's a boring old driver incompatibility. Updated my display driver from 390 to 415, and all is well. |
This seems to be a problem either with my specific environment or with how OpenMM has been ported into ChimeraX, but there's not a lot for me to go on in the traceback. This happens for both OpenMM 7.2.2 and 7.3, and isn't specific to a given simulation (I get the same error if I try to run OpenMM's benchmark.py using ChimeraX's python). Really just looking for pointers on where to start with debugging.
The text was updated successfully, but these errors were encountered: