Possible CGminer Bug
We have got an intermittant internet today and we are having short periods when basically data isn't pass and we get timeouts. We have seen that in our big mining test reg, running on the same internet connection, that after such an outage that CGminer (V2.3.4) appears to stop scheduling work correctly to some or all of the stack of boards. It does continue to intermittantly schedule work and is not a total stoppage but hash rates appear to fall to less that half that expected. This does appear to be a problem that a number of rig, and in particularly the bigger ones, are reporting. Once this happens there doen't seen to be any way to recover CGminer other than a complete restart.
We have got an intermittant internet today and we are having short periods when basically data isn't pass and we get timeouts. We have seen that in our big mining test reg, running on the same internet connection, that after such an outage that CGminer (V2.3.4) appears to stop scheduling work correctly to some or all of the stack of boards. It does continue to intermittantly schedule work and is not a total stoppage but hash rates appear to fall to less that half that expected. This does appear to be a problem that a number of rig, and in particularly the bigger ones, are reporting. Once this happens there doen't seen to be any way to recover CGminer other than a complete restart.
Yohan,
you're using an "old" version of cgminer, please build one of the lastest 2.4.x or even 2.5.0 (I'm not sure 2.5.0 is as stable as 2.4.x) but 2.4.3 as a minimum version.
See also https://bitcointalksearch.org/topic/m.968533
I'm using 2.4.3 (though on linux and with not so many boards) and I've never had the problem you're reporting.
spiccioli
Ive been using Cgminer 2.5.0 for the last 3 days and have had a consistent 2.6 U on each fpga for the last 3 days without interruption. I was having a problem with 2.4.3 where my Actual Icarus unit would shut off after about 12 hours, 2.5.0 seemed to fix that as well.
It is our plan to get Cairnsmore1 adopted into the official CGminer but we want to be in something of stable position. I think we are pretty much there now. I think we should look at 2.5.0 to seeif that is better and get that looked at in the next few days. What we are trying to avoid is unnecessarily changing when other things are changing as well. The reason for that is to minimise the risks of a support nightmare of changing several things together and something going badly wrong. That's a fairly normal approach on a project like this.
The problem, or bug, we saw was by sheer luck. If you have a rock solid internet connection you would not see it the same way we did. It just happens that our local area is getting internet improvements and we have been getting short interuptions on our service. These interruptions then lead to the drop of hashing rates. We have seen this happen under the same circunstances a number of times so we are pretty sure of the association.
Secondly: seriously? ... cgminer has problems in an old version when your internet connection is shit ...
Is this supposed to be some revelation or something? Seriously? A 20pt font bitching about a bug in an old version? Seriously?
Anyway ...
What you guys did with cgminer was ONLY:
1) Take a now OLD version of it and change the Icarus Serial I/O speed to half it's value.
2) change the names it shows everywhere
(Then break the license by releasing it without source code until we complained about that)
What CGMINER does support is a proper working Icarus bitstream, which I guess I must have misread here somewhere that this was supposed to work on your hardware ...
Cgminer also includes code to support an Icarus bitstream that runs slower or faster that may or may not be perfect but I can certainly say that I have no high certainty since I've never seen any hardware from you guys (that isn't a REV3 Icarus) and don't ever expect to either
The only support I've had with that code is a few people (thanks to them) who have your board and came to the #cgminer IRC channel and I helped them configure it and got some feedback about it.
Reporting an OLD unrelated bug in your thread as an excuse to bitch about cgminer support ... that you have not bothered to do anything about ... seriously?
What's that well known comment with cgminer? RTFM!
Or in this case the NEWS file.
There have been numerous changes to cgminer since Version 2.3.4 - April 25, 2012 (the NEWS file is now 413 lines longer since then)
... and quite a few are network/pool related ...
... and if the bug does still exist ... then report it with the current version in the right place like you know you should
I can explain the normal steps to deal with reporting bugs that I'm sure most people understand if that's something you need to learn about .............
