Bug 74190 - scrypt doesn't do anything with bfgminer on CAYMAN
Summary: scrypt doesn't do anything with bfgminer on CAYMAN
Status: RESOLVED DUPLICATE of bug 74140
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/Gallium/r600 (show other bugs)
Version: 10.0
Hardware: All Linux (All)
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-29 15:11 UTC by Thomas Rohloff
Modified: 2014-02-24 09:05 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
R600_DEBUG=cs bfgminer 2> ~/bfgminer.txt (1.00 MB, text/plain)
2014-01-29 15:11 UTC, Thomas Rohloff
Details

Description Thomas Rohloff 2014-01-29 15:11:27 UTC
Created attachment 93006 [details]
R600_DEBUG=cs bfgminer 2> ~/bfgminer.txt

I have a Radeon HD 6950. When I try to use scrypt with bfgminer (for mining litecoins, for example) bfgminer gives the following output every minute:

 [2014-01-29 15:57:34] OCL 0: Idle for more than 60 seconds, declaring SICK!
 [2014-01-29 15:57:34] OCL 0: Attempting to restart
 [2014-01-29 15:57:34] Thread 0 still exists, killing it off
 [2014-01-29 15:57:35] Thread 0 restarted

and the minig speed is 0.00 hashes/second
Comment 1 slicksam 2014-02-23 23:59:56 UTC
This may be the same issue I reported in https://bugs.freedesktop.org/show_bug.cgi?id=74140

If you check CPU usage, you should see a thread stuck at 100% - this is apparently it trying to compile the opencl program.  I have not tried waiting a long time to see if it does eventually fire up.
Comment 2 Thomas Rohloff 2014-02-24 09:05:46 UTC
(In reply to comment #1)
> This may be the same issue I reported in
> https://bugs.freedesktop.org/show_bug.cgi?id=74140
> 
> If you check CPU usage, you should see a thread stuck at 100% - this is
> apparently it trying to compile the opencl program.  I have not tried
> waiting a long time to see if it does eventually fire up.

Yes, that seems to be it.

But there seems to be a memory leak, too. The thread eats up more and more RAM. Also after each

 [2014-02-24 10:00:47] OCL 0: Idle for more than 60 seconds, declaring SICK!
 [2014-02-24 10:00:47] OCL 0: Attempting to restart
 [2014-02-24 10:00:47] Thread 0 still exists, killing it off
 [2014-02-24 10:00:48] Thread 0 restarted

it eats +1 core (so first 100%, then after that 200%, after the next 300% and so on). This repeats till it's killed cause of no more free RAM.

Should I add this information to your bug report?

*** This bug has been marked as a duplicate of bug 74140 ***


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.