Unknown Intel
 

~/Downloads/p95v294b8.linux64$ ./mprime -d
[Main thread Oct 10 12:51] Mersenne number primality test program version 29.4
[Main thread Oct 10 12:51] Optimizing for CPU architecture: Unknown Intel, L2 cache size: 256 KB, L3 cache size: 3 MB
[Main thread Oct 10 12:51] Starting worker.
[Work thread Oct 10 12:51] Worker starting
[Work thread Oct 10 12:51] Setting affinity to run worker on CPU core #1
[Work thread Oct 10 12:51] Setting affinity to run helper thread 1 on CPU core #1
[Work thread Oct 10 12:51] Setting affinity to run helper thread 2 on CPU core #2
[Work thread Oct 10 12:51] Setting affinity to run helper thread 3 on CPU core #2
[Work thread Oct 10 12:51] Resuming Gerbicz error-checking PRP test of M87196541 using FMA3 FFT length 4608K, Pass1=768, Pass2=6K, clm=1, 4 threads
[Work thread Oct 10 12:51] Iteration: 15218 / 87196541 [0.01%].
[Work thread Oct 10 12:52] Iteration: 20000 / 87196541 [0.02%], ms/iter: 20.459, ETA: 20d 15:25







The CPU is:
$ lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 4
On-line CPU(s) list: 0-3
Thread(s) per core: 2
Core(s) per socket: 2
Socket(s): 1
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 78
Model name: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz
Stepping: 3
CPU MHz: 2599.951
CPU max MHz: 2800.0000
CPU min MHz: 400.0000
BogoMIPS: 4800.00
Virtualization: VT-x
L1d cache: 32K
L1i cache: 32K
L2 cache: 256K
L3 cache: 3072K
NUMA node0 CPU(s): 0-3
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch epb invpcid_single kaiser tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp

I've added family 6 model 78 to the recognized list for the next release. The "bug" does not affect prime95's performance.

[QUOTE]
~/Downloads/p95v294b8.linux64$ ./mprime -d
[Main thread Oct 10 12:51] Mersenne number primality test program version 29.4
[Main thread Oct 10 12:51] Optimizing for CPU architecture: Unknown Intel, L2 cache size: 256 KB, L3 cache size: 3 MB
[Main thread Oct 10 12:51] Starting worker.
[Work thread Oct 10 12:51] Worker starting
[Work thread Oct 10 12:51] Setting affinity to run worker on CPU core #1
[Work thread Oct 10 12:51] Setting affinity to run helper thread 1 on CPU core #1
[Work thread Oct 10 12:51] Setting affinity to run helper thread 2 on CPU core #2
[Work thread Oct 10 12:51] Setting affinity to run helper thread 3 on CPU core #2
[Work thread Oct 10 12:51] Resuming Gerbicz error-checking PRP test of M87196541 using FMA3 FFT length 4608K, Pass1=768, Pass2=6K, clm=1, 4 threads
[Work thread Oct 10 12:51] Iteration: 15218 / 87196541 [0.01%].
[Work thread Oct 10 12:52] Iteration: 20000 / 87196541 [0.02%], ms/iter: 20.459, ETA: 20d 15:25
[/QUOTE]



I started this computation on a laptop, the cpu temperature has gone up to 75C-76C. I had to stop it, the system monitor was showing the "overloaded" warning.

I'm not suprised, laptops rarely have the cooling required for running flatout.

[QUOTE=VictordeHolland;497840]I'm not suprised, laptops rarely have the cooling required for running flatout.[/QUOTE]


I need to move this exponent to another computer, what is the exact procedure?

[QUOTE=SELROC;497841]I need to move this exponent to another computer, what is the exact procedure?[/QUOTE]

Consider using throttle to set duty cycle to within the thermal dissipation limits of the laptop. From undoc.txt:
[CODE]If you are running on a laptop or in a hot room and you want to slow the
program down to reduce heat, then you can add this line to prime.txt:
Throttle=n
where n is the percentage of time the program should run. For example,
Throttle=40 means the program will run 40% and be idle 60% of the time.
[/CODE]

[QUOTE=Prime95;497802]I've added family 6 model 78 to the recognized list for the next release. The "bug" does not affect prime95's performance.[/QUOTE]

[QUOTE=kriesel;497851]Consider using throttle to set duty cycle to within the thermal dissipation limits of the laptop. From undoc.txt:
[CODE]If you are running on a laptop or in a hot room and you want to slow the
program down to reduce heat, then you can add this line to prime.txt:
Throttle=n
where n is the percentage of time the program should run. For example,
Throttle=40 means the program will run 40% and be idle 60% of the time.
[/CODE][/QUOTE]


Throttle increases the ETA, I would like to move the exponent to another faster computer with better cooling.

[QUOTE=SELROC;497841]I need to move this exponent to another computer, what is the exact procedure?[/QUOTE]
To move an exponent in progress from a source machine to a target machine, in order, I think it is:

Stop source and target mprime instances.

Move the relevant worktodo file entry and the work in progress files. (Not just copy; copy, confirm, optionally make backup, remove originals from source or move them to a backup subdirectory.)

Restart target mprime instance.

(Then I'd configure the source for a suitable throttle setting, and have it get new work suitable for that.)

[QUOTE=kriesel;497862]To move an exponent in progress from a source machine to a target machine, in order, I think it is:

Stop source and target mprime instances.

Move the relevant worktodo file entry and the work in progress files. (Not just copy; copy, confirm, optionally make backup, remove originals from source or move them to a backup subdirectory.)

Restart target mprime instance.

(Then I'd configure the source for a suitable throttle setting, and have it get new work suitable for that.)[/QUOTE]

Don't forget the temporary file containing the work already done on such exponent.

You could also copy the source exponent into a file named worktodo.add, and copy such file into the target directory: the file will be "sucked" into the worktodo.txt in less than 60 minutes.

There could be a duplication of CPU work on your stats page: you may as well correct the attribution of the work to the target CPU.

[QUOTE=ET_;497863]Don't forget the temporary file containing the work already done on such exponent./QUOTE]
That's a little less than what I meant by [QUOTE]and the work in progress files[/QUOTE].
For example, if I wanted to relocate the first assignment in this list (from which I've concealed the AIDs):

[CODE][Worker #1]
ECM2=1,2,17714869,-1,50000,5000000,1
ECM2=1,2,17715431,-1,50000,5000000,1

[Worker #2]
ECM2=1,2,18155647,-1,50000,5000000,1
ECM2=1,2,18157949,-1,50000,5000000,1[/CODE]I'd move the worktodo entry [QUOTE]ECM2=1,2,17714869,-1,50000,5000000,1[/QUOTE] and move the corresponding first three files eH714869.* in the directory listing below (the current temporary file, and all the backups mprime/prime95 generated earlier that remain for that assignment).
[CODE] Directory of C:\Users\Ken\prime95x64

10/11/2018 09:27 AM <DIR> .
10/11/2018 09:27 AM <DIR> ..
10/11/2018 09:27 AM 4,428,820 eH714869
10/11/2018 08:57 AM 4,428,820 eH714869.bu
10/11/2018 08:27 AM 4,428,820 eH714869.bu2
10/11/2018 09:27 AM 4,539,012 eI155647
10/11/2018 08:57 AM 4,539,012 eI155647.bu
10/11/2018 08:27 AM 4,539,012 eI155647.bu2
06/30/2018 08:13 PM 23,482 gwnum.txt
08/28/2017 09:20 PM 1,085,185 libgmp-10.dll
01/18/2018 04:43 PM 1,515,031 libhwloc-5.dll
09/20/2017 04:17 PM 2,159 license.txt
10/11/2018 06:11 AM 538 local.txt
10/11/2018 06:11 AM 1,227,331 prime.log
10/11/2018 07:56 AM 853 prime.txt
02/09/2018 05:27 PM 34,314,240 prime95.exe
12/08/2017 06:07 PM 29,056 readme.txt
10/11/2018 06:11 AM 249,498 results.txt
10/30/2017 07:48 PM 37,292 undoc.txt
01/04/2018 10:31 PM 69,072 whatsnew.txt
10/11/2018 06:11 AM 312 worktodo.txt
19 File(s) 65,457,545 bytes[/CODE]Also, I'd keep track of such moves, as a precaution in case a primality test turned out to be bad. It would cast suspicion on the reliability of both the source system and target system.

[QUOTE=ET_;497863]Don't forget the temporary file containing the work already done on such exponent.

You could also copy the source exponent into a file named worktodo.add, and copy such file into the target directory: the file will be "sucked" into the worktodo.txt in less than 60 minutes.

There could be a duplication of CPU work on your stats page: you may as well correct the attribution of the work to the target CPU.[/QUOTE]




Thank you. I think, move the worktodo.txt file to the target worktodo.add and adjust worker/cores to fit the new work, right?