x38g reports

[Ghost0210]

It's this part of the error that's important:

<core_client_version>6.10.58</core_client_version>
<![CDATA[
<message>
Maximum elapsed time exceeded
</message>
<stderr_txt>

Seems that Boinc thinks that these tasks should be running a lot quicker than they are and times them out with the above error.
Have you tried Fred's Reschedular to adjust the RSC_FPOPS_BOUND on your tasks as this should solve the problem for you

Here's a link to the Fred's site

[Terror Australis]

Duuh - of course THAT's what a 177 error is 
Should have woken up but i'd been chasing hardware problems in another box all day and wasn't thinking. It's awhile since I had one
Thanks Ghost

T.A.

[perryjay]

I made two x38gs fight it out over this one..  http://setiathome.berkeley.edu/workunit.php?wuid=774709022  I ran mine on my CPU.   


Another x39e and I didn't quite match on this one. Went out to a third running it as v5.28.  http://setiathome.berkeley.edu/workunit.php?wuid=772279650

[Jason G]

Here are a couple of errors I came upon X38g on my 8600 GTS (256Mb of memory, driver 266.58):
...
full details http://setiathome.berkeley.edu/result.php?resultid=1961527829

looks like  regular, rarer now, -12.  Future work will get rid of those entirely, and they (two kind of -12) originate as hard coded limitations in the original nVidia supplied stock code.

http://setiathome.berkeley.edu/result.php?resultid=1961505285

Looks like a genuine failure of some sort, though x38g doesn't have as helpful output when those occur.  x39e is somewhere in this thread... I'll look for that, or make a newer variant available as appropriate as soon as a few more things are understood about the newer build behaviour.

Jason

[Edit:] here' the link to the post containing the 7zipped main exe (only), meant to be added to an existing x38g installation, with suitable app_info edits (or aistub/aimerge).
http://lunatics.kwsn.net/12-gpu-crunching/x38g-reports.msg39472.html#msg39472

[perryjay]

Just wanted to let everyone see what is happening with one of my errors... http://setiathome.berkeley.edu/workunit.php?wuid=770546468   5 -12s 1 -9 overflow.

Will it ever end?   


Oh, my other error shows 2 -9s and 2 -12s.

[Jason G]

Will it ever end?   

Yes it will... The -12's will end altogether, as soon as the V7 autocorrelation code is stable, then I get time to look at & rewrite  the triplet kernels (probably using a combination of Raistmer's opencl approach & my max bandwidth kernels)

Legacy builds disappear with the transition to V7, and newer builds are hoped to converge CPU & GPU results cross platform... So that puts an end to another bunch of weak similarity issues.

Long road... But I think when Joe's work, the project's polishing & all the builds are V7 compatible, then we could be looking for new sets of problems to solve... Or better yet, optimising again instead of troubleshooting & bugfixing.

Just better ask these hardware manufacturer's to stop devising new stuff so we can catch up for a while 

[perryjay]

Oh, it seems like since I cut back on my over clock I have been getting fewer inconclusives. We may have been chasing a problem on my side.  Most all of my incons right now are caused by a wingman's 450 throwing out -9s. I PMd him but I don't know if it will do any good.

[Jason G]

... Most all of my incons right now are caused by a wingman's 450 throwing out -9s. I PMd him but I don't know if it will do any good.

What's he running ?

[perryjay]

Appears to be stock. He also has a 430 in that rig that is turning in good results.  http://setiathome.berkeley.edu/result.php?resultid=1986202415

I have been teamed up with him on quite a few work units.

[Claggy]

I've just come across this invalid result from one of my wingmen:

http://setiathome.berkeley.edu/result.php?resultid=1973794071

Claggy

[Jason G]

I've just come across this invalid result from one of my wingmen:

http://setiathome.berkeley.edu/result.php?resultid=1973794071

Claggy

  Well at least newer builds don't end up in that unhelpful cascade when things go awry.  It looks like his original failure was arbitrarily in the preceding power-spectrum, which was already fairly hardened by x38g.  Looking at his error list he may have a few other issues going on, with -177s,  Cufft failures & possibly driver crashes. 

[perryjay]

Here's a nice one  http://setiathome.berkeley.edu/workunit.php?wuid=777762756  the invalid one is running a GTX 570 with the old v12 mod. Will we lose these guys when we go to the new V7?

[Jason G]

Will we lose these guys when we go to the new V7?

Yep.

[perryjay]

Great, then maybe we can tewll them to upgrade when the finally visit the forums to ask why they aren't getting any work!   Oh and the work units from my buddy with the bad 450 has started validating for me and kicking him out as invalid. Judging from the dozen or so times I was paired with him he must be kicking out hundreds if not thousands of those -9s. No reply from him from my PM. (Imagine that!     )

[perryjay]

Woke up this morning to two -1 errors.  http://setiathome.berkeley.edu/workunit.php?wuid=780336597  http://setiathome.berkeley.edu/workunit.php?wuid=779923870 .  Don't know what happened but looks like my computer rebooted overnight. EVGA precision has a habit of starting after BOINC Manager has started so it doesn't catch the over clock. I have to restart BM and client to get it right again.

Well, something is happening. I just downclocked again. I'm going to set things back to .5/.5 and try again.


FYI,  I picked up and ran an AP on my GPU last night. That could have been the problem. Everything is back up to speed after rebooting but my MB tasks on GPU are running high priority. That should settle down after a couple run here soon. I also have a few APs waiting so we shall see what happens.