All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 96906] OpenCL program causes steady stream of GPU fault detected errors
Date: Tue, 12 Jul 2016 18:57:45 +0000	[thread overview]
Message-ID: <bug-96906-502-e5YNkBCC5Y@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-96906-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 635 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=96906

--- Comment #1 from Jolan Luff <jolan@jolan.org> ---
The program in question is "Claymore's Dual Ethereum+Decred/Siacoin GPU
Miner v5.0 (Windows/Linux)":

https://bitcointalk.org/index.php?topic=1433925.0

I have it running on 5 computers on 8 cards total and some single GPU setups
hit it only sporadically, I have a dual GPU system where the program is
basically unusable, but in general the program still works despite some slow
down due to thousands of errors being generated and printed.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1514 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

  reply	other threads:[~2016-07-12 18:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-12 18:56 [Bug 96906] OpenCL program causes steady stream of GPU fault detected errors bugzilla-daemon
2016-07-12 18:57 ` bugzilla-daemon [this message]
2016-07-12 18:59 ` bugzilla-daemon
2016-07-17 18:21 ` bugzilla-daemon
2016-12-28 23:16 ` bugzilla-daemon
2017-01-02 20:35 ` bugzilla-daemon
2017-01-20 13:25 ` bugzilla-daemon
2017-07-09 12:05 ` bugzilla-daemon
2018-02-04 15:11 ` bugzilla-daemon
2019-05-20  2:20 ` bugzilla-daemon
2019-11-19  7:57 ` 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-96906-502-e5YNkBCC5Y@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.