From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 72785] bfgminer --scrypt on 7xxx+
Date: Wed, 26 Nov 2014 17:07:34 +0000 [thread overview]
Message-ID: <bug-72785-502-DIssKPh5ZR@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-72785-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 2306 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=72785
--- Comment #40 from Tom Stellard <tstellar@gmail.com> ---
(In reply to Linux User from comment #38)
> > Do you have an X server running?
> I am (on one of GPUs). And I can understand X could be slow, etc and
> adjusting intensity on GPU sharing X server is well known thing to me.
>
> But I'm talking about GPU lockups. When GPU crashes due to ring stall and
> driver have to restart it, its likely something else failing? Somehow,
> attempts to run bfgminer --scrypt with high intensity often can provoke ring
> stalls.
>
> > drm.rnodes=1 to your kernel command line.
> Cool, but...
> 1) It could be nice to view output on separate monitor and graphic terminal
> looks better than just framebuffer console. At least in trial runs I would
> prefer to deal with my favorite terminal, adjusting intensity of 1st GPU a
> bit.
> 2) I do not think apps should be cause fatal GPU deadlocks, effectively
> screwing all graphics, system-wide.
>
> Though thanks for render nodes hint - sounds like it can be really valuable
> thing to try on some headless machines, etc.
>
> P.S. also there is another silly issue. If I just install Ubuntu and run
> bfgminer on multi-GPU setup within X session, it would only see 1st GPU
> (where X server running). Remaining GPUs are not detected. Fix is to either
> run bfgminer as root (extremely unsafe!!!) or create new user and make
> "video" it's primary group. The user who installs Ubuntu is a member of
> "video" group, but "video" is his secondary group, which is very common.
> Somehow, kernel seems to disregard permissions in such case and would issue
> -EPERM on certain syscall, making bfgminer unable to find GPUs except one
> used by X. Generally it means that user can't use more than 1 GPU unless he
> is either root (very dangerous!) or video is his primary group (inconvenient
> and uncommon). I believe it is a bug and I should file it? Since I fail to
> understand how average Joe would be able to use some OpenCL program in
> multi-GPU setup and get it working "by default" on all available GPUs. I
> guess I should file it as new bug? Is it kernel issue or MESA, etc?
Enabling rendernodes should make both GPUs visible.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3244 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 prev parent reply other threads:[~2014-11-26 17:07 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 12:19 [Bug 72785] New: bfgminer --scrypt on 7xxx+ bugzilla-daemon
2014-01-03 18:19 ` [Bug 72785] " bugzilla-daemon
2014-01-04 23:52 ` bugzilla-daemon
2014-01-13 17:22 ` bugzilla-daemon
2014-01-13 17:31 ` bugzilla-daemon
2014-02-14 13:59 ` bugzilla-daemon
2014-02-14 14:02 ` bugzilla-daemon
2014-02-14 14:34 ` bugzilla-daemon
2014-02-14 16:18 ` bugzilla-daemon
2014-02-14 16:40 ` bugzilla-daemon
2014-02-14 16:47 ` bugzilla-daemon
2014-02-14 17:43 ` bugzilla-daemon
2014-02-14 17:53 ` bugzilla-daemon
2014-02-14 18:52 ` bugzilla-daemon
2014-02-14 18:55 ` bugzilla-daemon
2014-02-14 19:28 ` bugzilla-daemon
2014-02-14 19:33 ` bugzilla-daemon
2014-02-14 19:56 ` bugzilla-daemon
2014-02-14 20:12 ` bugzilla-daemon
2014-02-14 20:13 ` bugzilla-daemon
2014-02-14 20:43 ` bugzilla-daemon
2014-02-14 21:07 ` bugzilla-daemon
2014-02-14 21:10 ` bugzilla-daemon
2014-02-14 21:30 ` bugzilla-daemon
2014-02-15 11:52 ` bugzilla-daemon
2014-07-11 22:52 ` bugzilla-daemon
2014-07-14 14:36 ` bugzilla-daemon
2014-07-14 15:18 ` bugzilla-daemon
2014-08-21 16:30 ` bugzilla-daemon
2014-08-21 17:20 ` bugzilla-daemon
2014-08-22 13:49 ` bugzilla-daemon
2014-08-22 13:50 ` bugzilla-daemon
2014-08-23 9:21 ` bugzilla-daemon
2014-11-02 3:08 ` bugzilla-daemon
2014-11-02 12:46 ` bugzilla-daemon
2014-11-22 4:27 ` bugzilla-daemon
2014-11-24 17:43 ` bugzilla-daemon
2014-11-24 18:14 ` bugzilla-daemon
2014-11-24 19:33 ` bugzilla-daemon
2014-11-25 2:46 ` bugzilla-daemon
2014-11-26 17:07 ` bugzilla-daemon [this message]
2017-03-22 16:03 ` [Bug 72785] bfgminer --scrypt OpenCL on Clover RadeonSI bugzilla-daemon
2017-03-22 16:03 ` bugzilla-daemon
2018-05-30 6:43 ` 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-72785-502-DIssKPh5ZR@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).