Mersenne: Error writing intermediate file: rX250423
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I am running an LL test and was probably very low on hd space for a short while and noticed this error: Error writing intermediate file: rX250423 The equivalent p and q files seem to be written correctly, and the program is going ahead with more iterations. I checked the faq (btw, the footer of the list messages is misleading: the faq it points to is 404) on the http://www.mersenne.org/ site. I also googled and found an old 1998 message in a mailing list archive. Only a question, no answer. Since I'm almost 10% done, I was wondering if it's ok to continue, or would it be safer to start over? I guess prime95 would have automatically stopped, but I just want to be sure :) Oh, happy new year! P.S.: sorry if this is a dupe, seems like I wasn't subscribed anymore when I sent the mail the first time. - -- Robin Y. Millette (aka Lord D. Nattor) http://rym.waglo.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2-nr2 (Windows 2000) Comment: Using GnuPG with MultiZilla - http://enigmail.mozdev.org iD8DBQE/+l+HIpq5HjFcVUMRAk0xAJ97i2qlo+cJow2F5Azkn0F1tJYxswCfXHjI K91ioEkLo58qNY9vohUDJiQ= =DFnJ -END PGP SIGNATURE- _ Unsubscribe list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Re: Mersenne: Error 12002
At 12:47 PM 7/1/2003 -0800, Gordon Bower wrote: Looking through the Forum archives it appears Error 12002 is a version 21-specific problem that occurs when entropia.com is down even if mersenne.org is up. On Saturday entropia.com was indeed down. However, entropia's website has been up since sometime Sunday, and I have *still* been getting hourly 12002s on three different systems. I would also ask the keeper of the faq to add a few new lines to it about these new (since 2 years or so ago) error messages that aren't described in the online information. As suggested, I've added error 12002 to the FAQ. I've also emailed Scott to see if he can get Entropia to restart GIMPS message forwarding process _ Unsubscribe list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Mersenne: Error 12002
I've seen sporadic episodes of error messages before during temporary server outages. However, haven't seen one that lasted this long. I now have several machines that have been unable to report for six days in a row. One of them is nearly out of work (though I can reserve assignements manually if I need to.) Looking through the Forum archives it appears Error 12002 is a version 21-specific problem that occurs when entropia.com is down even if mersenne.org is up. On Saturday entropia.com was indeed down. However, entropia's website has been up since sometime Sunday, and I have *still* been getting hourly 12002s on three different systems. No firewalls on my end, and no settings have changed on my end either. Any advice? I would also ask the keeper of the faq to add a few new lines to it about these new (since 2 years or so ago) error messages that aren't described in the online information. GRB _ Unsubscribe list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Mersenne: error 1
well changing to version 22.12 didn't help, and I didn't get a copy of the last message I sent _ Unsubscribe list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Re: Mersenne: error 1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 09 December 2002 10:31 am, you wrote: well changing to version 22.12 didn't help, and I didn't get a copy of the last message I sent I did... I've been getting Error 1 for some time now... I think the server's having problems. - -- Barry Stokes paranoia, n.: A healthy understanding of the way the universe works. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE99HsNfymHpTUQ4e8RAlJbAJ4m0H2tb4Kyl1XtIUON71vjsiWcSwCfScSc uiBeScf6IjQPnwCTU5BOHNk= =B47Y -END PGP SIGNATURE- _ Unsubscribe list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Re: Mersenne: Error 2250
I have noticed that also and will start running out of work on some PCs this week. Nathan Russell wrote: I'm getting a lot of error 2250's in the past few days. I have enough work to keep me busy until January, so this isn't the end of the world, but I still wonder - is it a known issue? Thanks much! Nathan _ Unsubscribe list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers _ Unsubscribe list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Mersenne: Error 2250
I'm getting a lot of error 2250's in the past few days. I have enough work to keep me busy until January, so this isn't the end of the world, but I still wonder - is it a known issue? Thanks much! Nathan _ Unsubscribe list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Mersenne: ERROR: Exponent not assigned to this computer.
I've seen a couple of these errors recently. Primenet assigned them to me and later says they aren't mine. I hope I'm not wasting my time. I'm running v22.8.1 under Win2k. Cheers... Russ DIGITAL FREEDOM! -- http://www.eff.org/ _ Unsubscribe list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Re: Mersenne: ERROR 7: Server has run out of exponent to assign.
At 09:28 PM 9/30/2002 +, Russel Brooks wrote: I just got this error msg when my factoring machine uploaded results and tried to get more work. ERROR 7: Server has run of exponents to assign What now? More exponents are now available. There is a prime95/primenet bug that caused this. Version 18 factoring clients are accepting assignments and tossing them (v18 was designed to only go up to 20.something million). I'll work with Brad on a solution. _ Unsubscribe list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Mersenne: ERROR 7: Server has run out of exponent to assign.
Monday 9/30 05:30 PDT I just got this error msg when my factoring machine uploaded results and tried to get more work. ERROR 7: Server has run of exponents to assign What now? Cheers... Russ DIGITAL FREEDOM! -- http://www.eff.org/ _ Unsubscribe list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Re: Mersenne: Error rates
At 08:24 PM 8/30/02 -0400, you wrote: There is a lot of interesting data in this spreadsheet. Our overall error rate is roughly 3.5%. If you have an error-free run, the error rate is in the 1.4% to 2% area. If you have an SUM(INPUTS) != SUM(OUTPUTS) error or ROUNDOFF 0.40 error that is not caused by an approaching FFT crossover, then there is a 56% chance that your LL test will be no good! Question, then: Assume for the sake of argument that you watch your results.txt files, and let's say you had THREE such errors by the time the test was 50% completed. If that 56% figure is accurate, then this hypothetical test is almost certainly no good statistically. It isn't even worth finishing the remaining 50%, is it? Would a serious tester try the test on different hardware, and/or would it be worth saving the interim files, removing them, and starting over BEFORE submitting this likely invalid result... And if the answer to the above is yes, then why can't Prime95 be coded to simply credit partial time, and throw the number back in favor of a smaller exponent, a double-check, or factoring work, instead of permitting work to continue for another few weeks (or months) that is likely fruitless? I wouldn't throw back a result on just one sumout error, but on multiple ones before the test is completed why are we even bothering to complete it, if we KNOW the result is not only suspect, but highly so? _ Unsubscribe list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Re: Mersenne: Error rates
This would presumably give rise to a serious problem in which people could simply claim to have done work which failed, and turn up at the server and ask for credit to their user scores. There wouldn't be a reliable way (based on current mechanisms) to cross-check the validity of their claim if the results are incorrect and can't be verified by another user. Jeff Woods wrote: And if the answer to the above is yes, then why can't Prime95 be coded to simply credit partial time, and throw the number back in favor of a smaller exponent, a double-check, or factoring work, instead of permitting work to continue for another few weeks (or months) that is likely fruitless? Yours, -- === Gareth Randall === _ Unsubscribe list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Mersenne: Error rates
A user has broken down the GIMPS error rate for exponents between 2 million and 7 million. See ftp://mersenne.org/gimps/err_rate.xls. I'd ignore the data from 6 million to 7 million as there are many triple-checks to be done. The data from 5 million to 6 million will not change much at all. The data from 2 million to 5 million is accurate. There is a lot of interesting data in this spreadsheet. Our overall error rate is roughly 3.5%. If you have an error-free run, the error rate is in the 1.4% to 2% area. If you have an SUM(INPUTS) != SUM(OUTPUTS) error or ROUNDOFF 0.40 error that is not caused by an approaching FFT crossover, then there is a 56% chance that your LL test will be no good! _ Unsubscribe list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Re: Mersenne: Error message from prime95 on an old Win95 box
Try http://www.sysinternals.com/ntw2k/source/regmon.shtml to get the name and value of the registry entry. (or maybe anyone knows what's going wrong) Greetings, Mohk Am Mittwoch, 17. Juli 2002 03:34 schrieb A T Schrum: Hi Folks, I didn't find a reference to this problem. My old PentiumMMX 200 Mhz box running Win95 OSR2 (with tons of patches) now has Prime95 2.26.1 on it and it runs reasonably faster (about 20ms faster at 768K FFT size). But upon startup, Prime95 reports Can't write registry value and continues on. Should I be concerned? Thanks, -Allan _ Unsubscribe list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers _ Unsubscribe list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Re: Mersenne: Error message from prime95 on an old Win95 box
At 09:34 PM 7/16/2002 -0400, A T Schrum wrote: I didn't find a reference to this problem. My old PentiumMMX 200 Mhz box running Win95 OSR2 (with tons of patches) now has Prime95 2.26.1 on it and it runs reasonably faster (about 20ms faster at 768K FFT size). But upon startup, Prime95 reports Can't write registry value and continues on. Should I be concerned? I doubt it. Prime95 should be trying to create a registry entry to run the program at bootup. If you uncheck the Options/Start at Bootup menu item the problem should go away. I'm curious though. Do other Win95 users have the same trouble? _ Unsubscribe list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Re: Mersenne: Error message from prime95 on an old Win95 box
No go. The box was unchecked. I checked it, restarted Prime95, and the error message was not there. So I unchecked it, restarted Prime95, and the error message came back. George Woltman wrote: At 09:34 PM 7/16/2002 -0400, A T Schrum wrote: I didn't find a reference to this problem. My old PentiumMMX 200 Mhz box running Win95 OSR2 (with tons of patches) now has Prime95 2.26.1 on it and it runs reasonably faster (about 20ms faster at 768K FFT size). But upon startup, Prime95 reports Can't write registry value and continues on. Should I be concerned? I doubt it. Prime95 should be trying to create a registry entry to run the program at bootup. If you uncheck the Options/Start at Bootup menu item the problem should go away. I'm curious though. Do other Win95 users have the same trouble? _ Unsubscribe list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Re: Mersenne: Error message from prime95 on an old Win95 box
Sounds like the opposite problem: Prime95 is trying to delete a registry entry that doesn't exist. I had one do that to me recently. Rather than uncheck the box, manually edit ( in prime.ini ) the line windows service=1 (or whatever line it has to that effect) to ...=0 and it will no longer see a need to try to delete the registry entry. And the box will now show as unchecked. Hope that helps, Steve Harris -Original Message- From: A T Schrum [EMAIL PROTECTED] Date: Wednesday, July 17, 2002 5:26 PM No go. The box was unchecked. I checked it, restarted Prime95, and the error message was not there. So I unchecked it, restarted Prime95, and the error message came back. George Woltman wrote: At 09:34 PM 7/16/2002 -0400, A T Schrum wrote: I didn't find a reference to this problem. My old PentiumMMX 200 Mhz box running Win95 OSR2 (with tons of patches) now has Prime95 2.26.1 on it and it runs reasonably faster (about 20ms faster at 768K FFT size). But upon startup, Prime95 reports Can't write registry value and continues on. Should I be concerned? I doubt it. Prime95 should be trying to create a registry entry to run the program at bootup. If you uncheck the Options/Start at Bootup menu item the problem should go away. I'm curious though. Do other Win95 users have the same trouble? _ Unsubscribe list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers _ Unsubscribe list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Re: Mersenne: Error message from prime95 on an old Win95 box
At 06:01 PM 7/17/2002 -0400, A T Schrum wrote: No go. The box was unchecked. I checked it, restarted Prime95, and the error message was not there. So I unchecked it, restarted Prime95, and the error message came back. I reactivated an old Win98 box for debugging. You are correct. The error message is harmless. I've got a fix ready for download at ftp://mersenne.org/p95v227.zip The only new feature a v22.7 is SSE2 based trial factoring for factors above 2^64. It is about 4 times faster than v22.6. Since most P4 users are getting assigned prefactored exponents, the speedup is of no value. However, if you are working on 10 million digit numbers, you may get assigned a number that needs factoring and the new code will certainly help. _ Unsubscribe list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Re: Mersenne: Error message from prime95 on an old Win95 box
Hi Steve, My current prime.ini has Windows95Service=0, and the Win95 Service box is not checked. However, whenever the program starts, it gives me the Can't write registry value error. I looked into the latest source (source22.zip) and I see that for Win95 systems, it seems to always try to delete the key: HKEY_LOCAL_MACHINE\ Software\ Microsoft\ CurrentVersion\ RunServices\ Prime95 but cannot because it is not there (as you said). This is in the routine Service95(). But this is not supposed to be called unless Prime95 is setup as a Windows service. For some reason, on my Win95 box, Service95() is always called. I tried deleting the Windows95Service option from prime.ini, then set Prime95 to be a service and it properly changed the prime.ini file. I do not use the -A option with Prime95, so the prime.ini in the Prime95.exe directory is used. But whether the Windows95Service option is deleted or just set to zero, I still get the error. The code in Prime95.cpp looks fine, but I must be missing something. But wait, there's more. Just for grins, I tried it on my Win98 SE box and it shows the same behavior! If I uncheck the Start at bootup box, restart Prime95, I get the exact same error message. So this is not a Win95-specific problem. I always had my Win98 box set with Start at bootup so I never noticed this before. And just for more fun, I found another problem with Prime95 in how it operates. I have my Prime95 setup with Tray Icon. If I start Prime95, double-click on the icon to open Prime95, do a File- Exit real quick, the program hangs and stops responding to all mouse clicks. At this point, you must kill it. This is reproducible on my Win98 and Win95 box. If you wait a few more seconds before doing the File- Exit, then there is no problem. Note to everyone else: None of these problems are critical to the operation of Prime95. They amount to minor annoyances, so please don't blow this out of proportion. The details I supplied are to help George figure this out sometime when he is looking for something to do :-) Thanks for the air time. Regards, -Allan Steve Harris wrote: Sounds like the opposite problem: Prime95 is trying to delete a registry entry that doesn't exist. I had one do that to me recently. Rather than uncheck the box, manually edit ( in prime.ini ) the line windows service=1 (or whatever line it has to that effect) to ...=0 and it will no longer see a need to try to delete the registry entry. And the box will now show as unchecked. Hope that helps, Steve Harris _ Unsubscribe list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Mersenne: Error message from prime95 on an old Win95 box
Hi Folks, I didn't find a reference to this problem. My old PentiumMMX 200 Mhz box running Win95 OSR2 (with tons of patches) now has Prime95 2.26.1 on it and it runs reasonably faster (about 20ms faster at 768K FFT size). But upon startup, Prime95 reports Can't write registry value and continues on. Should I be concerned? Thanks, -Allan _ Unsubscribe list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Mersenne: ERROR: ROUND OFF
Hi all! Recentely Laura, one of my PCs started testing some Exponents close to the 768K FFT size boundary (i.e. M15143XXX etc.). Even with very reliable hardware, first of all 4X128 MB of ECC Kingston RIMM Modules, this time I wasn't able to avoid a long list of round off errors. This is an excerpt of Laura's results.txt file: [Thu May 30 10:42:24 2002] UID: guido72/Laura, M13612567 is not prime. Res64: E9A2C7414783CCD4. WX1: B3E434EC,11882707, [Fri May 31 17:31:08 2002] UID: guido72/Laura, M15143129 no factor to 2^65, WX1: 916F64C6 [Sun Jun 02 05:53:42 2002] Iteration: 2497408/15143129, ERROR: ROUND OFF (0.40625) 0.40 Possible hardware failure, consult the readme file. Continuing from last save file. [Sun Jun 02 06:00:19 2002] Disregard last error. Result is reproducible and thus not a hardware problem. [Tue Jun 04 22:11:24 2002] Iteration: 6883072/ , ERROR: ROUND OFF (0.40625) 0.40 Possible hardware failure, consult the readme file. Continuing from last save file. [Tue Jun 04 22:17:08 2002] Disregard last error. Result is reproducible and thus not a hardware problem. [Wed Jun 05 08:23:32 2002] Iteration: 7578880/15143129, ERROR: ROUND OFF (0.40625) 0.40 Possible hardware failure, consult the readme file. Continuing from last save file. [Wed Jun 05 08:31:58 2002] Disregard last error. Result is reproducible and thus not a hardware problem. [Fri Jun 07 19:59:42 2002] Iteration: 9193600/15143129, ERROR: ROUND OFF (0.40625) 0.40 Possible hardware failure, consult the readme file. Continuing from last save file. [Fri Jun 07 20:07:10 2002] Disregard last error. Result is reproducible and thus not a hardware problem. [Sat Jun 08 10:40:20 2002] Iteration: 10195072/15143129, ERROR: ROUND OFF (0.4375) 0.40 Possible hardware failure, consult the readme file. Continuing from last save file. [Sat Jun 08 10:54:02 2002] Disregard last error. Result is reproducible and thus not a hardware problem. [Sat Jun 08 12:29:26 2002] Iteration: 10304384/15143129, ERROR: ROUND OFF (0.40625) 0.40 Possible hardware failure, consult the readme file. Continuing from last save file. [Sat Jun 08 12:39:18 2002] Disregard last error. Result is reproducible and thus not a hardware problem. [Sat Jun 08 18:55:12 2002] Iteration: 10736384/15143129, ERROR: ROUND OFF (0.4375) 0.40 Possible hardware failure, consult the readme file. Continuing from last save file. [Sat Jun 08 19:04:09 2002] Disregard last error. Result is reproducible and thus not a hardware problem. [Sun Jun 09 08:38:35 2002] Iteration: 11667200/15143129, ERROR: ROUND OFF (0.4375) 0.40 Possible hardware failure, consult the readme file. Continuing from last save file. [Sun Jun 09 08:43:42 2002] Disregard last error. Result is reproducible and thus not a hardware problem. [Sun Jun 09 20:53:10 2002] Iteration: 12505600/15143129, ERROR: ROUND OFF (0.40625) 0.40 Possible hardware failure, consult the readme file. Continuing from last save file. [Sun Jun 09 21:03:53 2002] Disregard last error. Result is reproducible and thus not a hardware problem. [Mon Jun 10 07:45:44 2002] Iteration: 13239424/15143129, ERROR: ROUND OFF (0.40625) 0.40 Possible hardware failure, consult the readme file. Continuing from last save file. [Mon Jun 10 07:59:14 2002] Disregard last error. Result is reproducible and thus not a hardware problem. [Tue Jun 11 13:01:29 2002] UID: guido72/Laura, M15143129 is not prime. Res64: 1E14FF04F4FEB4CA. WX1: F611E917,4574601,0A000A00 As you may see from the 1st line of this file, the problems started just with these border line exponents. Are these results correct or am I returning useless data to the g.i.m.p.s.? I've tryed to downclock the Cpu, after having improoved its cooling system, but with no benefits. Is it better to unreserve these exponents? Thanks a lot for any piece of an advice! Best regards from Italy! PS. Hey George! Take a look to the top 100 producers list: I've definitively entered it, both of them, yours and Primenet one as well!! I think I'll climb a bit more before my (our) first MPrime discovery ;-) _ Unsubscribe list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Re: Mersenne: ERROR: ROUND OFF
At 10:20 PM 6/15/2002 +0200, Guido Lorenzini wrote: Recentely Laura, one of my PCs started testing some Exponents close to the 768K FFT size boundary (i.e. M15143XXX etc.). As you may see from the 1st line of this file, the problems started just with these border line exponents. Are these results correct or am I returning useless data to the g.i.m.p.s.? Your Pentium 4 does not have any hardware problems. Your result is likely OK as all your errors were below 0.5. Your result would only be incorrect if you had a 0.5625 error (prime95 will see that as a 0.4375 error). Here's what you need to do. Get version 22 from ftp://mersenne.org/gimps/p95v22.zip The FFT crossovers have been made more conservative (precisely because of your problem). _ Unsubscribe list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Mersenne: error result
I've been in GIMPS since before the first one was discovered. Today I finished an exponent, and saw some stuff I haven't seen before. After it completed, it said M14776187 stage 1 complete ---transformations --- time starting stage 1 GCD stage 1 GCD complete ERROR: factor doesn't divide N! contacting server etc. What went wrong? It looks like at the end of the L-L test, it did a GCD, thought it found a factor, but it wasn't a factor. For a while during this exponent, I had quick user switching on with WinXP. When I realized that prime95 was running twice as slow, I figured out that quick switching was causing two copies of primr95 to run. Could that cause a problem? +-+ | Jud McCranie | | | | Programming Achieved with Structure, Clarity, And Logic | +-+ _ Unsubscribe list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Re: Mersenne: error result
From: Jud McCranie [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, 24. May 2002 17:30 Subject: Mersenne: error result I've been in GIMPS since before the first one was discovered. Today I finished an exponent, and saw some stuff I haven't seen before. After it completed, it said M14776187 stage 1 complete ---transformations --- time starting stage 1 GCD stage 1 GCD complete ERROR: factor doesn't divide N! contacting server etc. The help file says this bug was fixed with version 20.5 concerning P-1 or ECM. Dieter Schmitt _ Unsubscribe list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Re: Mersenne: error result
Hi all, At 08:41 PM 5/24/2002 +0200, Dieter Schmitt wrote: stage 1 GCD complete ERROR: factor doesn't divide N! contacting server etc. The help file says this bug was fixed with version 20.5 concerning P-1 or ECM. Well another bug was fixed in 22.3. You either had a hardware glitch or ran across a rare GCD bug. Your diagnosis was correct. GCD returned a factor, but when prime95 tried verifying it the factor did not divide the Mersenne number. All in all, don't worry about it. The bug is rare enough that upgrading is not terribly important. _ Unsubscribe list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Re: Mersenne: error result
At 04:04 PM 5/24/2002 -0400, George Woltman wrote: Well another bug was fixed in 22.3. Is that available? The download page says version 21. +-+ | Jud McCranie | | | | Programming Achieved with Structure, Clarity, And Logic | +-+ _ Unsubscribe list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Re: Mersenne: error result
At 08:41 PM 5/24/2002 +0200, Dieter Schmitt wrote: The help file says this bug was fixed with version 20.5 concerning P-1 or ECM. I'm using ver 21.4.1. +-+ | Jud McCranie | | | | Programming Achieved with Structure, Clarity, And Logic | +-+ _ Unsubscribe list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Re: Mersenne: error: Another mprime is already running!
On Friday 01 March 2002 00:40, Mary K. Conner wrote: At 05:17 PM 2/28/02 -0500, George Woltman wrote: mprime should only raise this error if the pid in the local.ini file and the current pid are both running mprime (actually comparing the inode values). If there are any Linux experts that can tell me where this test is going wrong, I'd appreciate any insights. This is the first reported failure in 2 years. I'll have a look at the code see what I can come up with. I mucked about with it a bit, and it does appear that if the process running under the pid in the local.ini file is not mprime, it will not raise the error. Comparing inodes, if there is a hard link under two different names, it would raise the error. I.e. someone does 'ln mprime ll', runs ll, then tries to run mprime, the inodes will match although there is no process named 'mprime' running (it is possible to force the process to be named mprime by overwriting argv[0], at least on some systems). Someone might do the hard link if they are trying to save space on installations to run on multiple CPU's, I don't have a multiCPU machine, so I've never done such an installation. That would be a crude and surely unusual way of economising. un*x gurus normal Good Practise to keep executable binaries and scripts seperate from the data, as opposed to the Windows practise of keeping them all mixed up (which makes it much more awkward to set a proper security policy). I think practically every user setup script on unix-like systems (including linux) adds $HOME/bin to $PATH so the obvious place to store mprime is to create a bin directory in your home directory (if it doesn't already exist) put the binary executable in there. On a multi-cpu system you can then set up a directory for each CPU. None of these working directories need to, or should, contain a copy of mprime. So long as each instance has its own copy of local.ini, there will be no problem with Another copy is already running. Of course it is counterproductive to run more instances of mprime than there are processors in the system. (Real processors or virtual processors when running on the new Xeons with hyperthreading? I don't know ... but apparently Windows thinks a dual-processor system has four CPUs ... obviously there is scope for confusion here, especially if you have to rely on what the OS tells you, rather than being able to take off the cover and eyeball the hardware!) Regards Brian Beesley _ Unsubscribe list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Re: Mersenne: error: Another mprime is already running!
At 08:58 PM 3/1/02 +, Brian J Beesley wrote: That would be a crude and surely unusual way of economising Definitely so, but it's the only way I can think of that someone might use a hard link when installing mprime For someone coming from Windows, that might be the way they think to do it I couldn't think of any other non-freak-error way for this error to occur when no process named mprime was running _ Unsubscribe list info -- http://wwwndatechcom/mersenne/signuphtm Mersenne Prime FAQ -- http://wwwtasamcom/~lrwiman/FAQ-mers
Mersenne: Error: Primenet error 12031
? Regards Daran G. _ Unsubscribe list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
RE: Mersenne: ERROR 7: Server has run out of exponents to assign
I just sent in the results for an exponent and got the same error. According to the PrimeNet status page http://mersenne.org/primenet/ there are several thousand exponents available for factoring between 1340 and 1700. The server just isn't handing them out for some reason. Matt -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Kel Utendorf Sent: Wednesday, July 18, 2001 3:43 PM To: [EMAIL PROTECTED] Subject: Mersenne: ERROR 7: Server has run out of exponents to assign Hi All, Anyone else seeing this error? I'm trying to get exponents to factor but the server reports that there are none available...is that right? Am I seeing a server glitch? Thanks, Kel __ ___ Unsubscribe list info -- http://www.scruz.net/~luke/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers _ Unsubscribe list info -- http://www.scruz.net/~luke/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Re: Mersenne: Error 11: exponent already tested!?!
For those unaware of this PrimeNet feature: To extend an assignment or assignments up to 120 days, see: http://www.mersenne.org/ips/manualtests.html "Extend Exponent Assignments" toward the bottom of the page! Best Wishes, Stefanovic It should possibly be added that one does not need immediate access to the machine running the exponent to do this; all that is needed it to copy the exponent to the form! Nathan _ Unsubscribe list info -- http://www.scruz.net/~luke/signup.htm Mersenne Prime FAQ -- http://www.exu.ilstu.edu/mersenne/faq-mers.txt
Re: Mersenne: Error 11: exponent already tested!?!
On 20 Jul 2000 00:09:20 -0400 "Robert Deininger" [EMAIL PROTECTED] wrote: I have saved some of the hourly status and cleared reports, and I think I see what happened. On 13-May-2000: 8277083 64 4126527 105.0 -12.1 42.9 16-Apr-00 19:40 29-Jan-00 22:24 floris Vincent This exponent was assigned to floris on 29-Jan-2000. On 25-Jun-2000: 8277083 64 4126527 148.0 -55.1 -0.1 16-Apr-00 19:40 29-Jan-00 22:24 floris Vincent The exponent had just expired, but is still assigned to floris. I realize there are participants who will undergo "agonies similar to giving birth" unless ALL exponents through xxx are checked by such-and-such a date. Nevertheless, as the exponents being worked on start taking longer and longer on any given machine, could we PLEASE refocus GIMPS recordkeeping on the 'humane' aspect of the effort, rather than on the 'treadmill' aspect ? Because the GIMPS expiration limit has stayed at 60 days (rather than increasing with the exponents) I no longer try to run LL tests with my K6-III machine. [I run offline. If I am forced to "check in" by a given date even though I have not finished, for me it is simpler to just decline to participate.] The material I quoted from Robert Deininger appears to me to indicate that somebody who was working on an exponent failed to "check in" for at least 70 days. The exponent got assigned to a second person, who got upset when the original person suddenly completed his LL test. Wouldn't it be more 'humane' to wait a bit (i.e., to not 'expire' assignments after 70 days) ? Will the project truly suffer if "seemingly abandoned" exponents are NOT reassigned on a 'treadmill' schedule ? mikus _ Unsubscribe list info -- http://www.scruz.net/~luke/signup.htm Mersenne Prime FAQ -- http://www.exu.ilstu.edu/mersenne/faq-mers.txt
RE: Mersenne: Error 11: exponent already tested!?!
Another enhancement would be to add the functionality to force a checkin with the server. Currently I have found the only way to do this is to alter the number of hours per day field. This is fairly minor compared to the problem of duplicated effort mentioned below but may elevate the problem slightly. Cheers Andy -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Mikus Grinbergs Sent: Thursday, July 20, 2000 1:14 PM To: [EMAIL PROTECTED] Subject: Re: Mersenne: Error 11: exponent already tested!?! On 20 Jul 2000 00:09:20 -0400 "Robert Deininger" [EMAIL PROTECTED] wrote: I have saved some of the hourly status and cleared reports, and I think I see what happened. On 13-May-2000: 8277083 64 4126527 105.0 -12.1 42.9 16-Apr-00 19:40 29-Jan-00 22:24 floris Vincent This exponent was assigned to floris on 29-Jan-2000. On 25-Jun-2000: 8277083 64 4126527 148.0 -55.1 -0.1 16-Apr-00 19:40 29-Jan-00 22:24 floris Vincent The exponent had just expired, but is still assigned to floris. I realize there are participants who will undergo "agonies similar to giving birth" unless ALL exponents through xxx are checked by such-and-such a date. Nevertheless, as the exponents being worked on start taking longer and longer on any given machine, could we PLEASE refocus GIMPS recordkeeping on the 'humane' aspect of the effort, rather than on the 'treadmill' aspect ? Because the GIMPS expiration limit has stayed at 60 days (rather than increasing with the exponents) I no longer try to run LL tests with my K6-III machine. [I run offline. If I am forced to "check in" by a given date even though I have not finished, for me it is simpler to just decline to participate.] The material I quoted from Robert Deininger appears to me to indicate that somebody who was working on an exponent failed to "check in" for at least 70 days. The exponent got assigned to a second person, who got upset when the original person suddenly completed his LL test. Wouldn't it be more 'humane' to wait a bit (i.e., to not 'expire' assignments after 70 days) ? Will the project truly suffer if "seemingly abandoned" exponents are NOT reassigned on a 'treadmill' schedule ? mikus _ Unsubscribe list info -- http://www.scruz.net/~luke/signup.htm Mersenne Prime FAQ -- http://www.exu.ilstu.edu/mersenne/faq-mers.txt _ Unsubscribe list info -- http://www.scruz.net/~luke/signup.htm Mersenne Prime FAQ -- http://www.exu.ilstu.edu/mersenne/faq-mers.txt
Re: Mersenne: Error 11: exponent already tested!?!
ot upset when the original person suddenly completed his LL test. Wouldn't it be more 'humane' to wait a bit (i.e., to not 'expire' assignments after 70 days) ? Will the project truly suffer if "seemingly abandoned" exponents are NOT reassigned on a 'treadmill' schedule ? mikus For those unaware of this PrimeNet feature: To extend an assignment or assignments up to 120 days, see: http://www.mersenne.org/ips/manualtests.html "Extend Exponent Assignments" toward the bottom of the page! Best Wishes, Stefanovic
Re: Mersenne: Error 11: exponent already tested!?!
[EMAIL PROTECTED] wrote: Another enhancement would be to add the functionality to force a checkin with the server. Currently I have found the only way to do this is to alter the number of hours per day field. This is fairly minor compared to the problem of duplicated effort mentioned below but may elevate the problem slightly. Cheers Server check-in can be done at any time using the Advanced/ Manual Communication menu selection. See the ReadMe File for more information on the Advanced Menu. Best Wishes, Stefanovic _ Unsubscribe list info -- http://www.scruz.net/~luke/signup.htm Mersenne Prime FAQ -- http://www.exu.ilstu.edu/mersenne/faq-mers.txt
Re: Mersenne: Error 11: exponent already tested!?!
Hi all, At 08:01 PM 7/19/00 -0700, Dennis Peter wrote: I'm testing exponent 8277083 and I'm about 45% done. Every other time I've checked in, it was OK. Now I get this error message and the exponent is gone from my GIMPS user status page. I HOPE I DIDN'T WASTE MY CPU CYCLES. You did not. If you complete the exponent it will serve as a valid double-check. If you do not wish to complete the exponent I'll bet someone on the list will be glad to take your Pnnn and complete the test. Could someone explain what has happened, and can someone tell me how to fix my client to resolve this issue?? If Floris was using the automatic method as most people are, then he did not connect to the Internet for a 60 day period. That is, after 28 days the program will start trying to contact the server saying "I'm still working on Mnnn". The server won't release the exponent until 88 days after testing began. This algorithm seems to work well as the recycle rate is rather low. There is a downside to increasing the 60 day period to a higher value. If it takes longer to recycle exponents, there will be more "holes" and the server will have to hand out larger exponents. If Floris was using the manual method, then he neglected to use the manual web pages to extend his assignment. The suggestion that the manual web pages default to a value higher than 60 days is reasonable. I'll contact the primenet guys to see if they can change it. Best regards, George _ Unsubscribe list info -- http://www.scruz.net/~luke/signup.htm Mersenne Prime FAQ -- http://www.exu.ilstu.edu/mersenne/faq-mers.txt
Re: Mersenne: Error 11: exponent already tested!?!
Hi, Ahh. OK. I see now. I'm glad that my exponent will count as a double check. Thanks to everyone that answered! -Dennis Original Message Follows From: George Woltman [EMAIL PROTECTED] To: "Dennis Peter" [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: Mersenne: Error 11: exponent already tested!?! Date: Thu, 20 Jul 2000 14:01:21 -0400 Hi all, At 08:01 PM 7/19/00 -0700, Dennis Peter wrote: I'm testing exponent 8277083 and I'm about 45% done. Every other time I've checked in, it was OK. Now I get this error message and the exponent is gone from my GIMPS user status page. I HOPE I DIDN'T WASTE MY CPU CYCLES. You did not. If you complete the exponent it will serve as a valid double-check. If you do not wish to complete the exponent I'll bet someone on the list will be glad to take your Pnnn and complete the test. Could someone explain what has happened, and can someone tell me how to fix my client to resolve this issue?? If Floris was using the automatic method as most people are, then he did not connect to the Internet for a 60 day period. That is, after 28 days the program will start trying to contact the server saying "I'm still working on Mnnn". The server won't release the exponent until 88 days after testing began. This algorithm seems to work well as the recycle rate is rather low. There is a downside to increasing the 60 day period to a higher value. If it takes longer to recycle exponents, there will be more "holes" and the server will have to hand out larger exponents. If Floris was using the manual method, then he neglected to use the manual web pages to extend his assignment. The suggestion that the manual web pages default to a value higher than 60 days is reasonable. I'll contact the primenet guys to see if they can change it. Best regards, George Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com _ Unsubscribe list info -- http://www.scruz.net/~luke/signup.htm Mersenne Prime FAQ -- http://www.exu.ilstu.edu/mersenne/faq-mers.txt
Mersenne: Error 11: exponent already tested!?!
I got this error on my GIMPS client (version 20.4.1) x86: Error 11: exponent already tested I'm testing exponent 8277083 and I'm about 45% done. Every other time I've checked in, it was OK. Now I get this error message and the exponent is gone from my GIMPS user status page. Yet, the client continues to work on it. I HOPE I DIDN'T WASTE MY CPU CYCLES. Somehow, the exponent got cleared. It's in the cleared.txt document. (The cleared exponents page). It was cleared July 19th by a user named "Floris". Thanks Floris. I didn't know the server was checking out multiple exponents. Could someone explain what has happened, and can someone tell me how to fix my client to resolve this issue?? -Dennis Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com _ Unsubscribe list info -- http://www.scruz.net/~luke/signup.htm Mersenne Prime FAQ -- http://www.exu.ilstu.edu/mersenne/faq-mers.txt
Re: Mersenne: Error 11: exponent already tested!?!
On Wed, Jul 19, 2000 11:01 PM, Dennis Peter [EMAIL PROTECTED] wrote: I got this error on my GIMPS client (version 20.4.1) x86: Error 11: exponent already tested I'm testing exponent 8277083 and I'm about 45% done. Every other time I've checked in, it was OK. Now I get this error message and the exponent is gone from my GIMPS user status page. Yet, the client continues to work on it. I HOPE I DIDN'T WASTE MY CPU CYCLES. Somehow, the exponent got cleared. It's in the cleared.txt document. (The cleared exponents page). It was cleared July 19th by a user named "Floris". Thanks Floris. I didn't know the server was checking out multiple exponents. Could someone explain what has happened, and can someone tell me how to fix my client to resolve this issue?? I have saved some of the hourly status and cleared reports, and I think I see what happened. On 13-May-2000: 8277083 64 4126527 105.0 -12.1 42.9 16-Apr-00 19:40 29-Jan-00 22:24 floris Vincent This exponent was assigned to floris on 29-Jan-2000. On 25-Jun-2000: 8277083 64 4126527 148.0 -55.1 -0.1 16-Apr-00 19:40 29-Jan-00 22:24 floris Vincent The exponent had just expired, but is still assigned to floris. On 26-Jun-2000: 8277083 64 0.7 34.5 66.5 26-Jun-00 10:24 26-Jun-00 06:44 timbit home1 The exponent has been re-assigned to you, and you didn't realize it was previously assigned to floris. floris/Vincent continued to work on the exponent, finished the LL test in the last day or two, and checked in the result. I don't know why the server accepted the result, since the exponent was no longer assigned to floris. I think this was an error. Probably you should continue the LL test and get credit for double checking. I guess you should contant the primenet administrator and ask for some manual intervention to make sure your work isn't wasted. Alas, it appears the first LL test has been completed and checked in. Bummer. -- Robert --- Robert Deininger [EMAIL PROTECTED] _ Unsubscribe list info -- http://www.scruz.net/~luke/signup.htm Mersenne Prime FAQ -- http://www.exu.ilstu.edu/mersenne/faq-mers.txt
Re: Mersenne: Error
On 25 May 00, at 23:39, Ken Kriesel wrote: I saw something similar once, out of hundreds of ECM curves that I've run. It happened on the curve being run while I adjusted memory limits on the program (Version 20.4.1, April 25 file date), if I recall correctly. There was a problem with some versions which resulted in this error message appearing constantly. I think the problem was related to a factor which was already known being found again - this happens constantly but should be resolved by reference to the low?.txt file. [Thu May 25 15:00:24 2000] ECM found a factor in curve #263, stage #2 Sigma=1155032128984, B1=25, B2=2500. ERROR: Factor doesn't divide N! Suggest you ensure that you're running v20.4 that your lowm.txt file is up-to-date not corrupt. Sometimes you can get extra carriage returns in the file as a consequence of the way in which it's downloaded. Otherwise it's one for George. BTW from George's ECM status pages it seems that either factors have become _very_ hard to find recently. Anyone have any views on this? Regards Brian Beesley _ Unsubscribe list info -- http://www.scruz.net/~luke/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Re: Mersenne: Error
Brian, BTW from George's ECM status pages it seems that either factors have become _very_ hard to find recently. Anyone have any views on this? If you are referring to the normal factoring that Prime95 does, I am still getting them, I have also noticed a tendency to get quite a few '2 in a row' by that I mean if I get a factor, the next number is often a factor, far more than you would expect by chance, is there a reason for this ? My account name is 'MOates' if you want to check. PS. I am not a mathematician! Regards, Mike, -- ATLAS CELESTE - Bevis Star Atlas - "The CD-ROM" http://www.u-net.com/ph/mas/bevis/ Astronomy in the UKhttp://www.u-net.com/ph/ _ Unsubscribe list info -- http://www.scruz.net/~luke/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Re: Mersenne: Error
"Brian J. Beesley" wrote: On 25 May 00, at 23:39, Ken Kriesel wrote: I saw something similar once, out of hundreds of ECM curves that I've run. It happened on the curve being run while I adjusted memory limits on the program (Version 20.4.1, April 25 file date), if I recall correctly. There was a problem with some versions which resulted in this error message appearing constantly. I think the problem was related to a factor which was already known being found again - this happens constantly but should be resolved by reference to the low?.txt file. I got the same error in a F14 curve (I jumped out of my seat). George told me that it was a bug in v20.1 where the GCD routine sometimes returned bogus factors, which were then trapped in a sanity check. That error was fixed in 20.3 . I dont know about errors by faulty low[mp].txt files, but that sure was not the reason in my case, as F14 has no known factors and the error occurred only once out of hundreds of curves. [Thu May 25 15:00:24 2000] ECM found a factor in curve #263, stage #2 Sigma=1155032128984, B1=25, B2=2500. ERROR: Factor doesn't divide N! Suggest you ensure that you're running v20.4 that your lowm.txt file is up-to-date not corrupt. Sometimes you can get extra BTW from George's ECM status pages it seems that either factors have become _very_ hard to find recently. Anyone have any views on this? I think the 2^p+1 list still offers a few good candidates. There have been much fewer curves run on them than on their "2 less" counterparts. I'm focusing on F14 right now, while Richard Crandall's challenge still is on, but predictably, nothing much happened so far. Ciao, Alex. _ Unsubscribe list info -- http://www.scruz.net/~luke/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Re: Mersenne: Error
"Brian J. Beesley" wrote: There was a problem with some versions which resulted in this error message appearing constantly. I think the problem was related to a factor which was already known being found again - this happens constantly but should be resolved by reference to the low?.txt file. I am running v20.4.1, so I suspect I'm okay in that regard. I got the same error in a F14 curve (I jumped out of my seat). George told me that it was a bug in v20.1 where the GCD routine sometimes returned bogus factors, which were then trapped in a sanity check. That error was fixed in 20.3 . I dont know about errors by faulty low[mp].txt files, but that sure was not the reason in my case, as F14 has no known factors and the error occurred only once out of hundreds of curves. The exponent that I was running also has no known factors. BTW from George's ECM status pages it seems that either factors have become _very_ hard to find recently. Anyone have any views on this? I think the 2^p+1 list still offers a few good candidates. There have been much fewer curves run on them than on their "2 less" counterparts. I'm focusing on F14 right now, while Richard Crandall's challenge still is on, but predictably, nothing much happened so far. Ciao, Alex. I deliberately run ECM on exponents that 1) are relatively large and do not appear to be "immortal". For example, I wouldn't devote a large chuck of time to, say, M727, which has occupied the "hot seat" since I have joined GIMPS. I wonder how long it's been there... -or- 2) have had much less ECM run than their immediate neighbors. Examples would be M751 and F13. I have 250 curves on M751 queued to run, simply because I feel that the larger thrill connected with cracking such a nearly "immortal" exponent is worth the reduced chance, and because that exponent is currently less factored than its neighbors, making this a good opportunity to run a low unfactored exponent. Nathan Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com _ Unsubscribe list info -- http://www.scruz.net/~luke/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Mersenne: Error
I just got this in an ECM run on M(10079). What does it mean? Is something wrong with my machine? [Thu May 25 15:00:24 2000] ECM found a factor in curve #263, stage #2 Sigma=1155032128984, B1=25, B2=2500. ERROR: Factor doesn't divide N! Nathan Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com _ Unsubscribe list info -- http://www.scruz.net/~luke/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Re: Mersenne: Error
I saw something similar once, out of hundreds of ECM curves that I've run. It happened on the curve being run while I adjusted memory limits on the program (Version 20.4.1, April 25 file date), if I recall correctly. Ken At 03:42 PM 5/25/2000 EDT, you wrote: I just got this in an ECM run on M(10079). What does it mean? Is something wrong with my machine? [Thu May 25 15:00:24 2000] ECM found a factor in curve #263, stage #2 Sigma=1155032128984, B1=25, B2=2500. ERROR: Factor doesn't divide N! Nathan _ Unsubscribe list info -- http://www.scruz.net/~luke/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Re: Mersenne: error
On 17 May 00, at 16:57, Bruce A Metcalf wrote: I had a similar incident this past week running Prime95 version 20.4.1 under Windoze95 testing in the 4.7M range. Since it *is* a Windoze machine, I first tried just rebooting, only to get the same failure immediately upon Prime95 starting. I then reinstalled Prime95 from the download zip file and have been running fine since. No corruption of the data files were observed, and no reptition of the crash has yet occurred. If there's a sudden burst of these incidents, maybe something external is to blame. Maybe a virus infecting Prime95 or one of the DLLs it uses; could also be something hitting the comms routines in Windows. It's perhaps not coincidental that the PrimeNet server seems to have been having problems recently. Benny says (private communication) that the refreshed program found both his savefiles corrupt, so he's had to restart :( Perhaps this is a good time to suggest: (a) running a periodic backup job including the files in your Prime95 directory, so that you have something fairly recent to fall back on in the event of disaster; (b) adding a line "InterimFiles=100" to prime.ini, then exit restart Prime95/NTPrime. With v19.2 and v20.x, this will cause an extra save file to be written every 100 iterations, this extra save file will be kept indefinitely is therefore useful as a fallback. Also valuable if you run into hardware reliability problems e.g. a failed cooling fan. Note 1, you can change the value 100 if you wish. Note 2, to get rid of surplus save files you have to delete them manually. If there is any data I could collect on the occasion of another crash that could help analysis of the bug, please let me know and I'll try to secure and report same. At least write down everything in the error box. Don't rely exclusively on e.g. screen capture software, which may not function correctly on a system which is in some sort of distress. Regards Brian Beesley _ Unsubscribe list info -- http://www.scruz.net/~luke/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Mersenne: error
Hi, I've been using prime95 since sept. 1998 and never had any problems. Until yesterday I was testing an exponent in the 9.5 - 10 million range, but suddenly an error appeared while contacting the Primenet server (the exponent was almost finished +98%). I got the commen windows 95 error message: This program has performed an illegal operation and will be shut down. Details: PRIME95 caused an exception 6d9H in module KERNEL32.DLL at 0137:bff9a3c0. Registers: EAX=0098f2c0 CS=0137 EIP=bff9a3c0 EFLGS=0246 EBX=0005 SS=013f ESP=0098f2bc EBP=0098f310 ECX=0098f440 DS=013f ESI=0098f380 FS=38d7 EDX= ES=013f EDI=006308a4 GS=232e Bytes at CS:EIP: 5e 8b e5 5d c2 10 00 64 a1 00 00 00 00 55 8b ec Stack dump: 0098f380 06d9 bff9a3c0 bff798cf 816b508c 006308a4 7fcce1c0 00630914 06ba 006308a4 0098f354 7fccdd25 Every time I restart the program I get this same error. I restarted my computer many times but it doesn't seem to make any difference. Any suggestions ? Many thanks, Benny _ Unsubscribe list info -- http://www.scruz.net/~luke/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Re: Mersenne: error
On 17 May 00, at 9:57, Benny.VanHoudt wrote: I've been using prime95 since sept. 1998 and never had any problems. Until yesterday I was testing an exponent in the 9.5 - 10 million range, but suddenly an error appeared while contacting the Primenet server (the exponent was almost finished +98%). I got the commen windows 95 error message: This program has performed an illegal operation and will be shut down. Are you using HTTP or RPC to communicate with the PrimeNet server? If you're using RPC, try changing to HTTP. If you have a local proxy configured, make sure it's still operational. The other thing you could try is restoring the two .dll files which should be in the Prime95 directory; download a fresh copy of prime95.zip (from my server ftp://lettuce.edsc.ulst.ac.uk/gimps/software/prime95.zip if entropia.com is still being uncooperative) extract them. Or simply restore the files from a backup. That's what I did and the previous problem disappeared. The result is that prime95 is working again but was unable to use the files with the intermediate results. As a result it's starting all over again. It took my PC more than two months to get to the current point, and the exponent would have expired on the 19th of may. Any suggestions ? Benny Regards Brian Beesley --- Benny Van Houdt, University of Antwerp Dept. Math. and Computer Science PATS - Performance Analysis of Telecommunication Systems Research Group Universiteitsplein, 1 B-2610 Antwerp Belgium email: [EMAIL PROTECTED] _ Unsubscribe list info -- http://www.scruz.net/~luke/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Re: Mersenne: error
On 17 May 00, at 11:30, Benny.VanHoudt wrote: That's what I did and the previous problem disappeared. The result is that prime95 is working again but was unable to use the files with the intermediate results. As a result it's starting all over again. It took my PC more than two months to get to the current point, and the exponent would have expired on the 19th of may. Dou you still have the old savefiles and the worktodo.ini file? If they are in the same directory as Prime95 then it should just continue from wherever it was at when the last savefile was written. You could try renaming the Pnnn file to something else, then renaming Qnnn to Pnnn, this will fix any problem due to the Pnnn file being corrupt. (Where nnn is the exponent) If you're still out of luck, but have the files you think are neccessary, get back to me I'll take a look at them for you. Regards Brian Beesley _ Unsubscribe list info -- http://www.scruz.net/~luke/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Re: Mersenne: error
At 09:57 AM 5/17/00 +0200, Benny.VanHoudt wrote: I've been using prime95 since sept. 1998 and never had any problems. Until yesterday I was testing an exponent in the 9.5 - 10 million range, but suddenly an error appeared while contacting the Primenet server (the exponent was almost finished +98%). I got the commen windows 95 error message: This program has performed an illegal operation and will be shut down. I had a similar incident this past week running Prime95 version 20.4.1 under Windoze95 testing in the 4.7M range. Since it *is* a Windoze machine, I first tried just rebooting, only to get the same failure immediately upon Prime95 starting. I then reinstalled Prime95 from the download zip file and have been running fine since. No corruption of the data files were observed, and no reptition of the crash has yet occurred. I wasn't going to offer it as a bug report until it happened again, but it looks like I'm not alone. If there is any data I could collect on the occasion of another crash that could help analysis of the bug, please let me know and I'll try to secure and report same. Bruce A. Metcalf mailto:[EMAIL PROTECTED] http://myweb.magicnet.net/bmetcalf _ Unsubscribe list info -- http://www.scruz.net/~luke/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Re: Mersenne: Error 2250 using Linux mprime
On Mon, Oct 25, 1999 at 09:48:00PM -0400, George Woltman wrote: I took the liberty of looking at this. It appears that even w/ "gcc -static", the new glibc name resolution stuff contains explicit uses of several dynamic libraries. If these libraries aren't present, gethostbyname(3) will silently fail, yielding the 2250 errors. Note that this is _intentional_ -- see the glibc faqs (haven't read the usenet discussion you're referring to). You _can_, however, compile NSS statically, although that defeats most of the purpose. This might be an idea for mprime v19.1? /* Steinar */ _ Unsubscribe list info -- http://www.scruz.net/~luke/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Mersenne: Error 2250 using Linux mprime
Hi all, This was just reported to me. Others may find it useful. Regards, George I took the liberty of looking at this. It appears that even w/ "gcc -static", the new glibc name resolution stuff contains explicit uses of several dynamic libraries. If these libraries aren't present, gethostbyname(3) will silently fail, yielding the 2250 errors. There's a discussion of this in the usenet archives at: http://x35.deja.com/getdoc.xp?AN=414019916CONTEXT=940892973.188547100hitnu m=0 I worked around this by moving the following .so's to my bootdisk for my ips machines: libc.so.6 ld-linux.so.2 libnss_dns.so.2 libresolv.so.2 This may not be ideal for everyone. _ Unsubscribe list info -- http://www.scruz.net/~luke/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Mersenne: Error 11
I just communicated with the server, and got error 11 - exponent already tested on one I'm 95% through with. (A few weeks ago I had to transfer some exponents from one machine to another, so something may have gotten mixed up in the process.) Will this still count as a double check of that exponent? I have some other exponents queued up (that I transferred) - would the communication with the server warn me if they have been tested? +-+ | Jud McCranie| | | | Programming Achieved with Structure, Clarity, And Logic | +-+ _ Unsubscribe list info -- http://www.scruz.net/~luke/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Mersenne: Error 2250 connecting to PrimeNet
I have a 486-66 running RedHat 5.0 which I just upgraded to mprime 19.0.2 this morning. It's getting error 2250 when connecting to PrimeNet. Here's what I see when I select "Help/About PrimeNet Server" from the mprime menu: Your choice: 20 Contacting PrimeNet Server. ERROR 2250: Server unavailable The FAQ at http://www.entropia.com/ips/faq.html may have more information. Unable to get version information from PrimeNet server. Hit enter to continue: This returns immediately and it appears that it's not even trying to connect. When I do the same from the old (18.1.2) version it works just fine. I can also connect to PrimeNet from 19.0.2 on another machine. The FAQ suggests I might be using RPC instead of HTTP to communicate with PrimeNet. As far as I can tell I'm not; I have a line that says "UseHTTP=1" in my prime.ini file. One change I had to make between versions is that I had to switch to using sprime.tar.gz since the old RedHat box doesn't have glibc2.1 installed. _ Unsubscribe list info -- http://www.scruz.net/~luke/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Mersenne: Error message in Ver.18
Hi, Still a bit green on all this ... I have seen an error message I am not familiar with (i.e. not illegal sum-out) But: SUM(INPUTS) ! = SUM (OUTPUTS), 669721378183728.3 = 1.130101692988369e +300 possible hardware failure...etc.I see no refernce to this in the Readme file (as opposed to illegal sumout above) Any enlightenment on this would be most appreciated!!?? All The Best, Ian McLoughlin, Chematek U.K. Tel/Fax : +44(0)1904 679906 Mobile : +44(0)7801 823421 Website: www.chematekuk.co.uk _ Unsubscribe list info -- http://www.scruz.net/~luke/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Mersenne: Error PrimeNet
Hi, PrimeNet does not yet list celeron as a processor type in the full stats, yet I can select it in prime95 v19b. Otto. _ Unsubscribe list info -- http://www.scruz.net/~luke/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Mersenne: error in V19??!?
Whoops!!! Welcome to GIMPS Prime95 v19, with remote message notification. -- George Scott [Thu Sep 09 20:20:31 1999] Factoring M6539111 to 2^63 is 13.93% complete. [Fri Sep 10 04:58:58 1999] UID: jp/p3-500, M6539111 no factor to 2^63, WV1: 3ED32B8A [Fri Sep 10 06:21:31 1999] Factoring M6779911 to 2^63 is 14.45% complete. [Fri Sep 10 13:57:40 1999] UID: jp/p3-500, M6779911 no factor to 2^63, WV1: 41132D24 [Fri Sep 10 15:17:10 1999] Factoring M8329537 to 2^64 is 8.87% complete. [Sat Sep 11 05:24:12 1999] UID: jp/p3-500, M8329537 no factor to 2^64, WV1: 4FFD3775 [Sat Sep 11 08:19:02 1999] Iteration 670 / 7817869 [Sat Sep 11 10:34:45 1999] Iteration: 6742784/7817869, ERROR: ROUND OFF (0.4086303711) 0.40 Possible hardware failure, consult the readme file. Continuing from last save file. [Sat Sep 11 11:04:20 1999] Disregard last error. Result is reproducible and thus not a hardware problem. Iteration: 6742912/7817869, ERROR: ROUND OFF (0.4086303711) 0.40 Possible hardware failure, consult the readme file. Continuing from last save file. [worktodo.ini is... Test=7817869,63 Test=7888367,63 Test=6539111,63 Test=6779911,63 Test=7468187,63 Test=8329537,64 local.ini is CPUType=10 CPUSpeed=504 SelfTest64Passed=0 SelfTest80Passed=0 SelfTest96Passed=0 SelfTest112Passed=0 SelfTest128Passed=0 SelfTest160Passed=0 SelfTest192Passed=0 SelfTest224Passed=0 SelfTest256Passed=0 ComputerID=p3-500 CPUHours=24 OldRollingAverage=1386 LastEndDatesSent=936928821 RollingStartTime=0 SelfTest384Passed=1 RollingAverage=997 BroadcastID=1 _ Unsubscribe list info -- http://www.scruz.net/~luke/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Re: Mersenne: error in V19??!?
Hi John, At 11:08 AM 9/11/99 -0700, John R Pierce wrote: Iteration: 6742784/7817869, ERROR: ROUND OFF (0.4086303711) 0.40 Possible hardware failure, consult the readme file. Continuing from last save file. [Sat Sep 11 11:04:20 1999] Disregard last error. Result is reproducible and thus not a hardware problem. Iteration: 6742912/7817869, ERROR: ROUND OFF (0.4086303711) 0.40 Possible hardware failure, consult the readme file. Continuing from last save file. This is not a bug. Brian was right that v19 would ordinarily use a 448K FFT wheras v18 used a 384K FFT. However, v19 is finishing off your exponent using a 384K FFT. You now see why I was a little more conservative with the FFT crossover points. Your 0.4086 error is not much greater than 0.4 and not near the 0.5 error that would corrupt your result. I'd continue onward with your test - you probably would have gotten the same error in version 18. Regards, George _ Unsubscribe list info -- http://www.scruz.net/~luke/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Re: Mersenne: error in V19??!?
This is not a bug. Brian was right that v19 would ordinarily use a 448K FFT wheras v18 used a 384K FFT. However, v19 is finishing off your exponent using a 384K FFT. You now see why I was a little more conservative with the FFT crossover points. Your 0.4086 error is not much greater than 0.4 and not near the 0.5 error that would corrupt your result. I'd continue onward with your test - you probably would have gotten the same error in version 18. ah. yer right. I looked back in my results.txt and found... [Sun Sep 05 02:42:01 1999] Iteration: 4647424/7817869, ERROR: ROUND OFF (0.4007873535) 0.40 Possible hardware failure, consult the readme file. Continuing from last save file. [Sun Sep 05 03:01:47 1999] Disregard last error. Result is reproducible and thus not a hardware problem. this was with v18... Must just be something funky about this particular candidate, not one other one I've run on this system has triggered this same error (I've been running prime95 24/7 since June on this box) [Sat Jun 26 05:38:31 1999] UID: jp/p3-500, M7636493 is not prime. Res64: B1B90297D4483A26. WU1: AD93C932,1209352, [Wed Jul 14 04:06:17 1999] UID: jp/p3-500, M7636561 is not prime. Res64: 07124E50AF70224A. WU1: 9ADED520,5521093, [Sat Jul 31 02:52:42 1999] UID: jp/p3-500, M7636597 is not prime. Res64: D1ED8948161F652F. WU1: C42D91B1,7404799, [Fri Aug 20 20:36:32 1999] UID: jp/p3-500, M7539533 is not prime. Res64: 3CE1193877330039. WU1: A4347C02,0,8000 [Tue Aug 24 08:06:32 1999] UID: jp/p3-500, M7666597 is not prime. Res64: DB189558BA6AD87F. WU1: 0FA06293,6759810, _ Unsubscribe list info -- http://www.scruz.net/~luke/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
RE: Mersenne: error 12029
Same here, I think the messages are not getting through. This is intermittant so I think that any of the usual suspects could apply (server down, server too busy, weather too nice) The entropia.com site seemed to be down some earlier today. Back up now, for the time anyway. I think that's what done caused it :-) Right now I am trying to figure out why one computer (just a P5MMX-166) locks up every 5 minutes in one room and works fine (10.5 hours since last boot running mprime95) on my test bench. Not getting the primenet connection to work reliably is really confusing. (Is it real or is it memo-wrecked?) Believe it or not, I've had countless problems with that and, remarkably, it ended up being the flourescent light fixtures near the desk. It had me going there, wondering why it works okay in the lab, but when it's on that guy's desk, no go. I've even seen problems with some other guy's computer in the next cube was leaking so much RF that it must have been interfering or something. All I knew in that case was that moving the turning off the "suspicious" computer made the other one more reliable. Weird. What's that Oriental art of placing things in a room or house to achieve harmony? Feng Shui or something like that? :-) Aaron _ Unsubscribe list info -- http://www.scruz.net/~luke/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
Re: Mersenne: Error: Illegal Sumout
[...] "ERROR: ILLEGAL SUMOUT" [...] Any suggestions? It happened to me. Turned out to be bad tag RAM. Luke, could you explain what "tag RAM" is please? Help in identifying same would be nice too, if possible. its the part of the cache that holds the address bits. On pentium pro and pentium-II systems, its in the CPU module. On *some* plain pentium chipsets, its 1 or two discrete static ram (SRAM) chips, but on other P5 chipsets, its integrated into the memory controller chip. -jrp
Re: Mersenne: Error: Illegal Sumout
On Wed, 28 Oct 1998 16:59:47 -0500, George Woltman wrote: I think my Prime95 broke! I am on iteneration 479162/5518463 and get a continuous stream of "ERROR: ILLEGAL SUMOUT" messages which are constantly This is probably an interaction with some new piece of software. I know that the OS should protect you from such interactions, but this problem is quite common. The good news is that these errors do not seem to affect prime95's accuracy (unlike other error messages). A recent double-check had 3 SUMOUT errors, but the residues matched anyway. Speaking of error messages.. I have a PII-266 working on a 6 million number at the moment which is (almost) constantly spitting out ERROR: SUM(INPUTS) != SUM(OUTPUTS) errors and the occasional ERROR: ROUND OFF thrown in for fun.. I've had problems with the computer before (the motherboard almost literally fried itself overheating and was replaced - note that it isn't overclocked in any way), and I'm getting the (new) board replaced by the local manufacturer on monday. The question is whether I should just throw out the computations that have already been done, or continue when the new board arrives? -- Sincerely, | Don't waste your computer's idle time! Philip Heede | = = = = = = = = = = = = = =| http://www.distributed.net/ WWW: http://pah.person.dk | http://www.mersenne.org/ Email: [EMAIL PROTECTED] | http://www.thoic.com/keyblitz/ Regional representative for www.Distributed.Net in Denmark PGP Public RSA Fingerprint: 5DB0 21A6 A606 D9BC BD71 59CA 82B4 0C6E PGP Public DSS Fingerprint: FDA0 A1FD D025 EF15 1041 894F 4109 0B57 CDAA ACC3 ... If there is no God, who pops up the next Kleenex in the box? ** Tag(s) inserted by Bandit Tagger98 - http://www.gbar.dtu.dk/~c918704
Mersenne: Error: Illegal Sumout
I think my Prime95 broke! I am on iteneration 479162/5518463 and get a continuous stream of "ERROR: ILLEGAL SUMOUT" messages which are constantly sent to the primenet server. I am running version 16.3.1 of Prime95. I have no choice but to shut it down until I figure out what went wrong. Any suggestions? Thanks, Chuck Baker [EMAIL PROTECTED]
Re: Mersenne: Error: Illegal Sumout
At 01:29 PM 10/28/98 -0700, Chuck Baker wrote: I think my Prime95 broke! I am on iteneration 479162/5518463 and get a continuous stream of "ERROR: ILLEGAL SUMOUT" messages which are constantly sent to the primenet server. I am running version 16.3.1 of Prime95. I have no choice but to shut it down until I figure out what went wrong. Any suggestions? This is probably an interaction with some new piece of software. I know that the OS should protect you from such interactions, but this problem is quite common. Have you installed any new device drivers lately - especially those that might use MMX (audio and midi cards)? Are you running any new programs? The good news is that these errors do not seem to affect prime95's accuracy (unlike other error messages). A recent double-check had 3 SUMOUT errors, but the residues matched anyway. Hope that helps, George
Re: Mersenne: Error: Illegal Sumout
At 01:29 PM 10/28/98 -0700, Chuck Baker wrote: [...] "ERROR: ILLEGAL SUMOUT" [...] Any suggestions? It happened to me. Turned out to be bad tag RAM. --Luke
Mersenne: Error rate
Hi all, The first results are in from version 17.0 535 results have been reported with 7 mismatched residues. Of those 7, 2 had errors reported during the version 17.0 run. Thus, very preliminary data indicates that if you get an error-free double-check run under version 17, then there is about 1 in 100 chance that you are doing a first-time check that could find a new Mersenne prime. Actually, the odds could be lower as I assumed the 5 mismatches were due to a bad initial run as opposed to a bad version 17 run. Unfortunately, my database is not well enough organized to know whether any errors were reported on the initial run of those 5 numbers. I'll post updated numbers at a later date. Best regards, George
