Error, what's this about?

[sno.lcn]

EUE, but rig is perfectly stable (in sig, but currently @ 2.8ghz just to make sure) but I've gotten this twice today:



--- Opening Log file [April 24 22:58:01]


# SMP Client ################################################## ################
################################################## #############################

Folding@Home Client Version 5.91beta

http://folding.stanford.edu

################################################## #############################
################################################## #############################

Launch directory: C:\Program Files\Folding@Home Windows SMP Client V1.01
Executable: C:\Program Files\Folding@Home Windows SMP Client V1.01\fah.exe


[22:58:01] - Ask before connecting: No
[22:58:01] - User name: T32monkeys (Team 32)
[22:58:01] - User ID: 3D6282F058A24C0C
[22:58:01] - Machine ID: 1
[22:58:01]
[22:58:01] Loaded queue successfully.
[22:58:01]
[22:58:01] + Processing work unit
[22:58:01] Core required: FahCore_a1.exe
[22:58:01] Core found.
[22:58:01] Working on Unit 09 [April 24 22:58:01]
[22:58:01] + Working ...
[22:58:02]
[22:58:02] *------------------------------*
[22:58:02] Folding@Home Gromacs SMP Core
[22:58:02] Version 1.74 (March 10, 2007)
[22:58:02]
[22:58:02] Preparing to commence simulation
[22:58:02] - Ensuring status. Please wait.
[22:58:19] - Looking at optimizations...
[22:58:19] - Working with standard loops on this execution.
[22:58:19] - Previous termination of core was improper.
[22:58:19] - Going to use standard loops.
[22:58:19] - Files status OK
[22:58:32] - Expanded 3973097 -> 21619596 (decompressed 544.1 percent)
[22:58:33]
[22:58:33] Project: 2610 (Run 0, Clone 121, Gen 16)
[22:58:33]
[22:58:34] Entering M.D.
[22:58:40] Calling FAH init
[22:58:41] Writing local files
[22:58:41] Completed 25000 out of 500000 steps (5 percent)
[22:58:41] tein
[22:58:41] Writing local files
[22:58:41] Completed 25000 out of 500000 steps (5 percent)
[22:58:42] Extra SSE boost OK.
[23:18:01] Writing local files
[23:18:01] Completed 30000 out of 500000 steps (6 percent)
[23:37:20] Writing local files
[23:37:20] Completed 35000 out of 500000 steps (7 percent)
[23:56:37] Writing local files
[23:56:37] Completed 40000 out of 500000 steps (8 percent)
[00:03:32] rk/wudata_09.sas
[00:03:32] - Failed to delete work/wudata_09.goe
[00:03:32] Warning: check for stray files
[00:03:32]
[00:03:32] Folding@home Core Shutdown: EARLY_UNIT_END
[00:03:32] Finalizing output

Folding@Home Client Shutdown at user request.

Folding@Home Client Shutdown.

Any ideas?

[silent bob]

that is what is called a Early Unit End, That means it stopped . It could not continue at this time . Be thankful it happened only at 8% not 98% .
still sucks tho , sorry I am in a smart a$s mood tonite

[ChasR]

p2610 is a very cache and bandwidth intense WU. It could have overtaxed the system or, it could be that you EUE'd the same WU twice. The Win SMP client tends to delete the WU on an EUE. The AS, thinking you lost the WU, sends you the same WU again. You'll get a bad WU three times in a row before the AS gives up on your rig.

[pscout]

if it eue's again at 8% you can be pretty sure it will repeat a third time and that it is a 'bad' wu.

You can just let it go to 8% a third time like ChasR said, or delete the wu if the second one happens at the same point and get a new wu.. Just make sure you don't have any queued wu's for upload before you delete the work dir and queue.dat. Check the fahlog again to make sure before deleting.

If it eue's at a diferent point, then your rig is not as stable as you thought :eek:

[Adak]

If your flags don't include -forceasm, I'd add it, and delete the stray file mentioned in the log, of course.


[00:03:32] - Failed to delete work/wudata_09.goe
[00:03:32] Warning: check for stray files


How's your temps on this beasty, while folding? If it repeats on other WU's, I'd look to your overclocking stability, and back it off a bit.

good luck!

Adak

[sno.lcn]

p2610 is a very cache and bandwidth intense WU. It could have overtaxed the system or, it could be that you EUE'd the same WU twice. The Win SMP client tends to delete the WU on an EUE. The AS, thinking you lost the WU, sends you the same WU again. You'll get a bad WU three times in a row before the AS gives up on your rig.
Thanks for the info Chas!

if it eue's again at 8% you can be pretty sure it will repeat a third time and that it is a 'bad' wu.

You can just let it go to 8% a third time like ChasR said, or delete the wu if the second one happens at the same point and get a new wu.. Just make sure you don't have any queued wu's for upload before you delete the work dir and queue.dat. Check the fahlog again to make sure before deleting.

If it eue's at a diferent point, then your rig is not as stable as you thought :eek:
Damn, it's at 8% right now :-/

If your flags don't include -forceasm, I'd add it, and delete the stray file mentioned in the log, of course.



How's your temps on this beasty, while folding? If it repeats on other WU's, I'd look to your overclocking stability, and back it off a bit.

good luck!

Adak
It's running 49C @ 2.8ghz, I lapped the cpu & the ultra-120 so hopefully I can keep it cool enough when I crank it back up :drool:

[sno.lcn]

...Still sitting at 8% :(


*Edit: Seems to be working again :)