All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 64201] OpenCL usage result segmentation fault on r600g with HD6850.
Date: Fri, 10 May 2013 04:24:33 +0000	[thread overview]
Message-ID: <bug-64201-502-dbMKEekje2@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-64201-502@http.bugs.freedesktop.org/>


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

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

--- Comment #15 from Tom Stellard <tstellar@gmail.com> ---
(In reply to comment #8)
> (In reply to comment #7)
> > I would recommend using bfgminer for bitcoin mining.  It auto-detects the
> > mesa platform, and disabled unsupported features.  All you need to do to get
> > it to work is pass the -v1 flag.
> 
> I just want try openCL programs. Not intended to waste energy with those
> yet, until I produce my energy by solar panels...
> 
> With "bfgminer -v1 --benchmark", I think it start working first. But hey! I
> got GPU lockups which is serious bug I think! :-/
> I attached the kernel messages.
> 

I'm not sure that benchmark mode works for bfgminer.  Can you try without
--benchmark

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

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

  parent reply	other threads:[~2013-05-10  4:24 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-03 21:55 [Bug 64201] New: OpenCL usage result segmentation fault on r600g with HD6850 bugzilla-daemon
2013-05-03 22:02 ` [Bug 64201] " bugzilla-daemon
2013-05-03 22:03 ` bugzilla-daemon
2013-05-03 22:30 ` bugzilla-daemon
2013-05-03 23:02 ` bugzilla-daemon
2013-05-04  6:00 ` bugzilla-daemon
2013-05-04 12:26 ` bugzilla-daemon
2013-05-04 12:27 ` bugzilla-daemon
2013-05-04 12:36 ` bugzilla-daemon
2013-05-04 21:49 ` bugzilla-daemon
2013-05-04 23:52 ` bugzilla-daemon
2013-05-04 23:53 ` bugzilla-daemon
2013-05-05  0:18 ` bugzilla-daemon
2013-05-06 20:15 ` bugzilla-daemon
2013-05-06 20:59 ` bugzilla-daemon
2013-05-08  0:42 ` bugzilla-daemon
2013-05-10  3:16 ` bugzilla-daemon
2013-05-10  4:24 ` bugzilla-daemon [this message]
2013-05-10 13:26 ` bugzilla-daemon
2013-05-10 16:05 ` bugzilla-daemon
2013-05-10 16:07 ` bugzilla-daemon
2013-05-10 16:08 ` bugzilla-daemon
2013-05-10 16:20 ` bugzilla-daemon
2013-05-10 17:02 ` bugzilla-daemon
2013-05-10 19:39 ` bugzilla-daemon
2013-05-14 18:23 ` bugzilla-daemon
2013-05-17 17:51 ` bugzilla-daemon
2013-05-24 16:00 ` bugzilla-daemon
2013-05-24 16:08 ` bugzilla-daemon
2013-05-24 17:50 ` bugzilla-daemon
2013-05-24 18:50 ` bugzilla-daemon
2013-06-09 22:19 ` bugzilla-daemon
2013-06-09 22:41 ` bugzilla-daemon
2013-06-10 23:28 ` bugzilla-daemon
2013-06-10 23:30 ` bugzilla-daemon
2013-06-14  0:30 ` bugzilla-daemon
2013-06-28 21:30 ` bugzilla-daemon
2013-06-28 21:33 ` bugzilla-daemon
2013-06-28 21:38 ` bugzilla-daemon
2013-07-10  1:47 ` bugzilla-daemon
2013-07-12 13:21 ` bugzilla-daemon
2013-08-12  2:37 ` bugzilla-daemon
2013-08-14 17:37 ` bugzilla-daemon
2013-08-16  3:20 ` bugzilla-daemon
2013-08-16  3:45 ` bugzilla-daemon
2013-08-16  5:46 ` bugzilla-daemon
2013-09-04 17:02 ` bugzilla-daemon
2013-09-09  3:37 ` bugzilla-daemon
2013-09-09  3:39 ` bugzilla-daemon
2013-09-10 20:26 ` bugzilla-daemon
2013-09-16 20:10 ` bugzilla-daemon
2013-09-17 17:52 ` bugzilla-daemon
2013-09-17 19:06 ` bugzilla-daemon
2013-09-17 19:36 ` bugzilla-daemon
2013-09-19 20:46 ` bugzilla-daemon
2013-09-28  0:23 ` bugzilla-daemon
2013-09-28  1:53 ` bugzilla-daemon
2013-09-28  3:06 ` bugzilla-daemon
2017-01-26 19:43 ` [Bug 64201] bfgminer " bugzilla-daemon
2017-01-26 19:44 ` bugzilla-daemon
2017-03-02 20:43 ` bugzilla-daemon
2017-03-02 20:48 ` bugzilla-daemon
2017-03-22 15:41 ` 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-64201-502-dbMKEekje2@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.