Skip to content
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

CUDNN_STATUS_NOT_SUPPORTED #83

Open
edebrouwer opened this issue Feb 14, 2020 · 8 comments
Open

CUDNN_STATUS_NOT_SUPPORTED #83

edebrouwer opened this issue Feb 14, 2020 · 8 comments

Comments

@edebrouwer
Copy link

Hi, I'm having this error while trying to train the model on CelebA dataset :

Traceback (most recent call last):
File "train.py", line 347, in
train(args, dataset, generator, discriminator, device)
File "train.py", line 167, in train
fake_predict.backward()
File "/home/edward/anaconda3/lib/python3.6/site-packages/torch/tensor.py", line 195, in backward
torch.autograd.backward(self, gradient, retain_graph, create_graph)
File "/home/edward/anaconda3/lib/python3.6/site-packages/torch/autograd/init.py", line 99, in backward
allow_unreachable=True) # allow_unreachable flag
RuntimeError: cuDNN error: CUDNN_STATUS_NOT_SUPPORTED. This error may appear if you passed in a non-contiguous input.

I'm running Python 3.6.4 with torch 1.4.0. Nvidia-driver 418.56

Any idea where I could look for some fix ?

Thanks so much !

Edward

@rosinality
Copy link
Owner

Could you give me the error logs with CUDA_LAUNCH_BLOCKING=1?

@edebrouwer
Copy link
Author

I have exactly the same error logs with CUDA_LAUNCH_BLOKCING=1

@rosinality
Copy link
Owner

Could you check output dimensions? Sometimes this kind of error happens when tensor is too large.

@edebrouwer
Copy link
Author

edebrouwer commented Feb 17, 2020 via email

@rosinality
Copy link
Owner

Sorry but it is hard to know why...

@Dimbl4
Copy link

Dimbl4 commented Apr 10, 2020

@edebrouwer try to upgrade torch 1.4.0 to nightly, it helped me. (cuda 10.0, torch 1.5.0.dev20200313+cu100)

@KelestZ
Copy link

KelestZ commented Apr 12, 2020

Same issue. Did anyone fix it?

@seongeunso
Copy link

I had same issue in here, so I downgrade the torch version.
For me, torch 1.2.0 + cuda 10.0 works well (link)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants