FreeBSD 14.1 Random restarts...

ZioMario

ZioMario

Hello to everyone.

For some months I see a lot of spontaneous restarts on my FreeBSD 14.1 and finally I decided to investigate to understand the cause. It does not matter what I'm doing,the system freezes for some seconds and then,rarely it comes back,more often it reboots. Someone wrote a modern script that I can place on /usr/local/etc/rc.d or elsewhere that can store useful informations to understand where the problem is ? thanks.
 
mprime and prime95 are basically the same test, you don't need both. mprime is in ports.

For SuperPi you want the Linux version in a chroot. An older Debian works for me.

For memtest you probably want memtest86+.
 
Do You Monitor CPU/GPU Temperatures and Coolers Speeds Before/After Freezes?
Bash: 
kldload -n -v "coretemp" || kldload -n -v "amdtemp"
Bash: 
( sysctl "dev.cpu" "hw.acpi.thermal" "dev.amdtemp" 2>"/dev/null" | grep --extended-regexp --ignore-case "(Temperature|CPU[^F]+Freq[^_]|Core[^S]+Sensor)" | sed -E "s~([[:digit:]])C~\1°C~g; s~(CPU.*Freq.*[[:digit:]]+)~\1 MHz~i"; if which smartctl; then smartctl --scan | cut -f 1 -w | while read Device; do I=$(smartctl -a ${Device}); printf "%s\t«%s»\t%d°C\n" "${Device}" "$(printf "%s" "${I}" | grep --extended-regexp --ignore-case "Device[[:space:]]+Model" | grep --only-matching "\:[^$]*" | grep --only-matching "[^\:]*$" | grep --only-matching "[^[:space:]].*$")" "$(printf "%s" "${I}" | grep "Temperature" | cut -f 10 -w)"; done; fi ) | sort | grep --extended-regexp --color=Auto "[[:space:]][\+\−\-\±]?[0-9]+[,.][0-9]+|[[:space:]][\+\−\-\±]?[0-9]{2,}"
UseFool during Runing the MPrime :)
Is HDD-Led Flashing during Freeze?
Basically, if It happens «Often», I would Try to Work (for some Time) form an USB-Stick OS, like Tails, for Example, to DiAgnose is it a SoftWare or HardWare Trouble…
 
how much time does it need to complete ?

Code: 
Welcome to GIMPS, the hunt for huge prime numbers.  You will be asked a
few simple questions and then the program will contact the primenet server
to get some work for your computer.  Good luck!

Attention OVERCLOCKERS!!  Mprime has gained a reputation as a useful
stress testing tool for people that enjoy pushing their hardware to the
limit.  You are more than welcome to use this software for that purpose. 
Please select the stress testing choice below to avoid interfering with
the PrimeNet server.  Use the Options/Torture Test menu choice for your
stress tests.  Also, read the stress.txt file.

If you want to both join GIMPS and run stress tests, then Join GIMPS and
answer the questions.  After the server gets some work for you, stop
mprime, then run mprime -m and choose Options/Torture Test.

Join Gimps? (Y=Yes, N=Just stress testing) (Y): 
Use PrimeNet to get work and report results (Y): 

Create a user account at https://mersenne.org/update/ or you may join
GIMPS anonymously but it is not recommended.  See the readme.txt file for
details.
Your user ID or "ANONYMOUS" (ANONYMOUS): 
Optional computer name: ziomario
Computer uses a dial-up connection to the Internet (N): 
Use a proxy server (N): 
Output debug info to prime.log (0=none, 1=some, 2=too much) (0): 

Accept the answers above? (Y): 
Hours per day this program will run (24): 

CPU Information:
Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz
CPU speed: 4364.59 MHz, 8 hyperthreaded cores
CPU features: Prefetchw, SSE, SSE2, SSE4, AVX, AVX2, FMA
L1 cache size: 8x32 KB, L2 cache size: 8x256 KB, L3 cache size: 16 MB

Accept the answers above? (Y): 
Consult readme.txt prior to changing any of these settings.

Temporary disk space limit in GB/worker (6.000000): 
Daytime P-1/P+1/ECM stage 2 memory in GB (0.300000): 
Nighttime P-1/P+1/ECM stage 2 memory in GB (0.300000): 
Upload bandwidth limit in Mbps (0.250000): 
Upload large files time period start (00:00): 
Upload large files time period end (24:00): 
Download limit for certification work in MB/day (40): 
Skip advanced resource settings (Y): 

Accept the answers above? (Y): 
Number of workers to run (2): 

Use the following values to select a work type:
  0 - Whatever makes the most sense
 150 - First time prime tests
  152 - World record sized numbers to prime test
  151 - Double-check prime tests
  2 - Trial factoring
  4 - P-1 factoring
  153 - 100 million digit numbers to prime test
  160 - First time PRP on Mersenne cofactors
  161 - Double-check PRP on Mersenne cofactors
  5 - ECM for first factors of Mersenne numbers
  8 - ECM on Mersenne cofactors
  6 - ECM on Fermat numbers
  1 - Trial factoring to low limits

Options for worker #1

Type of work to get (0): 
CPU cores to use (multithreading) (4): 

Options for worker #2

Type of work to get (0): 
CPU cores to use (multithreading) (4): 
Get occasional proof certification work (Y): 

Accept the answers above? (Y): 
             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: [Main thread Dec 22 21:52] Starting workers.

[Comm thread Dec 22 21:52] Updating computer information on the server
[Worker #1 Dec 22 21:52] Worker starting
[Worker #2 Dec 22 21:52] Waiting 5 seconds to stagger worker starts.
[Worker #1 Dec 22 21:52] Setting affinity to run worker on CPU core #1
[Worker #1 Dec 22 21:52] No work to do at the present time.  Waiting.
[Comm thread Dec 22 21:52] Exchanging program options with server
[Comm thread Dec 22 21:52] Getting assignment from server
[Comm thread Dec 22 21:52] PrimeNet success code with additional info:
[Comm thread Dec 22 21:52] Server assigned Lucas Lehmer primality double-check work.
[Comm thread Dec 22 21:52] Got assignment 13AAFD8A615A81357F45BEFEDB29CA01: Double check M82492261
[Worker #1 Dec 22 21:52] Resuming.
[Comm thread Dec 22 21:52] Sending expected completion date for M82492261: Dec 30 2024
[Worker #1 Dec 22 21:52] Setting affinity to run helper thread 1 on CPU core #2
[Worker #1 Dec 22 21:52] Setting affinity to run helper thread 2 on CPU core #3
[Worker #1 Dec 22 21:52] Setting affinity to run helper thread 3 on CPU core #4
[Worker #1 Dec 22 21:52] Starting primality test of M82492261 using FMA3 FFT length 4480K, Pass1=448
, Pass2=10K, clm=2, 4 threads
[Comm thread Dec 22 21:52] Getting assignment from server
[Comm thread Dec 22 21:52] PrimeNet success code with additional info:
[Comm thread Dec 22 21:52] Server assigned Lucas Lehmer primality double-check work.
[Comm thread Dec 22 21:52] Got assignment BE6CA8C53C1B30F0423FBA45369E368E: Double check M82492331
[Comm thread Dec 22 21:52] Sending expected completion date for M82492331: Dec 30 2024
[Comm thread Dec 22 21:52] Done communicating with server.
[Worker #2 Dec 22 21:52] Worker starting
[Worker #2 Dec 22 21:52] Setting affinity to run worker on CPU core #5
[Worker #2 Dec 22 21:52] Setting affinity to run helper thread 1 on CPU core #6
[Worker #2 Dec 22 21:52] Setting affinity to run helper thread 2 on CPU core #7
[Worker #2 Dec 22 21:52] Setting affinity to run helper thread 3 on CPU core #8
[Worker #2 Dec 22 21:52] Starting primality test of M82492331 using FMA3 FFT length 4480K, Pass1=448
, Pass2=10K, clm=2, 4 threads
[Worker #1 Dec 22 21:54] Iteration: 10000 / 82492261 [0.01%], ms/iter: 11.030, ETA: 10d 12:43
[Worker #2 Dec 22 21:54] Iteration: 10000 / 82492331 [0.01%], ms/iter: 11.346, ETA: 10d 19:57
[Worker #1 Dec 22 21:56] Iteration: 20000 / 82492261 [0.02%], ms/iter: 11.471, ETA: 10d 22:47
[Worker #2 Dec 22 21:56] Iteration: 20000 / 82492331 [0.02%], ms/iter: 11.489, ETA: 10d 23:11
[Worker #1 Dec 22 21:58] Iteration: 30000 / 82492261 [0.03%], ms/iter: 11.750, ETA: 11d 05:09
[Worker #2 Dec 22 21:58] Iteration: 30000 / 82492331 [0.03%], ms/iter: 11.423, ETA: 10d 21:39
[Worker #1 Dec 22 22:00] Iteration: 40000 / 82492261 [0.04%], ms/iter: 11.613, ETA: 11d 01:58
[Worker #2 Dec 22 22:00] Iteration: 40000 / 82492331 [0.04%], ms/iter: 11.758, ETA: 11d 05:17
[Worker #1 Dec 22 22:02] Iteration: 50000 / 82492261 [0.06%], ms/iter: 11.872, ETA: 11d 07:52
[Worker #2 Dec 22 22:02] Iteration: 50000 / 82492331 [0.06%], ms/iter: 11.936, ETA: 11d 09:20
[Worker #1 Dec 22 22:04] Iteration: 60000 / 82492261 [0.07%], ms/iter: 12.135, ETA: 11d 13:51
[Worker #2 Dec 22 22:04] Iteration: 60000 / 82492331 [0.07%], ms/iter: 12.064, ETA: 11d 12:14
[Worker #1 Dec 22 22:06] Iteration: 70000 / 82492261 [0.08%], ms/iter: 11.970, ETA: 11d 10:03
[Worker #2 Dec 22 22:06] Iteration: 70000 / 82492331 [0.08%], ms/iter: 11.956, ETA: 11d 09:44
[Worker #1 Dec 22 22:08] Iteration: 80000 / 82492261 [0.09%], ms/iter: 11.889, ETA: 11d 08:10
[Worker #2 Dec 22 22:08] Iteration: 80000 / 82492331 [0.09%], ms/iter: 11.811, ETA: 11d 06:22
[Worker #1 Dec 22 22:10] Iteration: 90000 / 82492261 [0.10%], ms/iter: 11.883, ETA: 11d 07:59
[Worker #2 Dec 22 22:10] Iteration: 90000 / 82492331 [0.10%], ms/iter: 11.818, ETA: 11d 06:30
[Worker #1 Dec 22 22:12] Iteration: 100000 / 82492261 [0.12%], ms/iter: 11.978, ETA: 11d 10:08
[Worker #2 Dec 22 22:12] Iteration: 100000 / 82492331 [0.12%], ms/iter: 11.861, ETA: 11d 07:27
 
I think you got the number of CPU cores wrong.

You are using a newer version than I do, I am not familiar with all the new options.
 
What should show the mprime test if there is some hardware error ? I'm running it from 1 day and I see that the system is became a little slow,but nothing more.
 
You must log in or register to reply here.
Back
Top