From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 81896] New: GPU reset when running some "John the Ripper" (+ jumbo patch, from Git) OpenCL tests
Date: Wed, 30 Jul 2014 04:36:38 +0000 [thread overview]
Message-ID: <bug-81896-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2359 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=81896
Priority: medium
Bug ID: 81896
Assignee: dri-devel@lists.freedesktop.org
Summary: GPU reset when running some "John the Ripper" (+
jumbo patch, from Git) OpenCL tests
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: lbdkmjdf@sharklasers.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: git
Component: Drivers/Gallium/r600
Product: Mesa
Created attachment 103669
--> https://bugs.freedesktop.org/attachment.cgi?id=103669&action=edit
mixed outputs
I get GPU reset when running some opencl tests from this program from TTY. If
I'm running a DE when the lockup happens, the system stops responding.
Attached are:
- the mixed output from /var/log/syslog and this command:
$ R600_DEBUG=cs LWS=128 GWS=9216 ./john --test
--format=PBKDF2-HMAC-SHA256-opencl
- an attempt to clean it, only leaving the output from "R600_DEBUG=cs"
Also notice, there is random garbage after "Build log:", which comes from
clGetProgramBuildInfo (
https://github.com/magnumripper/JohnTheRipper/blob/bleeding-jumbo/src/common-opencl.c#L754
, prints "Build log:" in line 768)
My system:
Hardware: HP dv6, CPU: AMD A6-3400M, GPUs: Radeon HD 6520g (evergreen) + 6750M
(north islands)
OS: Kubuntu 14.04
Kernel: 3.15.7, and 3.13, both amd64
Mesa 10.3~git1407290730.9a53f9 (from oibaf's PPA,
https://launchpad.net/~oibaf/+archive/graphics-drivers ), compiled with LLVM
3.5-rc1.
________________
To reproduce, here's a mini "how to run" for "John The Ripper" + "jumbo"
patches:
$ git clone https://github.com/magnumripper/JohnTheRipper
$ cd JohnTheRipper/src
$ ./configure && make
$ cd ../run
$ ./john --help # prints usage help
$ # the following command prints a list of hash format tests that use opencl,
separated by spaces. remove the awk part to get one per line:
$ ./john --help | grep -Eo '[a-zA-Z0-9-]*-opencl' | awk '{printf "%s ", $0}';
echo
To run a test:
$ ./john --test --format=$format
where $format is one of the formats listed from the previous command
The program does verify the output. When it fails, it should print something
like "FAILED (get_hash[0](0))".
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4140 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2014-07-30 4:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 4:36 bugzilla-daemon [this message]
2014-07-30 4:38 ` [Bug 81896] GPU reset when running some "John the Ripper" (+ jumbo patch, from Git) OpenCL tests bugzilla-daemon
2014-07-30 4:48 ` bugzilla-daemon
2014-07-30 4:49 ` bugzilla-daemon
2015-07-11 8:39 ` bugzilla-daemon
2017-01-27 19:09 ` bugzilla-daemon
2018-05-30 7:11 ` [Bug 81896] [clover/sumo] " bugzilla-daemon
2019-09-18 19:16 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-81896-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.