|
Message-ID: <tencent_568897C1532707FD340C76B2@qq.com> Date: Wed, 13 Jan 2016 23:53:58 +0800 From: "李怡石" <liyishi.ch@...com> To: "john-users" <john-users@...ts.openwall.com> Subject: Does JTR support R9 290x GPU. I setup a new PC with 2x R9 290x GPU. While running ./john -test , I came across core dump. I installed the drivers and SDK as below. Does anyone use the 290x GPU with JTR successfully? AMD-APP-SDKInstaller-v3.0.130.135-GA-linux64.tar fglrx_15.302-0ubuntu1_amd64_ub_14.01.deb fglrx-core_15.302-0ubuntu1_amd64_ub_14.01.deb AMD-APP-SDK-v3.0.130.135-GA-linux64.sh fglrx-amdcccle_15.302-0ubuntu1_amd64_ub_14.01.deb fglrx-dev_15.302-0ubuntu1_amd64_ub_14.01.deb Type "apropos word" to search for commands related to "word"... Reading symbols from ./john...(no debugging symbols found)...done. (gdb) set args -test -format=oldoffice-opencl (gdb) run Starting program: /workspace/john/run/john -test -format=oldoffice-opencl [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Traceback (most recent call last): File "/usr/share/gdb/auto-load/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.19-gdb.py", line 63, in <module> from libstdcxx.v6.printers import register_libstdcxx_printers ImportError: No module named 'libstdcxx' Invalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 key Program received signal SIGSEGV, Segmentation fault. 0x00007ffff7e392fb in ?? () from /usr/lib/libatiadlxx.so (gdb) bt #0 0x00007ffff7e392fb in ?? () from /usr/lib/libatiadlxx.so #1 0x00007ffff7e4c009 in ADL2_Send () from /usr/lib/libatiadlxx.so #2 0x00007ffff2ad8b41 in ?? () from /usr/lib/libamdocl64.so #3 0x00007ffff2ad908c in ?? () from /usr/lib/libamdocl64.so #4 0x00007ffff2aaa8c7 in ?? () from /usr/lib/libamdocl64.so #5 0x00007ffff2aaa91c in ?? () from /usr/lib/libamdocl64.so #6 0x00007ffff2aafc74 in ?? () from /usr/lib/libamdocl64.so #7 0x00007ffff2a997c7 in ?? () from /usr/lib/libamdocl64.so #8 0x00007ffff2792f27 in ?? () from /usr/lib/libamdocl64.so #9 0x00007ffff27d0f19 in ?? () from /usr/lib/libamdocl64.so #10 0x00007ffff27d0f77 in ?? () from /usr/lib/libamdocl64.so #11 0x00007ffff27d1ba3 in ?? () from /usr/lib/libamdocl64.so #12 0x00007ffff26f5d64 in ?? () from /usr/lib/libamdocl64.so #13 0x00007ffff26f7207 in ?? () from /usr/lib/libamdocl64.so #14 0x00007ffff26f7396 in ?? () from /usr/lib/libamdocl64.so #15 0x00007ffff26b7760 in ?? () from /usr/lib/libamdocl64.so #16 0x00007ffff26d12f7 in ?? () from /usr/lib/libamdocl64.so #17 0x00007ffff26a1e53 in clIcdGetPlatformIDsKHR () from /usr/lib/libamdocl64.so #18 0x00007ffff7326cf5 in ?? () from /usr/lib/x86_64-linux-gnu/libOpenCL.so.1 #19 0x00007ffff7dea13a in call_init (l=<optimized out>, argc=argc@...ry=3, argv=argv@...ry=0x7fffffffe548, env=env@...ry=0x7fffffffe568) at dl-init.c:78 #20 0x00007ffff7dea223 in call_init (env=<optimized out>, argv=<optimized out>, argc=<optimized out>, l=<optimized out>) at dl-init.c:36 #21 _dl_init (main_map=0x7ffff7ffe1c8, argc=3, argv=0x7fffffffe548, env=0x7fffffffe568) at dl-init.c:126 #22 0x00007ffff7ddb30a in _dl_start_user () from /lib64/ld-linux-x86-64.so.2 #23 0x0000000000000003 in ?? () #24 0x00007fffffffe794 in ?? () #25 0x00007fffffffe7ad in ?? () #26 0x00007fffffffe7b3 in ?? () #27 0x0000000000000000 in ?? ()
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.