[batharoy]

Should I be worried about this?

This system has not been used at all today except folding.
The only other time I've seen this was after playing games.


Arguments: -advmethods -forcesse -verbosity 9

Warning:
By using the -forceSSE flag, you are overriding program
safeguards that monitor the stability of SSE
instructions on your system. If you did not intend
to do this, please restart the program without
-forceSSE. If work units are not completing fully,
then please discontinue use of the flag.

[20:08:39] - Ask before connecting: No
[20:08:39] - Use IE connection settings: Yes
[20:08:39] - User name: batharoy (Team 32)
[20:08:39] - User ID = 879FFEC15687258
[20:08:39] - Machine ID: 1
[20:08:39]
[20:08:40] Loaded queue successfully.
[20:08:40] Initialization complete
[20:08:40] + Benchmarking ...
[20:08:42] The benchmark result is 6448
[20:08:42]
[20:08:42] + Processing work unit
[20:08:42] Core required: FahCore_78.exe
[20:08:42] Core found.
[20:08:42] Working on Unit 08 [April 16 20:08:42]
[20:08:42] + Working ...
[20:08:42] - Calling 'FahCore_78.exe -dir work/ -suffix 08 -checkpoint 15 -forceSSE -verbose -lifeline 4294581341 -version 400'

[20:08:43] - Autosending finished units...
[20:08:43] Trying to send all finished work units
[20:08:43] + No unsent completed units remaining.
[20:08:43] - Autosend completed
[20:08:43] + Working...
[20:08:43]
[20:08:43] *------------------------------*
[20:08:43] Folding@home Gromacs Core
[20:08:43] Version 1.56 (February 2, 2004)
[20:08:43]
[20:08:43] Preparing to commence simulation
[20:08:43] - Ensuring status. Please wait.
[20:09:00] - Assembly optimizations manually forced on.
[20:09:00] - Not checking prior termination.
[20:09:00] - Expanded 671155 -> 3576045 (decompressed 532.8 percent)
[20:09:00] - Checksums don't match (work/wudata_08.xtc) .<---------------------WHATS THIS MEAN?
[20:09:00] - Starting from initial work packet
[20:09:00]
[20:09:00] Project: 212 (Run 44, Clone 97, Gen 2)
[20:09:00]
[20:09:00] Assembly optimizations on if available.
[20:09:00] Entering M.D.
[20:09:07] Protein: p212_villinURE212
[20:09:07]
[20:09:07] Writing local files
[20:09:12] Extra SSE boost OK.
[20:09:12] Writing local files
[20:09:14] Completed 0 out of 500000 steps (0)
[20:24:17] Timered checkpoint triggered.
[20:27:43] Writing local files
[20:27:44] Completed 5000 out of 500000 steps (1)
[20:42:47] Timered checkpoint triggered.
[20:46:09] Writing local files
[20:46:11] Completed 10000 out of 500000 steps (2)
[21:01:12] Timered checkpoint triggered.
[21:04:30] Writing local files
[21:04:32] Completed 15000 out of 500000 steps (3)
[21:19:33] Timered checkpoint triggered.
[21:22:52] Writing local files
[21:22:54] Completed 20000 out of 500000 steps (4)
[21:37:57] Timered checkpoint triggered.
[21:41:16] Writing local files
[21:41:18] Completed 25000 out of 500000 steps (5)
[21:56:21] Timered checkpoint triggered.
[21:59:39] Writing local files
[21:59:41] Completed 30000 out of 500000 steps (6)
[22:14:43] Timered checkpoint triggered.
[22:18:03] Writing local files
[22:18:05] Completed 35000 out of 500000 steps (7)
[22:33:07] Timered checkpoint triggered.
[22:36:26] Writing local files
[22:36:28] Completed 40000 out of 500000 steps (8)
[22:51:30] Timered checkpoint triggered.
[22:54:51] Writing local files
[22:54:53] Completed 45000 out of 500000 steps (9)
[23:09:55] Timered checkpoint triggered.
[23:13:14] Writing local files
[23:13:16] Completed 50000 out of 500000 steps (10)
[23:28:19] Timered checkpoint triggered




WOW I have 2 stars now

[OCn00b]

You don't need to worry about that. It just means that the frames are taking long enough to be saved by f@h. That just means that in theory, if the power went out or something like that, your unit would pick up where the last save point is instead of starting back at 0 frames.

I'm not sure what the checksums not matching is. Could be a corrupt f@h folder, but maybe not. Somebody more knowledgable than myself should be along shortly to clear that up for you

[batharoy]

What about the checksums dont match line?

[JetMech]

Checksums don't match is the warning that during prior shutdown the work was somehow currupted and the WU restarts from the beginning. This is normally seen during abrupt unnormal shutdowns such as power failure or after a lockup reboot. I have never personally seen the timered statement being displayed after each completed frame. Hopefully it indicates that each completed frame is being saved to the hard drive so checkpoints are being established and an improper shutdown won't make you have to start over. Crash it and restart and let us know what happened (j/k).

You are using the -forcesse argument which indicates to me that you are using an AMD processor. I bring this up because usually during a checksum not match restart, Extra Sse Boost will not be turned on and you have to restart to get it turned on. This did not happen in your case. I would be very interested to know how that WU completes. Please keep us posted.

[batharoy]

After a reboot (not a crash tho ) It didn't give me the checksum "error" this time. Its at frame 71 now at about 15 min a frame and still "triggered" after every frame. I'll check again after work to make sure every thing finished ok and post results here.

Thanks for your input folks.

[nikhsub1]

You have the -verbosity 9 flag running, which yeilds the MOST info in the logs, most likely JetMech does not have this flag and that is why he does not see the timered checkpoint. The timered checkpoint is like a save... every so often (it can be set from 1 min to 30 mins, i think default is 15mins) it does this, again you only see it because you have the -verbosity 9 flag on, without that flag you would not see the checkpoints. The checksums don't match could be a variety of things... just keep and eye on it. How is your OC?

[batharoy]

Just got home and every thing looks fine.
My OC should not be a problem
Barton 2500 @ 1985 11x180FSB on MSI KT4AV-L 46c under load.
Its just weird cause the next unit I recieved has been running for over 45 min. and hasn't received the "timered checkpoint" even once yet.

[05:30:13] Completed 500000 out of 500000 steps (100)
[05:30:15] Writing final coordinates.
[05:30:15] Past main M.D. loop
[05:31:15]
[05:31:15] Finished Work Unit:
[05:31:15] - Reading up to 494640 from "work/wudata_08.arc": Read 494640
[05:31:15] - Reading up to 602252 from "work/wudata_08.xtc": Read 602252
[05:31:15] goefile size: 0
[05:31:15] logfile size: 33903
[05:31:15] Leaving Run
[05:31:17] - Writing 1139199 bytes of core data to disk...
[05:31:17] ... Done.
[05:31:17] - Shutting down core
[05:31:17]
[05:31:17] Folding@home Core Shutdown: FINISHED_UNIT
[05:31:21] CoreStatus = 64 (100)
[05:31:21] Unit 8 finished with 94 percent of time to deadline remaining.
[05:31:21] Updated performance fraction: 0.977956
[05:31:21] Sending work to server


[05:31:21] + Attempting to send results
[05:31:21] - Reading file work/wuresults_08.dat from core
[05:31:21] (Read 1139199 bytes from disk)
[05:32:03] - Uploaded at ~26 kB/s
[05:32:03] - Averaged speed for that direction ~26 kB/s
[05:32:03] + Results successfully sent
[05:32:03] Thank you for your contribution to Folding@home.
[05:32:03] + Number of Units Completed: 33

[05:32:07] Trying to send all finished work units
[05:32:07] + No unsent completed units remaining.
[05:32:07] - Preparing to get new work unit...
[05:32:07] + Attempting to get work packet
[05:32:07] - Connecting to assignment server
[05:32:07] - Successful: assigned to (171.64.122.123).
[05:32:07] + News From Folding@Home: Welcome to Folding@Home
[05:32:08] Loaded queue successfully.
[05:32:11] - Receiving payload (expected size: 352914)
[05:32:24] - Downloaded at ~26 kB/s
[05:32:24] - Averaged speed for that direction ~25 kB/s
[05:32:24] + Received work.
[05:32:24] Trying to send all finished work units
[05:32:24] + No unsent completed units remaining.
[05:32:24] + Closed connections
[05:32:24]
[05:32:24] + Processing work unit
[05:32:24] Core required: FahCore_78.exe
[05:32:24] Core found.
[05:32:24] Working on Unit 09 [April 18 05:32:24]
[05:32:24] + Working ...
[05:32:24] - Calling 'FahCore_78.exe -dir work/ -suffix 09 -checkpoint 15 -forceSSE -verbose -lifeline 4294754673 -version 400'

[05:32:24]
[05:32:24] *------------------------------*
[05:32:24] Folding@home Gromacs Core
[05:32:24] Version 1.56 (February 2, 2004)
[05:32:24]
[05:32:24] Preparing to commence simulation
[05:32:24] - Assembly optimizations manually forced on.
[05:32:24] - Not checking prior termination.
[05:32:24] - Go method
[05:32:25] - Expanded 352402 -> 1760813 (decompressed 499.6 percent)
[05:32:25] - Starting from initial work packet
[05:32:25]
[05:32:25] Project: 563 (Run 44, Clone 6, Gen 138)
[05:32:25]
[05:32:25] Assembly optimizations on if available.
[05:32:25] Entering M.D.
[05:32:31] Protein: p563_BBA5_ext
[05:32:31]
[05:32:31] Writing local files
[05:32:31] Extra SSE boost OK.
[05:32:33] Writing local files
[05:32:35] Completed 0 out of 250000 steps (0)
[05:35:49] Writing local files
[05:35:51] Completed 2500 out of 250000 steps (1)
[05:39:06] Writing local files
[05:39:08] Completed 5000 out of 250000 steps (2)
[05:42:22] Writing local files
[05:42:24] Completed 7500 out of 250000 steps (3)
[05:45:39] Writing local files
[05:45:41] Completed 10000 out of 250000 steps (4)
[05:48:55] Writing local files
[05:48:57] Completed 12500 out of 250000 steps (5)
[05:52:11] Writing local files
[05:52:13] Completed 15000 out of 250000 steps (6)
[05:55:27] Writing local files
[05:55:29] Completed 17500 out of 250000 steps (7)
[05:58:44] Writing local files
[05:58:46] Completed 20000 out of 250000 steps (8)
[06:02:00] Writing local files
[06:02:02] Completed 22500 out of 250000 steps (9)
[06:05:16] Writing local files
[06:05:18] Completed 25000 out of 250000 steps (10)
[06:08:33] Writing local files
[06:08:35] Completed 27500 out of 250000 steps (11)
[06:11:50] Writing local files
[06:11:52] Completed 30000 out of 250000 steps (12)
[06:15:07] Writing local files
[06:15:08] Completed 32500 out of 250000 steps (13)
[06:18:24] Writing local files
[06:18:26] Completed 35000 out of 250000 steps (14)

[SavageBasher]

The checkpoint will only go if the current frame goes over that time (15 minutes).

[batharoy]

Understood.
Thanks for the help guys.

[JetMech]

Originally posted by nikhsub1
You have the -verbosity 9 flag running, which yeilds the MOST info in the logs, most likely JetMech does not have this flag and that is why he does not see the timered checkpoint. The timered checkpoint is like a save... every so often (it can be set from 1 min to 30 mins, i think default is 15mins) it does this, again you only see it because you have the -verbosity 9 flag on, without that flag you would not see the checkpoints. The checksums don't match could be a variety of things... just keep and eye on it. How is your OC?

You're right Nik. I've never used the verbosity flag 9 (getting kind of lazy about keeping up with all these improvements to the process). What I do know is that I have never successfully recovered a from crash with F@H4. Sounds like I need to check my setup.