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

could not create cudnn handle: CUDNN_STATUS_INTERNAL_ERROR #24

Closed
peternara opened this issue Aug 31, 2017 · 6 comments
Closed

could not create cudnn handle: CUDNN_STATUS_INTERNAL_ERROR #24

peternara opened this issue Aug 31, 2017 · 6 comments

Comments

@peternara
Copy link

peternara commented Aug 31, 2017

Hi, @argman

I have a next problem (training )

....
2017-08-31 18:22:46.750620: E tensorflow/stream_executor/cuda/cuda_dnn.cc:371] could not create cudnn handle: CUDNN_STATUS_INTERNAL_ERROR
2017-08-31 18:22:46.750670: E tensorflow/stream_executor/cuda/cuda_dnn.cc:338] could not destroy cudnn handle: CUDNN_STATUS_BAD_PARAM
2017-08-31 18:22:46.750683: F tensorflow/core/kernels/conv_ops.cc:672] Check failed: stream->parent()->GetConvolveAlgorithms( conv_parameters.ShouldIncludeWinogradNonfusedAlgo(), &algorithms)

Do you know this problem? (I used 2 gpu)

@argman
Copy link
Owner

argman commented Aug 31, 2017

@peternara , I think its caused by process not correctly stopped, you can check via ps -aux|grep python

@peternara
Copy link
Author

peternara commented Sep 1, 2017

@argman thank for rely.
This case is when a segment fault occurs. A python process exists, but some processes are dead. So, no model was created. I am only guessing a memory problem between cuda and tf.

@ashleylid
Copy link

I am also having this issue. There are no related python processes running.

@argman argman closed this as completed Dec 6, 2017
@flifuehu
Copy link

flifuehu commented Feb 5, 2018

Run sudo rm -rf ~/.nv/ to fix it.

@burakekincioglu
Copy link

@flifuehu what does this code do? sudo rm -rf ~/.nv/

@HuangShiqing
Copy link

@burakekincioglu
i think the code is to delete a file named ".nv" in your home directory.It may be a nvidia configuration file.
i think the reason it can resolve the problem of some guy is restart the configuration.
Anyway,it doesn't work for me

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

6 participants