I know it does not make any sense, all day yesterday I was running 2.1.1 - I had multiple 5870s on multiple rigs dying all day over and over
I downgraded back to 2.1.0
having 0 problems
its the only thing I changed
very strange indeed
Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 717. (Read 5805728 times)
January 02, 2012, 09:01:44 AM
January 02, 2012, 04:01:39 AM
Those with "comm errors" that lead to failures, are you using the ubuntu 11.11 binary on an older ubuntu?
Using Linuxcoin (which is based on ubuntu 11.04 I think? not sure) but compiled gcminer myself, and the same issue on windows, obviously using the windows binary.
January 02, 2012, 01:03:03 AM
Those with "comm errors" that lead to failures, are you using the ubuntu 11.11 binary on an older ubuntu?
January 01, 2012, 11:35:45 PM
Most unusual. There was no GPU speed or fan management code between 2.1.0 and 2.1.1...
On the other hand, there was one change between 2.0.8 and 2.1.0.
On the other hand, there was one change between 2.0.8 and 2.1.0.
And this wouldn't apply here, since I was coming from 2.0.7 (which still works great)....
Is there anything in 2.1.0 that would be causing sick/dead GPU's more frequently?
No.It looks like the GPU's only die when the comm issue comes up. 2.0.7 handles it better for some reason, still comm issue (which I've said before I don't think is from the miner) but the GPU's don't die. Running a rig on 2.1.1 and another on 2.0.7, I'll compare logs in the morning.
January 01, 2012, 11:08:57 PM
I just want to submit a possible bug with 2.1.1
I am a HUGE fan of cgminer and dev who is responsible for it
I have been using cgminer elusively on my 8 ghash rig since version 2.0.0
when I upgraded from 2.1.0 to 2.1.1 I am noticing my 5870s dying for some reason
I just watched one 5870 fan stop reporting RPM and then go to 127 Degrees and windows crashes
this happened three times in a row
I down graded back to 2.1.0 and the problem is not happening any more, that very same card is chillin at 57 degrees delivering a nice 432 mhash
I have also seen at least one 5870 die on all of my rigs since upgrading to 2.1.1
i downgraded back to 2.1.0 and have not seen any cards die as of yet
I will keep the thread upgraded if they die or not to see if my hunch is correct - that this is a problem with 2.1.1
thanks
Most unusual. There was no GPU speed or fan management code between 2.1.0 and 2.1.1...I am a HUGE fan of cgminer and dev who is responsible for it
I have been using cgminer elusively on my 8 ghash rig since version 2.0.0
when I upgraded from 2.1.0 to 2.1.1 I am noticing my 5870s dying for some reason
I just watched one 5870 fan stop reporting RPM and then go to 127 Degrees and windows crashes
this happened three times in a row
I down graded back to 2.1.0 and the problem is not happening any more, that very same card is chillin at 57 degrees delivering a nice 432 mhash
I have also seen at least one 5870 die on all of my rigs since upgrading to 2.1.1
i downgraded back to 2.1.0 and have not seen any cards die as of yet
I will keep the thread upgraded if they die or not to see if my hunch is correct - that this is a problem with 2.1.1
thanks
On the other hand, there was one change between 2.0.8 and 2.1.0.
So not sure what you're seeing there at all.
January 01, 2012, 10:46:16 PM
I just want to submit a possible bug with 2.1.1
I am a HUGE fan of cgminer and dev who is responsible for it
I have been using cgminer elusively on my 8 ghash rig since version 2.0.0
when I upgraded from 2.1.0 to 2.1.1 I am noticing my 5870s dying for some reason
I just watched one 5870 fan stop reporting RPM and then go to 127 Degrees and windows crashes
this happened three times in a row
I down graded back to 2.1.0 and the problem is not happening any more, that very same card is chillin at 57 degrees delivering a nice 432 mhash
I have also seen at least one 5870 die on all of my rigs since upgrading to 2.1.1
i downgraded back to 2.1.0 and have not seen any cards die as of yet
I will keep the thread upgraded if they die or not to see if my hunch is correct - that this is a problem with 2.1.1
thanks
I am a HUGE fan of cgminer and dev who is responsible for it
I have been using cgminer elusively on my 8 ghash rig since version 2.0.0
when I upgraded from 2.1.0 to 2.1.1 I am noticing my 5870s dying for some reason
I just watched one 5870 fan stop reporting RPM and then go to 127 Degrees and windows crashes
this happened three times in a row
I down graded back to 2.1.0 and the problem is not happening any more, that very same card is chillin at 57 degrees delivering a nice 432 mhash
I have also seen at least one 5870 die on all of my rigs since upgrading to 2.1.1
i downgraded back to 2.1.0 and have not seen any cards die as of yet
I will keep the thread upgraded if they die or not to see if my hunch is correct - that this is a problem with 2.1.1
thanks
January 01, 2012, 08:22:32 PM
How is 2.1.1 going with that? - ckolivas put in changes in 2.1.1 that hopefully might deal with that.
I'll try that tonight. Is it best to use the built or compile it from source?
January 01, 2012, 07:49:49 PM
gnar1ta$ if you put code tags around the code it won't be so long.
Yeah he just missed the closing tag.Actually, he didn't. The forum has a bug where it cuts off any part of the message that is too long without warning (at least when a huge part is wrapped in a code block). He should have used one of those "paste your text here" services and linked to that.
Fixed. How about the errors??
January 01, 2012, 06:43:21 PM
I can't see the temperature when using the latest cgminer, I had used the same commands as previous. Wonder what have I done wrong?
January 01, 2012, 03:47:27 PM
I see U columns that are aligning!
Yes, it's so sad... my sole double-digit U has degraded to single-digit like the rest. So much for my dreams of BTC wealth.
January 01, 2012, 03:44:17 PM
Code:
[P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
GPU 0: 69.5C 4535RPM | 357.0/363.8Mh/s | A:285 R:0 HW:0 U:5.02/m I: 9
GPU 1: 74.0C | 366.4/363.9Mh/s | A:299 R:0 HW:0 U:5.26/m I: 9
GPU 2: 67.5C 4108RPM | 372.9/363.8Mh/s | A:289 R:0 HW:0 U:5.09/m I: 9
GPU 3: 62.5C | 366.4/363.7Mh/s | A:262 R:0 HW:0 U:4.61/m I: 9
GPU 4: 68.0C 3564RPM | 370.8/363.6Mh/s | A:294 R:0 HW:0 U:5.18/m I: 9
GPU 5: 71.0C | 340.5/363.6Mh/s | A:318 R:1 HW:0 U:5.60/m I: 9
January 01, 2012, 01:23:30 PM
Feature request...
These are three 5970s. auto-fan is on with a target of 70C for all, 3C hysteresis. At this snapshot GPUs 1 and 5 ran 3C-4.5C hotter than their card-mates, and GPU 3 ran 5C cooler than its mate. I believe that because GPUs 1, 3, and 5 don't return fan values that cgminer is ignoring their temps w/r auto-fan. Assuming that cgminer can't tell via ADL or otherwise that two GPUs share a fan, I would like to able to tell that to cgminer and thus have my temp targets applied to (in my case) odd-numbered GPUs as well as to even-numbered ones.
Code:
[P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
GPU 0: 69.5C 4535RPM | 357.0/363.8Mh/s | A:285 R:0 HW:0 U:5.02/m I: 9
GPU 1: 74.0C | 366.4/363.9Mh/s | A:299 R:0 HW:0 U:5.26/m I: 9
GPU 2: 67.5C 4108RPM | 372.9/363.8Mh/s | A:289 R:0 HW:0 U:5.09/m I: 9
GPU 3: 62.5C | 366.4/363.7Mh/s | A:262 R:0 HW:0 U:4.61/m I: 9
GPU 4: 68.0C 3564RPM | 370.8/363.6Mh/s | A:294 R:0 HW:0 U:5.18/m I: 9
GPU 5: 71.0C | 340.5/363.6Mh/s | A:318 R:1 HW:0 U:5.60/m I: 9
These are three 5970s. auto-fan is on with a target of 70C for all, 3C hysteresis. At this snapshot GPUs 1 and 5 ran 3C-4.5C hotter than their card-mates, and GPU 3 ran 5C cooler than its mate. I believe that because GPUs 1, 3, and 5 don't return fan values that cgminer is ignoring their temps w/r auto-fan. Assuming that cgminer can't tell via ADL or otherwise that two GPUs share a fan, I would like to able to tell that to cgminer and thus have my temp targets applied to (in my case) odd-numbered GPUs as well as to even-numbered ones.
January 01, 2012, 01:05:39 PM
Your point being? U isn't A, R or HW...
Indeed. And that's exactly the problem. I would like all the columns to align.
It's not a big problem. But I have adopted it as my special cause.
January 01, 2012, 12:58:35 PM
Quote
commit 743d81b36bfe40b0c4a3f274220955d5016482be
Author: Con Kolivas <[email protected]>
Date: Sun Jan 1 20:25:04 2012 +1100
Adjust column width of A/R/HW to be the maximum of any device and align them.
Author: Con Kolivas <[email protected]>
Date: Sun Jan 1 20:25:04 2012 +1100
Adjust column width of A/R/HW to be the maximum of any device and align them.
cgminer version 2.1.1 - Started: [2012-01-01 09:17:46]
Code:
--------------------------------------------------------------------------------
[P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
GPU 0: 66.5C 4340RPM | 370.5/383.5Mh/s | A:3 R:0 HW:0 U:3.93/m I: 9
GPU 1: 70.5C | 359.7/374.0Mh/s | A:4 R:0 HW:0 U:5.24/m I: 9
GPU 2: 63.5C 4246RPM | 355.6/367.4Mh/s | A:5 R:0 HW:0 U:6.54/m I: 9
GPU 3: 58.5C | 367.7/368.9Mh/s | A:3 R:0 HW:0 U:3.93/m I: 9
GPU 4: 62.5C 4269RPM | 360.2/357.2Mh/s | A:8 R:0 HW:0 U:10.47/m I: 9
GPU 5: 66.5C | 369.1/359.4Mh/s | A:3 R:0 HW:0 U:3.93/m I: 9
--------------------------------------------------------------------------------
Your point being? U isn't A, R or HW...
January 01, 2012, 12:55:51 PM
Quote
commit 743d81b36bfe40b0c4a3f274220955d5016482be
Author: Con Kolivas <[email protected]>
Date: Sun Jan 1 20:25:04 2012 +1100
Adjust column width of A/R/HW to be the maximum of any device and align them.
Author: Con Kolivas <[email protected]>
Date: Sun Jan 1 20:25:04 2012 +1100
Adjust column width of A/R/HW to be the maximum of any device and align them.
cgminer version 2.1.1 - Started: [2012-01-01 09:17:46]
Code:
--------------------------------------------------------------------------------
[P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
GPU 0: 66.5C 4340RPM | 370.5/383.5Mh/s | A:3 R:0 HW:0 U:3.93/m I: 9
GPU 1: 70.5C | 359.7/374.0Mh/s | A:4 R:0 HW:0 U:5.24/m I: 9
GPU 2: 63.5C 4246RPM | 355.6/367.4Mh/s | A:5 R:0 HW:0 U:6.54/m I: 9
GPU 3: 58.5C | 367.7/368.9Mh/s | A:3 R:0 HW:0 U:3.93/m I: 9
GPU 4: 62.5C 4269RPM | 360.2/357.2Mh/s | A:8 R:0 HW:0 U:10.47/m I: 9
GPU 5: 66.5C | 369.1/359.4Mh/s | A:3 R:0 HW:0 U:3.93/m I: 9
--------------------------------------------------------------------------------
January 01, 2012, 10:57:42 AM
- Make curl use fresh connections whenever there is any communication issue
in case there are dead persistent connections preventing further comms from
working.
in case there are dead persistent connections preventing further comms from
working.
I awoke this morning to a miner which was in the throes of "the communication issue" as previously posted by me, others, and most recently, with debug output, by gnar1ta$. So I turned on the D/V/R display options and got a bunch of output from that (lots of HTTP 503 errors, among other info). Would this output be possibly helpful or is it hoped that the 2.1.1 change is the fix? I'd just post it but it's 265KB.
As before, after Q/restart operation is normal.
January 01, 2012, 10:40:22 AM
gnar1ta$ if you put code tags around the code it won't be so long.
Yeah he just missed the closing tag.Actually, he didn't. The forum has a bug where it cuts off any part of the message that is too long without warning (at least when a huge part is wrapped in a code block). He should have used one of those "paste your text here" services and linked to that.
Fixed. How about the errors??
January 01, 2012, 06:56:58 AM
gnar1ta$ if you put code tags around the code it won't be so long.
Yeah he just missed the closing tag.Actually, he didn't. The forum has a bug where it cuts off any part of the message that is too long without warning (at least when a huge part is wrapped in a code block). He should have used one of those "paste your text here" services and linked to that.
January 01, 2012, 05:03:07 AM
Happy New Year, new version 2.1.1, purely bugfixes and cosmetic changes. Links in top post.
- Include API examples in distribution tarball.
- Don't attempt to pthread_join when cancelling threads as they're already
detached and doing so can lead to a segfault.
- Give more generic message if slow pool at startup is the donation pool.
- Continue to attempt restarting GPU threads if they're flagged dead at 1 min.
intervals.
- Don't attempt to restart sick flagged GPUs while they're still registering
activity.
- Make curl use fresh connections whenever there is any communication issue
in case there are dead persistent connections preventing further comms from
working.
- Display pool in summary if only 1 pool.
- Adjust column width of A/R/HW to be the maximum of any device and align them.
- Include API examples in distribution tarball.
- Don't attempt to pthread_join when cancelling threads as they're already
detached and doing so can lead to a segfault.
- Give more generic message if slow pool at startup is the donation pool.
- Continue to attempt restarting GPU threads if they're flagged dead at 1 min.
intervals.
- Don't attempt to restart sick flagged GPUs while they're still registering
activity.
- Make curl use fresh connections whenever there is any communication issue
in case there are dead persistent connections preventing further comms from
working.
- Display pool in summary if only 1 pool.
- Adjust column width of A/R/HW to be the maximum of any device and align them.
January 01, 2012, 01:12:39 AM
gnar1ta$ if you put code tags around the code it won't be so long.
Yeah he just missed the closing tag. Jump to: