Hi,
At 10:48 PM 6/24/00 +0200, Steinar H. Gunderson wrote:
>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?
The ILLEGAL SUMOUT and SUMINP != SUMOUT error checks are done
on every iteration. The good news for you is that mprime usually
recovers from ILLEGAL SUMOUT errors without any problems.
> 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?
It could have - all it takes is one driver or OS bug that does not save the
FPU state properly to cause this error.
REgards,
George
_________________________________________________________________
Unsubscribe & list info -- http://www.scruz.net/~luke/signup.htm
Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
