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

Error when make #27

Open
sdsy888 opened this issue Dec 2, 2016 · 4 comments
Open

Error when make #27

sdsy888 opened this issue Dec 2, 2016 · 4 comments

Comments

@sdsy888
Copy link

sdsy888 commented Dec 2, 2016

It seems like this MNC project has some conflict with the latest version of cudnn(5.1)? Because if I turn off the "USE_CUDNN", there won't be any error.

What version of cudnn does this MNC project use, please?
Thank you!

make: *** [.build_release/src/caffe/solvers/adagrad_solver.o] Error 1
make: *** Waiting for unfinished jobs....
In file included from ./include/caffe/util/device_alternate.hpp:40:0,
                 from ./include/caffe/common.hpp:19,
                 from ./include/caffe/blob.hpp:8,
                 from ./include/caffe/net.hpp:10,
                 from ./include/caffe/solver.hpp:7,
                 from ./include/caffe/sgd_solvers.hpp:7,
                 from src/caffe/solvers/adam_solver.cpp:3:
./include/caffe/util/cudnn.hpp: In function ‘void caffe::cudnn::createPoolingDesc(cudnnPoolingStruct**, caffe::PoolingParameter_PoolMethod, cudnnPoolingMode_t*, int, int, int, int, int, int)’:
./include/caffe/util/cudnn.hpp:127:41: error: too few arguments to function ‘cudnnStatus_t cudnnSetPooling2dDescriptor(cudnnPoolingDescriptor_t, cudnnPoolingMode_t, cudnnNanPropagation_t, int, int, int, int, int, int)’
         pad_h, pad_w, stride_h, stride_w));
                                         ^
./include/caffe/util/cudnn.hpp:15:28: note: in definition of macro ‘CUDNN_CHECK’
     cudnnStatus_t status = condition; \
                            ^
In file included from ./include/caffe/util/cudnn.hpp:5:0,
                 from ./include/caffe/util/device_alternate.hpp:40,
                 from ./include/caffe/common.hpp:19,
                 from ./include/caffe/blob.hpp:8,
                 from ./include/caffe/net.hpp:10,
                 from ./include/caffe/solver.hpp:7,
                 from ./include/caffe/sgd_solvers.hpp:7,
                 from src/caffe/solvers/adam_solver.cpp:3:
/usr/local/cuda/include/cudnn.h:803:27: note: declared here
 cudnnStatus_t CUDNNWINAPI cudnnSetPooling2dDescriptor(
                           ^
make: *** [.build_release/src/caffe/solvers/adam_solver.o] Error 1
In file included from ./include/caffe/util/device_alternate.hpp:40:0,
                 from ./include/caffe/common.hpp:19,
                 from ./include/caffe/blob.hpp:8,
                 from ./include/caffe/net.hpp:10,
                 from ./include/caffe/solver.hpp:7,
                 from ./include/caffe/sgd_solvers.hpp:7,
                 from src/caffe/solvers/rmsprop_solver.cpp:3:
./include/caffe/util/cudnn.hpp: In function ‘void caffe::cudnn::createPoolingDesc(cudnnPoolingStruct**, caffe::PoolingParameter_PoolMethod, cudnnPoolingMode_t*, int, int, int, int, int, int)’:
./include/caffe/util/cudnn.hpp:127:41: error: too few arguments to function ‘cudnnStatus_t cudnnSetPooling2dDescriptor(cudnnPoolingDescriptor_t, cudnnPoolingMode_t, cudnnNanPropagation_t, int, int, int, int, int, int)’
         pad_h, pad_w, stride_h, stride_w));

@drinkingkazu
Copy link

drinkingkazu commented Dec 7, 2016

I had this issue when trying to build for pascal TitanX w/ cudnn 5.1.5.
I switched to another tower w/ maxwell TitanX w/ cudnn 4.0.7 and I could build w/o problem.
However I am facing #30 so not yet confirmed as the working case...

@drinkingkazu
Copy link

Just as a follow up, I can confirm the training proceeds fine w/ cudnn 4.0.7.
I took a quick look at cudnn.h for 5.1.5 and it looks like it is easy to make it compilable by changing caffe's cudnn usage to "v3" functions in cudnn.h, though I cannot comment what could be a drawback by "just make it compilable".

@sdsy888
Copy link
Author

sdsy888 commented Dec 8, 2016

@drinkingkazu Thank you for the information! I've met the memory problem on TitanBlack but nailed it on TitanX.

@hgaiser
Copy link

hgaiser commented Dec 8, 2016

Alternatively you can update caffe-mnc with the changes from upstream caffe to get cudnn 5 support. We did a similar thing in our fork and it is running fine on cudnn 5.

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

3 participants