Export to GitHub

pyrit - issue #124

SystemError: CUDA_ERROR_LAUNCH_TIMEOUT from X


Posted on Feb 28, 2010 by Happy Horse

What steps will reproduce the problem? 1. Running pyrit from within X crashes with GTS 250 2. Tried to minimize the buffersize without success 3.

What is the expected output? What do you see instead? Should be working fine since it works from a tty

What version of the product are you using? On what operating system? This is running pyrit 0.3 (r225) on gentoo amd64 with nvidia 190.53-r1 and sdk 2.3

Please provide any additional information below.

pyrit benchmark

Pyrit 0.3.0 (C) 2008-2010 Lukas Lueg http://pyrit.googlecode.com This code is distributed under the GNU General Public License v3+

Running benchmark (3215.5 PMKs/s)... | Exception in thread CUDA-Device #1 'GeForce GTS 250': Traceback (most recent call last): File "/usr/lib64/python2.6/threading.py", line 525, in __bootstrap_inner self.run() File "/usr/lib64/python2.6/site-packages/cpyrit/cpyrit.py", line 114, in run res = self.solve(essid, pwlist) SystemError: CUDA_ERROR_LAUNCH_TIMEOUT

Exception in thread CPU-Core (SSE2): Traceback (most recent call last): File "/usr/lib64/python2.6/threading.py", line 525, in __bootstrap_inner self.run() File "/usr/lib64/python2.6/site-packages/cpyrit/cpyrit.py", line 108, in run essid, pwlist = self.queue._gather(self.buffersize, timeout=0.5) File "/usr/lib64/python2.6/site-packages/cpyrit/cpyrit.py", line 552, in _gather self._check_cores() File "/usr/lib64/python2.6/site-packages/cpyrit/cpyrit.py", line 410, in _check_cores raise SystemError("The core '%s' has died unexpectedly" % core) SystemError: The core 'CUDA-Device #1 'GeForce GTS 250'' has died unexpectedly

Exception in thread CPU-Core (SSE2): Traceback (most recent call last): File "/usr/lib64/python2.6/threading.py", line 525, in __bootstrap_inner self.run() File "/usr/lib64/python2.6/site-packages/cpyrit/cpyrit.py", line 108, in run essid, pwlist = self.queue._gather(self.buffersize, timeout=0.5) File "/usr/lib64/python2.6/site-packages/cpyrit/cpyrit.py", line 552, in _gather self._check_cores() File "/usr/lib64/python2.6/site-packages/cpyrit/cpyrit.py", line 410, in _check_cores raise SystemError("The core '%s' has died unexpectedly" % core) SystemError: The core 'CUDA-Device #1 'GeForce GTS 250'' has died unexpectedly

Traceback (most recent call last): File "/usr/bin/pyrit", line 6, in <module> pyrit_cli.Pyrit_CLI().initFromArgv() File "/usr/lib64/python2.6/site-packages/pyrit_cli.py", line 106, in initFromArgv func(self, **options) File "/usr/lib64/python2.6/site-packages/pyrit_cli.py", line 815, in benchmark cp.enqueue('foo', pws) File "/usr/lib64/python2.6/site-packages/cpyrit/cpyrit.py", line 484, in enqueue self._check_cores() File "/usr/lib64/python2.6/site-packages/cpyrit/cpyrit.py", line 410, in _check_cores raise SystemError("The core '%s' has died unexpectedly" % core) SystemError: The core 'CUDA-Device #1 'GeForce GTS 250'' has died unexpectedly

I'm getting these messages in dmesg when it fails: kernel: NVRM: Xid (0002:00): 8, Channel 00000003

Comment #1

Posted on Feb 28, 2010 by Happy Horse

btw, I also tested with latest rev r229 and I get the same results

Comment #2

Posted on Mar 3, 2010 by Quick Rabbit

Hope this can help.

I also had problems in past if X server war running: more, also if start console in resolution bigger than 80x25. So if you have to run long session of batch/attack/etc better to leave PC to do that jobs without disturb it.

So, after some bad experieces I developed there 3 rules:

A. start PC with care to NOT do framebuffer, but running 80x25: if X server starts, in k/gdm choose "command line login"

B. do all activities on pyrit in command line

C. better avoid other activities on PC when pyrit is running.

Comment #3

Posted on Mar 15, 2010 by Quick Rabbit

I forgot to say that I am talking about NVIDIA card, ATI card needs X server running.

Comment #4

Posted on Apr 2, 2010 by Quick Camel

Please update your drivers to the version that is released together with cuda 3.0

Status: WontFix

Labels:
Type-Defect Priority-Medium