Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 26 May 2017 07:15:57 -0700
From: B B <>
Subject: Re: CL_OUT_OF_RESOURCES error with --format=dmg-opencl

> On May 25, 2017, at 2:23 PM, magnum <> wrote:
> On 2017-05-25 16:49, B B wrote:
>> I have been experiencing some errors on startup, and also a decrease in p/s. Also I can no longer specify GWS on the command line as this causes an error also. Without declaring GWS I seem to have to wait out or make multiple attempts before the process proceeds without error.
> I presume you are now using a version newer than May 15 (or more specifically commit ff70033e or newer)? Did you re-configure and "make clean" prior to building? Just so we don't spend time chasing ghosts.
Yes I was, but should note I clobbered a previous version. I did check the file dates but who knows, maybe I missed something.

>> Here are the errors:
>> OpenCL CL_OUT_OF_RESOURCES error in common-opencl.c:1515 - WaitForEvents failed—this happens with or without specifying GWS
>> OpenCL CL_OUT_OF_RESOURCES error in common-opencl.c:1820 - Error creating command queue— seems to happen randomly
>> I tried using GWS to get back the performance I had before the changes, which decreased by almost a third from 728 to 500.
>> The specifying of a GWS number worked well previously.
>> I figured that you would like to know about these errors regardless.
I tried to —restore a session and got the line 1820 error with a  new installation. I specified the LWS and GWS with the restored session but for some reason it ran at 500p/s even so.  I then restarted that session (as new) and while it did not seem, or output the results, to build the kernel (where is that?) it was very very fast to get going and I also regained previous speeds of +700p/s with my Nvidia card.

> Strange, it works for me (weak laptop GPU) with or without specifying LWS and/or GWS. What if you specify both, eg. "LWS=64 GWS=4096 ./john ...", are you still getting an error? You really shouldn’t
The above successful start was with these specifications, so no error.
> .

> The real WTF here is the old bad single-call kernel, with a duration 50 times longer than what is kosher. I have plans to rewrite this format to use our newer split kernel. Maybe I'll have time to do so next week or so.
>> Thanks for your work!
>> Let me know if this should be/have been posted to GitHub
>> Bill
> Opening a new issue with the info above is probably a jolly good idea so I get a reminder of this problem.

Not sure its a problem so I will hold off.

> Thanks,
> magnum
Thanks again,

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.