EXTREME Overclocking Forums
Home | Reviews | Forums | Downloads | $ EXTREME Deals $ | RealTime Pricing | Free Magazines | Gear | Folding Stats Newsletter | Contact Us


Go Back   EXTREME Overclocking Forums > Website Related Info (No Post Increase) > Official EOC Folding @ Home Team
Register Forum Rules FAQ Search Today's Posts Mark Forums Read

Welcome Guest Visitor! Please Register, It's Free and Fun To Participate!
The EXTREME Overclocking Forums are a place for people to learn how to overclock and tweak their PC's components like the CPU, memory (RAM), or video card in order to gain the maximum performance out of their system. There are lots of discussions about new processors, graphics cards, cooling products, power supplies, cases, and so much more!

You are currently viewing our boards as a "guest" which gives you limited access to view most discussions. You need to register before you can post: click the register link to proceed. Before you register, please read the forum rules. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload your own pictures, and access many other special features. Registration is fast, simple, and absolutely free! To start viewing messages, select the forum that you want to visit from the selection below.

After you have registered and read the forum rules, you can check out the FAQ for more information on using the forum. We hope you enjoy your stay here!

Note To Spammers: We do not allow unsolicited advertising! Spam is usually reported & deleted within minutes of it being posted, so don't waste your time (or ours)!


Please Register to Post a Reply
 
Thread Tools
Old 09-10-2009, 09:35 AM   #1
hwttdz
Running System Stock
Forum Newbie
 
Posts: 8
Last Seen: 09-28-2009
Some problems with a new folding at home member

So I'm having some troubles getting started with folding at home. I am running the linux smp client,

fah6 -smp -verbosity 9

The jobs seem to be crashing out before completion. Here's some output of the logfiles and

Code:
==> logfile_01.txt <==

*------------------------------*
Folding@Home Gromacs SMP Core
Version 2.10 (Sun Aug 30 03:43:28 CEST 2009)

- Looking at optimizations...
Delete mode
Deleting frame files
Deleting work files
Error: Missing work file=<>

==> logfile_02.txt <==
Completed 140000 out of 250000 steps  (56%)
Completed 142500 out of 250000 steps  (57%)
Completed 145000 out of 250000 steps  (58%)
Completed 147500 out of 250000 steps  (59%)
Completed 150000 out of 250000 steps  (60%)
Completed 152500 out of 250000 steps  (61%)
Completed 155000 out of 250000 steps  (62%)
Completed 157500 out of 250000 steps  (63%)
Completed 160000 out of 250000 steps  (64%)
Completed 162500 out of 250000 steps  (65%)

==> logfile_03.txt <==

*------------------------------*
Folding@Home Gromacs SMP Core
Version 2.10 (Sun Aug 30 03:43:28 CEST 2009)

- Looking at optimizations...
Delete mode
Deleting frame files
Deleting work files
Error: Missing work file=<>

==> logfile_04.txt <==
- Working with standard loops on this execution.
- Files status OK
- Expanded 4833957 -> 24039989 (decompressed 497.3 percent)
Called DecompressByteArray: compressed_data_size=4833957 data_size=24039989, decompressed_data_size=24039989 diff=0
- Digital signature verified

Project: 2671 (Run 48, Clone 92, Gen 99)

Entering M.D.
Completed 0 out of 250000 steps  (0%)

==> logfile_05.txt <==
Completed 55000 out of 250000 steps  (22%)
Completed 57500 out of 250000 steps  (23%)
Completed 60000 out of 250000 steps  (24%)
Completed 62500 out of 250000 steps  (25%)
Completed 65000 out of 250000 steps  (26%)
Completed 67500 out of 250000 steps  (27%)
Completed 70000 out of 250000 steps  (28%)
Completed 72500 out of 250000 steps  (29%)
Completed 75000 out of 250000 steps  (30%)
Completed 77500 out of 250000 steps  (31%)
And some of the .log files end with a NAN error.
Code:
Fatal error:
NaN detected at step 24914818

For more information and tips for trouble shooting please check the GROMACS Wiki at
http://wiki.gromacs.org/index.php/Errors
-------------------------------------------------------

Thanx for Using GROMACS - Have a Nice Day
Any help debugging would be greatly appreciated.
United States  Offline
    Register to Reply to This Post
Old 09-10-2009, 10:51 AM   #2
PatonB
Folder
Senior Member
 
Posts: 1,220
Last Seen: 12-11-2013
iTrader: 0 / 0%
How are you stopping the clients?

And the whole logs are usually better instead of snippegs, even if it seems like alot of extra info.

Thanks
Canada  Offline
    Register to Reply to This Post
Old 09-10-2009, 11:40 AM   #3
HotRod
Folding Team Captain
HotRod's Avatar
Retired Staff
 
Posts: 2,000
Last Seen: 07-22-2010
Age: 52
From: VA
iTrader: 13 / 100%
This is could be a bad WU.


More info here.

http://foldingforum.org/viewtopic.php?f=19&t=11392

http://foldingforum.org/viewtopic.ph...=11098&start=0
United States  Offline
    Register to Reply to This Post
Old 09-10-2009, 12:45 PM   #4
jevans64
The Folding Pylon
jevans64's Avatar
Senior Member
 
Posts: 2,692
Last Seen: Yesterday
Age: 50
From: Madison, AL
iTrader: 16 / 100%
A high percentages of p2671 seem to be failing. A very good indication of a WU fail is that it will crash at 0% and give you a code FF ( highlighted in logfile. ) It should attempt to try it three times then re-download the core file and pick up a NEW work unit. If you are constantly failing at anything other than 0%, then you have other issues. If that is the case then begin by doing a memory test with Memtest86+ or something.

Normally, I would go here ( http://foldingforum.org/viewforum.ph...1133c69eac6b56 ) and report it but since the p2761's have a high failure, I don't bother. My particular WU failure was already reported when I looked it up.

Code:
[03:33:22] Folding@Home Gromacs SMP Core
[03:33:22] Version 2.10 (Sun Aug 30 03:43:28 CEST 2009)
[03:33:22] 
[03:33:22] Preparing to commence simulation
[03:33:22] - Ensuring status. Please wait.
[03:33:32] - Assembly optimizations manually forced on.
[03:33:32] - Not checking prior termination.
[03:33:33] - Expanded 1492108 -> 24057197 (decompressed 1612.2 percent)
[03:33:33] Called DecompressByteArray: compressed_data_size=1492108 data_size=24057197, decompressed_data_size=24057197 diff=0
[03:33:34] - Digital signature verified
[03:33:34] 
[03:33:34] Project: 2671 (Run 24, Clone 41, Gen 91)
[03:33:34] 
[03:33:34] Assembly optimizations on if available.
[03:33:34] Entering M.D.
[03:33:40] Multi-core optimizations on
[03:33:57] Completed 0 out of 250000 steps  (0%)
[03:34:02] CoreStatus = FF (255)
[03:34:02] Client-core communications error: ERROR 0xff
[03:34:02] Deleting current work unit & continuing...
[03:34:15] - Preparing to get new work unit...
[03:34:15] + Attempting to get work packet
[03:34:15] - Connecting to assignment server
[03:34:16] - Successful: assigned to (171.67.108.24).
[03:34:16] + News From Folding@Home: Welcome to Folding@Home
[03:34:16] Loaded queue successfully.
[03:34:26] + Closed connections
[03:34:32] 
[03:34:32] + Processing work unit
[03:34:32] Core required: FahCore_a2.exe
[03:34:32] Core found.
[03:34:32] Working on Unit 09 [September 8 03:34:32]
[03:34:32] + Working ...

Last edited by jevans64 : 09-10-2009 at 12:59 PM.
United States  Offline
    Register to Reply to This Post
Old 09-10-2009, 01:45 PM   #5
_MtM_
Extreme Overclocker
_MtM_'s Avatar
Senior Member
 
Posts: 907
Last Seen: 03-22-2012
iTrader: 0 / 0%
Yup I agree with both, though I usually would say failure's need to be reported always or checked against the reported wu's atleast.

Even a high failure percentage does not always mean they will repeat an entire range, they will alway's try to minimize the overhead and if they can pick off the bad wu's one at a time on an econimical basis they will.

2671, and failure to start, is caused by bad previous gen's afaik which is what the 2.10 is preventing from repeating itself over and over again.

Edit: I'll make sure to include a section on how to best report a problem on the forum in the addition/changes suggestions I'm preparing for DSwarp. I agree with PatonB, complete log files, and more things, should be given, not partial logs even if this time the issue was 'solved' without them.
Netherlands  Offline
    Register to Reply to This Post
Old 09-23-2009, 02:02 PM   #6
hwttdz
Running System Stock
Forum Newbie
 
Posts: 8
Last Seen: 09-28-2009
Wow thanks for all the help. I must have missed the reply notification.

I think that this issue was primarily caused by an unstable processor. Unfortunately I do not know a good method of stress testing the processor for errors, anyways backing it off a slight bit seems to have made a difference.
United States  Offline
    Register to Reply to This Post
Old 09-23-2009, 02:16 PM   #7
_MtM_
Extreme Overclocker
_MtM_'s Avatar
Senior Member
 
Posts: 907
Last Seen: 03-22-2012
iTrader: 0 / 0%
Use stresscpu2 as it's made by the same people who made gromacs, which is the package allot of the folding@home cores are based on.

Link coming up in a sec

Edit: http://foldingforum.org/viewtopic.php?f=14&t=52 scroll down to 'Testing system stability'

Edit2: wow I just seen how badly I'm running behind with doing things I promised... no excuses ( been bussy for sure, just on other things ), need to do what I said and I will!

Last edited by _MtM_ : 09-23-2009 at 02:25 PM.
Netherlands  Offline
    Register to Reply to This Post
Sponsored Links:
Please Register to Post a Reply


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

All times are GMT -6. The time now is 02:23 AM.

Copyright 2000 - 2011, Jelsoft Enterprises Ltd.
Powered by vBulletin
Copyright 2000 - 2011, EXTREME Overclocking