Apologies for the double post, but some new things to report;


- [M]8420261[/M] successfully reported to Primenet using 30.8 (B2 = 857xB1? Primality tests saved is set to 10 on these exponents, not sure if that is sane at all but you did mention that B2 should be very high.)
- Indicated completion dates seem to be wildly off, this exponent took only 15 minutes to complete P-1 stage1 & 2 but indicated completion time for the next similar exponent is 5 hrs and 30 minutes.

[QUOTE=Prime95;593894][*]Use much more aggressive B2 bounds. While the optimal B2 calculations may not be perfect I recommend using them anyway.[/QUOTE]

Shall we leave the B1/B2 values in the worktodo file at B2 = 100*B1 so the program will choose the optimum figures for Stage 2, like in previous versions?

It crashes for me with
[CODE]Error code: 0xc0000005
Error offset: 0x0000000002084266[/CODE]
when entering stage 2 with
[CODE]Pminus1=N/A,1,2,21356873,-1,1000000,32400000,75[/CODE]
on Zen 2. Roundoff error check is enabled.

[QUOTE=lisanderke;593901]
- [M]8420261[/M] successfully reported to Primenet using 30.8 (B2 = 857xB1? Primality tests saved is set to 10 on these exponents, not sure if that is sane at all but you did mention that B2 should be very high.)
- Indicated completion dates seem to be wildly off, this exponent took only 15 minutes to complete P-1 stage1 & 2 but indicated completion time for the next similar exponent is 5 hrs and 30 minutes.[/QUOTE]

This looks fine. Yes, time estimates will be wildly off the mark. Tidying up the incorrect 0.0% stage 2 messages and these time estimates have not been worked on -- part of why I call this an emergency pre-beta release. I felt it was important to get these significant improvements into the 20M groups hands ASAP.

[QUOTE=lycorn;593902]Shall we leave the B1/B2 values in the worktodo file at B2 = 100*B1 so the program will choose the optimum figures for Stage 2, like in previous versions?[/QUOTE]

Good plan.

[QUOTE=Prime95;593861]

Sadly, wavefront P-1 will not benefit much. There are only 200 or so temporaries available if given 16GB RAM.
[/QUOTE]
However, for people who have sufficient RAM, like Ben Delo, I think it's better to use 30.8.
I will continue to use 30.7b8, considering that I only give 9GB of RAM to Prime95.

If this is of any help, here are the factor I found 6.2-6.3M with their B1/B2 value

[QUOTE=kruoli;593903]It crashes for me with
[CODE]Error code: 0xc0000005
Error offset: 0x0000000002084266[/CODE]
when entering stage 2 with
[CODE]Pminus1=N/A,1,2,21356873,-1,1000000,32400000,75[/CODE]
on Zen 2. Roundoff error check is enabled.[/QUOTE]

Where can I find error logs or where can I turn them on? I ran

[CODE]Pminus1=1,2,27237523,-1,3000000,300000000,75[/CODE]

and stage 1 was normal (FFT 1440K), stage 2 init finished with a roundoff warning (FFT 1680K) and ran stage 1 from a late savefile again (with FFT 1536k).

P95 then just blew up when it hit stage 2 init again. Using a Zen 3 5900X

Boom!!! Crash!!!
 

See photos of:
Prime95 Window
CPU SPecs
2 pages of Crash error page.

BUG report
 

BUG report -- P-1 missed a factor!
Win10, V30.8b1, on AMD R7 4800H, 4 cores, 1 worker, 16G(8Gx2) DDR4 RAM, 11G of which allocated to Prime95.
[CODE]
[Nov 26 11:49] P-1 on [M]M111298777[/M] with [B]B1=50000, B2=5000000[/B]
[Nov 26 11:49] Using FMA3 FFT length 6M, Pass1=1536, Pass2=4K, clm=1, 4 threads
[Nov 26 11:49] Setting affinity to run helper thread 1 on CPU core #3
[Nov 26 11:49] Setting affinity to run helper thread 2 on CPU core #4
[Nov 26 11:49] Setting affinity to run helper thread 3 on CPU core #5
[Nov 26 12:00] M111298777 stage 1 complete. 144422 transforms. Total time: 675.438 sec.
[Nov 26 12:01] Conversion of stage 1 result complete. 5 transforms, 1 modular inverse. Time: 40.386 sec.
[Nov 26 12:01] Switching to FMA3 FFT length 6720K, Pass1=896, Pass2=7680, clm=2, 4 threads
[Nov 26 12:01] Setting affinity to run helper thread 2 on CPU core #4
[Nov 26 12:01] Setting affinity to run helper thread 1 on CPU core #3
[Nov 26 12:01] Setting affinity to run helper thread 3 on CPU core #5
[Nov 26 12:01] Using 11104MB of memory. D: 330, 40x161 polynomial multiplication.
[Nov 26 12:01] Setting affinity to run polymult helper thread on CPU core #3
[Nov 26 12:01] Setting affinity to run polymult helper thread on CPU core #4
[Nov 26 12:01] Setting affinity to run polymult helper thread on CPU core #5
[Nov 26 12:25] M111298777 stage 2 complete. 154271 transforms. Total time: 1414.600 sec.
[Nov 26 12:25] Round off: 0
[Nov 26 12:25] Stage 2 GCD complete. Time: 24.876 sec.
[Nov 26 12:25] M111298777 completed P-1, B1=50000, B2=5016990, Wi4: 3F048071
[/CODE]
Results.json.txt:
[code]
[Fri Nov 26 12:25:50 2021]
{"status":[B]"NF"[/B], "exponent":111298777, "worktype":"P-1", [B]"b1":50000, "b2":5016990[/B], "fft-length":6881280, "security-code":"3F048071", "program":{"name":"Prime95", "version":"30.8", "build":1, "port":4}, "timestamp":"2021-11-26 04:25:50"}
[/code]
However, [M]M111298777[/M] has a P-1 smooth factor: 135398831970267435540791 (k = 5 × 23 × 37 × 313 × 1069 × 427241).
This is a TF factor found by me long ago. Theoretically, it could be found by the P-1 above.

[QUOTE=Zhangrc;593918]BUG report -- P-1 missed a factor!
Win10, V30.8b1, on AMD R7 4800H, 4 cores, 1 worker, 16G(8Gx2) DDR4 RAM, 11G of which allocated to Prime95.
[CODE]
[Nov 26 11:49] P-1 on [M]M111298777[/M] with [B]B1=50000, B2=5000000[/B]
[/code]
However, [M]M111298777[/M] has a P-1 smooth factor: 135398831970267435540791 (k = 5 × 23 × 37 × 313 × 1069 × 427241).
This is a TF factor found by me long ago. Theoretically, it could be found by the P-1 above.[/QUOTE]

Just as a double check I ran it with 30.7 and 50,000/500,000

[CODE][Comm thread Nov 25 23:36] Sending result to server: UID: petrw1/Magic_8_Ball, M111298777 has a factor: 135398831970267435540791 (P-1, B1=50000, B2=500000)[/CODE]

Thanks everyone! You've given me several bugs to hunt down. Please stop using 30.8 for now.

Edit: 30.8 removed from the server.