I'm having a problem with dynamic intensity with 2.7.1 on Windows XP:
When I start cgminer with dynamic intensity it generally operates around intensity 3 or 4 depending on what I'm doing on the PC. Last night I changed the intensity from dynamic to 8 (by typing "g, i, 8" in cgminer) and found the PC almost unresponsive this morning with an intensity of 13. I expected it to still be at 8.
Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 511. (Read 5806088 times)
August 22, 2012, 05:13:45 AM
August 22, 2012, 05:08:50 AM
2GB of system RAM, and is running flags " -g 1 -v 1 -w 256 -I 10 " i run two HD7950
August 22, 2012, 04:49:53 AM
winsows 7 x64
driver 12.8
SDK 2.7
cgminer 2.7.1
after few hours run appear error :
Most unusual. That is a fatal error because there are too many threads running or the system has run out of ram. This bug falls into the "I have no idea" category. driver 12.8
SDK 2.7
cgminer 2.7.1
after few hours run appear error :
Code:
[2012-08-22 08:41:14] Failed to create get_work_thread
August 22, 2012, 03:22:48 AM
winsows 7 x64
driver 12.8
SDK 2.7
cgminer 2.7.1
after few hours run appear error :
and cgminer crash.
i will go back to 2.7.0
driver 12.8
SDK 2.7
cgminer 2.7.1
after few hours run appear error :
Code:
[2012-08-22 08:39:59] Accepted 43ccdc0e.9f4a0881 GPU 1 pool 0
[2012-08-22 08:40:02] Accepted 56eb716f.b4d7f8c4 GPU 1 pool 0
[2012-08-22 08:40:04] Accepted 9f5505de.e0a3aeb7 GPU 1 pool 0
[2012-08-22 08:40:14] Pool 0 not providing work fast enough
[2012-08-22 08:40:51] Pool 0 communication failure, caching submissions
[2012-08-22 08:40:51] Share became stale while retrying submit, discarding
[2012-08-22 08:40:56] Share became stale while retrying submit, discarding
[2012-08-22 08:41:00] Share became stale while retrying submit, discarding
[2012-08-22 08:41:14] Pool 0 http://pool.ABCPool.co:8332 not responding!
[2012-08-22 08:41:14] Switching to http://mine3.btcguild.com:8332
[2012-08-22 08:41:14] Long-polling activated for http://mine3.btcguild.com:8332/LP/
[2012-08-22 08:41:14] Failed to create get_work_thread
[2012-08-22 08:41:14]
Summary of runtime statistics:
[2012-08-22 08:41:14] Started at [2012-08-21 21:21:42]
[2012-08-22 08:41:14] Runtime: 11 hrs : 19 mins : 29 secs
[2012-08-22 08:41:14] Average hashrate: 1146.9 Megahash/s
[2012-08-22 08:41:14] Solved blocks: 0
[2012-08-22 08:41:14] Queued work requests: 11182
[2012-08-22 08:41:14] Share submissions: 10516
[2012-08-22 08:41:14] Accepted shares: 10480
[2012-08-22 08:41:14] Rejected shares: 36
[2012-08-22 08:41:14] Reject ratio: 0.3%
[2012-08-22 08:41:14] Hardware errors: 0
[2012-08-22 08:41:14] Efficiency (accepted / queued): 94%
[2012-08-22 08:41:14] Utility (accepted shares / min): 15.42/min
[2012-08-22 08:41:14] Work Utility (diff1 shares solved / min): 15.48/min
[2012-08-22 08:41:14] Discarded work due to new blocks: 156
[2012-08-22 08:41:14] Stale submissions discarded due to new blocks: 3
[2012-08-22 08:41:14] Unable to get work from server occasions: 78
[2012-08-22 08:41:14] Work items generated locally: 0
[2012-08-22 08:41:14] Submitting work remotely delay occasions: 1
[2012-08-22 08:41:14] New blocks detected on network: 65
[2012-08-22 08:41:14] Pool: http://pool.ABCPool.co:8332
[2012-08-22 08:41:14] Queued work requests: 11180
[2012-08-22 08:41:14] Share submissions: 10516
[2012-08-22 08:41:14] Accepted shares: 10480
[2012-08-22 08:41:14] Rejected shares: 36
[2012-08-22 08:41:14] Reject ratio: 0.3%
[2012-08-22 08:41:14] Efficiency (accepted / queued): 94%
[2012-08-22 08:41:14] Discarded work due to new blocks: 154
[2012-08-22 08:41:14] Stale submissions discarded due to new blocks: 3
[2012-08-22 08:41:14] Unable to get work from server occasions: 78
[2012-08-22 08:41:14] Submitting work remotely delay occasions: 1
[2012-08-22 08:41:14] Pool: http://mine3.btcguild.com:8332
[2012-08-22 08:41:14] Queued work requests: 1
[2012-08-22 08:41:14] Share submissions: 0
[2012-08-22 08:41:14] Accepted shares: 0
[2012-08-22 08:41:14] Rejected shares: 0
[2012-08-22 08:41:14] Efficiency (accepted / queued): 0%
[2012-08-22 08:41:14] Discarded work due to new blocks: 1
[2012-08-22 08:41:14] Stale submissions discarded due to new blocks: 0
[2012-08-22 08:41:14] Unable to get work from server occasions: 0
[2012-08-22 08:41:14] Submitting work remotely delay occasions: 0
[2012-08-22 08:41:14] Pool: http://pit.deepbit.net:8332
[2012-08-22 08:41:14] Queued work requests: 1
[2012-08-22 08:41:14] Share submissions: 0
[2012-08-22 08:41:14] Accepted shares: 0
[2012-08-22 08:41:14] Rejected shares: 0
[2012-08-22 08:41:14] Efficiency (accepted / queued): 0%
[2012-08-22 08:41:14] Discarded work due to new blocks: 1
[2012-08-22 08:41:14] Stale submissions discarded due to new blocks: 0
[2012-08-22 08:41:14] Unable to get work from server occasions: 0
[2012-08-22 08:41:14] Submitting work remotely delay occasions: 0
[2012-08-22 08:41:14] Summary of per device statistics:
[2012-08-22 08:41:14] GPU0 | (5s):551.9 (avg):547.8 Mh/s | A:5049 R:15 HW:0 U:7.4/m I:10
[2012-08-22 08:41:14] GPU1 | (5s):602.9 (avg):599.1 Mh/s | A:5431 R:21 HW:0 U:8.0/m I:10
[2012-08-22 08:41:14] Failed to tq_push in queue_request
[2012-08-22 08:41:14] Failed to tq_push in queue_request
[2012-08-22 08:41:14] Failed to tq_push in queue_request
[2012-08-22 08:41:14] API failed (Socket Error: (10004) Interrupted system call) - API will not be available
[2012-08-22 08:41:14] Failed to tq_push in queue_request
[2012-08-22 08:41:14] Failed to tq_push in queue_request
[2012-08-22 08:41:14] Failed to tq_push in queue_request
[2012-08-22 08:41:14] Failed to tq_push in queue_request
[2012-08-22 08:41:14] Failed to tq_push in queue_request
[2012-08-22 08:41:14] Failed to tq_push in queue_request
[2012-08-22 08:41:14] Failed to tq_push in queue_request
[2012-08-22 08:41:14] Failed to tq_push in queue_request
[2012-08-22 08:41:14] Failed to tq_push in queue_request
[2012-08-22 08:41:14] Failed to tq_push in queue_request
[2012-08-22 08:41:14] Failed to tq_push in queue_request
[2012-08-22 08:41:14] Failed to tq_push in queue_request
[2012-08-22 08:41:14] Failed to tq_push in queue_request
[2012-08-22 08:41:14] Failed to tq_push in queue_request
[2012-08-22 08:41:14] Failed to tq_push in queue_request
and cgminer crash.
i will go back to 2.7.0
August 22, 2012, 02:43:59 AM
Failover only: does this override the default setting which is failover using backup pools when primary pool is lagging?
in other words if i use this parameter will it stay on one pool even if the pool is slow and not accepting shares at my full speed hashrate i could be sending them?
and default it would utilize another pool for some shares that the first pool isn't fast enough to select?
Yep, pretty much. in other words if i use this parameter will it stay on one pool even if the pool is slow and not accepting shares at my full speed hashrate i could be sending them?
and default it would utilize another pool for some shares that the first pool isn't fast enough to select?
August 22, 2012, 02:34:00 AM
Failover only: does this override the default setting which is failover using backup pools when primary pool is lagging?
in other words if i use this parameter will it stay on one pool even if the pool is slow and not accepting shares at my full speed hashrate i could be sending them?
and default it would utilize another pool for some shares that the first pool isn't fast enough to select?
in other words if i use this parameter will it stay on one pool even if the pool is slow and not accepting shares at my full speed hashrate i could be sending them?
and default it would utilize another pool for some shares that the first pool isn't fast enough to select?
August 21, 2012, 10:53:39 PM
My bonuspool account went apeshit exactly like that for a little while a few hours ago. I switched a couple parts around in my rigs so I wasn't sure if it was a hardware issue, but it seems to have gone away.
I don't think it's bonuspool. The common element was that we both had a pool go down. I use Eclipse and mtred, and when Eclipse went down this morning, I manually added mtred because it wasn't in the config at the time. Later on, I realized Eclipse had come up and was up for awhile, but the miner was doing -exactly- what Morblias was saying: except that I switched it myself, and it was failing to switch back. Actually, I didn't even switch it - I just added mtred manually while it was running, and it went over to mtred on it's own. Of course at first I expected the errors it was giving... because the pool was down. I even checked using ping.eu's port checker function and 8337 on eclipse was closed for all Eclipse servers. Later on when I knew the pool was up, the miner was doing exactly the same thing. Sitting on mtred, and saying Eclipse was down. I even checked again with ping.eu to make sure, and indeed Eclipse was up. So I just closed the miner, repoened it, and voila, connection to Eclipse.
I think this is pretty solid evidence
August 21, 2012, 10:28:52 PM
I can confirm this. At first I thought it was because I manually added a pool while cgminer was running and that messed it up, but now he's posting a similar issue. Did you add a pool like me or did it switch and fail to switch back on its own Morblias?
It switched and failed to switch back.
I will check with Clipse tomorrow to see if he was having any problems with the pool. I noticed it is having communication problems a lot with 2.7.1 and I am not convinced yet it is the pools, but who knows, maybe it is.
I will keep you posted what I find tomorrow. Thanks again for all your hard work ckolivas.
My bonuspool account went apeshit exactly like that for a little while a few hours ago. I switched a couple parts around in my rigs so I wasn't sure if it was a hardware issue, but it seems to have gone away.
August 21, 2012, 09:47:25 PM
I can confirm this. At first I thought it was because I manually added a pool while cgminer was running and that messed it up, but now he's posting a similar issue. Did you add a pool like me or did it switch and fail to switch back on its own Morblias?
It switched and failed to switch back.
I will check with Clipse tomorrow to see if he was having any problems with the pool. I noticed it is having communication problems a lot with 2.7.1 and I am not convinced yet it is the pools, but who knows, maybe it is.
I will keep you posted what I find tomorrow. Thanks again for all your hard work ckolivas.
August 21, 2012, 06:45:20 PM
I am most certainly not going to give one more second's thought to scrypt.
Don't mean to make you think of it, but, what the heck is "scrypt" anyway?
Sam
August 21, 2012, 06:39:54 PM
I am most certainly not going to give one more second's thought to scrypt.
Don't mean to make you think of it, but, what the heck is "scrypt" anyway?
Sam
August 21, 2012, 06:15:06 PM
Hi,
Big problems with my miner. I have been mining 2-3 months, but I had to make fresh install of my backup computer. All steps and logs are here:
https://bitcointalksearch.org/topic/cgminer-does-nothing-101758
Please, someone? RCP calls and job curls are missing... I have spotted the part in cgminer.c code, but so far I have not added own debugging messages while I hope someone knows what is wrong.
Absolutely no idea unless the 32 bit version of ubuntu you installed happened to have a broken curl library. Big problems with my miner. I have been mining 2-3 months, but I had to make fresh install of my backup computer. All steps and logs are here:
https://bitcointalksearch.org/topic/cgminer-does-nothing-101758
Please, someone? RCP calls and job curls are missing... I have spotted the part in cgminer.c code, but so far I have not added own debugging messages while I hope someone knows what is wrong.
August 21, 2012, 06:12:07 PM
just to see what kind of hashrate I would get with my 5830.
~256kh/s running at 870,1170, worksize 256, thread-concurrency 6720, vectors 4, gpu-threads 2, intensity 18 or should be if it is anything like the ones I have. Oh and it takes ~170w per card for LTC as opposed to 140w for BTC running at 1.1 volts core.
August 21, 2012, 06:10:03 PM
New version - 2.7.1, 21st August 2012
Something odd :I have 6 mining rigs. 4 have multiple cards, 2 have a single card with a total of 21 cards. Until 2.7.1, I've had next to zero hardware errors reported by cgminer, only one card in the 21 had occasional (maybe 1/day) errors, it was a 5870 in a 5-card rig.
With 2.7.1, I've got hardware errors reported on all cards in the rigs with multiple cards (in fact 18 out of 19 cards have errors). The cards in a single-card rig don't have errors reported (even a 5970 with its 2 GPUs, so if it may be linked to the number of cards, it's not with the number of GPUs).
Could something have prevented errors to be reported with previous versions ?
Some additional, maybe related information :
I had hardware errors on a 7970 when I used 2 threads on it, switching everything to dynamic with a 250ms target made these errors disappear (with no noticeable difference in hashrate).
All the cards are overclocked/downvolted/... but are set in a configuration which is(/was ?) known to be stable (ie: each time a card is SICK/DEAD or crashes cgminer it is downclocked), it's only when a new card is added that a rig can be temporarily unstable the time I find its sweet spot.
Note that I detect card making cgminer crash by monitoring their temperature: on my configuration a card was most of the time not detected SICK (I suspect it as something to do with my using the API to monitor the rigs: it seemed to crash cgminer before the 60s SICK delay) but crashed cgminer, before each crash I could witness the temperature of the offending card dropped markedly.
August 21, 2012, 05:53:39 PM
So I tried to use scrypt on cgminer 2.7.1 just to see what kind of hashrate I would get with my 5830. This is the command I ran:
Needs sdk 2.6+ August 21, 2012, 05:44:12 PM
Hopefully the dynamic mode for GPUs is fixed on windows.
What about on Linux? I've been noticing the -10 bug pop up since I upgraded to 2.7 last night. I've had to start just manually switching my intensity from 4 to 6. August 21, 2012, 05:41:26 PM
I can confirm this. At first I thought it was because I manually added a pool while cgminer was running and that messed it up, but now he's posting a similar issue. Did you add a pool like me or did it switch and fail to switch back on its own Morblias?
It switched and failed to switch back.
August 21, 2012, 05:39:46 PM
Other vector sizes have been tried. They suck.
They've been tried with scrypt you say? Because, with scrypt, a lot of the overhead is shifted to the loading and unloading of data. And I recall having 8 vectors working for me better than 4 with the VLIW5 based GPU as long as the code could be written to support it.Instead of just one uint8, we have two uint4 variables that have to load back and forth. Now, it might just be me, but that seems rather inefficient doing that many reads and writes.
If someone would give it a try, I think we could determine it once and for all.
August 21, 2012, 04:13:21 PM
I can confirm this. At first I thought it was because I manually added a pool while cgminer was running and that messed it up, but now he's posting a similar issue. Did you add a pool like me or did it switch and fail to switch back on its own Morblias?
It switched and failed to switch back.
August 21, 2012, 04:12:09 PM
When I went to 2.7.1, at some point one of my cgminers switched pools, and then would not switch back:
http://i.imgur.com/6PKRn.jpg
Bonuspool is definitely up and the cgminer on the right is connected to it, but on the left, it keeps saying it is online, won't switch to it, stays on pool 1, then says pool 0 is not responding (even though it isn't offline).
http://i.imgur.com/6PKRn.jpg
Bonuspool is definitely up and the cgminer on the right is connected to it, but on the left, it keeps saying it is online, won't switch to it, stays on pool 1, then says pool 0 is not responding (even though it isn't offline).
I can confirm this. At first I thought it was because I manually added a pool while cgminer was running and that messed it up, but now he's posting a similar issue. Did you add a pool like me or did it switch and fail to switch back on its own Morblias?
Jump to: