I'm sorry but after this commit my --format=office2010 is again not working...
I also re-installed AMD Catalyst 12.8 and rebootet, to make sure nothing else can be the reason for failing now.
make[1]: Verlasse Verzeichnis '/home/marc/JohnTheRipper/src'
cp opencl/_.cl ../run/
cp opencl__.h ../run/
marc@nerberd:/JohnTheRipper/src$ cd ../run/
marc@nerberd:/JohnTheRipper/run$ ./john --list=opencl-devices
Platform #0 name: AMD Accelerated Parallel Processing
Platform version: OpenCL 1.2 AMD-APP (938.2)
Device #0 name: Juniper
Device vendor: Advanced Micro Devices, Inc.
Device type: GPU (LE)
Device version: OpenCL 1.2 AMD-APP (938.2)
Driver version: CAL 1.4.1741
Global Memory: 512.5 MB
Global Memory Cache: 0.0 B
Local Memory: 32.0 KB (Local)
Max memory alloc. size: 128.1 MB
Max clock (MHz) : 675
Max Work Group Size: 256
Parallel compute cores: 10
Stream processors: 800 (10 x 80)
Device #1 name: Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz
Device vendor: GenuineIntel
Device type: CPU (LE)
Device version: OpenCL 1.2 AMD-APP (938.2)
Driver version: 2.0 (sse2,avx)
Global Memory: 15.0 GB
Global Memory Cache: 32.0 KB
Local Memory: 32.0 KB (Global)
Max memory alloc. size: 3.0 GB
Max clock (MHz) : 800
Max Work Group Size: 1024
Parallel compute cores: 8
OK, I can reproduce it if forcing vectorized mode (like the Juniper uses) on the Tahiti. Try forcing scalar mode as I described on the mailing list. I bet that will work.
I still think it's a driver bug (that was randomly hidden in the previous commit). And I think disabling vectorizing will work around it, but it will have some performance penalty. I will add some way to disable vectorizing at runtime (eg. with a john.conf setting). Could you please try disabling vectorizing the way I described earlier and report the result?
Yes, I don't mind but I guess Solar would like this conversation to be on the mailing list.
Commit 5d4f156 added today might make some difference to the better although I don't really expect it to. If it actually does make the problems go away, I will have to apologize to AMD for blaming them :-P
Isn't there any way to get AMD drivers with debug info not stripped out? Using a debugger I just end up with lots of anonymous hex digits deep inside some AMD library. No clue whatsoever.
Commit 5d4f1565d4f156 today
_might_ make some difference to the better although I don't really expect
it to. If it actually does make the problems go away, I will have to
apologize to AMD for blaming them :-P
Isn't there any way to get AMD drivers with debug info not stripped out?
Using a debugger I just end up with lots of anonymous hex digits deep
inside some AMD library. No clue whatsoever.
—
Reply to this email directly or view it on GitHubhttps://github.com/magnumripper/JohnTheRipper/commit/6a3aa3c7ffa148e9a24d52039609bcb5fb444b84#commitcomment-2176761.
I haven't found any drivers with debug information.
I saw a similar error on raw-sha256 (but it wasn't running on bull, only on CPU and segfault on GPU here) and it was because i was doing some misaligned access on memory. I was using a 64 bit pointer on a 32 bit aligned data.
mbrinkmann repliedNov 15, 2012
Hey Magnum,
I'm sorry but after this commit my --format=office2010 is again not working...
I also re-installed AMD Catalyst 12.8 and rebootet, to make sure nothing else can be the reason for failing now.
make[1]: Verlasse Verzeichnis '/home/marc/JohnTheRipper/src'
cp opencl/_.cl ../run/
cp opencl__.h ../run/
marc@nerberd:
/JohnTheRipper/src$ cd ../run//JohnTheRipper/run$ ./john --list=opencl-devicesmarc@nerberd:
Platform #0 name: AMD Accelerated Parallel Processing
Platform version: OpenCL 1.2 AMD-APP (938.2)
Device #0 name: Juniper
Device vendor: Advanced Micro Devices, Inc.
Device type: GPU (LE)
Device version: OpenCL 1.2 AMD-APP (938.2)
Driver version: CAL 1.4.1741
Global Memory: 512.5 MB
Global Memory Cache: 0.0 B
Local Memory: 32.0 KB (Local)
Max memory alloc. size: 128.1 MB
Max clock (MHz) : 675
Max Work Group Size: 256
Parallel compute cores: 10
Stream processors: 800 (10 x 80)
marc@nerberd:
/JohnTheRipper/run$ ./john --test --format=office2010-opencl/JohnTheRipper/run$OpenCL platform 0: AMD Accelerated Parallel Processing, 2 device(s).
Using device 0: Juniper
Local worksize (LWS) 64, Global worksize (GWS) 4096
Benchmarking: Office 2010 SHA-1 AES (100,000 iterations) [OpenCL 4x]... Speicherzugriffsfehler (Speicherabzug geschrieben)
marc@nerberd:
magnumripper repliedNov 15, 2012
That is really odd. If anything, this commit should make things more stable. Does the office-2007 format work fine? It is nearly identical.
magnumripper repliedNov 15, 2012
OK, I can reproduce it if forcing vectorized mode (like the Juniper uses) on the Tahiti. Try forcing scalar mode as I described on the mailing list. I bet that will work.
mbrinkmann repliedNov 15, 2012
i tested the other modes, no Office-Opencl Mode is working.
http://pastebin.com/4eGPD81b
Once i created my own branch, using the version before this commit, it is working again.
PS: If you prefer the mailinglist, i can also write there ;)
magnumripper repliedNov 15, 2012
I still think it's a driver bug (that was randomly hidden in the previous commit). And I think disabling vectorizing will work around it, but it will have some performance penalty. I will add some way to disable vectorizing at runtime (eg. with a john.conf setting). Could you please try disabling vectorizing the way I described earlier and report the result?
Yes, I don't mind but I guess Solar would like this conversation to be on the mailing list.
claudioandre repliedNov 19, 2012
I tried it (i'm using Catalyst 10.10):
I'm sure it worked fine on 10.06 (and some commit in the past, probably one of these i tried above).
So, seems driver is the one to blame.
magnumripper repliedNov 19, 2012
Commit 5d4f156 added today might make some difference to the better although I don't really expect it to. If it actually does make the problems go away, I will have to apologize to AMD for blaming them :-P
Isn't there any way to get AMD drivers with debug info not stripped out? Using a debugger I just end up with lots of anonymous hex digits deep inside some AMD library. No clue whatsoever.
mbrinkmann repliedNov 19, 2012
claudioandre repliedNov 20, 2012
I haven't found any drivers with debug information.
I saw a similar error on raw-sha256 (but it wasn't running on bull, only on CPU and segfault on GPU here) and it was because i was doing some misaligned access on memory. I was using a 64 bit pointer on a 32 bit aligned data.