29.4(64) Jacobi Error Worker 1 - this can't right

umbilicus · 2018-04-11, 01:27

I have an odd problem that occurs since the Jacobi test was introduced, and also only on 64bit version (I run 64 bit system).

The Jacobi test fails, but only with Worker #1. If I choose 4 windows, it assignes on CPU1 and I get the error message.
If I put 2 worker windows, it assignes on CPU2, i get the same error.
While the other worker windows have checked CPU2 without error.

When I change the CPU assigment in Taskmanager really fast after starting the run, and assign for example CPU4, i get the same error. when I Let Window4 run and only CPU4 is assigned to Prime95.exe, I restart Window1 , I can see it gets executed in CPU4 in Taskmanager correctly, but the Jacobi Test still fails.

That cant be right. Somehow the error has nothing to do with my actual hardware, but is limited to Worker window 1.

I run a non-overclocked recent Laptop with Intel i7 4-Core CPU (8 logical) and 64 Bit Windows 10.
The Prime95 32-Bit Version has no Problems with Jacobi test in 29.4
Stress Test runs with all settings have been executed for hours with no problems, too.

Here is the Error Message:

[Apr 11 03:19] Worker starting
[Apr 11 03:19] Setting affinity to run worker on CPU core #1
[Apr 11 03:19] Running Jacobi error check. Passed. Time: 32.845 sec.
[Apr 11 03:19] Resuming primality test of M48479807 using FMA3 FFT length 2560K, Pass1=640, Pass2=4K, clm=1
[Apr 11 03:19] Iteration: 185404 / 48479807 [0.38%].
[Apr 11 03:19] Possible hardware errors have occurred during the test! 1 ROUNDOFF > 0.4.
[Apr 11 03:19] Confidence in final result is fair.

Thank you for your help, I wan't to know If something with my hardware is faulty or not.

LaurV · 2018-04-11, 06:06

The message says that sometimes in the past, your test may have crashed, or not. This message will be periodically repeated until the test is finished, regardless of the fact that the test continues correctly or not, to make you (the user) aware of the fact that this test possibly had an error in the past. It says nothing about your test crashing now.

Errors happen sometimes.

Delete all temporary files (checkpoints) for this test, and do it again, and see if it still crashes. The 100k iterations will not be a big loss...

Does it do the same?

GP2 · 2018-04-11, 07:13

The Jacobi test did not fail. The message said "Passed."

There is a separate error a bit later that warns of possible hardware problems.

So this is unlikely to be related to version 29.4, but is probably some new hardware issue that has arisen. If you ran an earlier version of the software on the same exponent, chances are it would report the same hardware issues.

Prime95 · 2018-04-11, 15:19

You've had a *possible* roundoff error sometime in the past. Look in results.txt for the error message (it was also output to the worker window, but scrolled off unnoticed).

Some roundoff errors are innocuous, some are indications of a hardware error. I can sometimes give you a more educated guess if you post the error message here.

2018-04-11, 06:06	#2
LaurV Romulan Interpreter Jun 2011 Thailand 10010110110101₂ Posts	The message says that sometimes in the past, your test may have crashed, or not. This message will be periodically repeated until the test is finished, regardless of the fact that the test continues correctly or not, to make you (the user) aware of the fact that this test possibly had an error in the past. It says nothing about your test crashing now. Errors happen sometimes. Delete all temporary files (checkpoints) for this test, and do it again, and see if it still crashes. The 100k iterations will not be a big loss... Does it do the same? Last fiddled with by LaurV on 2018-04-11 at 06:07

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
error during Jacobi check on 330,000,000+ exponent	evanh	Hardware	5	2018-02-20 03:46
Endlessly Running Jacobi error check on v29.3	emiller	Software	10	2017-11-14 10:26
LL testing: Jacobi symbol of the (interim or final) residue minus 2 as error check	GP2	Number Theory Discussion Group	33	2017-08-21 22:14
Worker #5 and Worker#7 not running (Error ILLEGAL SUMOUT	skrupian08	Information & Answers	9	2016-08-23 16:35
Having more than 1 worker	Unregistered	Information & Answers	1	2010-06-07 01:12

2018-04-11, 01:27	#1
umbilicus Apr 2018 1 Posts	29.4(64) Jacobi Error Worker 1 - this can't right I have an odd problem that occurs since the Jacobi test was introduced, and also only on 64bit version (I run 64 bit system). The Jacobi test fails, but only with Worker #1. If I choose 4 windows, it assignes on CPU1 and I get the error message. If I put 2 worker windows, it assignes on CPU2, i get the same error. While the other worker windows have checked CPU2 without error. When I change the CPU assigment in Taskmanager really fast after starting the run, and assign for example CPU4, i get the same error. when I Let Window4 run and only CPU4 is assigned to Prime95.exe, I restart Window1 , I can see it gets executed in CPU4 in Taskmanager correctly, but the Jacobi Test still fails. That cant be right. Somehow the error has nothing to do with my actual hardware, but is limited to Worker window 1. I run a non-overclocked recent Laptop with Intel i7 4-Core CPU (8 logical) and 64 Bit Windows 10. The Prime95 32-Bit Version has no Problems with Jacobi test in 29.4 Stress Test runs with all settings have been executed for hours with no problems, too. Here is the Error Message: [Apr 11 03:19] Worker starting [Apr 11 03:19] Setting affinity to run worker on CPU core #1 [Apr 11 03:19] Running Jacobi error check. Passed. Time: 32.845 sec. [Apr 11 03:19] Resuming primality test of M48479807 using FMA3 FFT length 2560K, Pass1=640, Pass2=4K, clm=1 [Apr 11 03:19] Iteration: 185404 / 48479807 [0.38%]. [Apr 11 03:19] Possible hardware errors have occurred during the test! 1 ROUNDOFF > 0.4. [Apr 11 03:19] Confidence in final result is fair. Thank you for your help, I wan't to know If something with my hardware is faulty or not.

2018-04-11, 07:13	#3
GP2 Sep 2003 5031₈ Posts	The Jacobi test did not fail. The message said "Passed." There is a separate error a bit later that warns of possible hardware problems. So this is unlikely to be related to version 29.4, but is probably some new hardware issue that has arisen. If you ran an earlier version of the software on the same exponent, chances are it would report the same hardware issues.

2018-04-11, 15:19	#4
Prime95 P90 years forever! Aug 2002 Yeehaw, FL 3⁵×31 Posts	You've had a possible roundoff error sometime in the past. Look in results.txt for the error message (it was also output to the worker window, but scrolled off unnoticed). Some roundoff errors are innocuous, some are indications of a hardware error. I can sometimes give you a more educated guess if you post the error message here.