[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 06 Jul 2012 10:45:10 -0400
From: "Rick \"Zero_Chaos\" Farina" <zerochaos@...too.org>
To: john-users@...ts.openwall.com
Subject: Re: Re: 1.7.9-jumbo6 opencl on nvidia
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07/06/2012 04:12 AM, Samuele Giovanni Tonon wrote:
> On 07/05/2012 10:34 PM, Rick "Zero_Chaos" Farina wrote:
>> On 07/05/2012 03:59 PM, Rick "Zero_Chaos" Farina wrote:
>>> I notice that when I build for just op encl support or both opencl and
>>> cuda support that "john --test" fails:
>>
>>> OpenCL platform 0: NVIDIA CUDA, 1 device(s).
>>> Using device 0: NVS 4200M
>>> OpenCL error (UNKNOWN ERROR :() in file (common-opencl.c) at line (39) -
>>> (Source kernel not found!)
>>
>> Okay so I'm new at this.... it helps a lot when you actually install the
>> opencl kernels... *doh*
>>
>>> I am currently packaging this up for gentoo and it could be my fault but
>>> when I build straight from source for opencl I get this:
>>
>>
>> Below, however, is still a valid concern. This happens with my package
>> as well as with straight from source builds.
>>
>> Thanks!
>>
>>> OpenCL platform 0: NVIDIA CUDA, 1 device(s).
>>> Using device 0: NVS 4200M
>>> Local work size (LWS) 64, Global work size (GWS) 4194304
>>> Benchmarking: Netscape LDAP salted SHA-1 [OpenCL]... DONE
>>> Many salts: 26214K c/s real, 25982K c/s virtual
>>> Only one salt: 22469K c/s real, 22469K c/s virtual
>>
>>> OpenCL platform 0: NVIDIA CUDA, 1 device(s).
>>> Using device 0: NVS 4200M
>>> Max local work size 1024 Error -4
>>> Error -4
>>> Error -4
>>> Error -4
>>> Error -4
>>> Error -4
>>> Error -4
>>> Error -4
>>> Error -4
>>> Error -4
>>> Error -4
>>> Optimal local work size 1
>>> (to avoid this test on next run do export LWS=1)
>>> Local work size (LWS) 1, Global work size (GWS) 2097152
>>> Benchmarking: Raw MD5 [OpenCL]... OpenCL error
>>> (CL_MEM_OBJECT_ALLOCATION_FAILURE) in file (opencl_rawmd5_fmt.c) at line
>>> (338) - (failed in clEnqueueWriteBuffer buffer_keys)
>>> OpenCL error (CL_INVALID_CONTEXT) in file (rar_fmt.c) at line (356) -
>>> (Error Unmapping aes_key)
>>
>
> hello,
> this happens only when you do a -test .
> this is well known and it'is due to some uninitialization problem during
> the test cycle.
> if you do
> ./john -fo:ssha-opencl -test
> and
> ./john -fo:raw-md5-opencl -test
> separately it should work with no problem while we are investigating the
> issue.
Well, that's odd, but the commands you provided run fine so I'll not
worry about it. Thanks!
For any gentoo users concerned this is all in
app-crypt/johntheripper-1.7.9-r4
Keep up the great work guys.
- -Zero
>
> cheers
> Samuele
>
>
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJP9vn2AAoJEKXdFCfdEflKm+QP/0ZjuRMuYK7JksEKfBJt6CSm
4LeodM83ZrXMCsRCcLopr49NiTSZAsl4ZlHZTELVoxfr6+H926Bx+MtYNVOPmf+Q
QEPv0wlv4CeWM9SF1ZUbFrMUrCkYlSoUN+z+agfOoou2exIzroVfBwLyFveT+PuU
njMi1RJIj5R7EKkyNibRqi/nbEKYkkS51Ns1rt895ScJkggDuCVxjlSJv6edhZzO
iMoPoj2q7QNGbLqYKJOIuZPswUxhXr8k70LnDRiT4aDUNx0uOX2HkZ6PpGg7fZp3
bI+ZJWPFSiOeZ3trpJJ2XU/QYcNJTpWKQyVzmBUHw5IeQn7bGfTwqzR/+CbaMQ91
pcj0YInNoKiL2vHXIqxOBV0D+Kpi7eVQB3wTU7652Yo8dlvmS6GcNp5I+yL95Cvr
dG6Nl/Lw7yZdD8y4ihqNmj3VCKud0cle9gJSBWNnzc7bYTpWSwb18+crc+vSblx5
dpyQXsiVU6bsavDKf10hWbo3yVw7ehXbXEPdmvkke7uu3ZT7gwziLoterxxCKfuX
np8FdtrpHjRyFMJQp4jDmZ4MZfFnxNTq6JlL5aQhlSLHzIvb2xizDjYHdQEy4pTa
9zVpD3b6wZriqe0aCzP8aFKmmkqfbPBO6qc0o6DVpwH7vJWWjIWd/H4FuiylWYfy
4KdU/lxRvOnaJwFzkSTk
=KBHJ
-----END PGP SIGNATURE-----
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
