Prime95 v30.4 - Page 10

tha · 2021-02-08, 20:13

I am still using build 6.

A few times since I installed 30.4 the process got killed, but very infrequent. Restarting mprime than solves the problem.

I now have reached a point where mprime gets killed every time it is restarted.

I have left terminal open so I could run some tests if desired.

Should I just install build 9 or run some kind of test to see what causes this crashing?

Code:

[Work thread Feb 8 20:19] 
[Work thread Feb 8 20:19] P-1 on M15435689 with B1=1200000, B2=TBD
[Work thread Feb 8 20:19] Setting affinity to run helper thread 1 on CPU core #2
[Work thread Feb 8 20:19] Using FMA3 FFT length 800K, Pass1=320, Pass2=2560, clm=4, 4 threads
[Work thread Feb 8 20:19] Setting affinity to run helper thread 2 on CPU core #3
[Work thread Feb 8 20:19] Setting affinity to run helper thread 3 on CPU core #4
[Comm thread Feb 8 20:19] PrimeNet success code with additional info:
[Comm thread Feb 8 20:19] CPU credit is 4.2008 GHz-days.
[Comm thread Feb 8 20:19] Done communicating with server.
[Work thread Feb 8 20:31] M15435689 stage 1 is 57.73% complete. Time: 768.708 sec.
[Work thread Feb 8 20:42] M15435689 stage 1 complete. 3464242 transforms. Time: 1396.240 sec.
[Work thread Feb 8 20:42] With trial factoring done to 2^69, optimal B2 is 71*B1 = 85200000.
[Work thread Feb 8 20:42] If no prior P-1, chance of a new factor is 7.73%
[Work thread Feb 8 20:42] D: 840, relative primes: 1713, stage 2 primes: 4861699, pair%=92.99
[Work thread Feb 8 20:42] Using 11073MB of memory.
[Work thread Feb 8 20:42] Stage 2 init complete. 16975 transforms. Time: 14.521 sec.
Killed
henk@Z170:~/mersenne$ ./mprime -m
[Main thread Feb 8 21:01] Mersenne number primality test program version 30.4
[Main thread Feb 8 21:01] 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 Feb 8 21:01] Starting worker.
[Work thread Feb 8 21:01] Worker starting
[Work thread Feb 8 21:01] Setting affinity to run worker on CPU core #1
[Work thread Feb 8 21:01] 
[Work thread Feb 8 21:01] P-1 on M15435689 with B1=1200000, B2=TBD
[Work thread Feb 8 21:01] Setting affinity to run helper thread 1 on CPU core #2
[Work thread Feb 8 21:01] Setting affinity to run helper thread 3 on CPU core #4
[Work thread Feb 8 21:01] Using FMA3 FFT length 800K, Pass1=320, Pass2=2560, clm=4, 4 threads
[Work thread Feb 8 21:01] Setting affinity to run helper thread 2 on CPU core #3
[Work thread Feb 8 21:01] Resuming P-1 in stage 2 with B2=85200000
[Work thread Feb 8 21:01] Using 11073MB of memory.
Killed
henk@Z170:~/mersenne$ ./mprime -m
[Main thread Feb 8 21:02] Mersenne number primality test program version 30.4
[Main thread Feb 8 21:02] 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


 Starting worker.
[Work thread Feb 8 21:02] Worker starting
[Work thread Feb 8 21:02] Setting affinity to run worker on CPU core #1
[Work thread Feb 8 21:02] 
[Work thread Feb 8 21:02] P-1 on M15435689 with B1=1200000, B2=TBD
[Work thread Feb 8 21:02] Setting affinity to run helper thread 1 on CPU core #2
[Work thread Feb 8 21:02] Setting affinity to run helper thread 2 on CPU core #3
[Work thread Feb 8 21:02] Setting affinity to run helper thread 3 on CPU core #4
[Work thread Feb 8 21:02] Using FMA3 FFT length 800K, Pass1=320, Pass2=2560, clm=4, 4 threads
[Work thread Feb 8 21:02] Resuming P-1 in stage 2 with B2=85200000
[Work thread Feb 8 21:02] Using 11073MB of memory.
Killed
henk@Z170:~/mersenne$ ./mprime -m
[Main thread Feb 8 21:03] Mersenne number primality test program version 30.4
[Main thread Feb 8 21:03] 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


[Work thread Feb 8 21:03] Worker starting
[Work thread Feb 8 21:03] Setting affinity to run worker on CPU core #1
[Work thread Feb 8 21:03] 
[Work thread Feb 8 21:03] P-1 on M15435689 with B1=1200000, B2=TBD
[Work thread Feb 8 21:03] Setting affinity to run helper thread 1 on CPU core #2
[Work thread Feb 8 21:03] Using FMA3 FFT length 800K, Pass1=320, Pass2=2560, clm=4, 4 threads
[Work thread Feb 8 21:03] Setting affinity to run helper thread 2 on CPU core #3
[Work thread Feb 8 21:03] Setting affinity to run helper thread 3 on CPU core #4
[Work thread Feb 8 21:03] Resuming P-1 in stage 2 with B2=85200000
[Work thread Feb 8 21:03] Using 11073MB of memory.
Killed
henk@Z170:~/mersenne$

PhilF · 2021-02-08, 20:58

I'm not sure how much memory you have installed in that machine, but it looks to me like you should try lowering the amount of memory that P-1 testing is allowed to use.

OTOH, post #97 indicates the problem you are seeing might be fixed in build 9, so if I were you I would just go ahead update and worry about it only if it isn't fixed.

Prime95 · 2021-02-08, 21:35

Quote:

Originally Posted by kriesel

(Re an F20 issue:)Does the prime95 v30.4 b9/b8 differential only affect Fermats? What if anything in the b9 update relates to Mersennes?.

It affects Fermats and Mersennes, P-1 and ECM.

Quote:

Originally Posted by tha

.
I now have reached a point where mprime gets killed every time it is restarted.

Should I just install build 9 or run some kind of test to see what causes this crashing?

Try build 9. If that fails, send me the save file, worktodo.txt, prime.txt, and local.txt.

tha · 2021-02-08, 22:10

Quote:

Originally Posted by Prime95

Try build 9.

Worked!

tha · 2021-02-09, 08:17

In mprime -m if the menu is displayed and an option is chosen the menu will again be displayed first which does not add any value and only clutters things. Can the redisplay of the menu be removed?

Runtime Error · 2021-02-12, 16:05

I accidentally duplicated the same P-1 test line in my worktodo.txt file twice. It ran the first test and found a factor! But then it ran the second test (starting in the second stage) and failed to find a factor. Ran using mprime v30.4b8. My expectation is that it should find the same factor again, right? Thank you!!!

Exponent: 102597787

Code:

[Wed Feb 10 22:14:47 2021]
{"status":"F", "exponent":102597787, "worktype":"P-1", "factors":["1023696064449201832067818657"], "b1":1200000, "b2":67200000, "fft-length":5898240, "security-code":"5A5F339B", "program":{"name":"Prime95", "version":"30.4", "build":8, "port":8}, "timestamp":"2021-02-11 03:14:47", "user":"XXXXX"}

[Thu Feb 11 07:45:49 2021]
{"status":"NF", "exponent":102597787, "worktype":"P-1", "b1":1200000, "b2":120000000, "fft-length":5898240, "security-code":"5975DD9B", "program":{"name":"Prime95", "version":"30.4", "build":8, "port":8}, "timestamp":"2021-02-11 12:45:49", "user":"XXXXX"}

Code:

[Wed Feb 10 17:14:19 2021]
M102597787 stage 1 is 57.73% complete.
[Wed Feb 10 19:45:56 2021]
M102597787 stage 2 is 41.43% complete.
[Wed Feb 10 21:27:04 2021]
M102597787 stage 2 is 82.68% complete.
[Wed Feb 10 22:14:47 2021]
P-1 found a factor in stage #2, B1=1200000, B2=67200000.
UID: XXXXXX, M102597787 has a factor: 1023696064449201832067818657 (P-1, B1=1200000, B2=67200000)

< snip >

[Thu Feb 11 06:08:11 2021]
M102597787 stage 2 is 51.34% complete.
[Thu Feb 11 07:45:49 2021]
UID: XXXXXX, M102597787 completed P-1, B1=1200000, B2=120000000, Wi8: 5975DD9B

Dropbox link for backup files:
https://www.dropbox.com/sh/4iabn36d8...5SZWD-Esa?dl=0

Prime95 · 2021-02-23, 06:07

Quote:

Originally Posted by Runtime Error

I accidentally duplicated the same P-1 test line in my worktodo.txt file twice. It ran the first test and found a factor! My expectation is that it should find the same factor again, right?

Maybe not. I believe when the first P-1 finished it created a save file indicating that P-1 had been run to B1=1.2M, B2=67.2M. When the second P-1 line was processed prime95 took B2 from 67.2M to 120M and thus did not find a factor.

LaurV · 2021-02-23, 07:19

Doing that with gpuOwl will drop the second line (so, do no test, found no factor, save the time). That's because if a factor is found, the tool checks the rest of the worktodo and discards other tests for the same exponent which are scheduled further, to avoid doing the long PRP (if both P-1 and PRP scheduled) for an exponent which already has a factor. Doesn't P95 behave the same?

Prime95 · 2021-02-23, 17:50

Quote:

Originally Posted by LaurV

Doing that with gpuOwl will drop the second line (so, do no test, found no factor, save the time). That's because if a factor is found, the tool checks the rest of the worktodo and discards other tests for the same exponent which are scheduled further, to avoid doing the long PRP (if both P-1 and PRP scheduled) for an exponent which already has a factor. Doesn't P95 behave the same?

Prime95 does not do that.

Runtime Error · 2021-02-24, 00:18

Quote:

Originally Posted by Prime95

Maybe not. I believe when the first P-1 finished it created a save file indicating that P-1 had been run to B1=1.2M, B2=67.2M. When the second P-1 line was processed prime95 took B2 from 67.2M to 120M and thus did not find a factor.

Interesting, thank you!

2021-02-08, 20:58	#101
PhilF Feb 2005 Colorado 2·5·59 Posts	I'm not sure how much memory you have installed in that machine, but it looks to me like you should try lowering the amount of memory that P-1 testing is allowed to use. OTOH, post #97 indicates the problem you are seeing might be fixed in build 9, so if I were you I would just go ahead update and worry about it only if it isn't fixed. Last fiddled with by PhilF on 2021-02-08 at 21:04

2021-02-09, 08:17	#104
tha Dec 2002 807₁₀ Posts	In mprime -m if the menu is displayed and an option is chosen the menu will again be displayed first which does not add any value and only clutters things. Can the redisplay of the menu be removed?

2021-02-23, 07:19	#107
LaurV Romulan Interpreter Jun 2011 Thailand 2³·19·61 Posts	Doing that with gpuOwl will drop the second line (so, do no test, found no factor, save the time). That's because if a factor is found, the tool checks the rest of the worktodo and discards other tests for the same exponent which are scheduled further, to avoid doing the long PRP (if both P-1 and PRP scheduled) for an exponent which already has a factor. Doesn't P95 behave the same?