Forum > GPU crunching
x38g reports
perryjay:
Starting the thread on NC should be of help. I've noticed a number of my wingmen with the 560Ti throwing out -9s and other bad results giving them an invalid or error. It would be good to see if it is something in the card itself causing it.
perryjay:
Here's a strange one http://setiathome.berkeley.edu/workunit.php?wuid=771323155 Check out computer 5257703. He's showing he has two GTS460s but all his GPU work is coming up no GPUs found.
Okay, looked a little closer, he's running driver version 258.96 with the x32f app. I tried to PM him but we will see if he responds.
Jason G:
--- Quote from: perryjay on 15 Jul 2011, 11:05:46 am ---Here's a strange one http://setiathome.berkeley.edu/workunit.php?wuid=771323155 Check out computer 5257703. He's showing he has two GTS460s but all his GPU work is coming up no GPUs found.
--- End quote ---
He probably installed Boinc as a service (protected application)
perryjay:
That's possible too. I didn't think of that.
I hope it's just the driver. He's running an I7 and cranking out a lot of good work on it. With those two 460s running he'll take off like a house afire. ;D
another interesting one http://setiathome.berkeley.edu/workunit.php?wuid=763277874 they tried three times to prove me wrong when I didn't match that first -9 and still refused to give me canonical. ;D
Another one inconclusive http://setiathome.berkeley.edu/workunit.php?wuid=782642742 He's running a 470 with v38g. He found 20 spikes I found 12. Looking at his work I'd say I'll win.
Jason G:
--- Quote from: perryjay on 15 Jul 2011, 11:13:43 am ---another interesting one http://setiathome.berkeley.edu/workunit.php?wuid=763277874 they tried three times to prove me wrong when I didn't match that first -9 and still refused to give me canonical. ;D
--- End quote ---
Nice, the Cuda23 ones really dropped the ball with that task, the one that processed successfully missed a reportable gaussian the CPU apps & yourself picked up. That pretty much correlates with the chirp + gaussian weirdnesses we've been seeing, and need to investigate & understand more deeply. It is logical that the canonical was chosen as the AKv8 one, as it's likely 'in between' the 6.03 & yours, so representative. I also take it as a sign that x38g was moving in the right direction to make better matches to CPU apps on some types of results, but there is still work to do.
--- Quote ---Another one inconclusive http://setiathome.berkeley.edu/workunit.php?wuid=782642742 He's running a 470 with v38g. He found 20 spikes I found 12. Looking at his work I'd say I'll win.
--- End quote ---
He could have power or cooling issues or anything, hard to say. Once some of the more urgent issues are solved, I'll start playing with nVidia APi to see if I can extract thermal / power / clock info . Decent info along those lines could paint a clearer picture in some cases, if some info could be printed to stderr.
Jason
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version