log in |
Message boards : Number crunching : Constant calculation errors since the server crash and restoration
Author | Message |
---|---|
Since the server blue-screened and had to be rolled back to an old backup, I've been getting constant errors when attempting SRBase workloads. The program "TF 0.29 (opencl_ati_101)" always runs for 9 to 10 seconds, then errors out with a "calculation error". I've already tried restarting the project in the hopes that it was just a corrupted file from the crash, but to no avail. All other projects I'm contributing are working correctly, even the GPU-based ones. Any clues of what may be happening? | |
ID: 10209 · Rating: 0 · rate: / Reply Quote | |
There is no change in apps since crash, must be on your side. Mine is running on RX5500XT. Try to copy the app outside boinc and run mfakto.exe -st. Your selftests failed. | |
ID: 10210 · Rating: 0 · rate: / Reply Quote | |
Looks like my self-tests are indeed failing - problem being that they didn't use to fail before:
Loading binary kernel file mfakto_Kernels.elf
Compiling kernels.
GPUSievePrimes (adjusted) 82486
GPUsieve minimum exponent 1055144
Started a simple self-test ...
ERROR: self-test failed for M51332417 (cl_barrett15_69_gs)
no factor found
ERROR: self-test failed for M50896831 (cl_barrett15_71_gs)
no factor found
ERROR: self-test failed for M50979079 (cl_barrett15_73_gs)
no factor found
ERROR: self-test failed for M51232133 (cl_barrett15_73_gs)
no factor found
ERROR: self-test failed for M50830523 (cl_barrett15_73_gs)
no factor found
ERROR: self-test failed for M50752613 (cl_barrett15_73_gs)
no factor found
ERROR: self-test failed for M51507913 (cl_barrett15_73_gs)
no factor found
ERROR: self-test failed for M51916901 (cl_barrett15_74_gs)
no factor found
ERROR: self-test failed for M50805581 (cl_barrett15_82_gs)
no factor found
ERROR: self-test failed for M51157429 (cl_barrett15_82_gs)
no factor found
ERROR: self-test failed for M51406151 (cl_barrett15_82_gs)
no factor found
ERROR: self-test failed for M51478381 (cl_barrett15_82_gs)
no factor found
ERROR: self-test failed for M51350527 (cl_barrett15_82_gs)
no factor found
ERROR: self-test failed for M53061139 (cl_barrett15_82_gs)
no factor found
ERROR: self-test failed for M48629519 (cl_barrett15_83_gs)
no factor found
ERROR: self-test failed for M55069117 (cl_barrett15_69_gs)
no factor found
ERROR: self-test failed for M45448679 (cl_barrett15_83_gs)
no factor found
Self-test statistics
number of tests 30
successful tests 13
no factor found 17
self-test FAILED!
| |
ID: 10213 · Rating: 0 · rate: / Reply Quote | |
Driver problem? What driver is installed? | |
ID: 10214 · Rating: 0 · rate: / Reply Quote | |
Standard AMD drivers, version 24.10.1 | |
ID: 10215 · Rating: 0 · rate: / Reply Quote | |
Standard AMD drivers, version 24.10.1 If other projects are running with the card then we need an update soon for mfakto. The devs are working on it with 6000+ serie. Our coder has tested it on a smaller 6xxx card and it was working. | |
ID: 10216 · Rating: 0 · rate: / Reply Quote | |
Looks like my self-tests are indeed failing - problem being that they didn't use to fail before: Microsoft has the infuriating habit of overwriting AMD drivers (perhaps even Nvidia drivers and Intel drivers too) with their own castrated (no OpenCL) versions. My RX 6400 card only produces errors on TF, as does the Radeon 780M IGP of my Ryzen 7 8700G. Where is that mfakto.ini that I need to update? Why don't the developers show a more pro-active attitude? If AMD launches a new range of APUs and/or cards, they will be used. | |
ID: 10228 · Rating: 0 · rate: / Reply Quote | |
Standard AMD drivers, version 24.10.1 The 7000-series is out and the 8000-series is waiting round the corner. Time for an app that is based upon capabilities, not an entry in an *.ini file. | |
ID: 10229 · Rating: 0 · rate: / Reply Quote | |
Standard AMD drivers, version 24.10.1 Its still in testing and need another kernel file to run. | |
ID: 10231 · Rating: 0 · rate: / Reply Quote | |
If you want to try to test with beta1, run | |
ID: 10234 · Rating: 0 · rate: / Reply Quote | |
Tested Beta 1 on my RX 6600 - the vast majority of the tests passed, but not all:
Self-test statistics
number of tests 34026
successful tests 32619
no factor found 1407
self-test FAILED!
ERROR: self-test failed, exiting. | |
ID: 10236 · Rating: 0 · rate: / Reply Quote | |
Tested Beta 1 on my RX 6600 - the vast majority of the tests passed, but not all: thx, reported. | |
ID: 10237 · Rating: 0 · rate: / Reply Quote | |
Tested Beta 1 on my RX 6600 - the vast majority of the tests passed, but not all: Can you test with GPUtye=RDNA instead auto in inifile? Pls also post the gputype gfx<xxxx> | |
ID: 10241 · Rating: 0 · rate: / Reply Quote | |
Tested Beta 1 on my RX 6600 - the vast majority of the tests passed, but not all: Sorry for the delay, I didn't get any notifications. As for my last test setting GPUtype to RDNA, first, the GPU type which would be "gfx1032":
Runtime options
INI file mfakto.ini
Verbosity 1
SieveOnGPU yes
MoreClasses yes
GPUSievePrimes 81157
GPUSieveProcessSize 24 Kib
GPUSieveSize 96 Mib
FlushInterval 0
WorkFile worktodo.txt
ResultsFile results.txt
JSONResultsFile results.json.txt
LogFile mfakto.log
Checkpoints enabled
CheckpointDelay 300 s
Stages enabled
StopAfterFactor bitlevel
PrintMode compact
Logging disabled
V5UserID none
ComputerID none
TimeStampInResults yes
VectorSize 2
GPUType RDNA
SmallExp no
UseBinfile mfakto_Kernels.elf
Compile-time options
Select device - Get device info:
OpenCL device info
name gfx1032 (Advanced Micro Devices, Inc.)
device (driver) version OpenCL 2.0 AMD-APP (3628.0) (3628.0 (PAL,LC))
maximum threads per block 1024
maximum threads per grid 1073741824
number of multiprocessors 14 (896 compute elements)
clock rate 2044 MHz
Automatic parameters
threads per grid 0
optimizing kernels for RDNA
And second, the results - all the same tests that failed last time failed this time as well:
Self-test statistics
number of tests 34026
successful tests 32619
no factor found 1407
self-test FAILED!
ERROR: self-test failed, exiting.
| |
ID: 10252 · Rating: 0 · rate: / Reply Quote | |
beta2 could run but not released yet, we need to wait... but thx for the info, forwarded for further development | |
ID: 10253 · Rating: 0 · rate: / Reply Quote | |
Looks like my self-tests are indeed failing - problem being that they didn't use to fail before: Any answers yet? | |
ID: 10259 · Rating: 0 · rate: / Reply Quote | |
Looks like my self-tests are indeed failing - problem being that they didn't use to fail before: no news yet. | |
ID: 10260 · Rating: 0 · rate: / Reply Quote | |
beta2 is now available for download, pls retest with this version | |
ID: 10264 · Rating: 0 · rate: / Reply Quote | |
beta2 is now available for download, pls retest with this version Just tested the beta 2, the exact same 1407 tests failed. | |
ID: 10266 · Rating: 0 · rate: / Reply Quote | |
Message boards :
Number crunching :
Constant calculation errors since the server crash and restoration