Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 23 Oct 2014 21:37:40 -0800
From: Royce Williams <>
To: john-dev <>
Subject: Re: "Failed copy data to gpu" when using fork with descrypt-opencl

On Sun, Oct 19, 2014 at 11:06 AM, magnum <> wrote:
> On 2014-10-19 18:07, Royce Williams wrote:

>> What is the recommended way to  tell 'git bisect' to ignore Makefiles
>> generated by ./configure?
> Just delete the file after building and/or check out the stub again. I'm not
> very happy with the current Makefile mess, maybe we should drop that stub.

This helped, but there's too many other factors across the commit
(compilation failures, etc.) to really zoom in properly -- at my
levels of git skill and cycles right now, anyway.  If I ignore 'Self
test failed (get_hash[0](3))' errors and bisect accordingly, I get too
many hits to be useful (as far as I can tell):

There are only 'skip'ped commits left to test.
The first bad commit could be any of:
We cannot bisect more!
bisect run cannot continue any more

I also got the following error on recent makes, but do not know if
it's relevant or not:

DES_std.c: In function ‘DES_std_set_key’:
DES_std.c:637:17: warning: array subscript is above array bounds
   while (DES_key[i++]) k += 2;

So I'm stuck on how to move past my 'Failed Copy data to gpu' error.
The consequence is that I can only use one CPU core to send candidate
passwords to descrypt-opencl.

Is anyone else seeing this?


Powered by blists - more mailing lists

Your e-mail address:

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.