Hello:
I want to hear from some others -- are you having trouble with the new Gromacs core? My two fast machines have has several errors -- checksum and I/O errors, and they are overclocked. I suspect it is a RAM error, rather than a CPU or CPU overheating that is causing it, so I'll try a slightly slower FSB/RAM speed and see how things go with that. Otherwise, I'll have to get better RAM...
The Win2K client has had two (and one was with over 300 of 400 steps done! ) and they just aborted. The Linux client has had about 4 in a row, and in some cases, it tries restarting the unit back at a known point. The Linux units have all been the same: p539_BBA5_N in water, and I forget which WU it was in the Windows client.
But in the end, I have wasted a lot of time with these. The Windows client has an error message that I don't see in the Linux, that says in a nutshell, if you see more than a few of these, that there may be something going wrong with your computer, like overheating (I doubt this is a issue), overclocking, or other problems. I will try dropping my RAM/FSB speed back a bit -- maybe my RAM is kicking out errors that the Gromacs core is more "sensitive" to?
Troubles with the new Gromacs core?
Moderators: NeilBlanchard, Ralf Hutter, sthayashi, Lawrence Lee
-
- Moderator
- Posts: 7681
- Joined: Mon Dec 09, 2002 7:11 pm
- Location: Maynard, MA, Eaarth
- Contact:
Troubles with the new Gromacs core?
Last edited by NeilBlanchard on Tue Jun 03, 2003 7:44 am, edited 1 time in total.
I've had 2 in a row last week, on the same pc. Halfway it would just stop, 100% cpu time but no frames coming out any more. After I restart it I get a missing_work_files error and it starts downloading a new WU.
That pc is a tualatin-celeron running on 133 fsb, memory is 133 mhz sdram. It's been folding for like 2 months now without problems.
That pc is a tualatin-celeron running on 133 fsb, memory is 133 mhz sdram. It's been folding for like 2 months now without problems.
-
- Moderator
- Posts: 7681
- Joined: Mon Dec 09, 2002 7:11 pm
- Location: Maynard, MA, Eaarth
- Contact:
Well, so far...
Hello:
I've dropped the frequency slightly from 154mHz X 13 = 2002mHz to 152mHz X 13 = 1976mHz and so far, so good. It either was the RAM (I'm still minimizing the latencies @ 2-3-3) or the CPU but not from overheating. I've never seen anything above 51C; typically it 47-48C, and so my best guess is that the APacer PC2100 CAS2 is hicupping at a 15% oc with the tightest timings possible. I'm going to be replacing the SVC GC-68's with Alpha PAL8045's and I may be "forced" to buy some good PC2700 CAS 2 and see if I can't hit 166mHz X 13 = 2158mHz and still keep the temps in the low to mid 40's...
I've dropped the frequency slightly from 154mHz X 13 = 2002mHz to 152mHz X 13 = 1976mHz and so far, so good. It either was the RAM (I'm still minimizing the latencies @ 2-3-3) or the CPU but not from overheating. I've never seen anything above 51C; typically it 47-48C, and so my best guess is that the APacer PC2100 CAS2 is hicupping at a 15% oc with the tightest timings possible. I'm going to be replacing the SVC GC-68's with Alpha PAL8045's and I may be "forced" to buy some good PC2700 CAS 2 and see if I can't hit 166mHz X 13 = 2158mHz and still keep the temps in the low to mid 40's...