From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 101584] clover: ethminer -G --benchmark: ring buffer overflow, GPU faults
Date: Sun, 25 Jun 2017 09:21:19 +0000 [thread overview]
Message-ID: <bug-101584-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1264 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=101584
Bug ID: 101584
Summary: clover: ethminer -G --benchmark: ring buffer overflow,
GPU faults
Product: Mesa
Version: git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: haagch@frickel.club
QA Contact: dri-devel@lists.freedesktop.org
Created attachment 132229
--> https://bugs.freedesktop.org/attachment.cgi?id=132229&action=edit
dmesg
Tested with my RX 480 on mesa git and Linux 4.11 and 4.12-rc.
To reproduce, get https://github.com/ethereum-mining/ethminer
in libethash-cl/ethash_cl_miner_kernel.cl add
#pragma OPENCL EXTENSION cl_clang_storage_class_specifiers : enable
then cmake . and make and in ethminer/ run ./ethminer -G --benchmark
it outputs some progress and at 97% something goes wrong and I get GPU faults
and/or GPU hangs.
Interestingly with the closed source OpenCL runtime from amdgpu-pro it fails at
97% too.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2793 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2017-06-25 9:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-25 9:21 bugzilla-daemon [this message]
2017-06-25 16:08 ` [Bug 101584] clover: ethminer -G --benchmark: ring buffer overflow, GPU faults bugzilla-daemon
2017-06-28 1:36 ` bugzilla-daemon
2019-09-25 17:59 ` 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-101584-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).