Forum > GPU crunching
x38g reports
Jason G:
--- Quote from: perryjay on 30 Jun 2011, 02:30:05 pm ---Got the same count as this 460 running x38g but still went to inconclusive.. http://setiathome.berkeley.edu/workunit.php?wuid=771572553
--- End quote ---
Yeah now that initially looks to me like x38g failing invisibly with something. As we've seen they are numerically the same under bench conditions even with marginal results like the previous chirp/gaussfit weirdo, but no evidence appears that something went wrong.
I think x38g pushes the pulsefinding a touch too hard for some cards like the 460 & yours, causing some undocumented driver/kernel launch failures later in the process. x39e has that wound back a notch, and extra hardened launches with print & hard error outs before & after every Cuda call. That should make any repeat of what happens in x38g more obvious & descriptive. IOW: discount the x38g result as possibly bad on that wingman, and we'll have to thrash out x39e for problems so a more general update can be provided.
An interesting thing, if possible red herring, is that a 480 (running stock 6.10 cuda_fermi) failed with a Cuda incorrect function on that task (again without a lot of explanation). I know from my own & Steve's 480's that errors on these cards are exceedingly rare with all current builds .... So it's possible there is something funky going on with certain tasks as well.
Jason
perryjay:
Duh, right, me good x38g bad, got it! ;)
_heinz:
--- Quote from: _heinz on 29 Jun 2011, 03:27:58 am ---Hi Jason,
took x39e now for seti main on my GT540M (1GB), but get no work till now.
As soon as I have work, i will post again.
heinz
--- End quote ---
I got 5 tasks.
2 are conclusive,
one against SETI@home Enhanced v6.10 (cuda_fermi)
the other against SETI@home Enhanced v6.03
for 3 I have to wait.
hostid=6023152
Only issue every time when a seti wu will start the machines clock down again on my GT540M.
I run it together with primegrid.
To get my oc'ed values(750/900/1500) back I must restart the machine. EVGA Precision was not able to set the frequency new, if it is fallen down.
Still restart helps.
Standard clock is (672/900/1344)
30.06.2011 20:24:17 | | NVIDIA GPU 0: GeForce GT 540M (driver version unknown, CUDA version 4000, compute capability 2.1, 962MB, 172 GFLOPS peak)
BOINC 6.12.26(x64)
I have installed latest 275.50-notebook-win7-winvista-64bit-international-beta
Jason G:
--- Quote from: _heinz on 01 Jul 2011, 03:06:13 am ---...
Only issue every time when a seti wu will start the machines clock down again on my GT540M.
I run it together with primegrid....
--- End quote ---
OK heinz, I think that no other project has the application fixes for newer Cuda drivers yet. If you suspend primegrid for a while & verfiy you see no more downclocks, then I'd suggest if you want to run that then either go back to a Cuda 3.2 driver (until primegrid fixes their application) or encourage them to apply the boincapi fixes necessary in an application update.
Jason
_heinz:
--- Quote from: Jason G on 01 Jul 2011, 03:15:06 am ---
--- Quote from: _heinz on 01 Jul 2011, 03:06:13 am ---...
Only issue every time when a seti wu will start the machines clock down again on my GT540M.
I run it together with primegrid....
--- End quote ---
OK heinz, I think that no other project has the application fixes for newer Cuda drivers yet. If you suspend primegrid for a while & verfiy you see no more downclocks, then I'd suggest if you want to run that then either go back to a Cuda 3.2 driver (until primegrid fixes their application) or encourage them to apply the boincapi fixes necessary in an application update.
Jason
--- End quote ---
from where I can download the boincapi fixes ? If I get them, I can compile a new pg version, to see if that fixes the issue.
thanks
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version