Trial Factoring

Author	Message
rebirther Volunteer moderator Project administrator Project developer Project tester Project scientist Send message Joined: 2 Jan 13 Posts: 7479 Credit: 43,656,417 RAC: 40,627	Message 5990 - Posted: 2 Apr 2020, 19:59:00 UTC Last modified: 2 Apr 2020, 20:01:38 UTC
There will be a new batch 77-78bit needed by GIMPs: - runtime 16,5h (@RX5500 XT) - 49500 credits - deadline 8d (+1d grace_period) - 10k WUs
ID: 5990 · Rating: 0 · rate: / Reply Quote

RFGuy_KCCO Send message Joined: 2 Dec 14 Posts: 10 Credit: 1,252,818,983 RAC: 0	Message 6001 - Posted: 4 Apr 2020, 5:56:09 UTC - in response to Message 5990.
There will be a new batch 77-78bit needed by GIMPs: - runtime 16,5h (@RX5500 XT) - 49500 credits - deadline 8d (+1d grace_period) - 10k WUs 16+ hours per WU? If that is correct, you're going to have to give more than 49,500 points per WU. Not worth running it at those rates, unless someone just loves this project. ____________
ID: 6001 · Rating: 0 · rate: / Reply Quote

rebirther Volunteer moderator Project administrator Project developer Project tester Project scientist Send message Joined: 2 Jan 13 Posts: 7479 Credit: 43,656,417 RAC: 40,627	Message 6003 - Posted: 4 Apr 2020, 6:01:22 UTC - in response to Message 6001.
There will be a new batch 77-78bit needed by GIMPs: - runtime 16,5h (@RX5500 XT) - 49500 credits - deadline 8d (+1d grace_period) - 10k WUs 16+ hours per WU? If that is correct, you're going to have to give more than 49,500 points per WU. Not worth running it at those rates, unless someone just loves this project. The nvidia 2070 do this in 3,5h
ID: 6003 · Rating: 0 · rate: / Reply Quote

Luigi R. Send message Joined: 17 Jul 18 Posts: 21 Credit: 35,672,299 RAC: 13	Message 6009 - Posted: 4 Apr 2020, 8:14:39 UTC
Rebirther, maybe you should write on News when you increase TF exponent. 77-78 are very long on my gpu (GTX1060).
ID: 6009 · Rating: 0 · rate: / Reply Quote

Luigi R. Send message Joined: 17 Jul 18 Posts: 21 Credit: 35,672,299 RAC: 13	Message 6010 - Posted: 4 Apr 2020, 8:17:47 UTC - in response to Message 6001.
Not worth running it at those rates, unless someone just loves this project. Me. :)
ID: 6010 · Rating: 0 · rate: / Reply Quote

rebirther Volunteer moderator Project administrator Project developer Project tester Project scientist Send message Joined: 2 Jan 13 Posts: 7479 Credit: 43,656,417 RAC: 40,627	Message 6011 - Posted: 4 Apr 2020, 8:24:44 UTC - in response to Message 6009.
Rebirther, maybe you should write on News when you increase TF exponent. 77-78 are very long on my gpu (GTX1060). was below, its different now, the next batches are for 75,76,77
ID: 6011 · Rating: 0 · rate: / Reply Quote

Hal Bregg Send message Joined: 7 Aug 19 Posts: 23 Credit: 6,059,933 RAC: 0	Message 6013 - Posted: 4 Apr 2020, 9:59:45 UTC - in response to Message 6003. Last modified: 4 Apr 2020, 10:29:03 UTC
There will be a new batch 77-78bit needed by GIMPs: - runtime 16,5h (@RX5500 XT) - 49500 credits - deadline 8d (+1d grace_period) - 10k WUs 16+ hours per WU? If that is correct, you're going to have to give more than 49,500 points per WU. Not worth running it at those rates, unless someone just loves this project. The nvidia 2070 do this in 3,5h Split the tasks for longer and shorter ones. And put in FAQ 'top rage card required for long tasks' or something like that. It will make clear who should try to crunch the project.
ID: 6013 · Rating: 0 · rate: / Reply Quote

rebirther Volunteer moderator Project administrator Project developer Project tester Project scientist Send message Joined: 2 Jan 13 Posts: 7479 Credit: 43,656,417 RAC: 40,627	Message 6014 - Posted: 4 Apr 2020, 10:17:10 UTC - in response to Message 6013.
There will be a new batch 77-78bit needed by GIMPs: - runtime 16,5h (@RX5500 XT) - 49500 credits - deadline 8d (+1d grace_period) - 10k WUs 16+ hours per WU? If that is correct, you're going to have to give more than 49,500 points per WU. Not worth running it at those rates, unless someone just loves this project. The nvidia 2070 do this in 3,5h Split the tasks for long and shorter ones. And put in FAQ 'top rage card required for long tasks' or something like that. It will make clear who should try to crunch the project. Sorry, this is not planned, the next batch is smaller and you can use the checkpoints, the deadline is high enough.
ID: 6014 · Rating: 0 · rate: / Reply Quote

forretrio Send message Joined: 28 Nov 16 Posts: 7 Credit: 25,040,159 RAC: 0	Message 6015 - Posted: 4 Apr 2020, 10:31:46 UTC
Came here to check why the new batch is taking me up to 8 hours (1650) to complete and whoa I didn't expect a mix between 10 minutes tasks and 8+ hours task. Should I expect some long batches in the future? ____________
ID: 6015 · Rating: 0 · rate: / Reply Quote

Hal Bregg Send message Joined: 7 Aug 19 Posts: 23 Credit: 6,059,933 RAC: 0	Message 6016 - Posted: 4 Apr 2020, 10:33:28 UTC - in response to Message 6014.
There will be a new batch 77-78bit needed by GIMPs: - runtime 16,5h (@RX5500 XT) - 49500 credits - deadline 8d (+1d grace_period) - 10k WUs 16+ hours per WU? If that is correct, you're going to have to give more than 49,500 points per WU. Not worth running it at those rates, unless someone just loves this project. The nvidia 2070 do this in 3,5h Split the tasks for longer and shorter ones. And put in FAQ 'top rage card required for long tasks' or something like that. It will make clear who should try to crunch the project. Sorry, this is not planned, the next batch is smaller and you can use the checkpoints, the deadline is high enough. No worries, reb. I thought it would help to stop unnecessarily whining about credits and running times.
ID: 6016 · Rating: 0 · rate: / Reply Quote

KEP Volunteer tester Send message Joined: 28 Nov 14 Posts: 92 Credit: 1,102,770 RAC: 0	Message 6017 - Posted: 4 Apr 2020, 11:09:20 UTC - in response to Message 6015. Last modified: 4 Apr 2020, 11:11:46 UTC
Came here to check why the new batch is taking me up to 8 hours (1650) to complete and whoa I didn't expect a mix between 10 minutes tasks and 8+ hours task. Should I expect some long batches in the future? Yes, it is with Trial Factoring (TF), as is what GPU72 is doing, in order to help GIMPs (Great Internet Mersenne Prime search) boost their search, the same as primetesting, test takes longer the higher the bit. We started out with very small tests, because of testing of setup and software. Now that we have gone in to production phase, it was requested by GPU72 that we took 10000 task that could finish the last needed bit to be trialfactored, so they could be released to a different kind of factoring (P-1) and eventually thereafter to Primality testing. It is more or less (dependant on hardware) such that everytime you increse 1 bit, the task doubles in runtime if the n stays the same. Once everything works, it might be a good idea (if possible) to set up a project, for small tasks and for long running tasks.
ID: 6017 · Rating: 0 · rate: / Reply Quote

mmonnin Send message Joined: 1 Feb 17 Posts: 30 Credit: 544,175,973 RAC: 50,156	Message 6018 - Posted: 4 Apr 2020, 13:10:32 UTC
On my GPU its 16.5x more credit and 17x longer so about in line with the 3k credit tasks. The 1500 credit tasks gave a bit more credit/hour.
ID: 6018 · Rating: 0 · rate: / Reply Quote

rebirther Volunteer moderator Project administrator Project developer Project tester Project scientist Send message Joined: 2 Jan 13 Posts: 7479 Credit: 43,656,417 RAC: 40,627	Message 6020 - Posted: 4 Apr 2020, 13:39:33 UTC
After checking with other projects I will increase the credits for all new batches by a factor of 3.3
ID: 6020 · Rating: 0 · rate: / Reply Quote

rebirther Volunteer moderator Project administrator Project developer Project tester Project scientist Send message Joined: 2 Jan 13 Posts: 7479 Credit: 43,656,417 RAC: 40,627	Message 6023 - Posted: 4 Apr 2020, 16:47:12 UTC
The windows opencl app was updated to the latest version.
ID: 6023 · Rating: 0 · rate: / Reply Quote

RFGuy_KCCO Send message Joined: 2 Dec 14 Posts: 10 Credit: 1,252,818,983 RAC: 0	Message 6024 - Posted: 4 Apr 2020, 20:06:23 UTC - in response to Message 6020.
After checking with other projects I will increase the credits for all new batches by a factor of 3.3 Awesome! Thank you!
ID: 6024 · Rating: 0 · rate: / Reply Quote

VietOZ Send message Joined: 7 Apr 17 Posts: 3 Credit: 1,248,606,969 RAC: 0	Message 6025 - Posted: 4 Apr 2020, 20:18:21 UTC - in response to Message 6023.
The windows opencl app was updated to the latest version. Error on my 5700XT Stderr output <core_client_version>7.14.2</core_client_version> <![CDATA[ <message> (unknown error) - exit code 195 (0xc3)</message> <stderr_txt> 15:08:48 (2440): wrapper (7.5.26012): starting 15:08:48 (2440): wrapper: running mfakto.exe () mfakto 0.15pre6-Win (64bit build) Runtime options Inifile mfakto.ini Verbosity 1 SieveOnGPU yes MoreClasses yes GPUSievePrimes 82486 GPUSieveProcessSize 24Ki bits GPUSieveSize 96Mi bits FlushInterval 8 WorkFile worktodo.txt ResultsFile results.txt Checkpoints enabled CheckpointDelay 300s Stages enabled StopAfterFactor class PrintMode compact V5UserID none ComputerID none TimeStampInResults no VectorSize 2 GPUType AUTO SmallExp no UseBinfile mfakto_Kernels.elf Compiletime options Select device - Get device info: WARNING: Unknown GPU name, assuming GCN. Please post the device name "gfx1010 (Advanced Micro Devices, Inc.)" to http://www.mersenneforum.org/showthread.php?t=15646 to have it added to mfakto. Set GPUType in mfakto.ini to select a GPU type yourself to avoid this warning. OpenCL device info name gfx1010 (Advanced Micro Devices, Inc.) device (driver) version OpenCL 2.0 AMD-APP (3004.5) (3004.5 (PAL,LC)) maximum threads per block 1024 maximum threads per grid 1073741824 number of multiprocessors 20 (1280 compute elements) clock rate 1830MHz Automatic parameters threads per grid 0 optimizing kernels for GCN Loading binary kernel file mfakto_Kernels.elf Compiling kernels. BUILD OUTPUT Error: AMD HSA Code Object loading failed. END OF BUILD OUTPUT Error -11 (Build program failure): clBuildProgram ERROR: load_kernels(0) failed 15:08:49 (2440): mfakto.exe exited; CPU time 0.000000 15:08:49 (2440): app exit status: 0x2 15:08:49 (2440): called boinc_finish(195) </stderr_txt> ]]>
ID: 6025 · Rating: 0 · rate: / Reply Quote

rebirther Volunteer moderator Project administrator Project developer Project tester Project scientist Send message Joined: 2 Jan 13 Posts: 7479 Credit: 43,656,417 RAC: 40,627	Message 6026 - Posted: 4 Apr 2020, 21:01:17 UTC - in response to Message 6025.
Strange, I went back to the older version. I have tested this on my 5500XT card without any problems. The program compiles the mfakto_Kernels.elf and its running. I will report this in forum.
ID: 6026 · Rating: 0 · rate: / Reply Quote

VietOZ Send message Joined: 7 Apr 17 Posts: 3 Credit: 1,248,606,969 RAC: 0	Message 6027 - Posted: 4 Apr 2020, 21:51:24 UTC
Still error Stderr output <core_client_version>7.14.2</core_client_version> <![CDATA[ <message> (unknown error) - exit code 195 (0xc3)</message> <stderr_txt> 16:48:30 (9832): wrapper (7.5.26012): starting 16:48:30 (9832): wrapper: running mfakto-x64.exe () mfakto 0.14-Win (64bit build) Runtime options Inifile mfakto.ini Verbosity 1 SieveOnGPU yes MoreClasses yes GPUSievePrimes 82486 GPUSieveProcessSize 24Ki bits GPUSieveSize 96Mi bits FlushInterval 8 WorkFile worktodo.txt ResultsFile results.txt Checkpoints enabled CheckpointDelay 300s Stages enabled StopAfterFactor class PrintMode compact V5UserID none ComputerID none TimeStampInResults no VectorSize 2 GPUType AUTO SmallExp no UseBinfile mfakto_Kernels.elf Compiletime options Select device - Get device info - Compiling kernels. WARNING: Unknown GPU name, assuming GCN. Please post the device name "gfx1010 (Advanced Micro Devices, Inc.)" to http://www.mersenneforum.org/showthread.php?t=15646 to have it added to mfakto. Set GPUType in mfakto.ini to select a GPU type yourself to avoid this warning. OpenCL device info name gfx1010 (Advanced Micro Devices, Inc.) device (driver) version OpenCL 2.0 AMD-APP (3004.5) (3004.5 (PAL,LC)) maximum threads per block 1024 maximum threads per grid 1073741824 number of multiprocessors 20 (1280 compute elements) clock rate 1830MHz Automatic parameters threads per grid 256 optimizing kernels for GCN Started a simple selftest ... ######### testcase 1/17 (M60003157[58-59]) ######### ######### testcase 2/17 (M60008017[58-59]) ######### ######### testcase 3/17 (M60009827[58-59]) ######### ######### testcase 4/17 (M50863909[69-70]) ######### ######### testcase 5/17 (M51375383[69-70]) ######### ######### testcase 6/17 (M51406301[70-71]) ######### ERROR: selftest failed for M51406301 (cl_barrett15_82_gs) no factor found ERROR: selftest failed for M51406301 (cl_barrett15_83_gs) no factor found ERROR: selftest failed for M51406301 (cl_barrett15_88_gs) no factor found ERROR: selftest failed for M51406301 (cl_barrett15_73_gs) no factor found ERROR: selftest failed for M51406301 (cl_barrett32_87_gs) no factor found ERROR: selftest failed for M51406301 (cl_barrett32_88_gs) no factor found ERROR: selftest failed for M51406301 (cl_barrett32_92_gs) no factor found ERROR: selftest failed for M51406301 (cl_barrett32_76_gs) no factor found ERROR: selftest failed for M51406301 (cl_barrett32_77_gs) no factor found ERROR: selftest failed for M51406301 (cl_barrett32_79_gs) no factor found ######### testcase 7/17 (M47644171[70-71]) ######### ######### testcase 8/17 (M51038681[71-72]) ######### ######### testcase 9/17 (M49717271[71-72]) ######### ######### testcase 10/17 (M50752613[72-73]) ######### ######### testcase 11/17 (M50908933[72-73]) ######### ######### testcase 12/17 (M53076719[73-74]) ######### ######### testcase 13/17 (M53123843[74-75]) ######### ######### testcase 14/17 (M60009109[34-35]) ######### ######### testcase 15/17 (M60002273[34-35]) ######### ######### testcase 16/17 (M60004333[63-64]) ######### ######### testcase 17/17 (M3321928703[90-91]) ######### Selftest statistics number of tests 108 successful tests 98 no factor found 10 selftest FAILED! 16:48:39 (9832): mfakto-x64.exe exited; CPU time 0.000000 16:48:39 (9832): app exit status: 0x4 16:48:39 (9832): called boinc_finish(195) </stderr_txt> ]]>
ID: 6027 · Rating: 0 · rate: / Reply Quote

rebirther Volunteer moderator Project administrator Project developer Project tester Project scientist Send message Joined: 2 Jan 13 Posts: 7479 Credit: 43,656,417 RAC: 40,627	Message 6028 - Posted: 5 Apr 2020, 7:10:38 UTC - in response to Message 6027.
Do you have installed AMD SDK?
ID: 6028 · Rating: 0 · rate: / Reply Quote

mmonnin Send message Joined: 1 Feb 17 Posts: 30 Credit: 544,175,973 RAC: 50,156	Message 6030 - Posted: 5 Apr 2020, 12:25:00 UTC - in response to Message 6023.
The windows opencl app was updated to the latest version. All errors with the latest version. No changes on my end. http://srbase.my-firewall.org/sr5/results.php?hostid=205182
ID: 6030 · Rating: 0 · rate: / Reply Quote

Author

Message

rebirther
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist

Send message
Joined: 2 Jan 13
Posts: 7479
Credit: 43,656,417
RAC: 40,627
2M in Sierpinski / Riesel Base credit

5M in Sierpinski / Riesel Base - short credit

1M in Sierpinski / Riesel Base - long credit

500k in Sierpinski / Riesel Base - average credit

There will be a new batch 77-78bit needed by GIMPs:
- runtime 16,5h (@RX5500 XT)
- 49500 credits
- deadline 8d (+1d grace_period)
- 10k WUs

ID: 5990 · Rating: 0 · rate:

Reply Quote

RFGuy_KCCO
Send message
Joined: 2 Dec 14
Posts: 10
Credit: 1,252,818,983
RAC: 0
1M in Sierpinski / Riesel Base credit

1M in Sierpinski / Riesel Base - short credit

10M in Sierpinski / Riesel Base - long credit

2M in Sierpinski / Riesel Base - average credit

There will be a new batch 77-78bit needed by GIMPs:
- runtime 16,5h (@RX5500 XT)
- 49500 credits
- deadline 8d (+1d grace_period)
- 10k WUs

16+ hours per WU? If that is correct, you're going to have to give more than 49,500 points per WU. Not worth running it at those rates, unless someone just loves this project.
____________

ID: 6001 · Rating: 0 · rate:

Reply Quote

rebirther
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist

Send message
Joined: 2 Jan 13
Posts: 7479
Credit: 43,656,417
RAC: 40,627
2M in Sierpinski / Riesel Base credit

There will be a new batch 77-78bit needed by GIMPs:
- runtime 16,5h (@RX5500 XT)
- 49500 credits
- deadline 8d (+1d grace_period)
- 10k WUs

16+ hours per WU? If that is correct, you're going to have to give more than 49,500 points per WU. Not worth running it at those rates, unless someone just loves this project.

The nvidia 2070 do this in 3,5h

ID: 6003 · Rating: 0 · rate:

Reply Quote

Luigi R.

Send message
Joined: 17 Jul 18
Posts: 21
Credit: 35,672,299
RAC: 13
100k in Sierpinski / Riesel Base credit

100k in Sierpinski / Riesel Base - short credit

500k in Sierpinski / Riesel Base - long credit

Rebirther, maybe you should write on News when you increase TF exponent.
77-78 are very long on my gpu (GTX1060).

ID: 6009 · Rating: 0 · rate:

Reply Quote

Luigi R.

Send message
Joined: 17 Jul 18
Posts: 21
Credit: 35,672,299
RAC: 13
100k in Sierpinski / Riesel Base credit

Not worth running it at those rates, unless someone just loves this project.

Me. :)

ID: 6010 · Rating: 0 · rate:

Reply Quote

rebirther
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist

Send message
Joined: 2 Jan 13
Posts: 7479
Credit: 43,656,417
RAC: 40,627
2M in Sierpinski / Riesel Base credit

Rebirther, maybe you should write on News when you increase TF exponent.
77-78 are very long on my gpu (GTX1060).

was below, its different now, the next batches are for 75,76,77

ID: 6011 · Rating: 0 · rate:

Reply Quote

Hal Bregg
Send message
Joined: 7 Aug 19
Posts: 23
Credit: 6,059,933
RAC: 0
10k in Sierpinski / Riesel Base credit

10k in Sierpinski / Riesel Base - short credit

10k in Sierpinski / Riesel Base - average credit

There will be a new batch 77-78bit needed by GIMPs:
- runtime 16,5h (@RX5500 XT)
- 49500 credits
- deadline 8d (+1d grace_period)
- 10k WUs

16+ hours per WU? If that is correct, you're going to have to give more than 49,500 points per WU. Not worth running it at those rates, unless someone just loves this project.

The nvidia 2070 do this in 3,5h

Split the tasks for longer and shorter ones. And put in FAQ 'top rage card required for long tasks' or something like that. It will make clear who should try to crunch the project.

ID: 6013 · Rating: 0 · rate:

Reply Quote

rebirther
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist

Send message
Joined: 2 Jan 13
Posts: 7479
Credit: 43,656,417
RAC: 40,627
2M in Sierpinski / Riesel Base credit

There will be a new batch 77-78bit needed by GIMPs:
- runtime 16,5h (@RX5500 XT)
- 49500 credits
- deadline 8d (+1d grace_period)
- 10k WUs

16+ hours per WU? If that is correct, you're going to have to give more than 49,500 points per WU. Not worth running it at those rates, unless someone just loves this project.

The nvidia 2070 do this in 3,5h

Split the tasks for long and shorter ones. And put in FAQ 'top rage card required for long tasks' or something like that. It will make clear who should try to crunch the project.

Sorry, this is not planned, the next batch is smaller and you can use the checkpoints, the deadline is high enough.

ID: 6014 · Rating: 0 · rate:

Reply Quote

forretrio
Send message
Joined: 28 Nov 16
Posts: 7
Credit: 25,040,159
RAC: 0
500k in Sierpinski / Riesel Base credit

500k in Sierpinski / Riesel Base - short credit

5M in Sierpinski / Riesel Base - long credit

Came here to check why the new batch is taking me up to 8 hours (1650) to complete and whoa I didn't expect a mix between 10 minutes tasks and 8+ hours task. Should I expect *some* long batches in the future?
____________

ID: 6015 · Rating: 0 · rate:

Reply Quote

Hal Bregg
Send message
Joined: 7 Aug 19
Posts: 23
Credit: 6,059,933
RAC: 0
10k in Sierpinski / Riesel Base credit

There will be a new batch 77-78bit needed by GIMPs:
- runtime 16,5h (@RX5500 XT)
- 49500 credits
- deadline 8d (+1d grace_period)
- 10k WUs

16+ hours per WU? If that is correct, you're going to have to give more than 49,500 points per WU. Not worth running it at those rates, unless someone just loves this project.

The nvidia 2070 do this in 3,5h

Split the tasks for longer and shorter ones. And put in FAQ 'top rage card required for long tasks' or something like that. It will make clear who should try to crunch the project.

Sorry, this is not planned, the next batch is smaller and you can use the checkpoints, the deadline is high enough.

No worries, reb. I thought it would help to stop unnecessarily whining about credits and running times.

ID: 6016 · Rating: 0 · rate:

Reply Quote

KEP
Volunteer tester
Send message
Joined: 28 Nov 14
Posts: 92
Credit: 1,102,770
RAC: 0
100k in Sierpinski / Riesel Base credit

10k in Sierpinski / Riesel Base - long credit

100k in Sierpinski / Riesel Base - average credit

Came here to check why the new batch is taking me up to 8 hours (1650) to complete and whoa I didn't expect a mix between 10 minutes tasks and 8+ hours task. Should I expect *some* long batches in the future?

Yes, it is with Trial Factoring (TF), as is what GPU72 is doing, in order to help GIMPs (Great Internet Mersenne Prime search) boost their search, the same as primetesting, test takes longer the higher the bit.

We started out with very small tests, because of testing of setup and software. Now that we have gone in to production phase, it was requested by GPU72 that we took 10000 task that could finish the last needed bit to be trialfactored, so they could be released to a different kind of factoring (P-1) and eventually thereafter to Primality testing.

It is more or less (dependant on hardware) such that everytime you increse 1 bit, the task doubles in runtime if the n stays the same. Once everything works, it might be a good idea (if possible) to set up a project, for small tasks and for long running tasks.

ID: 6017 · Rating: 0 · rate:

Reply Quote

mmonnin
Send message
Joined: 1 Feb 17
Posts: 30
Credit: 544,175,973
RAC: 50,156
2M in Sierpinski / Riesel Base credit

2M in Sierpinski / Riesel Base - short credit

5M in Sierpinski / Riesel Base - average credit

On my GPU its 16.5x more credit and 17x longer so about in line with the 3k credit tasks. The 1500 credit tasks gave a bit more credit/hour.

ID: 6018 · Rating: 0 · rate:

Reply Quote

rebirther
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist

Send message
Joined: 2 Jan 13
Posts: 7479
Credit: 43,656,417
RAC: 40,627
2M in Sierpinski / Riesel Base credit

After checking with other projects I will increase the credits for all new batches by a factor of 3.3

ID: 6020 · Rating: 0 · rate:

Reply Quote

rebirther
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist

Send message
Joined: 2 Jan 13
Posts: 7479
Credit: 43,656,417
RAC: 40,627
2M in Sierpinski / Riesel Base credit

The windows opencl app was updated to the latest version.

ID: 6023 · Rating: 0 · rate:

Reply Quote

RFGuy_KCCO
Send message
Joined: 2 Dec 14
Posts: 10
Credit: 1,252,818,983
RAC: 0
1M in Sierpinski / Riesel Base credit

After checking with other projects I will increase the credits for all new batches by a factor of 3.3

Awesome! Thank you!

ID: 6024 · Rating: 0 · rate:

Reply Quote

VietOZ
Send message
Joined: 7 Apr 17
Posts: 3
Credit: 1,248,606,969
RAC: 0
2M in Sierpinski / Riesel Base credit

1M in Sierpinski / Riesel Base - average credit

The windows opencl app was updated to the latest version.

Error on my 5700XT

Stderr output <core_client_version>7.14.2</core_client_version> <![CDATA[ <message> (unknown error) - exit code 195 (0xc3)</message> <stderr_txt> 15:08:48 (2440): wrapper (7.5.26012): starting 15:08:48 (2440): wrapper: running mfakto.exe () mfakto 0.15pre6-Win (64bit build) Runtime options Inifile mfakto.ini Verbosity 1 SieveOnGPU yes MoreClasses yes GPUSievePrimes 82486 GPUSieveProcessSize 24Ki bits GPUSieveSize 96Mi bits FlushInterval 8 WorkFile worktodo.txt ResultsFile results.txt Checkpoints enabled CheckpointDelay 300s Stages enabled StopAfterFactor class PrintMode compact V5UserID none ComputerID none TimeStampInResults no VectorSize 2 GPUType AUTO SmallExp no UseBinfile mfakto_Kernels.elf Compiletime options Select device - Get device info: WARNING: Unknown GPU name, assuming GCN. Please post the device name "gfx1010 (Advanced Micro Devices, Inc.)" to http://www.mersenneforum.org/showthread.php?t=15646 to have it added to mfakto. Set GPUType in mfakto.ini to select a GPU type yourself to avoid this warning. OpenCL device info name gfx1010 (Advanced Micro Devices, Inc.) device (driver) version OpenCL 2.0 AMD-APP (3004.5) (3004.5 (PAL,LC)) maximum threads per block 1024 maximum threads per grid 1073741824 number of multiprocessors 20 (1280 compute elements) clock rate 1830MHz Automatic parameters threads per grid 0 optimizing kernels for GCN Loading binary kernel file mfakto_Kernels.elf Compiling kernels. BUILD OUTPUT Error: AMD HSA Code Object loading failed. END OF BUILD OUTPUT Error -11 (Build program failure): clBuildProgram ERROR: load_kernels(0) failed 15:08:49 (2440): mfakto.exe exited; CPU time 0.000000 15:08:49 (2440): app exit status: 0x2 15:08:49 (2440): called boinc_finish(195) </stderr_txt> ]]>

ID: 6025 · Rating: 0 · rate:

Reply Quote

rebirther
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist

Send message
Joined: 2 Jan 13
Posts: 7479
Credit: 43,656,417
RAC: 40,627
2M in Sierpinski / Riesel Base credit

Strange, I went back to the older version. I have tested this on my 5500XT card without any problems. The program compiles the mfakto_Kernels.elf and its running. I will report this in forum.

ID: 6026 · Rating: 0 · rate:

Reply Quote

VietOZ
Send message
Joined: 7 Apr 17
Posts: 3
Credit: 1,248,606,969
RAC: 0
2M in Sierpinski / Riesel Base credit

Still error

Stderr output <core_client_version>7.14.2</core_client_version> <![CDATA[ <message> (unknown error) - exit code 195 (0xc3)</message> <stderr_txt> 16:48:30 (9832): wrapper (7.5.26012): starting 16:48:30 (9832): wrapper: running mfakto-x64.exe () mfakto 0.14-Win (64bit build) Runtime options Inifile mfakto.ini Verbosity 1 SieveOnGPU yes MoreClasses yes GPUSievePrimes 82486 GPUSieveProcessSize 24Ki bits GPUSieveSize 96Mi bits FlushInterval 8 WorkFile worktodo.txt ResultsFile results.txt Checkpoints enabled CheckpointDelay 300s Stages enabled StopAfterFactor class PrintMode compact V5UserID none ComputerID none TimeStampInResults no VectorSize 2 GPUType AUTO SmallExp no UseBinfile mfakto_Kernels.elf Compiletime options Select device - Get device info - Compiling kernels. WARNING: Unknown GPU name, assuming GCN. Please post the device name "gfx1010 (Advanced Micro Devices, Inc.)" to http://www.mersenneforum.org/showthread.php?t=15646 to have it added to mfakto. Set GPUType in mfakto.ini to select a GPU type yourself to avoid this warning. OpenCL device info name gfx1010 (Advanced Micro Devices, Inc.) device (driver) version OpenCL 2.0 AMD-APP (3004.5) (3004.5 (PAL,LC)) maximum threads per block 1024 maximum threads per grid 1073741824 number of multiprocessors 20 (1280 compute elements) clock rate 1830MHz Automatic parameters threads per grid 256 optimizing kernels for GCN Started a simple selftest ... ######### testcase 1/17 (M60003157[58-59]) ######### ######### testcase 2/17 (M60008017[58-59]) ######### ######### testcase 3/17 (M60009827[58-59]) ######### ######### testcase 4/17 (M50863909[69-70]) ######### ######### testcase 5/17 (M51375383[69-70]) ######### ######### testcase 6/17 (M51406301[70-71]) ######### ERROR: selftest failed for M51406301 (cl_barrett15_82_gs) no factor found ERROR: selftest failed for M51406301 (cl_barrett15_83_gs) no factor found ERROR: selftest failed for M51406301 (cl_barrett15_88_gs) no factor found ERROR: selftest failed for M51406301 (cl_barrett15_73_gs) no factor found ERROR: selftest failed for M51406301 (cl_barrett32_87_gs) no factor found ERROR: selftest failed for M51406301 (cl_barrett32_88_gs) no factor found ERROR: selftest failed for M51406301 (cl_barrett32_92_gs) no factor found ERROR: selftest failed for M51406301 (cl_barrett32_76_gs) no factor found ERROR: selftest failed for M51406301 (cl_barrett32_77_gs) no factor found ERROR: selftest failed for M51406301 (cl_barrett32_79_gs) no factor found ######### testcase 7/17 (M47644171[70-71]) ######### ######### testcase 8/17 (M51038681[71-72]) ######### ######### testcase 9/17 (M49717271[71-72]) ######### ######### testcase 10/17 (M50752613[72-73]) ######### ######### testcase 11/17 (M50908933[72-73]) ######### ######### testcase 12/17 (M53076719[73-74]) ######### ######### testcase 13/17 (M53123843[74-75]) ######### ######### testcase 14/17 (M60009109[34-35]) ######### ######### testcase 15/17 (M60002273[34-35]) ######### ######### testcase 16/17 (M60004333[63-64]) ######### ######### testcase 17/17 (M3321928703[90-91]) ######### Selftest statistics number of tests 108 successful tests 98 no factor found 10 selftest FAILED! 16:48:39 (9832): mfakto-x64.exe exited; CPU time 0.000000 16:48:39 (9832): app exit status: 0x4 16:48:39 (9832): called boinc_finish(195) </stderr_txt> ]]>

ID: 6027 · Rating: 0 · rate:

Reply Quote

rebirther
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist

Send message
Joined: 2 Jan 13
Posts: 7479
Credit: 43,656,417
RAC: 40,627
2M in Sierpinski / Riesel Base credit

Do you have installed AMD SDK?

ID: 6028 · Rating: 0 · rate:

Reply Quote

mmonnin
Send message
Joined: 1 Feb 17
Posts: 30
Credit: 544,175,973
RAC: 50,156
2M in Sierpinski / Riesel Base credit

The windows opencl app was updated to the latest version.

All errors with the latest version. No changes on my end.
http://srbase.my-firewall.org/sr5/results.php?hostid=205182

ID: 6030 · Rating: 0 · rate:

Reply Quote