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


> On May 28, 2017, at 12:09 PM, magnum <> wrote:
>> On 2017-05-26 16:15, B B wrote:
>> 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.
> Note that the speed shown in status output is the average from the very start of job (ie. complete run-time since original start of job - not just this resume session) so if you run at some poor speed for several hours and then resume with much better speed, it won't show in the status until run long enough to change the average. I think that's what confusing you.
> magnum
Oh probably so, lost a couple days on the restart then.

Thanks for the help!

I will look for the split kernel improvement on the github mailing list.


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.