-
Notifications
You must be signed in to change notification settings - Fork 18.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
Getting invalid device function error while trying to make runtest in Ubuntu 14.04 with Cuda 6.0 #626
Comments
@dasabir Hello dasabir, have you solved your problem now? I'm stuck in the same problem with yours...And I haven't found solution from the page of kloudkl. Could you please share your way to solve the problem? |
Hi @wusx11 , I should say I could solve the problem. Though I have done a fresh re-install of Ubuntu 14.04, yet I think last time I was making a mistake in the Makefile.config file. For cuda 6.0 I was uncommenting line 14 and 15 as instructed. But I was not putting an escape character () at the end of line 13. Could you please try it? If that resolves the problem, then this issue can also be closed. |
Hi @dasabir , I hadn't put an escape character at the end of the line 13 as well... And after I did that, it works well! Thank you so much! |
Hi @wusx11, I'm glad that the issue was resolved. I think its time to close the ticket. Also I would request the contributors to add a flag in the comment section of the makefile.config in this regard. |
And uncomment the line 24/25 for CUDA 6.0 is necessary. |
@dasabir Hmm.... i'm unclear too... ㅠ_ㅠ thanks |
I face the same issue, and i solved it successfully. CUDA_ARCH := -gencode arch=compute_20,code=sm_20 uncomment the last two lines -gencode arch=compute_35,code=sm_35 after these you need to make again |
I'm running this error with
and
and
|
I am facing a similar error. using latest CUDA version (8.0) with enabled GPU Nvidia Geforce 820M Ubuntu 16.04. How to change the CUDA arch. [ RUN ] TanHLayerTest/2.TestTanH |
@vamsus have you been able to solve the problem? |
@TheShadow29 I solved CUDA 8.0 installation. By disabling CUDNN support. As Nvidia 820M compute capability is 2.1. To support CUDNN compute capability should be more than 3.0. (https://developer.nvidia.com/cuda-gpus) u can check your GPU compute capability. Disable it by commenting line in the makefile. If u face same error then follow this installation guide link. (http://docs.nvidia.com/cuda/cuda-installation-guide-linux/index.html#axzz4ajfl49uf). |
Hi,
I have installed and compiled caffe successfully (I mean I ran 'make all' and 'make test' without any error). While running 'make runtest' I'm getting an "invalid device function error". The full log is given below. I'm using cuda 6.0 in Ubuntu 14.04 LTS. The gcc/g++ version is 4.6 and I installed and changed the make files as described in '#337' by weinman. I had to install gcc/g++ 4.6 as I was having an error as described in the above link while using gcc/g++ 4.8
Any help will be highly appreciated
The log is below:::
[ RUN ] StochasticPoolingLayerTest/1.TestGradientGPU
F0705 07:26:44.199472 14804 pooling_layer.cu:186] Check failed: error == cudaSuccess (8 vs. 0) invalid device function
*** Check failure stack trace: ***
@ 0x2ad77f5559fd google::LogMessage::Fail()
@ 0x2ad77f55789d google::LogMessage::SendToLog()
@ 0x2ad77f5555ec google::LogMessage::Flush()
@ 0x2ad77f5581be google::LogMessageFatal::~LogMessageFatal()
@ 0x610fba caffe::PoolingLayer<>::Forward_gpu()
@ 0x431c58 caffe::GradientChecker<>::CheckGradientSingle()
@ 0x474124 caffe::StochasticPoolingLayerTest_TestGradientGPU_Test<>::TestBody()
@ 0x55b30d testing::internal::HandleExceptionsInMethodIfSupported<>()
@ 0x553131 testing::Test::Run()
@ 0x553216 testing::TestInfo::Run()
@ 0x553357 testing::TestCase::Run()
@ 0x5536ae testing::internal::UnitTestImpl::RunAllTests()
@ 0x55ae8d testing::internal::HandleExceptionsInMethodIfSupported<>()
@ 0x55278e testing::UnitTest::Run()
@ 0x4120dd main
@ 0x2ad7818ffec5 (unknown)
@ 0x416e57 (unknown)
make: *** [runtest] Aborted (core dumped)
Thanks,
Abir
The text was updated successfully, but these errors were encountered: