-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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 9 - {Question] #443
Comments
I've been running CUDA Version 9.0.176 for a while now without issue. I did run into some installation issues which were solved by disabling the half operators (also improve memory usage): torch/cutorch#797 Memory usage seems a bit worse with Cuda 9 as per this issue. |
@ProGamerGov Sorry to bother you here with this issue, but it seems you got past the |
@subzerofun Whats terminal output in relation to the error? It looks like I might have solved the issue like this according my
Then I appear to have had a few issues with cuDNN:
This was what I had up until the issue with Torch:
There may or may not have been some manual things that I did, so this may be incomplete. |
Thanks for the quick reply and the bash commands! The first part is nearly a mirror of my attempts, tried it ~4 times with slightly different cmds and env vars, but cutorch simply refused to compile without errors. I've tried the nvcc flag Warnings look like this: warning: 'THCudaHalfStorage_get' has C-linkage specified, but returns user-defined type 'half' (aka '__half') which is incompatible with C [-Wreturn-type-c-linkage]
extern "C" half THCudaHalfStorage_get(THCState * state, const THCudaHalfStorage *, ptrdiff_t); For some reason the special nvcc flag did not help in my case, although i've tried with:
And this line (cmake output) irritates me – the "no_half..." flag is set two times. But my environment variables are clean! compute_61 = GTX 1080 Ti, compute_35 = GTX 780 Since the standard install (the first part of your history) always failed for me at [21%] (regardless of the flag) i've followed another tip: 1. Comment out the cutorch and cunn packages in install.sh: if [ -x "$path_to_nvcc" ]
then
echo "Found CUDA on your machine. Installing CUDA packages"
#cd ${THIS_DIR}/extra/cutorch && $PREFIX/bin/luarocks make rocks/cutorch-scm-1.rockspec || exit 1
#cd ${THIS_DIR}/extra/cunn && $PREFIX/bin/luarocks make rocks/cunn-scm-1.rockspec || exit 1
fi and i can finally get to [100%], but with literally hundreds of "HalfTensor" warnings. That can't be too good, can it? Can't remember that my last torch install produced that many warnings... 2. Activate torch paths + environment: export PATH=/Users/thatsme/torch/install/bin:$PATH
. /Users/thatsme/torch/install/bin/torch-activate 3. Manually install the two missing pkgs from the source repos:
And again, hundreds of warnings like: warning: 'THC_float2half' has C-linkage specified, but returns user-defined type 'half' (aka '__half') which is incompatible with C [-Wreturn-type-c-linkage]
extern "C" half THC_float2half(float a);
^
/Users/squanchy-birdup/torch/install/include/THC/generic/THCStorage.h:28:17: warning: 'THCudaHalfStorage_get' has C-linkage specified, but returns user-defined type 'half' (aka '__half') which is incompatible with C [-Wreturn-type-c-linkage]
extern "C" half THCudaHalfStorage_get(THCState * state, const THCudaHalfStorage *, ptrdiff_t); 4. Run The first batch of 164/164 passes and then the second fails here: 134/210 Kmeans ............ [WAIT]./test.sh: line 34: 89405 Abort trap: 6
th -lnn -e "nn.test()" My Tensorflow 1.4 + PyTorch installs were relatively painless and both frameworks are working, so i'm sure that the cudnn files (include + lib) are in the right place. My bash source only has entries for CUDA 9 & cudnn 7. Since macOS has some small deviations in the cuda directories - compared to linux – i can't follow your second part exactly. One thing i don't understand in your cmds: Sorry for the excessively long message 📝, but i've gone through the Issue sections of torch/distro and cutorch numerous times and somehow nothing is bringing me closer to a working install ... Do you have any idea what's causing my issues? Why the |
@subzerofun Unfortunately I don't know a whole lot about Torch itself or cutorch. So I wouldn't know where to start in regards to your issue. |
@ProGamerGov OK, thanks nonetheless for the help! Wasted a few hours too much, forcing Torch to work with CUDA 9.0 or 9.1 ... Reverted back to 8.0 and now the install went fine. The Now i have three different cuda versions installed 🙃... will write a bash function that can toggle between CUDA 9.0 and 8.0 for Torch: Since the standard CUDA_ROOT path on macOS is always A way to create a completely self-contained torch install (incl. all CUDA 8.0 libs and source files) would be a better solution... Docker would be perfect for it – but GPU passthrough doesn't work in the macOS version. |
Should expect any problems when updating to Cuda 9? I have several GPU renderers that will require the update with newer versions, but I'm wondering if it might cause problems for my favorite terminal app, neural style? Has anyone tried it yet?
The text was updated successfully, but these errors were encountered: