Yes, but end results still the same:

https://srbase.my-firewall.org/sr5/result.php?resultid=146304058

Let me know what I need to do next.

Thanx, Skip

Here's the bottom of test.log:

######### test case 34070/34071 (M332196671[91-92]) ######### Starting trial factoring M332196671 from 2^91 to 2^92 (1509608.98 GHz-days) Date Time | class Pct | time ETA | GHz-d/day Sieve Wait Mar 21 16:50 | 484 0.1% | 0.009 n.a. | n.a. 82486 0.00% M332196671 has a factor: 3466064070766392947648319689 (91.485357 bits, 732699.112106 GHz-d) found 1 factor for M332196671 from 2^91 to 2^92 [mfakto 0.15pre8 cl_barrett32_92_gs_2] self-test for M332196671 passed (cl_barrett32_92_gs)! tf(): total time spent: 0.009s ######### test case 34071/34071 (M112404491[91-92]) ######### Starting trial factoring M112404491 from 2^91 to 2^92 (4461450.54 GHz-days) Date Time | class Pct | time ETA | GHz-d/day Sieve Wait Mar 21 16:50 | 1848 0.1% | 0.009 n.a. | n.a. 82486 0.00% M112404491 has a factor: 3941616367695054034124905537 (91.670846 bits, 2992945.937358 GHz-d) found 1 factor for M112404491 from 2^91 to 2^92 [mfakto 0.15pre8 cl_barrett32_92_gs_2] self-test for M112404491 passed (cl_barrett32_92_gs)! tf(): total time spent: 0.009s Self-test statistics number of tests 34026 successful tests 34026 self-test PASSED!

So, Do I have a wrapper problem?

In my case it is a vega20 (radeon VII)

TF v0.17 (opencl_ati_101) was running fine last year.

done. failed.

./mfakto-x64 -st


######### test case 34071/34071 (M112404491[91-92]) #########
Starting trial factoring M112404491 from 2^91 to 2^92 (4461450.54 GHz-days)
Date Time | class Pct | time ETA | GHz-d/day Sieve Wait
Mar 21 19:45 | 1848 0.1% | 0.010 n.a. | n.a. 82486 0.00%
M112404491 has a factor: 3941616367695054034124905537 (91.670846 bits, 2992945.937358 GHz-d)

found 1 factor for M112404491 from 2^91 to 2^92 [mfakto 0.15pre8 cl_barrett32_92_gs_2]
self-test for M112404491 passed (cl_barrett32_92_gs)!
tf(): total time spent: 0.011s

Self-test statistics
number of tests 34026
successful tests 33288
no factor found 738

self-test FAILED!

ERROR: self-test failed, exiting.

The same for me on a VII.
All end with error, exit code 195

Can you also be running a selftest, unfortunately most of the issues coming from linux where windows has no problems.

./mfakto -st

We need to collect some datas and track down the issue.

Sure, but I need more instruction where or how to do this selftest.
In the terminal the command is unknown. In the project folder there is also no mfakto file.

I can offer this:

<core_client_version>7.16.6</core_client_version>
<![CDATA[
<message>
process exited with code 195 (0xc3, -61)</message>
<stderr_txt>
2024-03-21 14:29:27 (291202): wrapper (7.24.26018): starting
2024-03-21 14:29:27 (291202): wrapper (7.24.26018): starting
2024-03-21 14:29:27 (291202): wrapper: running ./mfakto-x64 (-d 0)
2024-03-21 14:29:27 (291202): wrapper: created child process 291204
2024-03-21 14:29:28 (291202): ./mfakto-x64 exited; CPU time 0.002019
2024-03-21 14:29:28 (291202): app exit status: 0x1
2024-03-21 14:29:28 (291202): called boinc_finish(195)

</stderr_txt>
]]>

./mfakto-x64 -st is also not working. Maybe the needed app was not downloaded in the project folder? There is only a mfakto-linux64-v10.zip file. Shall I upzip this?

The same for me on a VII.
All end with error, exit code 195

more recent result that's (as of this minute) still visible:

https://srbase.my-firewall.org/sr5/result.php?resultid=146304034

The same for me on a VII.
All end with error, exit code 195

your cuda100 app P100s are now failing with this:

./mfaktc.exe: error while loading shared libraries: libcudart.so.10.1: cannot open shared object file: No such file or directory

maybe you removed the cuda toolkit?

I wanted to try v32, but even after resetting the project in the client, the server only sent me v28 cuda100 tasks. Oddly enough, the cuda100 tasks used to work on the P100 but now they don't. So I put this as an app_config.xml:

<app_config> <app_version> <app_name>TF</app_name> <plan_class>cuda120</plan_class> <min_gpu_ram_mb>384</min_gpu_ram_mb> <gpu_ram_used_mb>384</gpu_ram_used_mb> <gpu_peak_flops_scale>0.22</gpu_peak_flops_scale> <cpu_frac>0.01</cpu_frac> </app_version> </app_config>

Now I can run the new v32 and it works fine, but the app_config has to be used at least on this particular computer. I have not tried the rest yet.

EDIT: Actually, I spoke too soon. This app_config does NOT prevent the download of v28 cuda100 tasks. So I'm still not able to run all my GPUs.

you need to add support for every cc level explicitly.

the whole section would be something like this:

--generate-code arch=compute_50,code=sm_50 --generate-code arch=compute_52,code=sm_52 --generate-code arch=compute_60,code=sm_60 --generate-code arch=compute_62,code=sm_62 --generate-code arch=compute_70,code=sm_70 --generate-code arch=compute_75,code=sm_75 --generate-code arch=compute_72,code=sm_72 --generate-code arch=compute_80,code=sm_80 --generate-code arch=compute_86,code=sm_86 --generate-code arch=compute_89,code=sm_89

plus whatever other flags you have there