OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.1

[cablepair]

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

[-ck]

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...
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.

[gnar1ta$]

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.

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.

[-ck]

Those with "comm errors" that lead to failures, are you using the ubuntu 11.11 binary on an older ubuntu?

[P4man]

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.

[cablepair]

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

[ancow]

Just had the following little (late) new-year's present from the latest version of cgminer from git:

Code:

[2012-01-02 13:59:38] Accepted 00000000.935b8a14.f87bc58e GPU 0 thread 1
[2012-01-02 13:59:38] Rejected 00000000.935b8a14.f87bc58e GPU 0 thread 1
[2012-01-02 14:00:06] LONGPOLL requested work restart, waiting on fresh work
[2012-01-02 14:00:08] LONGPOLL detected new block on network, waiting on fresh work
[2012-01-02 14:00:09] LONGPOLL requested work restart, waiting on fresh work
[2012-01-02 14:00:12] LONGPOLL requested work restart, waiting on fresh work
[2012-01-02 14:00:13] LONGPOLL requested work restart, waiting on fresh work
[2012-01-02 14:00:15] LONGPOLL requested work restart, waiting on fresh work
[2012-01-02 14:00:16] LONGPOLL requested work restart, waiting on fresh work
[...]
[2012-01-02 14:01:57] Accepted 00000000.dbe81ea1.3c890b62 GPU 0 thread 0
[2012-01-02 14:01:57] Rejected 00000000.dbe81ea1.3c890b62 GPU 0 thread 0
[2012-01-02 14:01:57] Rejected 00000000.dbe81ea1.3c890b62 GPU 0 thread 0
[2012-01-02 14:01:57] Rejected 00000000.dbe81ea1.3c890b62 GPU 0 thread 0
[2012-01-02 14:01:57] Rejected 00000000.dbe81ea1.3c890b62 GPU 0 thread 0
[2012-01-02 14:01:57] Rejected 00000000.dbe81ea1.3c890b62 GPU 0 thread 0
[2012-01-02 14:01:57] Rejected 00000000.dbe81ea1.3c890b62 GPU 0 thread 0
[2012-01-02 14:01:57] Rejected 00000000.dbe81ea1.3c890b62 GPU 0 thread 0
[2012-01-02 14:01:57] Rejected 00000000.dbe81ea1.3c890b62 GPU 0 thread 0
[2012-01-02 14:01:57] Rejected 00000000.dbe81ea1.3c890b62 GPU 0 thread 0
[2012-01-02 14:01:57] Rejected 00000000.dbe81ea1.3c890b62 GPU 0 thread 0
[2012-01-02 14:01:57] Rejected 00000000.dbe81ea1.3c890b62 GPU 0 thread 0
[2012-01-02 14:01:57] Rejected 00000000.dbe81ea1.3c890b62 GPU 0 thread 0
[2012-01-02 14:01:57] Rejected 00000000.dbe81ea1.3c890b62 GPU 0 thread 0
[2012-01-02 14:01:57] Rejected 00000000.dbe81ea1.3c890b62 GPU 0 thread 0
[2012-01-02 14:01:57] Rejected 00000000.dbe81ea1.3c890b62 GPU 0 thread 0
[2012-01-02 14:01:57] Rejected 00000000.dbe81ea1.3c890b62 GPU 0 thread 0
[2012-01-02 14:01:57] Rejected 00000000.dbe81ea1.3c890b62 GPU 0 thread 0
[2012-01-02 14:01:57] Rejected 00000000.dbe81ea1.3c890b62 GPU 0 thread 0
[2012-01-02 14:01:57] Rejected 00000000.dbe81ea1.3c890b62 GPU 0 thread 0
[2012-01-02 14:01:57] Rejected 00000000.dbe81ea1.3c890b62 GPU 0 thread 0
[2012-01-02 14:01:58] Rejected 00000000.dbe81ea1.3c890b62 GPU 0 thread 0
[2012-01-02 14:01:58] Rejected 00000000.dbe81ea1.3c890b62 GPU 0 thread 0
[2012-01-02 14:01:58] Rejected 00000000.dbe81ea1.3c890b62 GPU 0 thread 0
[2012-01-02 14:01:58] Rejected 00000000.dbe81ea1.3c890b62 GPU 0 thread 0
[2012-01-02 14:01:58] Rejected 00000000.dbe81ea1.3c890b62 GPU 0 thread 0

and the corresponding 26 new dupes on BTC Guild. Around the same time my KDE became seriously unresponsive until I disabled mining altogether. I assume the latter is some bug in fglrx, but the dupes are somewhat suspicious. (restarting cgminer doesn't help with the unresponsiveness)

[Proofer]

Those with "comm errors" that lead to failures, are you using the ubuntu 11.11 binary on an older ubuntu?

11.04; cgminer homemade from your github repo.

Haven't seen the comm issue yet with 2.1.1, but that's been slightly less than 24 hours and I had longer runs with prior versions without seeing the problem.

[Proofer]

Feature request...

On startup output all settings to stderr.

Edit:  Or not. ... I realize I can in effect do this myself by adding a command to my cgminer startup script to copy cgminer.conf to my logs dir, adding a timestamp to the filename.  And for extra credit, copy only if it's been changed since the last copy.

[P4man]

I just compiled 2.1.1 on linuxcoin; For no apparent reason, it still seems to send a few shares to a failover pool each time after receiving a long poll. There is no indication of the primary pool being slow or down:

Code:

[2012-01-02 18:07:00] LONGPOLL requested work restart, waiting on fresh work
[2012-01-02 18:07:03] Accepted 00000000.638a8cdc.d04fad04 GPU 0 thread 2 pool 0
[2012-01-02 18:07:04] Accepted 00000000.5ca59695.abfef338 GPU 1 thread 1 pool 1 <<<<<<<
[2012-01-02 18:07:07] Accepted 00000000.1d1a6056.49d23631 GPU 0 thread 0 pool 0
[2012-01-02 18:07:07] Accepted 00000000.c4c1a1be.5059d232 GPU 0 thread 0 pool 0
[2012-01-02 18:07:18] Accepted 00000000.a2ba11d9.85832b6c GPU 0 thread 0 pool 0
[2012-01-02 18:07:42] Accepted 00000000.c36507c8.fbb965c8 GPU 1 thread 1 pool 0
[2012-01-02 18:07:44] Accepted 00000000.e068f69c.5b961150 GPU 1 thread 3 pool 0
[2012-01-02 18:07:48] Accepted 00000000.7538e8a6.d5b2dfa5 GPU 0 thread 2 pool 0
[2012-01-02 18:07:49] Accepted 00000000.3e93607e.846b1a21 GPU 1 thread 3 pool 0
[2012-01-02 18:08:10] Accepted 00000000.dd33c2bd.3cbf5975 GPU 0 thread 0 pool 0
[2012-01-02 18:08:12] Accepted 00000000.022ca257.0997122e GPU 1 thread 3 pool 0
[2012-01-02 18:08:14] LONGPOLL detected new block on network, waiting on fresh w
ork
[2012-01-02 18:08:22] Accepted 00000000.595178f1.18a8cb3d GPU 1 thread 1 pool 1  <<<<<<<
[2012-01-02 18:08:23] Accepted 00000000.849a98d9.464ec1ba GPU 1 thread 3 pool 1  <<<<<<<
[2012-01-02 18:08:27] Accepted 00000000.f09dc720.6b21b7c1 GPU 1 thread 1 pool 1  <<<<<<<
[2012-01-02 18:08:41] Accepted 00000000.4a6aa090.2b98099c GPU 1 thread 1 pool 0
[2012-01-02 18:08:46] Accepted 00000000.367074fe.7dc3a313 GPU 1 thread 1 pool 0
[2012-01-02 18:08:52] Accepted 00000000.12b021b0.8991d572 GPU 1 thread 1 pool 0
[2012-01-02 18:08:54] Accepted 00000000.0d25fa80.1e252b53 GPU 0 thread 2 pool 0
[2012-01-02 18:08:57] Accepted 00000000.50292a8d.add8ae8e GPU 1 thread 1 pool 0
[2012-01-02 18:09:07] Accepted 00000000.998e8934.7ee9f88c GPU 1 thread 3 pool 0
[2012-01-02 18:09:13] Accepted 00000000.934a726d.f8b42525 GPU 1 thread 3 pool 0

IM leaving my windows machine on 2.0.8 for now, if I get the "network hang bug" Ill be able to see if that bug is solved in 2.1.1

[simonk83]

Hmm, bit of an issue here...


With cgminer 2.0.8 I get this:

GPU 3: 72.5C 2704RPM | 422.8/437.8Mh/s | A:4 R:0 HW:0 U:4.34/m I:9



With 2.1.1. I get this:

GPU 3:  74.0C 2447RPM | 378.5/384.7Mh/s | A:26 R:0 HW:0 U:6.34/m I: 9



Pretty big speed drop there, it's almost like it doesn't actually apply the overclock (even though it's reporting 930mhz).  This is a 5870, and I'm using the exact same .bat file to start both instances.

[P4man]

You cant draw conclusions over such a  short timeframe. Let it run for a few hours, then compare. And compare the average reported on top, not the 5s average which can fluctuate a lot.

[simonk83]

You cant draw conclusions over such a  short timeframe. Let it run for a few hours, then compare. And compare the average reported on top, not the 5s average which can fluctuate a lot.

I've been running 2.08 for days, and 420Mh is the average.

Before this test I ran 2.1.1 for a few hours and only noticed the speeds just now.  I went back to 2.0.8 to test and grab the "screenshot" and then again with 2.1.1 and grabbed that screenshot.

[gnar1ta$]

2.1.1

Code:

[2012-01-02 07:13:04] Pool 0 communication resumed, submitting work
[2012-01-02 07:13:04] Rejected 00000000.b0b545fc.f5c0bfa7 GPU 1 thread 1 pool 0
[2012-01-02 07:13:06] Accepted 00000000.2dffb765.2a7d652a GPU 1 thread 1 pool 0
[2012-01-02 07:13:07] Accepted 00000000.27f2502f.3ce76d2b GPU 3 thread 3 pool 0
[2012-01-02 07:13:08] Pool 0 communication failure, caching submissions
[2012-01-02 07:13:09] Pool 0 communication resumed, submitting work
[2012-01-02 07:13:09] Rejected 00000000.49e6dd08.2b6a6479 GPU 4 thread 10 pool 0
[2012-01-02 07:13:11] Pool 0 communication failure, caching submissions
[2012-01-02 07:13:15] Pool 0 communication resumed, submitting work
[2012-01-02 07:13:15] Accepted 00000000.ed517576.0c71ca9d GPU 5 thread 11 pool 0
[2012-01-02 07:13:20] Pool 0 communication failure, caching submissions
[2012-01-02 07:13:23] Pool 0 communication resumed, submitting work
[2012-01-02 07:13:23] Accepted 00000000.e4dbe71a.38ebcab1 GPU 3 thread 9 pool 0
[2012-01-02 07:13:24] Pool 0 communication failure, caching submissions
[2012-01-02 07:13:24] Pool 0 communication resumed, submitting work
[2012-01-02 07:13:24] Accepted 00000000.9bb3b52c.8158e26a GPU 2 thread 2 pool 0
[2012-01-02 07:13:27] Accepted 00000000.5a9dc65a.5137f0a3 GPU 3 thread 9 pool 0
[2012-01-02 07:13:31] Accepted 00000000.9561d04e.5628b44c GPU 4 thread 10 pool 0
[2012-01-02 07:13:38] Pool 0 communication failure, caching submissions
[2012-01-02 07:13:38] Pool 0 communication resumed, submitting work
[2012-01-02 07:13:38] Accepted 00000000.be2f6d7e.fd4f0b14 GPU 1 thread 7 pool 0
[2012-01-02 07:13:38] Pool 0 communication failure, caching submissions
[2012-01-02 07:13:38] Pool 0 communication resumed, submitting work
[2012-01-02 07:13:38] Accepted 00000000.a8887535.69385436 GPU 3 thread 3 pool 0
[2012-01-02 07:13:42] Pool 0 communication failure, caching submissions
[2012-01-02 07:13:46] Pool 0 communication resumed, submitting work
[2012-01-02 07:13:46] Rejected 00000000.37f13ba5.00343e58 GPU 3 thread 3 pool 0
[2012-01-02 07:13:48] Pool 0 communication failure, caching submissions
[2012-01-02 07:13:54] Pool 0 communication resumed, submitting work
[2012-01-02 07:13:54] Accepted 00000000.d0f64ff1.b3410a8e GPU 5 thread 11 pool 0
[2012-01-02 07:13:55] Accepted 00000000.4ba4218b.7a9fbede GPU 4 thread 4 pool 0
[2012-01-02 07:13:56] Pool 0 communication failure, caching submissions
[2012-01-02 07:14:03] Pool 0 communication resumed, submitting work
[2012-01-02 07:14:03] Accepted 00000000.543570da.3d83e326 GPU 4 thread 4 pool 0
[2012-01-02 07:14:04] Accepted 00000000.e55028b1.a3c0ca62 GPU 1 thread 7 pool 0
[2012-01-02 07:14:06] Accepted 00000000.d048a0cf.aedae05d GPU 3 thread 9 pool 0
[2012-01-02 07:14:06] Pool 0 communication failure, caching submissions
[2012-01-02 07:14:06] Pool 0 communication resumed, submitting work
[2012-01-02 07:14:06] Accepted 00000000.6dd7c39b.d1e25783 GPU 3 thread 9 pool 0
[2012-01-02 07:14:06] Accepted 00000000.e096a20c.03b55f25 GPU 4 thread 10 pool 0
[2012-01-02 07:14:08] Accepted 00000000.8af1cab4.490d4f09 GPU 4 thread 10 pool 0
[2012-01-02 07:14:09] Accepted 00000000.57eb97c0.c9585ae2 GPU 4 thread 10 pool 0
[2012-01-02 07:14:10] Pool 0 communication failure, caching submissions
[2012-01-02 07:14:10] Pool 0 communication resumed, submitting work
[2012-01-02 07:14:10] Accepted 00000000.024f145c.d0add7bd GPU 2 thread 8 pool 0
[2012-01-02 07:14:12] Pool 0 communication failure, caching submissions
[2012-01-02 07:14:13] Pool 0 communication resumed, submitting work
[2012-01-02 07:14:13] Accepted 00000000.b0e1b282.abdad171 GPU 3 thread 9 pool 0
[2012-01-02 07:14:13] Accepted 00000000.9f4303a4.9932976c GPU 5 thread 11 pool 0
[2012-01-02 07:14:14] Accepted 00000000.63bc1fc1.959a4ae2 GPU 3 thread 9 pool 0
[2012-01-02 07:14:14] Pool 0 communication failure, caching submissions
[2012-01-02 07:14:15] Pool 0 communication resumed, submitting work
[2012-01-02 07:14:15] Accepted 00000000.856a63c4.28ac77c0 GPU 3 thread 9 pool 0
[2012-01-02 07:14:17] Pool 0 communication failure, caching submissions
[2012-01-02 07:14:17] Pool 0 communication resumed, submitting work
[2012-01-02 07:14:17] Accepted 00000000.2e0a05dd.2a22906f GPU 3 thread 3 pool 0
[2012-01-02 07:14:18] Accepted 00000000.04a7bfc7.84616197 GPU 5 thread 11 pool 0
[2012-01-02 07:14:20] Accepted 00000000.ddb4420f.e3fee3d4 GPU 1 thread 1 pool 0
[2012-01-02 07:14:20] Accepted 00000000.de1ea58a.58196872 GPU 2 thread 8 pool 0
[2012-01-02 07:14:21] Accepted 00000000.1705088a.aae2b09e GPU 3 thread 3 pool 0
[2012-01-02 07:14:23] Pool 0 communication failure, caching submissions
[2012-01-02 07:14:25] Pool 0 communication resumed, submitting work
[2012-01-02 07:14:25] Accepted 00000000.2084a552.ac8911f0 GPU 2 thread 2 pool 0
[2012-01-02 07:14:25] Rejected 00000000.96ea687a.4aa9653f GPU 2 thread 2 pool 0

2.0.7

Code:

[2012-01-02 07:13:00] Pool 0 communication failure, caching submissions
[2012-01-02 07:13:23] Pool 0 communication resumed, submitting work
[2012-01-02 07:13:23] Accepted 00000000.76595ff9.de32d2f2 GPU 1 thread 5 pool 0
[2012-01-02 07:13:31] Pool 0 communication failure, caching submissions
[2012-01-02 07:13:32] Pool 0 communication resumed, submitting work
[2012-01-02 07:13:32] Rejected 00000000.df7eac5a.8914a61c GPU 3 thread 3 pool 0
[2012-01-02 07:13:32] Rejected 00000000.ebda8037.8f7db879 GPU 0 thread 0 pool 0
[2012-01-02 07:13:33] Pool 0 communication failure, caching submissions
[2012-01-02 07:13:34] Pool 0 communication resumed, submitting work
[2012-01-02 07:13:34] Accepted 00000000.11873818.f24c4c5c GPU 1 thread 5 pool 0
[2012-01-02 07:13:34] Accepted 00000000.8a0f5c9f.ea8ded3d GPU 1 thread 5 pool 0
[2012-01-02 07:13:34] Pool 0 communication failure, caching submissions
[2012-01-02 07:13:37] Pool 0 communication resumed, submitting work
[2012-01-02 07:13:37] Accepted 00000000.8bbad5cc.b9d2a4a7 GPU 0 thread 4 pool 0
[2012-01-02 07:13:37] Pool 0 communication failure, caching submissions
[2012-01-02 07:13:39] Pool 0 communication resumed, submitting work
[2012-01-02 07:13:39] Accepted 00000000.74512c85.88c0e5dd GPU 1 thread 5 pool 0
[2012-01-02 07:13:39] Accepted 00000000.337a5fc9.41c5a471 GPU 0 thread 4 pool 0
[2012-01-02 07:13:41] Pool 0 communication failure, caching submissions
[2012-01-02 07:13:43] Pool 0 communication resumed, submitting work
[2012-01-02 07:13:43] Accepted 00000000.aa5740bb.d834d2d0 GPU 2 thread 2 pool 0
[2012-01-02 07:13:45] Accepted 00000000.671c0adc.b63e24e0 GPU 1 thread 5 pool 0
[2012-01-02 07:13:45] Pool 0 communication failure, caching submissions
[2012-01-02 07:13:47] Pool 0 communication resumed, submitting work
[2012-01-02 07:13:47] Accepted 00000000.eb2af372.4ce713cf GPU 0 thread 4 pool 0
[2012-01-02 07:13:48] Pool 0 communication failure, caching submissions
[2012-01-02 07:13:52] Pool 0 communication resumed, submitting work
[2012-01-02 07:13:52] Rejected 00000000.d73372e3.ecadb2ae GPU 1 thread 5 pool 0
[2012-01-02 07:13:54] Accepted 00000000.b1f34824.9a9bf85f GPU 1 thread 5 pool 0
[2012-01-02 07:13:55] Rejected 00000000.8ee49284.1e96e567 GPU 2 thread 2 pool 0
[2012-01-02 07:13:55] Accepted 00000000.fb282837.330dd629 GPU 3 thread 7 pool 0
[2012-01-02 07:13:57] Pool 0 communication failure, caching submissions
[2012-01-02 07:13:57] Pool 0 communication resumed, submitting work
[2012-01-02 07:13:57] Rejected 00000000.5fdd51e4.31ca44dc GPU 3 thread 3 pool 0
[2012-01-02 07:14:02] Pool 0 communication failure, caching submissions
[2012-01-02 07:14:03] Pool 0 communication resumed, submitting work
[2012-01-02 07:14:03] Accepted 00000000.3f6a0be0.16aaac50 GPU 1 thread 5 pool 0
[2012-01-02 07:14:06] Pool 0 communication failure, caching submissions
[2012-01-02 07:14:08] Pool 0 communication resumed, submitting work
[2012-01-02 07:14:08] Accepted 00000000.7f7e5e4b.177e4b7f GPU 1 thread 5 pool 0
[2012-01-02 07:14:08] Accepted 00000000.3d50007b.8fe6da3f GPU 0 thread 4 pool 0
[2012-01-02 07:14:11] Accepted 00000000.cdbf7249.16c5e2c8 GPU 1 thread 5 pool 0
[2012-01-02 07:14:13] Pool 0 communication failure, caching submissions
[2012-01-02 07:14:16] Pool 0 communication resumed, submitting work
[2012-01-02 07:14:16] Accepted 00000000.f674cc25.6f8f32a2 GPU 2 thread 2 pool 0
[2012-01-02 07:14:19] Accepted 00000000.58c68476.725bc8a9 GPU 1 thread 1 pool 0
[2012-01-02 07:14:22] Pool 0 communication failure, caching submissions
[2012-01-02 07:14:32] Pool 0 communication resumed, submitting work
[2012-01-02 07:14:32] Accepted 00000000.945939ab.834c8b6b GPU 3 thread 7 pool 0
[2012-01-02 07:14:32] Pool 0 communication failure, caching submissions
[2012-01-02 07:14:32] Pool 0 communication resumed, submitting work
[2012-01-02 07:14:32] Accepted 00000000.1fb1c87d.4adc4165 GPU 2 thread 2 pool 0
[2012-01-02 07:14:34] Accepted 00000000.17180ee7.0992118c GPU 1 thread 1 pool 0
[2012-01-02 07:14:35] Pool 0 communication failure, caching submissions
[2012-01-02 07:14:37] Pool 0 communication resumed, submitting work
[2012-01-02 07:14:37] Rejected 00000000.97064369.f7508701 GPU 1 thread 1 pool 0
[2012-01-02 07:14:46] Pool 0 communication failure, caching submissions
[2012-01-02 07:14:55] Pool 0 communication resumed, submitting work
[2012-01-02 07:14:55] Accepted 00000000.b55d89c3.4b3e16fe GPU 2 thread 6 pool 0
[2012-01-02 07:14:55] Pool 0 communication failure, caching submissions
[2012-01-02 07:14:56] Pool 0 communication resumed, submitting work
[2012-01-02 07:14:56] Rejected 00000000.04cfa007.0b8f337f GPU 1 thread 5 pool 0
[2012-01-02 07:14:56] Rejected 00000000.13017bca.b4fb5d48 GPU 0 thread 0 pool 0

The comm issue isn't new, but the 2.1.x locks up, which this was when I got to it so I could not turn on debugging (2.0.7 cleared up and was still hashing) Here is the last entries from the 2.1.1 screen:

Code:

[2012-01-02 09:25:32] Accepted 00000000.5b2fd745.f4b5aba4 GPU 3 thread 3 pool 0
[2012-01-02 09:30:47] LONGPOLL detected new block on network, waiting on fresh work

5 minute gap on timestamps.  It still gets LONGPOLL messages but it isn't hashing??

Here is from 2.1.0 on a different day - same thing, last entries:

Code:

[2011-12-29 08:52:15] LONGPOLL detected new block on network, waiting on fresh work
[2011-12-29 09:10:32] LONGPOLL detected new block on network, waiting on fresh work

[simonk83]

You cant draw conclusions over such a  short timeframe. Let it run for a few hours, then compare. And compare the average reported on top, not the 5s average which can fluctuate a lot.

I've been running 2.08 for days, and 420Mh is the average.

Before this test I ran 2.1.1 for a few hours and only noticed the speeds just now.  I went back to 2.0.8 to test and grab the "screenshot" and then again with 2.1.1 and grabbed that screenshot.

Ok, weirdly, I just tried 2.0.7 and that's giving the same behaviour as 2.1.1...  odd as it was fine back when I used it daily.   Maybe I'll reboot

EDIT:  Reboot didn't help.  Stuck at 380Mhash.   Weird.

[DeathAndTaxes]

You cant draw conclusions over such a  short timeframe. Let it run for a few hours, then compare. And compare the average reported on top, not the 5s average which can fluctuate a lot.

I've been running 2.08 for days, and 420Mh is the average.

Before this test I ran 2.1.1 for a few hours and only noticed the speeds just now.  I went back to 2.0.8 to test and grab the "screenshot" and then again with 2.1.1 and grabbed that screenshot.

Ok, weirdly, I just tried 2.0.7 and that's giving the same behaviour as 2.1.1...  odd as it was fine back when I used it daily.   Maybe I'll reboot

EDIT:  Reboot didn't help.  Stuck at 380Mhash.   Weird.

You change your driver recently.  The SDK change doesn't take place until system reboot.

[simonk83]

You cant draw conclusions over such a  short timeframe. Let it run for a few hours, then compare. And compare the average reported on top, not the 5s average which can fluctuate a lot.

I've been running 2.08 for days, and 420Mh is the average.

Before this test I ran 2.1.1 for a few hours and only noticed the speeds just now.  I went back to 2.0.8 to test and grab the "screenshot" and then again with 2.1.1 and grabbed that screenshot.

Ok, weirdly, I just tried 2.0.7 and that's giving the same behaviour as 2.1.1...  odd as it was fine back when I used it daily.   Maybe I'll reboot

EDIT:  Reboot didn't help.  Stuck at 380Mhash.   Weird.

You change your driver recently.  The SDK change doesn't take place until system reboot.

Nope, unfortunately not.   2.0.8 still works fine...  weird.

[-ck]

By the way, if you're using the donation option, and you've been having lots of communication issues lately, it's probably that   The pool your donations are going to is still having lots of teething problems with its migration.

[kano]

You cant draw conclusions over such a  short timeframe. Let it run for a few hours, then compare. And compare the average reported on top, not the 5s average which can fluctuate a lot.

I've been running 2.08 for days, and 420Mh is the average.

Before this test I ran 2.1.1 for a few hours and only noticed the speeds just now.  I went back to 2.0.8 to test and grab the "screenshot" and then again with 2.1.1 and grabbed that screenshot.

Ok, weirdly, I just tried 2.0.7 and that's giving the same behaviour as 2.1.1...  odd as it was fine back when I used it daily.   Maybe I'll reboot

EDIT:  Reboot didn't help.  Stuck at 380Mhash.   Weird.

When A:NNNN is at least a few thousand then the figures may be of interest.
Until then they mean nothing for anyone but your own interest.

The first time I ran 2.1.1 I also used the --gpu-memdiff option for the first time and it jumped UP 20Mh/s for the first few minutes then it dropped back to normal.
I was wondering if I had missed something all this time (one of my GPU's steps the clock down 30 due to heat) and I thought that was something I had missed all this time.
But an hour later it showed the usual average.

So yeah give it an hour and look at the 2nd number only.

[simonk83]

Read my second reply, it was running for at least an hour the first time I noticed.  

Besides, its completely repeatable.   Start 2.0.8 and I immediately get 420mH or thereabout.   Start 2.0.7 or 2.1.1 and its immediately capped at 380mH and sticks there.