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.

Sign up for GitHub

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

Jump to bottom

CUDA not working #9

Open
thomhughes opened this issue Jan 30, 2020 · 3 comments
Open

CUDA not working #9

thomhughes opened this issue Jan 30, 2020 · 3 comments

Comments

@thomhughes
Copy link

thomhughes commented Jan 30, 2020 •
edited
Loading 

[Taichi version 0.3.25, cuda 10.0, commit c5ce590f]
Using CUDA Device [0]: GeForce GTX 980 Ti
Device Compute Capability: 5.2
[E 01/30/20 00:43:20.664] [unified_allocator.cpp:UnifiedAllocator@23] Cuda Error cudaErrorMemoryAllocation: out of memory
[E 01/30/20 00:43:20.664] Received signal 6 (Aborted)
***********************************
* Taichi Compiler Stack Traceback *
***********************************
/home/thom/taichi/lib/python3.7/site-packages/taichi/core/../lib/taichi_core.so: taichi::signal_handler(int)
/usr/lib/libc.so.6(+0x3bfb0) [0x7fd8a2b08fb0]
/usr/lib/libc.so.6: gsignal
/home/thom/taichi/lib/python3.7/site-packages/taichi/core/../lib/taichi_core.so: taichi::Tlang::UnifiedAllocator::UnifiedAllocator(unsigned long, bool)
/home/thom/taichi/lib/python3.7/site-packages/taichi/core/../lib/taichi_core.so: taichi::Tlang::UnifiedAllocator::create(bool)
/home/thom/taichi/lib/python3.7/site-packages/taichi/core/../lib/taichi_core.so: taichi::Tlang::Program::Program(taichi::Tlang::Arch)
/home/thom/taichi/lib/python3.7/site-packages/taichi/core/../lib/taichi_core.so(+0x81ca79) [0x7fd87f0aba79]
/home/thom/taichi/lib/python3.7/site-packages/taichi/core/../lib/taichi_core.so(+0x612fe4) [0x7fd87eea1fe4]
/usr/lib/libpython3.7m.so.1.0: _PyMethodDef_RawFastCallDict
/usr/lib/libpython3.7m.so.1.0: _PyCFunction_FastCallDict
/usr/lib/libpython3.7m.so.1.0: _PyObject_Call_Prepend
/usr/lib/libpython3.7m.so.1.0: PyObject_Call
/usr/lib/libpython3.7m.so.1.0(+0x152813) [0x7fd8a28dd813]
/usr/lib/libpython3.7m.so.1.0: _PyObject_FastCallKeywords
/usr/lib/libpython3.7m.so.1.0(+0x156fb2) [0x7fd8a28e1fb2]
/usr/lib/libpython3.7m.so.1.0: _PyEval_EvalFrameDefault
/usr/lib/libpython3.7m.so.1.0: _PyEval_EvalCodeWithName
/usr/lib/libpython3.7m.so.1.0: _PyFunction_FastCallKeywords
/usr/lib/libpython3.7m.so.1.0(+0x156e30) [0x7fd8a28e1e30]
/usr/lib/libpython3.7m.so.1.0: _PyEval_EvalFrameDefault
/usr/lib/libpython3.7m.so.1.0: _PyFunction_FastCallDict
/usr/lib/libpython3.7m.so.1.0: _PyObject_FastCall_Prepend
/usr/lib/libpython3.7m.so.1.0(+0x152893) [0x7fd8a28dd893]
/usr/lib/libpython3.7m.so.1.0(+0x152a88) [0x7fd8a28dda88]
/usr/lib/libpython3.7m.so.1.0: _PyEval_EvalFrameDefault
/usr/lib/libpython3.7m.so.1.0: _PyFunction_FastCallKeywords
/usr/lib/libpython3.7m.so.1.0(+0x156e30) [0x7fd8a28e1e30]
/usr/lib/libpython3.7m.so.1.0: _PyEval_EvalFrameDefault
/usr/lib/libpython3.7m.so.1.0: _PyEval_EvalCodeWithName
/usr/lib/libpython3.7m.so.1.0: PyEval_EvalCodeEx
/usr/lib/libpython3.7m.so.1.0: PyEval_EvalCode
/usr/lib/libpython3.7m.so.1.0(+0x1fee85) [0x7fd8a2989e85]
/usr/lib/libpython3.7m.so.1.0: PyRun_FileExFlags
/usr/lib/libpython3.7m.so.1.0: PyRun_SimpleFileExFlags
/usr/lib/libpython3.7m.so.1.0(+0x206610) [0x7fd8a2991610]
/usr/lib/libpython3.7m.so.1.0: _Py_UnixMain
/usr/lib/libc.so.6: __libc_start_main
python(_start+0x2e) [0x563762dac05e]

I have tried using both cuda 10.0 and 10.1. Sorry if this is a known issue, I've tried searching for a solution online.

Thank you :) would really like to try and mess around with all this.
@yuanming-hu
Copy link
Member

We are actively working on supporting pre-Pascal GPUs, which has a different unified memory behavior compared to Pascal devices - sorry about the inconvenience. Meanwhile, most examples do not need a GPU to run.

@kkinhhhnhh
Copy link 

[Taichi version 0.3.25, cuda 10.0, commit c5ce590f]
Using CUDA Device [0]: GeForce GTX 980 Ti
Device Compute Capability: 5.2
[E 01/30/20 00:43:20.664] [unified_allocator.cpp:UnifiedAllocator@23] Cuda Error cudaErrorMemoryAllocation: out of memory
[E 01/30/20 00:43:20.664] Received signal 6 (Aborted)
***********************************
* Taichi Compiler Stack Traceback *
***********************************
/home/thom/taichi/lib/python3.7/site-packages/taichi/core/../lib/taichi_core.so: taichi::signal_handler(int)
/usr/lib/libc.so.6(+0x3bfb0) [0x7fd8a2b08fb0]
/usr/lib/libc.so.6: gsignal
/home/thom/taichi/lib/python3.7/site-packages/taichi/core/../lib/taichi_core.so: taichi::Tlang::UnifiedAllocator::UnifiedAllocator(unsigned long, bool)
/home/thom/taichi/lib/python3.7/site-packages/taichi/core/../lib/taichi_core.so: taichi::Tlang::UnifiedAllocator::create(bool)
/home/thom/taichi/lib/python3.7/site-packages/taichi/core/../lib/taichi_core.so: taichi::Tlang::Program::Program(taichi::Tlang::Arch)
/home/thom/taichi/lib/python3.7/site-packages/taichi/core/../lib/taichi_core.so(+0x81ca79) [0x7fd87f0aba79]
/home/thom/taichi/lib/python3.7/site-packages/taichi/core/../lib/taichi_core.so(+0x612fe4) [0x7fd87eea1fe4]
/usr/lib/libpython3.7m.so.1.0: _PyMethodDef_RawFastCallDict
/usr/lib/libpython3.7m.so.1.0: _PyCFunction_FastCallDict
/usr/lib/libpython3.7m.so.1.0: _PyObject_Call_Prepend
/usr/lib/libpython3.7m.so.1.0: PyObject_Call
/usr/lib/libpython3.7m.so.1.0(+0x152813) [0x7fd8a28dd813]
/usr/lib/libpython3.7m.so.1.0: _PyObject_FastCallKeywords
/usr/lib/libpython3.7m.so.1.0(+0x156fb2) [0x7fd8a28e1fb2]
/usr/lib/libpython3.7m.so.1.0: _PyEval_EvalFrameDefault
/usr/lib/libpython3.7m.so.1.0: _PyEval_EvalCodeWithName
/usr/lib/libpython3.7m.so.1.0: _PyFunction_FastCallKeywords
/usr/lib/libpython3.7m.so.1.0(+0x156e30) [0x7fd8a28e1e30]
/usr/lib/libpython3.7m.so.1.0: _PyEval_EvalFrameDefault
/usr/lib/libpython3.7m.so.1.0: _PyFunction_FastCallDict
/usr/lib/libpython3.7m.so.1.0: _PyObject_FastCall_Prepend
/usr/lib/libpython3.7m.so.1.0(+0x152893) [0x7fd8a28dd893]
/usr/lib/libpython3.7m.so.1.0(+0x152a88) [0x7fd8a28dda88]
/usr/lib/libpython3.7m.so.1.0: _PyEval_EvalFrameDefault
/usr/lib/libpython3.7m.so.1.0: _PyFunction_FastCallKeywords
/usr/lib/libpython3.7m.so.1.0(+0x156e30) [0x7fd8a28e1e30]
/usr/lib/libpython3.7m.so.1.0: _PyEval_EvalFrameDefault
/usr/lib/libpython3.7m.so.1.0: _PyEval_EvalCodeWithName
/usr/lib/libpython3.7m.so.1.0: PyEval_EvalCodeEx
/usr/lib/libpython3.7m.so.1.0: PyEval_EvalCode
/usr/lib/libpython3.7m.so.1.0(+0x1fee85) [0x7fd8a2989e85]
/usr/lib/libpython3.7m.so.1.0: PyRun_FileExFlags
/usr/lib/libpython3.7m.so.1.0: PyRun_SimpleFileExFlags
/usr/lib/libpython3.7m.so.1.0(+0x206610) [0x7fd8a2991610]
/usr/lib/libpython3.7m.so.1.0: _Py_UnixMain
/usr/lib/libc.so.6: __libc_start_main
python(_start+0x2e) [0x563762dac05e]

I have tried using both cuda 10.0 and 10.1. Sorry if this is a known issue, I've tried searching for a solution online.

Thank you :) would really like to try and mess around with all this.

Screenshot_20200129-161928

@ashkspark
Copy link

Is the CUDA version stable? Is the CUDA library compatible with CUPY?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@thomhughes @yuanming-hu @ashkspark @kkinhhhnhh