[QUOTE=Prime95;590042]Try work preference of 155. It's been there all along, probably never been tested.[/QUOTE]Tried it in mprime, which accepts the preference without question, but then when it contacts the server for new work:[quote][COLOR="blue"][Work thread Oct 11 21:26] Running Jacobi error check.[/COLOR] [Oct 11 21:26] Getting assignment from server
[Comm thread Oct 11 21:26] PrimeNet success code with additional info:
[Comm thread Oct 11 21:26]
[Comm thread Oct 11 21:26] Got assignment 17FE[SPOILER]--yes-I-masked-the-aid--[/SPOILER]F9CE: [COLOR="Red"]Unknown work type M58874623[/COLOR]
[Comm thread Oct 11 21:26] Received unknown work type: 151.
[Comm thread Oct 11 21:26] Visit [url]http://mersenneforum.org[/url] for help.
[Comm thread Oct 11 21:26] Will try contacting server again in 70 minutes.
[COLOR="Blue"][Work thread] Passed. Time: 23.059 sec.[/COLOR][/quote]Worktype 151 = [c]Double-check prime tests[/c] so I'm not sure why it's calling it unknown.
But it's also claiming to receive a worktype of [c]M58874623[/c] which clearly is not right.
Note that these exponents have been [url=https://www.mersenne.org/report_exponent/?exp_lo=58874623&full=1]assigned to me[/url] as a PRP double-check on the server, but did not get added to worktodo.txt because mprime believes the assignment line to be invalid.

Also minor complaint -- the above is not a copy-paste error, the primenet server communication really does happen in the middle of the Jacobi error check leading to confused mixed messages from [COLOR="blue"]work-thread[/COLOR] and comm-thread on same lines.

All the above behavior is the same in both v30.6b4 and v30.7b4

[QUOTE=James Heinrich;590192]Tried it in mprime, which accepts the preference without question, but then when it contacts the server for new work:Worktype 151 = [c]Double-check prime tests[/c] so I'm not sure why it's calling it unknown.
But it's also claiming to receive a worktype of [c]M58874623[/c] which clearly is not right.[/QUOTE]

Try it again. I tweaked the server-side PHP code.

[QUOTE=Prime95;590196]Try it again. I tweaked the server-side PHP code.[/QUOTE]It auto-retried, seems happier now:[quote][Comm thread Oct 11 23:08] Getting assignment from server
[Comm thread Oct 11 23:08] PrimeNet success code with additional info:
[Comm thread Oct 11 23:08] Server assigned PRPDC work.
[Comm thread Oct 11 23:08] Got assignment E422[SPOILER]000000000000000000000000[/SPOILER]19AD: PRPDC M58876087
[Comm thread Oct 11 23:08] Sending expected completion date for M58876087: Oct 18 2021
[Comm thread Oct 11 23:08] Done communicating with server.[/quote]

[QUOTE=kruoli;590157]The save file gets used, it nearly immediately goes to "Conversion of stage 1 result complete". No "optimal B2..." message appears. In fact, there is no mention at all what B2 is going to be used. Only the result uncovers: B2=100*B1 gets used, which is neither optimal nor the B2 stated in the worktodo.txt.[/QUOTE]

Optimal B2 does not work when continuing from an existing save file. For one, the previous B2 may be beyond the optimal B2. I believe optimal B2 will work if you extend B1 past the previous B2.

Anyway, I've corrected (in 30.7 build 5) the problem where the B2 supplied in worktodo.txt is replaced by 100 * B1.

[QUOTE=Prime95;590120]Please tell me your current worker/#cores configuration.
Then tell me which number(s) you try to change to reproduce the problem.[/QUOTE]
See the attachment below for details (the video inside the 7z file). The bug is really strange because I couldn't find any variable in prime.txt and local.txt which equals to 3.

Hmm, previous stable version of mprime observed this entry in prime.txt:

[CODE]
^C[Main thread Oct 13 14:57] Stopping all worker windows.
[Work thread Oct 13 14:57] Worker stopped.
[Main thread Oct 13 14:57] Execution halted.
[Main thread Oct 13 14:57] Choose Test/Continue to restart.
5

tha@Z170:~/Mersenne30$ cat prime.txt
V24OptionsConverted=1
V30OptionsConverted=1
WGUID_version=2
StressTester=0
UsePrimenet=1
DialUp=0
V5UserID=Tha
OutputIterations=400000
ResultsFileIterations=999999999
DiskWriteTime=30
NetworkRetryTime=2
NetworkRetryTime2=70
DaysOfWork=3
DaysBetweenCheckins=1
NumBackupFiles=1
SilentVictory=0
Priority=1
RunOnBattery=1
WorkPreference=4

[B]Stage1GCD=0[/B]

[PrimeNet]
Debug=0
ProxyHost=
UploadRateLimit=128
UploadStartTime=00:00
UploadEndTime=24:00
DownloadDailyLimit=1024

[Worker #1]
tha@Z170:~/Mersenne30$ ./mprime -m
[Main thread Oct 13 14:58] Mersenne number primality test program version 30.7
[Main thread Oct 13 14:58] Optimizing for CPU architecture: Core i3/i5/i7, L2 cache size: 4x256 KB, L3 cache size: 8 MB
Main Menu

1. Test/Primenet
2. Test/Workers
3. Test/Status
4. Test/Continue
5. Test/Exit
6. Advanced/Test
7. Advanced/Time
8. Advanced/P-1
9. Advanced/ECM
10. Advanced/Manual Communication
11. Advanced/Unreserve Exponent
12. Advanced/Quit Gimps
13. Options/CPU
14. Options/Resource Limits
15. Options/Preferences
16. Options/Torture Test
17. Options/Benchmark
18. Help/About
19. Help/About PrimeNet Server
Your choice: 4
[Main thread Oct 13 14:58] Starting worker.
[Work thread Oct 13 14:58] Worker starting
[Work thread Oct 13 14:58] Setting affinity to run worker on CPU core #1
[Work thread Oct 13 14:58]
[Work thread Oct 13 14:58] P-1 on M9240013 with B1=2000000, B2=TBD
[Work thread Oct 13 14:58] Setting affinity to run helper thread 1 on CPU core #2
[Work thread Oct 13 14:58] Setting affinity to run helper thread 3 on CPU core #4
[Work thread Oct 13 14:58] Setting affinity to run helper thread 2 on CPU core #3
[Work thread Oct 13 14:58] Using FMA3 FFT length 480K, Pass1=384, Pass2=1280, clm=4, 4 threads
[Work thread Oct 13 15:01] M9240013 stage 1 is 13.86% complete. Time: 174.373 sec.
[Work thread Oct 13 15:04] M9240013 stage 1 is 27.72% complete. Time: 186.784 sec.
[Work thread Oct 13 15:07] M9240013 stage 1 is 41.58% complete. Time: 177.911 sec.
[Work thread Oct 13 15:10] M9240013 stage 1 is 55.44% complete. Time: 176.519 sec.
[Work thread Oct 13 15:13] M9240013 stage 1 is 69.30% complete. Time: 176.450 sec.
[Work thread Oct 13 15:16] M9240013 stage 1 is 83.17% complete. Time: 186.553 sec.
[Work thread Oct 13 15:19] M9240013 stage 1 is 97.03% complete. Time: 183.830 sec.
[Work thread Oct 13 15:20] M9240013 stage 1 complete. 5771292 transforms. Total time: 1302.166 sec.
[Work thread Oct 13 15:20] [B]P-1 found a factor in stage #1, B1=2000000.[/B]
[Work thread Oct 13 15:20] M9240013 has a factor: 411692187356691061619881660439392355722667064629522661791 (P-1, B1=2000000)
[Comm thread Oct 13 15:20] Sending result to server: UID: Tha/Z170-m30.7, M9240013 has a factor: 411692187356691061619881660439392355722667064629522661791 (P-1, B1=2000000)
[Comm thread Oct 13 15:20]
[Work thread Oct 13 15:20]
[Work thread Oct 13 15:20] [B]P-1 on M9265469 [/B]with B1=2000000, B2=TBD
[Work thread Oct 13 15:20] Setting affinity to run helper thread 1 on CPU core #2
[/CODE]

George - The Gerbicz error checking needs to be 1% or 1,000,000 whichever is [U]greater[/U] by default. This needs to be editable in the GUI (not just by editing a file) similar to 'iterations between screen outputs:' is in the options > preferences menu.

It would also be nice if both these settings could be configured either by number of iterations [U]or[/U] percentage.

[QUOTE=tha;590405]Hmm, previous stable version of mprime observed this entry in prime.txt:[/QUOTE]

Yes, this was changed. Now, you need to set it to [C]Stage1GCD=-1[/C].

[QUOTE=ZacHFX;590117]No luck with anything there. I'm assuming it's mostly caused by the L3 cache issues reported everywhere. Will see what happens when they fix that sometime in the next few weeks.[/QUOTE]

I'm happy to report that after an update today, whatever problems Win11 was having with Prime95 on my Ryzen seem to have been fixed. I'm back to my old iterations/s.

[QUOTE=rainchill;590408]George - The Gerbicz error checking needs to be 1% or 1,000,000 whichever is [U]greater[/U] by default.[/quote]

Why?

[quote]This needs to be editable in the GUI (not just by editing a file) similar to 'iterations between screen outputs:' is in the options > preferences menu.

It would also be nice if both these settings could be configured either by number of iterations [U]or[/U] percentage.[/QUOTE]

Why?

Why not time based? Like Gerbicz roughly once an hour so that I don't lose too much work.

Actually, you are the first person to ask for this. If so few people care, it seems like a good option to leave to manually editing the prime.txt file.

[QUOTE=Zhangrc;590369]See the attachment below for details (the video inside the 7z file). The bug is really strange because I couldn't find any variable in prime.txt and local.txt which equals to 3.[/QUOTE]

I see it, but still cannot reproduce it.

Do you have any workers set to 100M digit testing? There is some strange code in prime95 that forces this work to be multi-threaded to reduce the amount of abandoned 100Mdigit tests.

Try sending me prime.txt, local.txt and I'll try to reproduce again. Weird.