x38g reports

[Jason G]

I've only got two errors, both -12s. This one is interesting though  http://setiathome.berkeley.edu/workunit.php?wuid=770546468  Take a look at the one that did complete it. 23 triplets found??

Sure!   if ||| is one triplet, |||| is 2 triplets, and ||||| is 5 triplets.  Add a few more |'s in the same 'PulsePoT' and you get to 23 pretty quickly, which is bigger than where the nVidia code commits suicide.

I've yet to hear a good explanation of why ET might not think that's a good way to catch our attention, so do want to rewrite that to eliminate the -12s.  It's only relatively recently  that I feel my Cuda experience is getting to the point where I can consider that particular rewrite (among others), so reengineering it to match CPU is on the list, though much lower down than some other issues.

Jason

[Raistmer]

Approach used in OpenCL->CUDA build shold never experience this problem. Maybe it's worth to incorporate it in "pure CUDA" build too.

[Slavac]

We've got Jason sorted for a new PSU.

[perryjay]

Great news Slavic. 

Get shopping Jason!!   

[Jason G]

Approach used in OpenCL->CUDA build shold never experience this problem. Maybe it's worth to incorporate it in "pure CUDA" build too.

Yeah, when I rewrite that I'll take yours into consideration & apply the 'max bandwidth' approach that's been working well for me so far as well.  As mentioned I do want that issue gone, and as errors go it's becoming more common as hardware gets faster & the work noiser.

 

We've got Jason sorted for a new PSU.

Wow looks like I end up with enough to get the 'big one'.     I'll let everyone know the good news on main & issue thanks as well. 

[Josef W. Segur]

Not unexpected, http://setiathome.berkeley.edu/workunit.php?wuid=766762437 which we looked at pretty closely ended with all 5 getting credit. The stock CUDA 6.08 got canonical so was strongly similar to CRUNCH3R's 6.01 CUDA for 64 bit Linux.
                                                            Joe

[Jason G]

Thanks for keeping track of that one.   Yep looks like we need to at least take a look at the gaussians then.  I'm not happy with the outwardly clean looking 6.03 run being marginalised.  While we can discount the legacy Cuda builds' accuracy for a mixed bag of reasons (& the spikes in 6.03 for that matter), and the x38g one for stability & the unexplored gaussfit code, it's going to be the marginal cases that'll show us where to look.   They are going to get stranger I suppose.

Jason

[Slavac]

X39e's up and running on two 560ti's.  We'll see how she does.

[_heinz]

Hi Jason,
I get one -9 resultoverflow resultid=1981104197
SETI@Home Informational message -9 result_overflow
NOTE: The number of results detected exceeds the storage space allocated.

I thought this is solved ?

[Claggy]

Hi Jason,
I get one -9 resultoverflow resultid=1981104197
SETI@Home Informational message -9 result_overflow
NOTE: The number of results detected exceeds the storage space allocated.

I thought this is solved ?

That's quite Normal, as long as your wingman finds too many signals too,

You were probably thinking of error that happens when there are too many triplets,

Claggy

[Slavac]

x38 was giving me quite a few invalids, thus killing my RAC.  x39 seems to have killed the invalids issues though I'm getting a few errors.  After a few days of run time I'll post what errors I'm getting.

The x39 build also seems to have reduced the frequency of the downclocks I was experiencing.

Jason should I be running a particular driver with the 560's? 

[perryjay]

According to Martin of Martin's lighthouse...

266.66 is the first release with 560 Ti support.

 

If that's any help.   

[Mike]

The 275.xx drivers should be a little fast at least.

[perryjay]

Got another invalid  http://setiathome.berkeley.edu/workunit.php?wuid=765094268  I found 11 spikes the other two only found three.

Oh, FYI, I've had a couple of driver restarts so I've cut back just a bit on my over clock. I'm now at 883/1766/1804. I'm also only running two at a time because of running Raistmer's app for the NV AP.

[Jason G]

Got another invalid  http://setiathome.berkeley.edu/workunit.php?wuid=765094268  I found 11 spikes the other two only found three.

Nothing weird there, just 2 CPU apps with missed spikes due to inaccuracy ganging up on you.  Looks like x39e is going well so far on that one.