|
Date: Fri, 10 Oct 2014 00:18:38 -0800 From: Royce Williams <royce@...ho.org> To: john-dev <john-dev@...ts.openwall.com> Subject: Re: "Failed copy data to gpu" when using fork with descrypt-opencl On Fri, Oct 10, 2014 at 12:05 AM, Solar Designer <solar@...nwall.com> wrote: > Thank you for reporting this. On further occasions, please direct such > postings to john-users rather than john-dev. This is essentially user > experience, and it's useful for other users to know that they may/should > use --fork for this purpose, and that it failed in this version for this > GPU type. Ah, understood -- makes sense. Will do so in the future. > On Thu, Oct 09, 2014 at 11:58:26PM -0800, Royce Williams wrote: >> When running this version of bleeding-jumbo: >> >> commit 3d8c4ea17f918130e62108be91309883c7023541 >> Merge: 379881a 53cbf8b >> Author: Dhiru Kholia <dhiru@...nwall.com> >> Date: Thu Oct 9 20:28:03 2014 +0200 >> >> ... I'm getting the following error when I try to use fork to get more >> CPU cores participating in feeding my GPU: > > Did this work for you before, on this same GPU, with older > bleeding-jumbo? Can you identify the newer version that worked? Unfortunately, it's the first time that I had a CPU in this system that had multiple cores, so I hadn't tried it before. It also fails to work on a snapshot from September 16th using the same GPU. > And yes, you're right in using --fork to speedup descrypt-opencl. > In fact, once this issue is resolved, I think you'll want to use > something like --fork=4. Thanks for the specifics. I found your general guidance about this in notes from one of the contests, but wasn't sure what value to use. Royce
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.