What does my result mean?

2013-03-16, 23:01

I got 6 Workers here which say:

Code:

[Mar 16 23:45] Worker starting
[Mar 16 23:45] Setting affinity to run worker on logical CPU #1
[Mar 16 23:45] Beginning a continuous self-test to check your computer.
[Mar 16 23:45] Please read stress.txt.  Choose Test/Stop to end this test.
[Mar 16 23:45] Test 1, 7800 Lucas-Lehmer iterations of M9961473 using AMD K10 type-2 FFT length 512K, Pass1=512, Pass2=1K.
[Mar 16 23:47] Test 2, 7800 Lucas-Lehmer iterations of M9961471 using AMD K10 FFT length 512K, Pass1=512, Pass2=1K.
[Mar 16 23:48] Test 3, 7800 Lucas-Lehmer iterations of M9837183 using AMD K10 type-2 FFT length 512K, Pass1=512, Pass2=1K.
[Mar 16 23:49] Test 4, 7800 Lucas-Lehmer iterations of M9737185 using AMD K10 FFT length 512K, Pass1=512, Pass2=1K.
[Mar 16 23:51] Test 5, 7800 Lucas-Lehmer iterations of M9537183 using AMD K10 type-2 FFT length 512K, Pass1=512, Pass2=1K.
[Mar 16 23:52] Test 6, 7800 Lucas-Lehmer iterations of M9437185 using AMD K10 FFT length 512K, Pass1=512, Pass2=1K.
[Mar 16 23:53] Test 7, 7800 Lucas-Lehmer iterations of M9437183 using AMD K10 type-2 FFT length 512K, Pass1=512, Pass2=1K.
[Mar 16 23:53] FATAL ERROR: Rounding was 0.5, expected less than 0.4
[Mar 16 23:53] Hardware failure detected, consult stress.txt file.
[Mar 16 23:53] Torture Test completed 6 tests in 8 minutes - 1 errors, 0 warnings.
[Mar 16 23:53] Worker stopped.

Code:

[Mar 16 23:45] Worker starting
[Mar 16 23:45] Setting affinity to run worker on logical CPU #2
[Mar 16 23:45] Beginning a continuous self-test to check your computer.
[Mar 16 23:45] Please read stress.txt.  Choose Test/Stop to end this test.
[Mar 16 23:45] Test 1, 7800 Lucas-Lehmer iterations of M9961473 using AMD K10 type-2 FFT length 512K, Pass1=512, Pass2=1K.
[Mar 16 23:47] FATAL ERROR: Rounding was 0.5, expected less than 0.4
[Mar 16 23:47] Hardware failure detected, consult stress.txt file.
[Mar 16 23:47] Torture Test completed 0 tests in 2 minutes - 1 errors, 0 warnings.
[Mar 16 23:47] Worker stopped.

Code:

[Mar 16 23:45] Worker starting
[Mar 16 23:45] Setting affinity to run worker on logical CPU #3
[Mar 16 23:45] Beginning a continuous self-test to check your computer.
[Mar 16 23:45] Please read stress.txt.  Choose Test/Stop to end this test.
[Mar 16 23:45] Test 1, 7800 Lucas-Lehmer iterations of M9961473 using AMD K10 type-2 FFT length 512K, Pass1=512, Pass2=1K.
[Mar 16 23:47] Test 2, 7800 Lucas-Lehmer iterations of M9961471 using AMD K10 FFT length 512K, Pass1=512, Pass2=1K.
[Mar 16 23:48] Test 3, 7800 Lucas-Lehmer iterations of M9837183 using AMD K10 type-2 FFT length 512K, Pass1=512, Pass2=1K.
[Mar 16 23:49] Test 4, 7800 Lucas-Lehmer iterations of M9737185 using AMD K10 FFT length 512K, Pass1=512, Pass2=1K.
[Mar 16 23:49] FATAL ERROR: Rounding was 0.49609375, expected less than 0.4
[Mar 16 23:49] Hardware failure detected, consult stress.txt file.
[Mar 16 23:49] Torture Test completed 3 tests in 4 minutes - 1 errors, 0 warnings.
[Mar 16 23:49] Worker stopped.

Code:

[Mar 16 23:45] Worker starting
[Mar 16 23:45] Setting affinity to run worker on logical CPU #4
[Mar 16 23:45] Beginning a continuous self-test to check your computer.
[Mar 16 23:45] Please read stress.txt.  Choose Test/Stop to end this test.
[Mar 16 23:45] Test 1, 7800 Lucas-Lehmer iterations of M9961473 using AMD K10 type-2 FFT length 512K, Pass1=512, Pass2=1K.
[Mar 16 23:46] FATAL ERROR: Rounding was 0.5, expected less than 0.4
[Mar 16 23:46] Hardware failure detected, consult stress.txt file.
[Mar 16 23:46] Torture Test completed 0 tests in 1 minutes - 1 errors, 0 warnings.
[Mar 16 23:46] Worker stopped.

Code:

[Mar 16 23:45] Worker starting
[Mar 16 23:45] Setting affinity to run worker on logical CPU #5
[Mar 16 23:45] Beginning a continuous self-test to check your computer.
[Mar 16 23:45] Please read stress.txt.  Choose Test/Stop to end this test.
[Mar 16 23:45] Test 1, 7800 Lucas-Lehmer iterations of M9961473 using AMD K10 type-2 FFT length 512K, Pass1=512, Pass2=1K.
[Mar 16 23:47] FATAL ERROR: Rounding was 0.5, expected less than 0.4
[Mar 16 23:47] Hardware failure detected, consult stress.txt file.
[Mar 16 23:47] Torture Test completed 0 tests in 2 minutes - 1 errors, 0 warnings.
[Mar 16 23:47] Worker stopped.

Code:

[Mar 16 23:45] Worker starting
[Mar 16 23:45] Setting affinity to run worker on logical CPU #6
[Mar 16 23:45] Beginning a continuous self-test to check your computer.
[Mar 16 23:45] Please read stress.txt.  Choose Test/Stop to end this test.
[Mar 16 23:45] Test 1, 7800 Lucas-Lehmer iterations of M9961473 using AMD K10 type-2 FFT length 512K, Pass1=512, Pass2=1K.
[Mar 16 23:47] Test 2, 7800 Lucas-Lehmer iterations of M9961471 using AMD K10 FFT length 512K, Pass1=512, Pass2=1K.
[Mar 16 23:48] Test 3, 7800 Lucas-Lehmer iterations of M9837183 using AMD K10 type-2 FFT length 512K, Pass1=512, Pass2=1K.
[Mar 16 23:49] Test 4, 7800 Lucas-Lehmer iterations of M9737185 using AMD K10 FFT length 512K, Pass1=512, Pass2=1K.
[Mar 16 23:50] Test 5, 7800 Lucas-Lehmer iterations of M9537183 using AMD K10 type-2 FFT length 512K, Pass1=512, Pass2=1K.
[Mar 16 23:51] FATAL ERROR: Rounding was 0.5, expected less than 0.4
[Mar 16 23:51] Hardware failure detected, consult stress.txt file.
[Mar 16 23:51] Torture Test completed 4 tests in 5 minutes - 1 errors, 0 warnings.
[Mar 16 23:51] Worker stopped.

Als last the Main thread

Code:

[Main thread Mar 16 23:45] Mersenne number primality test program version 27.9
[Main thread Mar 16 23:45] Optimizing for CPU architecture: AMD Bulldozer, L2 cache size: 2 MB, L3 cache size: 8 MB
[Main thread Mar 16 23:45] Starting workers.
[Main thread Mar 16 23:53] Execution halted.

So what does tese results mean? theres no log file or sth.

Thanks for helping!

kracker · 2013-03-17, 00:17

Are you OC'ing?

That means your cpu is unstable right now, it failed the test.

Mr. P-1 · 2013-03-17, 03:16

It means what it says. Your system is producing incorrect results.

Parabol · 2013-04-15, 23:46

Sorry could not find any better place for my Q..

[Apr 14 15:33] Stopping primality test of M60685363 at iteration 25282264 [41.66%]
[Apr 14 15:33] Aborting processing of this work unit.

What does that mean ??

Tks .. Parabol

Uncwilly · 2013-04-16, 03:36

Quote:

Originally Posted by Parabol

[Apr 14 15:33] Stopping primality test of M60685363 at iteration 25282264 [41.66%]
[Apr 14 15:33] Aborting processing of this work unit.

Did you get your exponent from PrimeNet? It appears that it was assigned on April 13. If you can do 41.66% of the test in a day, that is amazing. If you chose the exponent and started working on it with out getting it from PrimeNet, that could be your problem.

Mr. P-1 · 2013-04-16, 04:22

Quote:

Originally Posted by Uncwilly

Did you get your exponent from PrimeNet? It appears that it was assigned on April 13. If you can do 41.66% of the test in a day, that is amazing. If you chose the exponent and started working on it with out getting it from PrimeNet, that could be your problem.

Alternatively, if he did get the exponent from Primenet, but it expired. Parabol, have you just restarted work on this after a long hiatus? For example, has your machine been off?

Parabol · 2013-04-16, 21:52

@Uncwilly .. yes got it from primenet
---------------------------------
[Sun Apr 07 18:32:58 2013 - ver 27.9]
Exchanging program options with server
Exchanging program options with server
Getting assignment from server
PrimeNet success code with additional info:
Server assigned Lucas Lehmer primality test work.
Got assignment 0F6B1B2277EBC54A472952E3DCC2AAA8: LL M60685363
Sending expected completion date for M60685363: Apr 22 2013
---------------------------------
@Mr. P-1 .. No and No .. machine is running H24
then I got this one below
-------------------------------
[Sun Apr 14 15:33:49 2013 - ver 27.9]
Updating computer information on the server
Sending expected completion date for M59370133: Apr 21 2013
Sending expected completion date for M61421771: Apr 15 2013
Sending expected completion date for M62376469: Apr 15 2013
Sending expected completion date for M61462879: Apr 15 2013
Sending expected completion date for M60685363: Apr 23 2013
PrimeNet error 43: Invalid assignment key
ap: no such assignment key, GUID: 269069001df0c30df294c53eda8640cc, key: 0F6B1B2277EBC54A472952E3DCC2AAA8
Getting assignment from server
PrimeNet success code with additional info:
Server assigned Lucas Lehmer primality double-check work.
Got assignment 57C1A44B0123F5FE8B50E7FE9AD8A291: Double check M31172131
Sending expected completion date for M31172131: Apr 18 2013
Sending expected completion date for M61419829: Apr 14 2013
Sending expected completion date for M62377459: Apr 15 2013
Sending expected completion date for M61469999: Apr 15 2013
--------------------------------------
The assignment key for PrimeNet error 43 looks to me the same as the one
from the initial assignment..
However overclocking may have played a role here (put it back now to moderate)
Got the same error code (43) on two other instances (D-LL)

Thanks for answering .. will see how it works with the lower Clock-Setting
Parabol

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Suspect result	stebbo	PrimeNet	23	2017-06-03 11:14
Odd result	swellman	YAFU	15	2016-02-25 00:38
Odd result	1997rj7	PrimeNet	2	2009-12-04 08:48
strange GMP-ECM result	yoyo	GMP-ECM	1	2009-08-08 07:09
New Result	R.D. Silverman	NFSNET Discussion	1	2005-04-19 23:45

2013-03-17, 00:17	#2
kracker "Mr. Meeseeks" Jan 2012 California, USA 3²·241 Posts	Are you OC'ing? That means your cpu is unstable right now, it failed the test.

2013-03-17, 03:16	#3
Mr. P-1 Jun 2003 7·167 Posts	It means what it says. Your system is producing incorrect results.

2013-04-15, 23:46	#4
Parabol Apr 2013 2 Posts	Primality test stopping ? Sorry could not find any better place for my Q.. [Apr 14 15:33] Stopping primality test of M60685363 at iteration 25282264 [41.66%] [Apr 14 15:33] Aborting processing of this work unit. What does that mean ?? Tks .. Parabol

2013-04-16, 21:52	#7
Parabol Apr 2013 2₁₆ Posts	@Uncwilly .. yes got it from primenet --------------------------------- [Sun Apr 07 18:32:58 2013 - ver 27.9] Exchanging program options with server Exchanging program options with server Getting assignment from server PrimeNet success code with additional info: Server assigned Lucas Lehmer primality test work. Got assignment 0F6B1B2277EBC54A472952E3DCC2AAA8: LL M60685363 Sending expected completion date for M60685363: Apr 22 2013 --------------------------------- @Mr. P-1 .. No and No .. machine is running H24 then I got this one below ------------------------------- [Sun Apr 14 15:33:49 2013 - ver 27.9] Updating computer information on the server Sending expected completion date for M59370133: Apr 21 2013 Sending expected completion date for M61421771: Apr 15 2013 Sending expected completion date for M62376469: Apr 15 2013 Sending expected completion date for M61462879: Apr 15 2013 Sending expected completion date for M60685363: Apr 23 2013 PrimeNet error 43: Invalid assignment key ap: no such assignment key, GUID: 269069001df0c30df294c53eda8640cc, key: 0F6B1B2277EBC54A472952E3DCC2AAA8 Getting assignment from server PrimeNet success code with additional info: Server assigned Lucas Lehmer primality double-check work. Got assignment 57C1A44B0123F5FE8B50E7FE9AD8A291: Double check M31172131 Sending expected completion date for M31172131: Apr 18 2013 Sending expected completion date for M61419829: Apr 14 2013 Sending expected completion date for M62377459: Apr 15 2013 Sending expected completion date for M61469999: Apr 15 2013 -------------------------------------- The assignment key for PrimeNet error 43 looks to me the same as the one from the initial assignment.. However overclocking may have played a role here (put it back now to moderate) Got the same error code (43) on two other instances (D-LL) Thanks for answering .. will see how it works with the lower Clock-Setting Parabol