-
Notifications
You must be signed in to change notification settings - Fork 495
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
error in ms_deformable_col2im_cuda: invalid device function #13
Comments
me too ....... do you have troubles with running 'maks.sh'? , I can run mask.sh in my shell, but I can run with pycharm. |
@chen1234520 Do you see errors during the compilation? Please provide more details about the environment you use, including system, CUDA, pytorch, e.t.c. Thank you! |
@jackroos I am also getting this error. There is no error in the compilation stage. On running the code I can see the epochs along with this error. Following is the my environment details: Kindly help me in this regard. Thank you |
@ayberksener Could you check if you can run the unit test as described in the README? |
Have you solved the problem yet? |
Similar issue, I got an 'error in ms_Deformable_im2col_cuda: invalid device function' when run with "python test.py": |
I encountered the same issue. Not sure whether it is relevant to slurm. Using More specifically, I use single node 8 GPUs via slurm, while only one GPU is working and the remaining 7 GPUs cannot find the multiscaledeformableattention in Cuda kernel. |
I solve this problem by install pytorch=1.5 with cuda=9.2, i.e., : It seems that the cuda operator is only compatible with pytorch-1.5 with cuda 9.2. |
My cuda verison is 11.0, and I also have troubles with running python test.py because of no moudel named multiscaledeformableattention,but I have run make.sh successfully.I guess the project does not support cuda11 compilation. |
I had the same issue as @ycliu93 . I was able to train on one node, but it threw this error when I shifted to multiple nodes. |
help help!!!! Thanks!
The text was updated successfully, but these errors were encountered: