Date: Thu, 13 Jun 2019 23:15:35 +0200 From: magnum <john.magnum@...hmail.com> To: john-users@...ts.openwall.com Subject: Re: Unable to use OpenCL on arm64v8/debian stretch On 2019-06-13 22:06, Solar Designer wrote: >> On 2019-06-13 15:08, billwhittaker@...e-mail.net wrote: >>> When I run, as in README-OPENCL, >>> ../run/john --test --format=wpapsk-opencl >>> I see >>> Device 0@...i: Mali-T860 >>> Benchmarking: wpapsk-opencl, WPA/WPA2/PMF/PMKID PSK [PBKDF2-SHA1 >>> OpenCL]... OpenCL CL_INVALID_PROGRAM_EXECUTABLE (-45) error in >>> opencl_wpapsk_fmt_plug.c:262 - Error creating kernel >>> >>> What does the error mean and what can I do to eliminate it? > > On Thu, Jun 13, 2019 at 08:30:38PM +0200, magnum wrote: >> Before we even start to think about that, you need to upgrade to latest >> release, which is 1.9.0-jumbo-1. If you still have problems after that, >> please repost. > > magnum, I see no reason to think the above wasn't already with > 1.9.0-jumbo-1. In fact, the mention of "ASIMD" suggests it was with a > revision very close to 1.9.0-jumbo-1 even if not the release exactly. > (We sort of mistakenly reported Aarch64's SIMD as NEON before.) Well the *output* says "Device 0" so it's some time before the released version. I didn't notice the "ASIMD" though, so I thought it could be much older - but anyway let's change to the released version and we'll know exactly what is running. Because it does get weirder, hang on: We switched to 1-based device numbers at February 26 and to ASIMD at April 8. So that means this build is... *what*?! Older than Feb 26 *and* newer than April 8? Is this some custom backport mix? A rebuild without "make clean"? I have no idea so I'm not keen on discussing the issue until I do. The easy way to get there: Install the very release, build from scratch and re-test. Then I'll be all ears - then I'll also be able to tell what's in line 262 of opencl_wpapsk_fmt_plug.c for sure. magnum
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.