Prime95 version 29.4

[primesearcher]

The latest Prime95 version that work for me is "Prime95 29.5 B5". Any version after "29.5 B5", till "29.6 Build 1" bring this message in the log, under all four CPU cores - "No FFT lengths available in the range specified". Whether my CPU is not supported anymore, bug or something else?

CPU: AMD Athlon X4 880K
OS: Windows 10 Enterprise x64, Version 1809 (OS Build 17763.316)

[Prime95]

Originally Posted by primesearcher

Whether my CPU is not supported anymore, bug or something else?

CPU: AMD Athlon X4 880K
OS: Windows 10 Enterprise x64, Version 1809 (OS Build 17763.316)

Bug.

In 29.5b5 or 29.6 what do you see in the main window at startup. Somthing like "optimizing for ....... architecture". In Options/CPU, what features and cache sizes are reported?

Which torture test are you running or are you running benchmarks? What settings are you using in the dialog box?

[primesearcher]

Originally Posted by Prime95

Bug.

In 29.5b5 or 29.6 what do you see in the main window at startup. Somthing like "optimizing for ....... architecture". In Options/CPU, what features and cache sizes are reported?

Which torture test are you running or are you running benchmarks? What settings are you using in the dialog box?

I see Optimizing for "AMD Bulldozer, L2 cache size: 2x2 MB"
attached image

I run everyting on default setting - "Just Stress Testing-->Blend(all of the above)"
attached image

In Options/CPU
attached image

What I found now is, when enable check box "Disable AVX", everything run smooth with no errors.
attached image

[Prime95]

Fixed in 29.6 build 2

Note that for the first time ever Bulldozer users can torture test using FMA3 and AVX FFTs. However, you may find the SSE2 FFTs are more stressful.

[nickstrauss]

I downloaded the linux64 executable and it runs ok.

I built from source and getting error messages:

[Comm thread Feb 22 21:09] <= Recv header: X-Powered-By: PHP/7.1.10
[Comm thread Feb 22 21:09] <= Recv header: Date: Sat, 23 Feb 2019 03:09:34 GMT
[Comm thread Feb 22 21:09] <= Recv header: Content-Length: 84
[Comm thread Feb 22 21:09] <= Recv header:
[Comm thread Feb 22 21:09] <= Recv data: pnErrorResult=7
[Comm thread Feb 22 21:09] pnErrorDetail=parameter ss: Invalid int value/precision ''
[Comm thread Feb 22 21:09] ==END==
[Comm thread Feb 22 21:09]
[Comm thread Feb 22 21:09] == Info: Connection #0 to host v5.mersenne.org left intact
[Comm thread Feb 22 21:09] RESPONSE:
[Comm thread Feb 22 21:09] pnErrorResult=7
[Comm thread Feb 22 21:09] pnErrorDetail=parameter ss: Invalid int value/precision ''
[Comm thread Feb 22 21:09] ==END==
[Comm thread Feb 22 21:09]
[Comm thread Feb 22 21:09] PrimeNet error 7: Invalid parameter
[Comm thread Feb 22 21:09] parameter ss: Invalid int value/precision ''
[Comm thread Feb 22 21:09] Visit http://mersenneforum.org for help.
[Comm thread Feb 22 21:09] Will try contacting server again in 70 minutes.

[kriesel]

The following worker window contents appeared on an i7-7500U system (Win10 Home, 8GB ram) running prime95 V29.4b8 x64.
The software would give completion time estimates in File, Status, but could not run the P-1 assignment that it estimated time for.
Maybe some build of prime95 could check feasibility of a manually inserted assignment and warn the user, during status output, before it comes up as the current work, and stalls a worker?
This system previously completed a 503M P-1 run.
The Intel spec sheet indicates this processor includes AVX2.
https://ark.intel.com/content/www/us...-3-50-ghz.html

Prime95 indicates SSE, SSE2, SSE4, AVX, AVX2, FMA.

[Mar 16 12:59:16] Worker starting
[Mar 16 12:59:16] Setting affinity to run worker on CPU core #1
[Mar 16 12:59:16] Optimal P-1 factoring of M605000003 using up to 4096MB of memory.
[Mar 16 12:59:16] Assuming no factors below 2^84 and 2 primality tests saved if a factor is found.
[Mar 16 12:59:19] Optimal bounds are B1=4100000, B2=66625000
[Mar 16 12:59:19] Chance of finding a factor is an estimated 3.14%
[Mar 16 12:59:19] Cannot initialize FFT code, errcode=1002
[Mar 16 12:59:19] Worker stopped.
[Mar 20 11:31:42] Worker starting
[Mar 20 11:31:42] Setting affinity to run worker on CPU core #1
[Mar 20 11:31:42] Optimal P-1 factoring of M605000003 using up to 4096MB of memory.
[Mar 20 11:31:42] Assuming no factors below 2^84 and 2 primality tests saved if a factor is found.
[Mar 20 11:31:43] Optimal bounds are B1=4100000, B2=66625000
[Mar 20 11:31:43] Chance of finding a factor is an estimated 3.14%
[Mar 20 11:31:43] Cannot initialize FFT code, errcode=1002
[Mar 20 11:31:43] Worker stopped.

The same fft error code appears on an i7-8750H system (Win10 Home, 16GB ram, 8GB available to prime95) on prime95 V29.4b8 or v29.6b7.
https://ark.intel.com/content/www/us...-4-10-ghz.html
From prime95 V29.6b7 on i7-8750H:

Mar 20 12:30] Worker starting
[Mar 20 12:30] Setting affinity to run worker on CPU core #1
[Mar 20 12:30] Optimal P-1 factoring of M605000003 using up to 8MB of memory.
[Mar 20 12:30] Assuming no factors below 2^84 and 2 primality tests saved if a factor is found.
[Mar 20 12:30] Optimal bounds are B1=5720000, B2=5720000
[Mar 20 12:30] Chance of finding a factor is an estimated 1.83%
[Mar 20 12:30] Cannot initialize FFT code, errcode=1002
[Mar 20 12:30] Worker stopped.

Prime95 indicates SSE, SSE2, SSE4, AVX, AVX2, FMA.

[PhilF]

The 8750H is configured for 8MB memory, not 8GB.

[kriesel]

Originally Posted by PhilF

The 8750H is configured for 8MB memory, not 8GB.

Nope. Well, upon review it looks like I missed that adjustment in the one case, i7-8750H v29.6b7 test, but had set 8192MB in the 29.4b8 trial on the same system, and they both failed the same way. Max system ram would be 32GB on the system involved. Mine came with 16GB installed. I changed the prime95 settings from the puny 8MB default to 8192MB (half of installed RAM) in preparation for running P-1 on midrange exponents (~300-500M). P-1 benefits from a lot of memory. The default 8MB starves it. Even at 1GB vs 2GB, or 4 to 8GB, on a gpu, I see benefit. I have another system with the prime95 limit set at 32GB. It helps stage 2 considerably.

Here's the i7-8750H V29.6b7 x64 prime95 run twice more, with 8MB and 8192MB allowed for P-1; bounds change, probability changes, error code does not. It just can't run the exponent/ fft length, and memory allocation doesn't matter.

[Mar 20 17:39] Worker starting
[Mar 20 17:39] Setting affinity to run worker on CPU core #1
[Mar 20 17:39] Optimal P-1 factoring of M605000003 using up to 8MB of memory.
[Mar 20 17:39] Assuming no factors below 2^84 and 2 primality tests saved if a factor is found.
[Mar 20 17:39] Optimal bounds are B1=5720000, B2=5720000
[Mar 20 17:39] Chance of finding a factor is an estimated 1.83%
[Mar 20 17:39] Cannot initialize FFT code, errcode=1002
[Mar 20 17:39] Worker stopped.
[Mar 20 17:40] Worker starting
[Mar 20 17:40] Setting affinity to run worker on CPU core #1
[Mar 20 17:40] Optimal P-1 factoring of M605000003 using up to 8192MB of memory.
[Mar 20 17:40] Assuming no factors below 2^84 and 2 primality tests saved if a factor is found.
[Mar 20 17:40] Optimal bounds are B1=4290000, B2=86872500
[Mar 20 17:40] Chance of finding a factor is an estimated 3.31%
[Mar 20 17:40] Cannot initialize FFT code, errcode=1002
[Mar 20 17:40] Worker stopped.

[PhilF]

Are the Affinity settings in local.txt honored when doing benchmarks?

[Prime95]

Originally Posted by PhilF

Are the Affinity settings in local.txt honored when doing benchmarks?

I don't remember. Try AffinityVerbosityBench=1 in prime.txt.

[kriesel]

V29.4 has been superseded by a few versions, and 29.8b6 has been out a while. At what point does a thread like this one get unstickied?