+- +-
Say hello if visiting :) by Gecko
11 Jan 2023, 07:43:05 pm

Seti is down again by Mike
09 Aug 2017, 10:02:44 am

Some considerations regarding OpenCL MultiBeam app tuning from algorithm view by Raistmer
11 Dec 2016, 06:30:56 am

Loading APU to the limit: performance considerations by Mike
05 Nov 2016, 06:49:26 am

Better sleep on Windows - new round by Raistmer
26 Aug 2016, 02:02:31 pm

Author Topic: x38g reports  (Read 150247 times)

Offline perryjay

  • Knight Templar
  • ****
  • Posts: 427
Re: x38g reports
« Reply #120 on: 30 Jun 2011, 10:21:02 am »
Here's another one you guys might like to ponder http://setiathome.berkeley.edu/workunit.php?wuid=766762437  it gives a 6.03, 6.08, x38g, and my x39e plus another it has just been sent out to running optimized Linux. He should be reporting in soon.

Offline Jason G

  • Construction Fraggle
  • Knight who says 'Ni!'
  • *****
  • Posts: 8980
Re: x38g reports
« Reply #121 on: 30 Jun 2011, 10:49:00 am »
Same one I reckon  :D

Offline perryjay

  • Knight Templar
  • ****
  • Posts: 427
Re: x38g reports
« Reply #122 on: 30 Jun 2011, 12:12:46 pm »
May want to see this one too.  http://setiathome.berkeley.edu/workunit.php?wuid=771931438  First three to run it got -12s I completed and a 6.03 completed with the same count I had. Still got sent out to another.


Am I finding what you guys are looking for or wasting your time? If these don't help let me know more of what I should look for.   ;)


Here's a poor guy with a new GTX 590 throwing a bunch of -9s. http://setiathome.berkeley.edu/show_host_detail.php?hostid=6016350 He's showing 122 invalids with only 36 valid results. He's running x32f.
« Last Edit: 30 Jun 2011, 12:28:45 pm by perryjay »

Offline Josef W. Segur

  • Janitor o' the Board
  • Knight who says 'Ni!'
  • *****
  • Posts: 3112
Re: x38g reports
« Reply #123 on: 30 Jun 2011, 12:35:35 pm »
AK_v8b_win_SSSE3x.exe has just gotten to bodgy and calculates its score as 1.293091 which is close though I'd rather the first difference were in the 6th significant digit than the 5th.

If you are too, I'm content to call this one "remaining chirp annoyances, with added yet to be divined nVidia Gaussfit implementation vagaries"

Agreed, and I hope Crunch3r's 64 bit Linux build will resolve it. Otherwise that WU will end up in the very rare "Too many success results" category.

...
Am I finding what you guys are looking for or wasting your time? If these don't help let me know more of what I should look for.   ;)
...

You're doing fine, we just wish the project were fully funded and had several technicians available to look into these cases.  8)
                                                             Joe

Offline perryjay

  • Knight Templar
  • ****
  • Posts: 427
Re: x38g reports
« Reply #124 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

Offline Jason G

  • Construction Fraggle
  • Knight who says 'Ni!'
  • *****
  • Posts: 8980
Re: x38g reports
« Reply #125 on: 30 Jun 2011, 09:16:02 pm »
Got the same count as this 460 running x38g but still went to inconclusive..  http://setiathome.berkeley.edu/workunit.php?wuid=771572553

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
« Last Edit: 30 Jun 2011, 09:35:32 pm by Jason G »

Offline perryjay

  • Knight Templar
  • ****
  • Posts: 427
Re: x38g reports
« Reply #126 on: 30 Jun 2011, 10:39:37 pm »
Duh, right, me good x38g bad, got it!   ;)

Offline _heinz

  • Volunteer Developer
  • Knight who says 'Ni!'
  • *****
  • Posts: 2117
Re: x38g reports
« Reply #127 on: 01 Jul 2011, 03:06:13 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
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

Offline Jason G

  • Construction Fraggle
  • Knight who says 'Ni!'
  • *****
  • Posts: 8980
Re: x38g reports
« Reply #128 on: 01 Jul 2011, 03:15:06 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....

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

Offline _heinz

  • Volunteer Developer
  • Knight who says 'Ni!'
  • *****
  • Posts: 2117
Re: x38g reports
« Reply #129 on: 01 Jul 2011, 06:53:16 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....

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
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

Offline Jason G

  • Construction Fraggle
  • Knight who says 'Ni!'
  • *****
  • Posts: 8980
Re: x38g reports
« Reply #130 on: 01 Jul 2011, 07:21:47 am »
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
  pretty sure I gave you that info ... Looking...

[Edit:] found it:
http://lunatics.kwsn.net/5-windows/re-ap-blanking-experiment.msg39031.html#msg39031

Offline perryjay

  • Knight Templar
  • ****
  • Posts: 427
Re: x38g reports
« Reply #131 on: 01 Jul 2011, 09:28:34 am »
Quote
May want to see this one too.  http://setiathome.berkeley.edu/workunit.php?wuid=771931438  First three to run it got -12s I completed and a 6.03 completed with the same count I had. Still got sent out to another.

Last man finished. Three of us got validated. Last man also ran it as a 6.03.

Offline Jason G

  • Construction Fraggle
  • Knight who says 'Ni!'
  • *****
  • Posts: 8980
Re: x38g reports
« Reply #132 on: 01 Jul 2011, 12:11:03 pm »
Well am back up & running with a spare 450W PSU myself & had to put in the old 9600GSO to get operational again.  The 750W one driving the GTX 480 seems to have bitten the dust, so it's out of action until I can RMA it. 

Oh well, looks like crunching, development & everything else will be in slow motion for the time being  ::)

Offline arkayn

  • Janitor o' the Board
  • Knight who says 'Ni!'
  • *****
  • Posts: 1230
  • Aaaarrrrgggghhhh
    • My Little Place On The Internet
Re: x38g reports
« Reply #133 on: 01 Jul 2011, 12:23:17 pm »
Ouch!!!!

I am currently using my AMD Quad as my primary desktop since the iMac is just getting old and crash happy. I use my Q8200 machine as the music supplier.

Offline perryjay

  • Knight Templar
  • ****
  • Posts: 427
Re: x38g reports
« Reply #134 on: 01 Jul 2011, 02:19:14 pm »
What, you don't have a dozen or so extras laying around? Sorry to hear that Jason, hope you get going again real soon. Things are still running good here, no problems to report. I have got my first AP on GPU but will be awhile before I get to it. Hope nothing smokes here by trying to run it. I haven't changed any settings so it will have to fend for itself when it starts.

 

Welcome, Guest.
Please login or register.
 
 
 
Forgot your password?
Members
Total Members: 97
Latest: ToeBee
New This Month: 0
New This Week: 0
New Today: 0
Stats
Total Posts: 59559
Total Topics: 1672
Most Online Today: 355
Most Online Ever: 983
(20 Jan 2020, 03:17:55 pm)
Users Online
Members: 0
Guests: 28
Total: 28
Powered by EzPortal