-
Notifications
You must be signed in to change notification settings - Fork 75
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
Segmentation fault #47
Comments
I also meet this problem when I transfer a CUDA tensor by float_quantize yesterday, and cannot figure out what made this mistake. |
hi @ASHWIN2605 and @yhhu99, sorry to hear this and thank you for letting me know. Would you kindly help try out v0.2.0 to see if you encounter the same issue? I will look into it in the meantime. |
thanks for your reply, but I wonder know that how can I change the version? |
can you try |
please downgrade to v2.0.0 for now. I will look into fixing this. |
unfortunately I cannot replicate the segmentation fault you are seeing. I am on torch v1.8.0 and CUDA11.1. Not sure if this is due to the difference in our CUDA versions. Can you provide me a minimal example to replicate the issue you are seeing? Also, maybe try removing the cached compilation and recompile it. For example try |
Hi, It was my bad.I didn't update the CUDA version of Pytorch installation to latest 11.0.I had only my NVCC updated in my linux machine to version 11.0 earlier and now after updating the Pytorch CUDA veraion to 11.0,it is working fine without the segmentation fault error.Thank you for the trials you made. @yhhu99 I hope this will help you as well. |
Thank you! I think I know where the problem is. |
Closing because this seems to be resolved. |
Hello,
I am trying to run the fixed_baseline.sh for lp_train configuration in my linux machine, with the following configurations.
Python = 3.8
CUDA = 11.0
PyTorch = 1.8.0
The code is running fine in CPU, but if I changed the device to CUDA then I am getting a Segmentation fault (core dumped).Please if you have seen this in past, kindly help me to resolve this.
The text was updated successfully, but these errors were encountered: