Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 29 Feb 2012 00:19:06 +0100
From: Samuele Giovanni Tonon <samu@...uxasylum.net>
To: john-dev@...ts.openwall.com
Subject: Re: Re: OpenCL errors

On 02/28/12 23:48, Claudio André wrote:
> Hi, below (and attached) more information.
> 
> The error only happens while testing with ./john --test or ./john --test=0.
> 
> It works fine if i test only one format.
> - ./john -test -fo:raw-sha1-opencl or ./john -test=0 -fo:raw-sha1-opencl

this is good: seems a problem related to the fact that when doing
multiple test there's no "destructor" of the previous format.

> Catalyst: 11.11, driver: 8.911, more detais on the image.

oh this is strange: i thought amd sdk 2.6 only worked with 12.1, maybe
this is why you are not getting the sem_wait problem.

does this happens when using sdk 2.5 ? supposing you are using
the one from amd and just untarring it should not be a problem, if you
could try it would be great however i don't want to mess your notebook
so feel free to not do that if you are not confident you can go back to
2.6.


Cheers
Samuele


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.