 Show Posts
|
|
Pages: [1]
|
|
Argon2 SOLO no any accepted block with 3.8.5
No error, cpu usage 100%, but no accepted block.
same with 2x2680v1/Manjaro and 1700x/W10
3.8.4.1 accepting blocks on both config.
|
|
|
|
Nist5 looks pretty good in 3.8.2.1 using GBT. Did you ever find a block? This would indicate that GBT basically works as is. nist5 for algo test. other: http://prntscr.com/ijay5wworking fine  |
|
|
|
|
All algo back to normal, no any problem.
Thanks!
|
|
|
|
Excellent data, it wil take some time to analyze it. Edit: I have an initial question about this data that will affect the bug fix release. You initially reported that yescryptr16 crashed but this shows that it was hashing and submitting rejects. Were both of these tests with the same code? I need to know if v3.8.3.1 can hash or if it crashes before starting to hash. 1700x or E5-2640 + manjaro + 3.8.3.1 Segmentation fault, no any hash http://prntscr.com/ij6v61 <-original git compiled without any change 8700k + win10 + 3.8.3.1 start working, crash after 1-2 minute, normal hashrate 1khs +/- 5%, windows also from git, not self compiled I'm using -march=znver1 -DUSE_SPH_SHA tweaks for amd and sandybridge for E5 thats all |
|
|
|
still Segmentation fault
same error with other wallet
If it crashes with BLOCK_VERSION_CURRENT 3 and std_longpoll_rpc_call from 3.8.2 I'm stumped. git + 2 patch, no build modification http://prntscr.com/iixh31Ok, undo those changes, start fresh and make the following change to std_get_new_work: if ( ( memcmp( work->data, g_work->data, algo_gate.work_cmp_size )
&& clean_job )
|| ( *nonceptr >= *end_nonce_ptr )
del: || ( !opt_benchmark && strcmp( work->job_id, g_work->job_id ) ) )
add: || ( have_stratum && strcmp( work->job_id, g_work->job_id ) ) )
{
One more shot in the dark, replace std_get_new_work with the old version. If that doesn't work apply all patches above: replace std_get_new_work and std_longpoll_rpc_call with old versions, and #define BLOCK_VERSION_CURRENT 3 as per old version. Ater that I'm really stuck. Edit: This is really strange. I need you to confirm the previous version still works. I've reviewed the changes I made. There were none to yescrypt but many other algos were changed. I made a few changes to common code: Increasing the block version count, reverting did not help. Removing getwork code from longpoll. This was my first suspect if my assumption that getwork doesn't use longpoll. But reversing that change did not help either. I made a change to how new work is detected to fix an issue with super-fast algos. But reversing that didn't fix it either. I made a change to how shares are detected but that only applies when a solution is found. The last change was to the API which also doesn't apply. I'm at a loss to explain it. some getwork code from longpoll This problem is bugging me, it defies logic. I'm beginning to suspect it may be an isolated issue. If anyone else is solo mining with v3.8.3.1 using getwork or gbt please post your results, success or failure, Please include the algo, your CPU, OS, any deveation from defaults and any relevant console output. windows 10 local wallet 3.8.2.1 -> http://prntscr.com/ij3qkpinterzone/c11 simply crashed -> 3.8.2.1 http://prntscr.com/ij3pmaBWK/nist5 also crashed -> 3.8.2.1 http://prntscr.com/ij3ou2Solaris/xevan http://prntscr.com/ij3lnl -> 3.8.2.1 http://prntscr.com/ij3nmcUTC/scryptjane:14 http://prntscr.com/ij3zoo -> 3.8.2.1 http://prntscr.com/ij40duon localhost / win 10 |
|
|
|
still Segmentation fault
same error with other wallet
If it crashes with BLOCK_VERSION_CURRENT 3 and std_longpoll_rpc_call from 3.8.2 I'm stumped. git + 2 patch, no build modification http://prntscr.com/iixh31Ok, undo those changes, start fresh and make the following change to std_get_new_work: if ( ( memcmp( work->data, g_work->data, algo_gate.work_cmp_size )
&& clean_job )
|| ( *nonceptr >= *end_nonce_ptr )
del: || ( !opt_benchmark && strcmp( work->job_id, g_work->job_id ) ) )
add: || ( have_stratum && strcmp( work->job_id, g_work->job_id ) ) )
{
|
|
|
|
still Segmentation fault
same error with other wallet
If it crashes with BLOCK_VERSION_CURRENT 3 and std_longpoll_rpc_call from 3.8.2 I'm stumped. git + 2 patch, no build modification http://prntscr.com/iixh31 |
|
|
|
|
still Segmentation fault
same error with other wallet
|
|
|
|
./cpuminer -a yescryptr16 -o http://192.168.1.150:49751 -u XY -p XY1 --no-stratum
********** cpuminer-opt 3.8.2.1 ***********
A CPU miner with multi algo support and optimized for CPUs
with AES_NI and AVX2 and SHA extensions.
BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT
CPU: AMD Ryzen 7 1700X Eight-Core Processor .
SW built on Feb 18 2018 with GCC 7.3.0.
CPU features: SSE2 AES AVX AVX2 SHA.
SW features: SSE2 AES AVX AVX2 SHA.
Algo features: SSE2 AVX SHA.
Start mining with AVX SHA.
[2018-02-23 22:17:46] 16 miner threads started, using 'yescryptr16' algorithm.
[2018-02-23 22:17:47] Current block is 83506
[2018-02-23 22:17:47] No payout address provided, switching to getwork
[2018-02-23 22:19:30] CPU #0: 4096 H, 40.29 H/s
[2018-02-23 22:19:32] yescryptr16 block 83507, diff 0.11, net 3051.57 kH/s
[2018-02-23 22:19:32] CPU #10: 2419 H, 28.93 H/s
[2018-02-23 22:19:32] CPU #14: 1988 H, 26.30 H/s
[2018-02-23 22:19:32] CPU #13: 2221 H, 28.62 H/s
[2018-02-23 22:19:32] CPU #11: 2362 H, 28.94 H/s ./cpuminer -a yescryptr16 -o http://192.168.1.150:49751 -u XY -p XY1 --no-stratum
********** cpuminer-opt 3.8.3.1 ***********
A CPU miner with multi algo support and optimized for CPUs
with AES_NI and AVX2 and SHA extensions.
BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT
CPU: AMD Ryzen 7 1700X Eight-Core Processor .
SW built on Feb 23 2018 with GCC 7.3.0.
CPU features: SSE2 AES AVX AVX2 SHA.
SW features: SSE2 AES AVX AVX2 SHA.
Algo features: SSE2 AVX SHA.
Start mining with AVX SHA.
[2018-02-23 22:17:18] 16 miner threads started, using 'yescryptr16' algorithm.
[2018-02-23 22:17:19] Current block is 83506
[2018-02-23 22:17:19] No payout address provided, switching to getwork
Segmentation fault
Solo mining looks bad, only for me? Dual E5-2640 similar error, Manjaro 17 on both |
|
|
|
|
Number of transaction: 35
But only 28 listed.
7 disappeared pow block.
|
|
|
|
|
solo, ccminer 2.0 + cpuminer-opt 3.6.5
|
|
|
|
|
