Test fail (result = 0) on EPYC AMD Dual socket

[itsmalu]

Hello there,
I'm trying to test some of my new AMD EPYC

Unfortunately, I had no problem to test it on single socket motherboard but in dual socket (reaching 512 cores) I randomly have tests that are failing.
Using -debug I can see tests are doing timeout but no reason of why and how to fix
exemple :
24181.989705: ECDSA verified\Elapsed\Bps: 4676648960 \ 6.67604 \ 7.00513e+08
24181.989952: ECDSA verified\Elapsed\Bps: 4865392640 \ 6.67808 \ 7.28562e+08
24181.990059: ECDSA verified\Elapsed\Bps: 4666163200 \ 6.67744 \ 6.98795e+08
24181.990106: ECDSA verified\Elapsed\Bps: 4687134720 \ 6.6775 \ 7.0193e+08
24181.990215: ECDSA verified\Elapsed\Bps: 4550819840 \ 6.68036 \ 6.81224e+08
24181.990320: ECDSA verified\Elapsed\Bps: 4718592000 \ 6.67724 \ 7.06669e+08
24181.990480: ECDSA verified\Elapsed\Bps: 4687134720 \ 6.67691 \ 7.01992e+08
24181.990606: ECDSA verified\Elapsed\Bps: 4928307200 \ 6.67636 \ 7.38173e+08
24181.990945: ECDSA verified\Elapsed\Bps: 4676648960 \ 6.67871 \ 7.00232e+08
24181.991230: ECDSA verified\Elapsed\Bps: 4760535040 \ 6.67733 \ 7.1294e+08
24181.991354: ECDSA verified\Elapsed\Bps: 4928307200 \ 6.67969 \ 7.37805e+08
24181.991594: ECDSA verified\Elapsed\Bps: 4750049280 \ 6.67816 \ 7.11281e+08
24181.992252: ECDSA verified\Elapsed\Bps: 4791992320 \ 6.67838 \ 7.17538e+08
24181.992398: ECDSA verified\Elapsed\Bps: 4928307200 \ 6.67984 \ 7.37789e+08
24181.992497: ECDSA verified\Elapsed\Bps: 4802478080 \ 6.67843 \ 7.19103e+08
24181.992549: ECDSA verified\Elapsed\Bps: 4550819840 \ 6.68007 \ 6.81253e+08
24181.992610: ECDSA verified\Elapsed\Bps: 4729077760 \ 6.67795 \ 7.08164e+08
24181.993097: ECDSA verified\Elapsed\Bps: 4886364160 \ 6.6785 \ 7.31655e+08
24181.993420: ECDSA verified\Elapsed\Bps: 4540334080 \ 6.6796 \ 6.79731e+08
24181.994345: ECDSA verified\Elapsed\Bps: 4718592000 \ 6.67818 \ 7.06569e+08
24381.942129: Test Timeout


Launching test multple time sometimes works and fix a test, but another timeout :-/
Tried in -d 1 to -d 4 same problem

Any idea ?

[David (PassMark)]

Likely a timer is expiring before the large number of test processes can terminate and provide an overall result.

Can you try setting the number of test processes in the preferences window to something lower (eg. 100, 200, 300) to see if that works.

[Tim (PassMark)]

We have increased the timeout based on the number of test threads running, could you please try this debug build and let us know if you're still seeing the timeout issues (and send us a debug log is so).