CUDA_ERROR_OUT_OF_MEMO - Githubissues

GoogleCodeExporter commented 9 years ago

What steps will reproduce the problem?
1. Run: pyrit benchmark

What is the expected output? What do you see instead?

Expected is running benchmark, bu the only result I get is:

Traceback (most recent call last):
  File "/usr/bin/pyrit", line 531, in <module>
    sys.exit(Pyrit_CLI().initFromArgv())
  File "/usr/bin/pyrit", line 92, in initFromArgv
    }.setdefault(commands[0] if len(commands) > 0 else 'help',
self.print_help)()
  File "/usr/bin/pyrit", line 413, in benchmark
    cp = cpyrit.CPyrit()
  File "/usr/lib64/python2.6/site-packages/cpyrit.py", line 191, in __init__
    self.cores.append(CUDACore(queue=self, dev_idx=dev_idx))
  File "/usr/lib64/python2.6/site-packages/cpyrit.py", line 113, in __init__
    _cpyrit_cuda.CUDADevice.__init__(self, dev_idx)
SystemError: CUDA_ERROR_OUT_OF_MEMORY

What version of the product are you using? On what operating system?
Tested on GF 8400GS, Core 2 Duo 2Ghz
Fedora 11 x86_64 Kernel 2.6.29.6-213.fc11
CUDA Toolkit 2.3 
NVIDIA Drivers 185.18.14
Pyrit 0.2.3

Original issue reported on code.google.com by xapei...@gmail.com on 30 Jul 2009 at 8:33

GoogleCodeExporter commented 9 years ago

Does the problem persist between cold(!) boots ?

Original comment by lukas.l...@gmail.com on 30 Jul 2009 at 10:30

GoogleCodeExporter commented 9 years ago

Hi, thanks for reply.
The problem persist between cold boots. But i tried run pyrit in text mode 
before
loging in desktop and voila...  

Little update:
pyrit works after loging into KDE, but i have to switch to virtual terminal
(ctrl+alt+f1 etc.) and run pyrit there.

So, for me, problem solved. Thanks for help.

Original comment by xapei...@gmail.com on 31 Jul 2009 at 9:00

GoogleCodeExporter commented 9 years ago

A out-of-memory-error by the cuda-driver is *very* uncommon. This is because 
apart
from the kernel-image, pyrit consumes gpu-memory only in terms of a few hundred
kilobytes.

Given that the 8400GS is probably the "lowest-possible-profile" yet still
cuda-compatible gpu there is, my guess is that it can barely handle the
framebuffer-memory..·

Closed for now, thanks for reporting.

Original comment by lukas.l...@gmail.com on 31 Jul 2009 at 9:23

Changed state: Invalid

GoogleCodeExporter commented 9 years ago

I also get this same problem with Fedora 11 x86_64, but with two 8600M GT 
cards. Is
there a solution not involving a virtual terminal?

Original comment by VampireP...@gmail.com on 2 Sep 2009 at 4:27

GoogleCodeExporter commented 9 years ago

Is it the exact same traceback:

File "/usr/lib64/python2.6/site-packages/cpyrit.py", line 113, in __init__
    _cpyrit_cuda.CUDADevice.__init__(self, dev_idx)
SystemError: CUDA_ERROR_OUT_OF_MEMORY

??

Original comment by lukas.l...@gmail.com on 2 Sep 2009 at 7:23

GoogleCodeExporter commented 9 years ago

hi, i got the same issue here:

StarK wcrack # pyrit list_cores
Pyrit 0.4.0 (C) 2008-2011 Lukas Lueg http://pyrit.googlecode.com
This code is distributed under the GNU General Public License v3+

Traceback (most recent call last):
  File "/usr/bin/pyrit-2.7", line 6, in <module>
    pyrit_cli.Pyrit_CLI().initFromArgv()
  File "/usr/lib64/python2.7/site-packages/pyrit_cli.py", line 115, in initFromArgv
    func(self, **options)
  File "/usr/lib64/python2.7/site-packages/pyrit_cli.py", line 291, in list_cores
    with cpyrit.cpyrit.CPyrit() as cp:
  File "/usr/lib64/python2.7/site-packages/cpyrit/cpyrit.py", line 440, in __init__
    self.cores.append(CUDACore(queue=self, dev_idx=dev_idx))
  File "/usr/lib64/python2.7/site-packages/cpyrit/cpyrit.py", line 245, in __init__
    _cpyrit_cuda.CUDADevice.__init__(self, dev_idx)
SystemError: CUDA_ERROR_OUT_OF_MEMORY
StarK wcrack # lspci | grep VGA
01:00.0 VGA compatible controller: NVIDIA Corporation G92 [GeForce 8800 GT] 
(rev a2)

i use nvidia-drivers 319.17 and cuda-sdk : 5.0.35-r1 (on gentoo ~amd64)

Original comment by hisoka2501 on 27 May 2013 at 2:19

http403 / pyrit

CUDA_ERROR_OUT_OF_MEMO #23