What does "git describe" show? There was a bugfix recently for this very issue.
Just checking over past 2 hours with fresh build of
Code:
v1.0-5442-g7645686
Will report back if problem still occurs. Thanks for feedback.
Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 185. (Read 5805670 times)
November 04, 2013, 03:32:27 AM
Just checking over past 2 hours with fresh build of
Will report back if problem still occurs. Thanks for feedback.
November 04, 2013, 03:00:25 AM
I started operating a larger number of bitburner Furys over the weekend (48 boards x 16 chips) and am constantly running into some hang condition with latest cgminer (git master). After some hours of operation mining stops and cgminer obviously is blocked in an infinite loop.
The related output is:
And there it remains until I quit and restart cgminer, where mining starts immediately again.
From the source code I see the hang occurs in the first while-loop in hash_pop(), but I don't quite understand why this happens. Any suggestions how to track down the problem? Thanks.
What does "git describe" show? There was a bugfix recently for this very issue. The related output is:
Code:
[2013-11-03 02:39:26] Waiting for work to be available from pools.
And there it remains until I quit and restart cgminer, where mining starts immediately again.
From the source code I see the hang occurs in the first while-loop in hash_pop(), but I don't quite understand why this happens. Any suggestions how to track down the problem? Thanks.
November 04, 2013, 02:52:02 AM
I started operating a larger number of bitburner Furys over the weekend (48 boards x 16 chips) and am constantly running into some hang condition with latest cgminer (git master). After some hours of operation mining stops and cgminer obviously is blocked in an infinite loop.
The related output is:
And there it remains until I quit and restart cgminer, where mining starts immediately again.
From the source code I see the hang occurs in the first while-loop in hash_pop(), but I don't quite understand why this happens. Any suggestions how to track down the problem? Thanks.
The related output is:
Code:
[2013-11-03 02:39:15] Accepted 3f0e2f2a Diff 1.04K/1024 BBF 2 pool 0
[2013-11-03 02:39:16] Network diff set to 391M
[2013-11-03 02:39:16] New block detected on network before longpoll
[2013-11-03 02:39:16] Stratum from pool 0 requested work restart
[2013-11-03 02:39:17] BBF3: Idled 1 miners
[2013-11-03 02:39:17] BBF1: Idled 1 miners
[2013-11-03 02:39:18] BBF2: Idled 1 miners
[2013-11-03 02:39:18] BBF4: Idled 1 miners
[2013-11-03 02:39:18] BBF0: Idled 1 miners
[2013-11-03 02:39:19] BBF5: Idled 1 miners
[2013-11-03 02:39:26] Waiting for work to be available from pools.
And there it remains until I quit and restart cgminer, where mining starts immediately again.
From the source code I see the hang occurs in the first while-loop in hash_pop(), but I don't quite understand why this happens. Any suggestions how to track down the problem? Thanks.
November 04, 2013, 12:56:06 AM
Skip that and go straight to
http://ck.kolivas.org/apps/cgminer/temp/cgminer-lmfao.exe
I'm getting itchy here with too much accumulated for a new release, so consider lmfao as the release candidate.
EDIT: Never mind, v3.7.0 is out which is basically the same as lmfao. Just try that one.
http://ck.kolivas.org/apps/cgminer/temp/cgminer-lmfao.exe
I'm getting itchy here with too much accumulated for a new release, so consider lmfao as the release candidate.
EDIT: Never mind, v3.7.0 is out which is basically the same as lmfao. Just try that one.
November 03, 2013, 09:37:27 PM
Four hours into the lol test and looking good - no issues. I'll keep it going unattended for another 11 hours or so now if possible.
Edit: the lol test ran 14 hours, mainly unattended. Somewhere along the way AMU6 went zombie but it was the only problem flagged. I see 3.7.0 is out so I'll go straight to it next. I'm very impressed at the amount of work you put into keeping cgminer current, ckolivas - that changelog is amazing for a "spare time" project. Thank you!
Edit: the lol test ran 14 hours, mainly unattended. Somewhere along the way AMU6 went zombie but it was the only problem flagged. I see 3.7.0 is out so I'll go straight to it next. I'm very impressed at the amount of work you put into keeping cgminer current, ckolivas - that changelog is amazing for a "spare time" project. Thank you!
November 03, 2013, 08:33:14 PM
OK, so I'm stopping "gtfo" after just over 7 hours running with just the one previously-reported zombie in my last "Edit."
Logfile (without --debug) here, if you need it:
https://dl.dropboxusercontent.com/u/44240170/logfile-gtfo.txt
Starting cgminer-ftw and leaving to run overnight....
Ah. NOT!!! Two AMU LEDS on solid, then one has gone out, but the other is reported as zombie.
Think I'll go back to "gtfo" for the night...
Logfile for "ftw" here:
https://dl.dropboxusercontent.com/u/44240170/logfile-ftw.txt
Tomorrow then... :/
Yep that confirms my suspicions then, thanks. Looks like LOL it is.Logfile (without --debug) here, if you need it:
https://dl.dropboxusercontent.com/u/44240170/logfile-gtfo.txt
Starting cgminer-ftw and leaving to run overnight....
Ah. NOT!!! Two AMU LEDS on solid, then one has gone out, but the other is reported as zombie.
Think I'll go back to "gtfo" for the night...
Logfile for "ftw" here:
https://dl.dropboxusercontent.com/u/44240170/logfile-ftw.txt
Tomorrow then... :/
https://dl.dropboxusercontent.com/u/44240170/logfile-gtfo2.txt
Back to 3.5.1 for the night and I'll try "lol" tomorrow when I can keep an eye on it :/
http://ck.kolivas.org/apps/cgminer/temp/cgminer-rofl.exe
November 03, 2013, 07:18:36 PM
OK, so I'm stopping "gtfo" after just over 7 hours running with just the one previously-reported zombie in my last "Edit."
Logfile (without --debug) here, if you need it:
https://dl.dropboxusercontent.com/u/44240170/logfile-gtfo.txt
Starting cgminer-ftw and leaving to run overnight....
Ah. NOT!!! Two AMU LEDS on solid, then one has gone out, but the other is reported as zombie.
Think I'll go back to "gtfo" for the night...
Logfile for "ftw" here:
https://dl.dropboxusercontent.com/u/44240170/logfile-ftw.txt
Tomorrow then... :/
Yep that confirms my suspicions then, thanks. Looks like LOL it is.Logfile (without --debug) here, if you need it:
https://dl.dropboxusercontent.com/u/44240170/logfile-gtfo.txt
Starting cgminer-ftw and leaving to run overnight....
Ah. NOT!!! Two AMU LEDS on solid, then one has gone out, but the other is reported as zombie.
Think I'll go back to "gtfo" for the night...
Logfile for "ftw" here:
https://dl.dropboxusercontent.com/u/44240170/logfile-ftw.txt
Tomorrow then... :/
https://dl.dropboxusercontent.com/u/44240170/logfile-gtfo2.txt
Back to 3.5.1 for the night and I'll try "lol" tomorrow when I can keep an eye on it :/
November 03, 2013, 07:12:09 PM
OK, so I'm stopping "gtfo" after just over 7 hours running with just the one previously-reported zombie in my last "Edit."
Logfile (without --debug) here, if you need it:
https://dl.dropboxusercontent.com/u/44240170/logfile-gtfo.txt
Starting cgminer-ftw and leaving to run overnight....
Ah. NOT!!! Two AMU LEDS on solid, then one has gone out, but the other is reported as zombie.
Think I'll go back to "gtfo" for the night...
Logfile for "ftw" here:
https://dl.dropboxusercontent.com/u/44240170/logfile-ftw.txt
Tomorrow then... :/
Yep that confirms my suspicions then, thanks. Looks like LOL it is. Logfile (without --debug) here, if you need it:
https://dl.dropboxusercontent.com/u/44240170/logfile-gtfo.txt
Starting cgminer-ftw and leaving to run overnight....
Ah. NOT!!! Two AMU LEDS on solid, then one has gone out, but the other is reported as zombie.
Think I'll go back to "gtfo" for the night...
Logfile for "ftw" here:
https://dl.dropboxusercontent.com/u/44240170/logfile-ftw.txt
Tomorrow then... :/
November 03, 2013, 06:05:56 PM
OK, so I'm stopping "gtfo" after just over 7 hours running with just the one previously-reported zombie in my last "Edit."
Logfile (without --debug) here, if you need it:
https://dl.dropboxusercontent.com/u/44240170/logfile-gtfo.txt
Starting cgminer-ftw and leaving to run overnight....
Ah. NOT!!! Two AMU LEDS on solid, then one has gone out, but the other is reported as zombie.
Think I'll go back to "gtfo" for the night...
Logfile for "ftw" here:
https://dl.dropboxusercontent.com/u/44240170/logfile-ftw.txt
Tomorrow then... :/
Logfile (without --debug) here, if you need it:
https://dl.dropboxusercontent.com/u/44240170/logfile-gtfo.txt
Starting cgminer-ftw and leaving to run overnight....
Ah. NOT!!! Two AMU LEDS on solid, then one has gone out, but the other is reported as zombie.
Think I'll go back to "gtfo" for the night...
Logfile for "ftw" here:
https://dl.dropboxusercontent.com/u/44240170/logfile-ftw.txt
Tomorrow then... :/
November 03, 2013, 05:01:12 PM
Here's the real next test one:
http://ck.kolivas.org/apps/cgminer/debug/cgminer-gtfo.exe
EDIT: Followed by:
http://ck.kolivas.org/apps/cgminer/temp/cgminer-lol.exe
http://ck.kolivas.org/apps/cgminer/debug/cgminer-gtfo.exe
EDIT: Followed by:
http://ck.kolivas.org/apps/cgminer/temp/cgminer-lol.exe
Running "gtfo" now. Random LEDs are coming on for a longish while (10+ seconds?). Just had four on at once but no failures yet.
I know I'm tempting fate with this update, but I've been running "gtfo" (great name!) for 2 hours now and no zombies or other strange behaviour noted. I'll leave it and check again after a few more hours.
Me too, 6.3 hours and counting, "gtfo" is the best candidate yet, it seems. We may not get to find out what "lol" is about, lol.
However this one undoes one change that I really didn't want to do. Can you please see if this makes things worse again?
http://ck.kolivas.org/apps/cgminer/temp/cgminer-ftw.exe
OK, I'm reluctantly stopping the gtfo test after 10 hours error-free to give ftw a try - such an optimistic name deserves a chance too.
Edit: 15 minutes in to the ftw test AMU 5 has gone to zero hash rate and its LED is staying on. I'll try the lol test now.
November 03, 2013, 04:34:00 PM
Actually LOL builds on GTFO so it shouldn't be any worse (better in fact).
(I appreciate your naming conventions more than you know. re: LOL, WTF, GTFO... Very funny)
November 03, 2013, 04:17:58 PM
upgraded from 3.6.2 to 3.6.6 two days ago, and have twice run into a new issue.
(5) different machines running 3.6.6 at (3) different physical locations, different carriers.
each miner set up for (6) pool entries, (3) btcguild, (2) eligius, (1) deepbit, set to "failover" mode.
I've now had (2) of them completely stall, no new work.
At that point ALL work in/out of cgminer stops..I get idle miner notifications from btcguild, but it doesn't fail down to eligius or deepbit.
For now I'm going back to 3.6.2, but wanted you to know I'd seen something new. I'm sorry I don't have better logs.
No I have not had this reported. There are some issues with pools that use round robin DNS and stratum and possibly you have run into that. There is nothing really different in 3.6.6 versus 3.6.2 if I recall correctly that might have made this come up so if you may well have the same issue with 3.6.2. I've made some changes to the upcoming code that hopefully will help this but a new release is not due out just yet while I keep bashing my head against the AMU wall.(5) different machines running 3.6.6 at (3) different physical locations, different carriers.
each miner set up for (6) pool entries, (3) btcguild, (2) eligius, (1) deepbit, set to "failover" mode.
I've now had (2) of them completely stall, no new work.
At that point ALL work in/out of cgminer stops..I get idle miner notifications from btcguild, but it doesn't fail down to eligius or deepbit.
For now I'm going back to 3.6.2, but wanted you to know I'd seen something new. I'm sorry I don't have better logs.
November 03, 2013, 04:13:39 PM
Here's the real next test one:
http://ck.kolivas.org/apps/cgminer/debug/cgminer-gtfo.exe
EDIT: Followed by:
http://ck.kolivas.org/apps/cgminer/temp/cgminer-lol.exe
http://ck.kolivas.org/apps/cgminer/debug/cgminer-gtfo.exe
EDIT: Followed by:
http://ck.kolivas.org/apps/cgminer/temp/cgminer-lol.exe
Running "gtfo" now. Random LEDs are coming on for a longish while (10+ seconds?). Just had four on at once but no failures yet.
I know I'm tempting fate with this update, but I've been running "gtfo" (great name!) for 2 hours now and no zombies or other strange behaviour noted. I'll leave it and check again after a few more hours.
Me too, 6.3 hours and counting, "gtfo" is the best candidate yet, it seems. We may not get to find out what "lol" is about, lol.
However this one undoes one change that I really didn't want to do. Can you please see if this makes things worse again?
http://ck.kolivas.org/apps/cgminer/temp/cgminer-ftw.exe
November 03, 2013, 03:33:32 PM
ckolivas
it is normal for 3.6.6-1?
in other versions there is no such
This is not a solo. So on any script coins. Not only at me.
3.6.4 works fine
Yeah I probably screwed that up for $scryptcoins when I fixed it for bitcoin.it is normal for 3.6.6-1?
in other versions there is no such
This is not a solo. So on any script coins. Not only at me.
3.6.4 works fine
I thought I'd confirm this, as more and more scrypt miners are getting confused.
Commits 3f6b9d67 and 36c6da8 introduce an inconsistency between share difficulty and network difficulty when cgminer is in scrypt mode. This causes many shares to be considered as blocks, even when they are not.
This doesn't seem to cause any real issue, but if you're getting annoyed by all those fake "Found block" messages, just use the stable version (tag v3.6.6).
November 03, 2013, 03:01:28 PM
Looks like my little erupters are supercharged! Woohoo!! I'm rocking!
I'll be happy to sell my 1.2Ph/s erupters for 10 BTC each. Any buyers?
ps. Past results are not guarantees of future returns.
M
Code:
cgminer version 3.6.6 - Started: [2013-11-03 10:44:15]
--------------------------------------------------------------------------------
(5s):11.14G (avg):22.93Ph/s | A:41306 R:681 HW:458 WU:166.6/m
ST: 2 SS: 0 NB: 37 LW: 84634 GF: 1 RF: 0
Connected to ggggg diff 81 with stratum as user xxxxxxxxxxx
Block: 000217b3743e8a5b... Diff:391M Started: [14:54:36] Best share: 1.24M
--------------------------------------------------------------------------------
[P]ool management [S]ettings [D]isplay options [Q]uit
AMU 0: | 335.7M/1.206Ph/s | A:1161 R: 0 HW:16 WU: 4.8/m
AMU 1: | 335.5M/336.4Mh/s | A: 929 R: 0 HW:14 WU: 4.3/m
AMU 2: | 335.4M/335.8Mh/s | A:1613 R: 91 HW:11 WU: 4.7/m
AMU 3: | 335.3M/1.206Ph/s | A: 972 R: 0 HW:12 WU: 4.7/m
AMU 4: | 335.6M/1.206Ph/s | A:1434 R: 0 HW:10 WU: 4.6/m
AMU 5: | 335.6M/1.206Ph/s | A: 701 R: 0 HW:16 WU: 4.5/m
AMU 6: | 335.5M/1.206Ph/s | A:1183 R: 0 HW:13 WU: 4.5/m
AMU 7: | 335.5M/336.1Mh/s | A:1757 R: 0 HW:21 WU: 4.8/m
AMU 8: | 335.3M/336.1Mh/s | A:1150 R: 89 HW: 9 WU: 4.7/m
AMU 9: | 335.6M/335.8Mh/s | A: 967 R: 0 HW:10 WU: 4.8/m
AMU 10: | 335.3M/1.206Ph/s | A:1316 R:111 HW: 7 WU: 4.7/m
AMU 11: | 335.3M/1.206Ph/s | A:1185 R: 0 HW:12 WU: 4.8/m
AMU 12: | 335.6M/1.206Ph/s | A:1002 R: 0 HW:12 WU: 4.6/m
AMU 13: | 335.5M/336.1Mh/s | A:1396 R: 0 HW:15 WU: 4.5/m
AMU 14: | 335.4M/335.9Mh/s | A:1942 R: 0 HW:12 WU: 4.9/m
AMU 15: | 335.7M/335.9Mh/s | A:1090 R: 0 HW:14 WU: 4.7/m
AMU 16: | 335.6M/336.2Mh/s | A:1128 R: 0 HW:22 WU: 4.7/m
AMU 17: | 337.5M/1.206Ph/s | A: 627 R: 0 HW: 8 WU: 4.6/m
AMU 18: | 335.2M/336.0Mh/s | A: 838 R: 0 HW: 9 WU: 4.8/m
AMU 19: | 335.7M/1.206Ph/s | A:1529 R: 0 HW:14 WU: 4.6/m
AMU 20: | 335.5M/336.1Mh/s | A:1160 R: 0 HW: 8 WU: 4.7/m
AMU 21: | 335.6M/1.206Ph/s | A: 979 R: 0 HW: 6 WU: 4.6/m
AMU 22: | 335.5M/1.206Ph/s | A: 987 R: 0 HW:10 WU: 4.6/m
AMU 23: | 335.4M/1.206Ph/s | A: 862 R: 0 HW: 7 WU: 4.7/m
AMU 24: | 335.2M/336.0Mh/s | A:1533 R: 69 HW:22 WU: 4.6/m
AMU 25: | 335.1M/1.206Ph/s | A:1575 R: 0 HW:23 WU: 4.6/m
AMU 26: | 335.4M/336.4Mh/s | A: 938 R: 0 HW:15 WU: 4.6/m
AMU 27: | 335.4M/1.206Ph/s | A: 983 R:237 HW: 8 WU: 4.7/m
AMU 28: | 335.7M/336.2Mh/s | A: 970 R: 0 HW:14 WU: 4.7/m
AMU 29: | 335.5M/336.8Mh/s | A:1144 R: 84 HW:10 WU: 4.4/m
AMU 30: | 335.5M/1.206Ph/s | A:1245 R: 0 HW:14 WU: 4.4/m
AMU 31: | 335.3M/1.206Ph/s | A: 759 R: 0 HW:17 WU: 4.3/m
AMU 32: | 335.7M/336.2Mh/s | A:1530 R: 0 HW:14 WU: 4.5/m
AMU 33: | 335.0M/1.206Ph/s | A: 708 R: 0 HW:11 WU: 4.5/m
AMU 34: | 335.4M/336.4Mh/s | A:1000 R: 0 HW:14 WU: 4.4/m
AMU 35: | 335.7M/1.206Ph/s | A:1013 R: 0 HW: 8 WU: 4.8/m
--------------------------------------------------------------------------------
I'll be happy to sell my 1.2Ph/s erupters for 10 BTC each. Any buyers?
ps. Past results are not guarantees of future returns.
M
November 03, 2013, 01:31:08 PM
Despite what it may look like, we are making progress.
Next:
http://ck.kolivas.org/apps/cgminer/temp/cgminer-wtf.exe
Ignore that binary, it's known broken. Here's the real next test one:Next:
http://ck.kolivas.org/apps/cgminer/debug/cgminer-gtfo.exe
EDIT: Followed by:
http://ck.kolivas.org/apps/cgminer/temp/cgminer-lol.exe
Running "gtfo" now. Random LEDs are coming on for a longish while (10+ seconds?). Just had four on at once but no failures yet.
I know I'm tempting fate with this update, but I've been running "gtfo" (great name!) for 2 hours now and no zombies or other strange behaviour noted. I'll leave it and check again after a few more hours.
Me too, 6.3 hours and counting, "gtfo" is the best candidate yet, it seems. We may not get to find out what "lol" is about, lol.
November 03, 2013, 12:31:32 PM
Despite what it may look like, we are making progress.
Next:
http://ck.kolivas.org/apps/cgminer/temp/cgminer-wtf.exe
Ignore that binary, it's known broken. Here's the real next test one:Next:
http://ck.kolivas.org/apps/cgminer/debug/cgminer-gtfo.exe
EDIT: Followed by:
http://ck.kolivas.org/apps/cgminer/temp/cgminer-lol.exe
Running "gtfo" now. Random LEDs are coming on for a longish while (10+ seconds?). Just had four on at once but no failures yet.
I know I'm tempting fate with this update, but I've been running "gtfo" (great name!) for 2 hours now and no zombies or other strange behaviour noted. I'll leave it and check again after a few more hours.
Edit: First zombie after about 5 hours, although it occurred at exactly the same time as I decided to sit down at the
PC and upload some photos to Flickr. I suppose it could be coincidence, but I wonder if it might have caused
a slight delay on the broadband which could have caused a momentary disturbance? I re-plugged the zombie
AMU 24 and it came back as AMU 34. I'm continuing to upload photos and all is apparently ok again. Strange.
November 03, 2013, 09:24:22 AM
ckolivas
it is normal for 3.6.6-1?
in other versions there is no such
This is not a solo. So on any script coins. Not only at me.
3.6.4 works fine
Yeah I probably screwed that up for $scryptcoins when I fixed it for bitcoin.it is normal for 3.6.6-1?
in other versions there is no such
This is not a solo. So on any script coins. Not only at me.
3.6.4 works fine
I thought I'd confirm this, as more and more scrypt miners are getting confused.
Commits 3f6b9d67 and 36c6da8 introduce an inconsistency between share difficulty and network difficulty when cgminer is in scrypt mode. This causes many shares to be considered as blocks, even when they are not.
This doesn't seem to cause any real issue, but if you're getting annoyed by all those fake "Found block" messages, just use the stable version (tag v3.6.6).
November 03, 2013, 07:07:07 AM
Despite what it may look like, we are making progress.
Next:
http://ck.kolivas.org/apps/cgminer/temp/cgminer-wtf.exe
Ignore that binary, it's known broken. Here's the real next test one:Next:
http://ck.kolivas.org/apps/cgminer/debug/cgminer-gtfo.exe
EDIT: Followed by:
http://ck.kolivas.org/apps/cgminer/temp/cgminer-lol.exe
Running "gtfo" now. Random LEDs are coming on for a longish while (10+ seconds?). Just had four on at once but no failures yet.
November 03, 2013, 04:33:44 AM
I tried Cudaminer but it kept crashing but thats a topic for another day. Its just strange that benchmark gets great rates but it wont run like normal. Is it normal for benchmark to run perfectly but when you step out of benchmark it goes crazy? Heck I just want to GPU mine and step away from cpuminer. I would even let someone into the box to check it out.
Benchmark is for bitcoin mining. You are failing to scrypt mine.That makes sense. Is there a way to see why scrypt mining is failing? The 9100 is the one the screen is attached to and the GeForce 8600 GT is the higher power one i want to use for gpu mining
Jump to: