Hmmm... Just a few minutes ago, my mprime v20 gave me:
Iteration: 8312000 / 15269993 [54.43%]. Per iteration time: 0.424 sec. (190008097
clocks)
Iteration: 8312694/15269993, ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult the readme file.
Continuing from last save file.
Waiting five minutes before restarting.
Resuming M15269993 at iteration 8312652 [54.43%]
Iteration: 8313000 / 15269993 [54.44%]. Per iteration time: 0.428 sec. (191927493
clocks)
Iteration: 8314000 / 15269993 [54.44%]. Per iteration time: 1.913 sec. (857236303
clocks)
This machine is overclocked (112MHz x 4.0 for a 400MHz Pentium II), but
it has run mprime (and about 100 hours of torture testing in one go) stably
for about two years now. What puzzles me, is that there are only 42
iterations from the saving to the illegal sumout... Isn't it so that mprime
only checks for errors every 64 iterations or something? In that case, could
the saving (I'm using Linux 2.4.0-test1 and an unstable ReiserFS patch as
well -- not exactly the `safest' platform, but we run these QA tests on pairs
of machines and compare residues during the entire test) have caused the error?
/* Steinar */
--
Homepage: http://members.xoom.com/sneeze/
_________________________________________________________________
Unsubscribe & list info -- http://www.scruz.net/~luke/signup.htm
Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
