dwaaan / pyrit

Automatically exported from code.google.com/p/pyrit
0 stars 0 forks source link

pyrit 0.4.0 w/OpenCL doesn't work for ANY cores #271

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Compile and install cpyrit-opencl-0.4.0 and pyrit-0.4.0
2. Run pyrit selftest
3. Profit?

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

Pyrit 0.3.0 would show three OpenCL devices, one core2duo, one 9400M, and one 
9600M GT. I can't compile that version anymore, but it used to run on an older 
version of Mac OS X. I can boot an old backup to find out if necessary. I seem 
to recall I could use the GPU which was NOT being used for the display. This is 
the opposite behavior of the poclbm.py miner which can only use the active GPU. 
Weird!

Anyway, Pyrit 0.3.0 could use the core2duo and the 9600M GT without dying 
(although you could not use it on a .cap file which was being appended by 
another process. In other words, you couldn't capture packets and use pyrit at 
the same time, but it worked once I stopped capturing packets. 

Pyrit 0.4.0 on the latest Mac OS X (10.6.6) compiles easily, but doesn't show 
the core2duo and borks on both GPUs:

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

Cores incorporated in the test:
#1:  'OpenCL-Device 'GeForce 9400M''
#2:  'OpenCL-Device 'GeForce 9600M GT''
#3:  'Network-Clients'

Running selftest...
Exception in thread OpenCL-Device 'GeForce 9600M GT':
Traceback (most recent call last):
  File "/System/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/threading.py", line 522, in __bootstrap_inner
    self.run()
  File "/Library/Python/2.6/site-packages/cpyrit/cpyrit.py", line 113, in run
    self._testComputeFunction(101)
  File "/Library/Python/2.6/site-packages/cpyrit/cpyrit.py", line 102, in _testComputeFunction
    self.solve(Core.TV_ESSID, [Core.TV_PW] * i))):
SystemError: Failed to create command-queue (CL_DEVICE_NOT_AVAILABLE)

Exception in thread OpenCL-Device 'GeForce 9400M':
Traceback (most recent call last):
  File "/System/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/threading.py", line 522, in __bootstrap_inner
    self.run()
  File "/Library/Python/2.6/site-packages/cpyrit/cpyrit.py", line 110, in run
    essid, pwlist = self.queue._gather(self.buffersize, timeout=0.5)
  File "/Library/Python/2.6/site-packages/cpyrit/cpyrit.py", line 632, in _gather
    self._check_cores()
  File "/Library/Python/2.6/site-packages/cpyrit/cpyrit.py", line 490, in _check_cores
    raise SystemError("The core '%s' has died unexpectedly" % core)
SystemError: The core 'OpenCL-Device 'GeForce 9600M GT'' has died unexpectedly

Traceback (most recent call last):
  File "/usr/local/bin/pyrit", line 6, in <module>
    pyrit_cli.Pyrit_CLI().initFromArgv()
  File "/Library/Python/2.6/site-packages/pyrit_cli.py", line 115, in initFromArgv
    func(self, **options)
  File "/Library/Python/2.6/site-packages/pyrit_cli.py", line 1242, in selftest
    cp.enqueue(essid, pws)
  File "/Library/Python/2.6/site-packages/cpyrit/cpyrit.py", line 564, in enqueue
    self._check_cores()
  File "/Library/Python/2.6/site-packages/cpyrit/cpyrit.py", line 490, in _check_cores
    raise SystemError("The core '%s' has died unexpectedly" % core)
SystemError: The core 'OpenCL-Device 'GeForce 9400M'' has died unexpectedly

What version of the product are you using? On what operating system?

0.4.0 on Mac OS X 10.6.6

Please provide any additional information below.

Original issue reported on code.google.com by deadba...@gmail.com on 2 Mar 2011 at 4:08

GoogleCodeExporter commented 8 years ago
While I don't have the same exact issue as the OP, I'm using a similar OS X 
configuration (Pyrit 0.4.0 on Mac OS X 10.6.6, and I have enabled "Performance 
Mode" in the Energy Saver preference page), so I figured I'd post the issues 
I've run into:

I am able to run pyrit selftest just fine. Results are below:
Pyrit 0.4.0 (C) 2008-2011 Lukas Lueg http://pyrit.googlecode.com
This code is distributed under the GNU General Public License v3+

Cores incorporated in the test:
#1:  'CUDA-Device #1 'GeForce 9600M GT''
#2:  'CUDA-Device #2 'GeForce 9400M''

Running selftest...

All results verified. Your installation seems OK

However, after running pyrit for a while (via pyrit benchmark), I get the 
following error:
File 
"/System/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/threadin
g.py", line 522, in __bootstrap_inner
    self.run()
  File "/Library/Python/2.6/site-packages/cpyrit/cpyrit.py", line 110, in run
    essid, pwlist = self.queue._gather(self.buffersize, timeout=0.5)
  File "/Library/Python/2.6/site-packages/cpyrit/cpyrit.py", line 632, in _gather
    self._check_cores()
  File "/Library/Python/2.6/site-packages/cpyrit/cpyrit.py", line 490, in _check_cores
    raise SystemError("The core '%s' has died unexpectedly" % core)
SystemError: The core 'CUDA-Device #2 'GeForce 9400M'' has died unexpectedly

Traceback (most recent call last):
  File "/usr/local/bin/pyrit", line 6, in <module>
    pyrit_cli.Pyrit_CLI().initFromArgv()
  File "/Library/Python/2.6/site-packages/pyrit_cli.py", line 115, in initFromArgv
    func(self, **options)
  File "/Library/Python/2.6/site-packages/pyrit_cli.py", line 803, in batchprocess
    for results in dbiterator:
  File "/Library/Python/2.6/site-packages/cpyrit/cpyrit.py", line 780, in next
    self.cp.enqueue(self.essid, passwords)
  File "/Library/Python/2.6/site-packages/cpyrit/cpyrit.py", line 564, in enqueue
    self._check_cores()
  File "/Library/Python/2.6/site-packages/cpyrit/cpyrit.py", line 490, in _check_cores
    raise SystemError("The core '%s' has died unexpectedly" % core)
SystemError: The core 'CUDA-Device #2 'GeForce 9400M'' has died unexpectedly

One thing for the OP regarding the 0.3.0 and using the CPU at the same time. 
Per the Wiki:
Problem: Pyrit no longer uses all CPUs after installing a GPU-driven 
extension-module
Solution: This behaviour is intended. Pyrit keeps one CPU free for scheduling 
work with every GPU it uses.

The Late 2008 MBP I'm using has one Core 2 Duo processor in it. My assumption 
is that this "one" cpu is being kept free for scheduling work. 

Hope that helps. Any information/help with the crashing issue would be greatly 
appreciated. 

Original comment by njaeh...@gmail.com on 9 Mar 2011 at 8:08

GoogleCodeExporter commented 8 years ago
The error "SystemError: The core 'CUDA-Device #2 'GeForce 9400M'' has died 
unexpectedly" is actually just a failed check as the real error is happening in 
another thread. Do you get the same error as above as well ("SystemError: 
Failed to create command-queue (CL_DEVICE_NOT_AVAILABLE)") ?

Original comment by lukas.l...@gmail.com on 10 Mar 2011 at 5:16

GoogleCodeExporter commented 8 years ago
Lucas, I'm not quite sure what you mean

Original comment by deadba...@gmail.com on 10 Mar 2011 at 7:11

GoogleCodeExporter commented 8 years ago
it was aimed at comment #1

Original comment by lukas.l...@gmail.com on 10 Mar 2011 at 7:13

GoogleCodeExporter commented 8 years ago
oops looks like ive got a similar issue 

lex@LEXLINTOWER:~$ pyrit benchmark
Pyrit 0.4.0 (C) 2008-2011 Lukas Lueg http://pyrit.googlecode.com
This code is distributed under the GNU General Public License v3+

Calibrating... Exception in thread OpenCL-Device 'Cayman':
Traceback (most recent call last):
  File "/usr/lib/python2.7/threading.py", line 552, in __bootstrap_inner
    self.run()
  File "/usr/local/lib/python2.7/dist-packages/cpyrit/cpyrit.py", line 113, in run
    self._testComputeFunction(101)
  File "/usr/local/lib/python2.7/dist-packages/cpyrit/cpyrit.py", line 103, in _testComputeFunction
    raise ValueError("Test-vector does not result in correct PMK.")
ValueError: Test-vector does not result in correct PMK.

Exception in thread OpenCL-Device 'Cayman':
Traceback (most recent call last):
  File "/usr/lib/python2.7/threading.py", line 552, in __bootstrap_inner
    self.run()
  File "/usr/local/lib/python2.7/dist-packages/cpyrit/cpyrit.py", line 110, in run
    essid, pwlist = self.queue._gather(self.buffersize, timeout=0.5)
  File "/usr/local/lib/python2.7/dist-packages/cpyrit/cpyrit.py", line 632, in _gather
    self._check_cores()
  File "/usr/local/lib/python2.7/dist-packages/cpyrit/cpyrit.py", line 490, in _check_cores
    raise SystemError("The core '%s' has died unexpectedly" % core)
SystemError: The core 'OpenCL-Device 'Cayman'' has died unexpectedly

Traceback (most recent call last):
  File "/usr/local/bin/pyrit", line 6, in <module>
    pyrit_cli.Pyrit_CLI().initFromArgv()
  File "/usr/local/lib/python2.7/dist-packages/pyrit_cli.py", line 115, in initFromArgv
    func(self, **options)
  File "/usr/local/lib/python2.7/dist-packages/pyrit_cli.py", line 1176, in benchmark
    cp.enqueue('foo', ['barbarbar'] * 500)
  File "/usr/local/lib/python2.7/dist-packages/cpyrit/cpyrit.py", line 564, in enqueue
    self._check_cores()
  File "/usr/local/lib/python2.7/dist-packages/cpyrit/cpyrit.py", line 490, in _check_cores
    raise SystemError("The core '%s' has died unexpectedly" % core)
SystemError: The core 'OpenCL-Device 'Cayman'' has died unexpectedly

Original comment by xanderda...@gmail.com on 23 Oct 2011 at 5:42

GoogleCodeExporter commented 8 years ago
Same here, is there any fix?

Original comment by gat...@gmail.com on 2 May 2012 at 6:16

GoogleCodeExporter commented 8 years ago
It also freezes the entire os with some coloured patterns on the screen, is my 
gpu broken?

Original comment by gat...@gmail.com on 3 May 2012 at 8:44

GoogleCodeExporter commented 8 years ago
Any luck fixing this error? I'm getting the same error with a 8500GT

SystemError: The core 'CUDA-Device #1 'GeForce 8500 GT'' has died unexpectedly

Original comment by mannydia...@gmail.com on 25 Nov 2012 at 9:51