dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 101584] clover: ethminer -G --benchmark: ring buffer overflow, GPU faults
Date: Wed, 28 Jun 2017 01:36:51 +0000	[thread overview]
Message-ID: <bug-101584-502-qAzWigr3B4@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-101584-502@http.bugs.freedesktop.org/>


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

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

--- Comment #1 from Christoph Haag <haagch@frickel.club> ---
Created attachment 132290
  --> https://bugs.freedesktop.org/attachment.cgi?id=132290&action=edit
without X

Thanks to a tip from tom stellard I tried it without X (after exiting sddm). 

I've tried to start the miner with "real work" from a pool as recommended:

GPU_FORCE_64BIT_PTR=0 GPU_MAX_HEAP_SIZE=100 GPU_USE_SYNC_OBJECTS=1
GPU_MAX_ALLOC_PERCENT=100 GPU_SINGLE_ALLOC_PERCENT=100 ./ethminer
--farm-recheck 200 -G -S eu1.ethermine.org:4444 etc. etc.

I get gpu faults, but no hangs or other issues and the system is usable
normally after exiting the miner.

The -G --benchmark mode still has worse troubles with hangs etc.

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

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

  parent reply	other threads:[~2017-06-28  1:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-25  9:21 [Bug 101584] clover: ethminer -G --benchmark: ring buffer overflow, GPU faults bugzilla-daemon
2017-06-25 16:08 ` bugzilla-daemon
2017-06-28  1:36 ` bugzilla-daemon [this message]
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-qAzWigr3B4@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).