Hey guys, have any of you had an issue with V11.5, where when connection was lost to the pool, the miner resumed when the connection was restored, but at a lower hashrate?
At ~1:45am this morning, my miner lost connection, and when the connection was restored, the AMD cards mined at less than 50% of their usual hash rate. Strangely though, the NVidia cards on the rig resumed at their normal hashrate.
AMD Cards: Powercolor RX470, MSI Armor RX480
NVidia Cards: 2 x GTX 1050Ti
The log file:
01:43:23:567 15b0 ETH - Total Speed: 86.369 Mh/s, Total Shares: 913, Rejected: 1, Time: 12:03
01:43:23:567 15b0 ETH: GPU0 28.862 Mh/s, GPU1 29.061 Mh/s, GPU2 14.241 Mh/s, GPU3 14.206 Mh/s
01:43:24:223 15b0 buf: {"id":6,"jsonrpc":"2.0","result":true}
01:43:27:285 15b0 ETH: checking pool connection...
01:43:27:285 15b0 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
01:43:27:348 1370 checked ETH share on CPU, spent 5ms
01:43:27:348 1370 sent: {"worker":"Frankenstein","id":12,"method":"eth_submitWork","params": #RooiWillie - Line shortened for readability
01:43:27:348 1370 ETH: put share nonce 95e143d80337a242
01:43:27:363 15b0 ETH: 03/24/18-01:43:27 - SHARE FOUND - (GPU 2)
01:43:27:504 15b0 buf: {"id":3,"jsonrpc":"2.0","result": #RooiWillie - Line shortened for readability
01:43:27:692 15b0 buf: {"id":12,"jsonrpc":"2.0","result":true}
01:43:27:692 15b0 ETH: Share accepted (343 ms)!
01:43:37:301 15b0 ETH: checking pool connection...
01:43:37:301 15b0 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
01:43:37:520 15b0 buf: {"id":3,"jsonrpc":"2.0","result": #RooiWillie - Line shortened for readability
01:43:43:363 15b0 sent: {"id":6,"worker":"Frankenstein","jsonrpc":"2.0","method":"eth_submitHashrate","params": #RooiWillie - Line shortened for readability
01:43:43:582 15b0 buf: {"id":6,"jsonrpc":"2.0","result":true}
#RooiWillie - Removed a few log entries to make it more readable...
01:45:29:770 15b0 ETH: checking pool connection...
01:45:29:770 15b0 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
01:45:29:989 15b0 buf: {"id":3,"jsonrpc":"2.0","result": #RooiWillie - Line shortened for readability
01:45:36:645 15b0 buf: {"id":0,"jsonrpc":"2.0","result": #RooiWillie - Line shortened for readability
01:45:36:645 15b0 remove first packet 248
01:45:36:645 15b0 ETH: 03/24/18-01:45:36 - New job from eu1.ethermine.org:5555
01:45:36:645 15b0 target: 0x0000000112e0be82 (diff: 4000MH), epoch 176(2.37GB)
01:45:36:676 15b0 ETH - Total Speed: 56.436 Mh/s, Total Shares: 914, Rejected: 1, Time: 12:05
01:45:36:676 15b0 ETH: GPU0 12.901 Mh/s, GPU1 15.053 Mh/s, GPU2 14.250 Mh/s, GPU3 14.232 Mh/s
this happens to me as well for hardcoded bios.
temporary solution is disable p0-p6 in overdriventool. or hardcode your bios to use the same clocks on p0-p6.
this must be a bug, since this is not happening on previous versions.