CUDA_V12_app

[Sutaru Tsureku]

In past with Crunch3r's BOINC V6.1.0 (mod of stock V5.10.1x) and CPU-affinity I saw a crunching speed up of ~ 1 - 2 % with MB WUs.

Intel Core2 Extreme QX6700.
This is a 2x DUO-CPU. 2x shared L2-Cache. So cache miss can happen.

Now with the current available Quad-CPUs which have a L2-Cache/CPU-Core this Cache miss can happen much more.

It would be nice to have again a Truxoft- or Crunch3r- BOINC mod with this.

[Pappa]

In past with Crunch3r's BOINC V6.1.0 (mod of stock V5.10.1x) and CPU-affinity I saw a crunching speed up of ~ 1 - 2 % with MB WUs.

Intel Core2 Extreme QX6700.
This is a 2x DUO-CPU. 2x shared L2-Cache. So cache miss can happen.

Now with the current available Quad-CPUs which have a L2-Cache/CPU-Core this Cache miss can happen much more.

It would be nice to have again a Truxoft- or Crunch3r- BOINC mod with this.

You could test Raistmers App as he asked you to do. What you could, report would mean he moves it ahead or it truly dead. It is your choice.

It is just that simple... BS Aside.

[Sutaru Tsureku]

You could test Raistmers App as he asked you to do. What you could, report would mean he moves it ahead or it truly dead. It is your choice.

It is just that simple... BS Aside.

Don't you think it's time to stop with this?

I think enough is ENOUGH. 

Let it be!

[Franz]

Please, look at this task: http://setiathome.berkeley.edu/result.php?resultid=1483022945

With 3 GPU 275

   

<core_client_version>6.10.17</core_client_version>
<![CDATA[
<message>
Incorrect function. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
setiathome_CUDA: Found 3 CUDA device(s):
   Device 1 : GeForce GTX 275
           totalGlobalMem = 939524096
           sharedMemPerBlock = 16384
           regsPerBlock = 16384
           warpSize = 32
           memPitch = 262144
           maxThreadsPerBlock = 512
           clockRate = 1512000
           totalConstMem = 65536
           major = 1
           minor = 3
           textureAlignment = 256
           deviceOverlap = 1
           multiProcessorCount = 30
   Device 2 : GeForce GTX 275
           totalGlobalMem = 939524096
           sharedMemPerBlock = 16384
           regsPerBlock = 16384
           warpSize = 32
           memPitch = 262144
           maxThreadsPerBlock = 512
           clockRate = 1512000
           totalConstMem = 65536
           major = 1
           minor = 3
           textureAlignment = 256
           deviceOverlap = 1
           multiProcessorCount = 30
   Device 3 : GeForce GTX 275
           totalGlobalMem = 939524096
           sharedMemPerBlock = 16384
           regsPerBlock = 16384
           warpSize = 32
           memPitch = 262144
           maxThreadsPerBlock = 512
           clockRate = 1512000
           totalConstMem = 65536
           major = 1
           minor = 3
           textureAlignment = 256
           deviceOverlap = 1
           multiProcessorCount = 30
setiathome_CUDA: CUDA Device 3 specified, checking...
   Device 3: GeForce GTX 275 is okay
SETI@home using CUDA accelerated device GeForce GTX 275
V12 mÿdification by Raistmer
Priority of worker thread rised successfully
Priority of process adjusted successfully
Total GPU memory 939524096    free GPU memory 256602112
setiathome_enhanced 6.02 Visual Studio/Microsoft C++

Build features: Non-graphics   CUDA    VLAR autokill enabled    FFTW   USE_SSE   x86   
     CPUID: Intel(R) Core(TM)2 Quad CPU    Q9650  @ 3.00GHz

     Cache: L1=64K L2=6144K

CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3
libboinc: 6.3.22

Work Unit Info:
...............
WU true angle range is :  2.472358
After app init: total GPU memory 939524096    free GPU memory 223047680
Cuda error 'cudaAcc_CalcChirpData_kernel2' in file 'd:/BoincSeti_Prog/sinbad_repositories/LunaticsUnited/SETI_CUDA_MB_exp/client/cuda/cudaAcc_CalcChirpData.cu' in line 106 : unknown error.
Cuda error 'cufftExecC2C' in file 'd:/BoincSeti_Prog/sinbad_repositories/LunaticsUnited/SETI_CUDA_MB_exp/client/cuda/cudaAcc_fft.cu' in line 143 : unknown error.
Cuda error 'cufftExecC2C' in file 'd:/BoincSeti_Prog/sinbad_repositories/LunaticsUnited/SETI_CUDA_MB_exp/client/cuda/cudaAcc_fft.cu' in line 143 : unknown error.
Cuda error 'cudaAcc_GetPowerSpectrum_kernel' in file 'd:/BoincSeti_Prog/sinbad_repositories/LunaticsUnited/SETI_CUDA_MB_exp/client/cuda/cudaAcc_PowerSpectrum.cu' in line 56 : unknown error.
Cuda error );cudaAcc_GetPowerSpectrum_kernel' in file 'd:/BoincSeti_Prog/sinbad_repositories/LunaticsUnited/SETI_CUDA_MB_exp/client/cuda/cudaAcc_PowerSpectrum.cu' in line 56 : unknown error.
Cuda error 'cudaAcc_summax32_kernel' in file 'd:/BoincSeti_Prog/sinbad_repositories/LunaticsUnited/SETI_CUDA_MB_exp/client/cuda/cudaAcc_summax.cu' in line 147 : unknown error.
Cuda error 'cudaAcc_summax32_kernel' in file 'd:/BoincSeti_Prog/sinbad_repositories/LunaticsUnited/SETI_CUDA_MB_exp/client/cuda/cudaAcc_summax.cu' in line 147 : unknown error.
Cuda error 'cudaMemcpy(PowerSpectrumSumMax, dev_PowerSpectrumSumMax, cudaAcc_NumDataPoints / fftlen * sizeof(*dev_PowerSpectrumSumMax), cudaMemcpyDeviceToHost)' in file 'd:/BoincSeti_Prog/sinbad_repositories/LunaticsUnited/SETI_CUDA_MB_exp/client/cuda/cudaAcc_summax.cu' in line 160 : unknown error.

</stderr_txt>
]]>

Thanks for any help
Franz

[Raistmer]

You could test Raistmers App as he asked you to do. What you could, report would mean he moves it ahead or it truly dead. It is your choice.

It is just that simple... BS Aside.

Don't you think it's time to stop with this?

I think enough is ENOUGH. 

Let it be!

I think we stop this topic. All PMs sent and recived IMO.

[Raistmer]

Please, look at this task: http://setiathome.berkeley.edu/result.php?resultid=1483022945

With 3 GPU 275

As one can see nVidia's error reporting system provide not much help in debugging.
"unknown error" all that said.
How often you got such results?
If it's only 1 per few dozens - well, you should just live with that for now. If much often, then it's topic to discuss.

ADDON: And I would recommend to change driver to 191.* or 190.* and go with CUDA 2.3
195.* just unndeeded for non-fermi cards and may have some new issues indeed.

[In the world of software it's often happens that newer != better, just look on Vista release over XP ]

[Sutaru Tsureku]

It's a Win7 OS.
From what I read of Fred and his 2x GTX295 PC, he couldn't let run Win7 without probs (CUDA errors, driver crashs).
So he's down to WinXP and everything is fine.

[Franz]

It's a Win7 OS.
From what I read of Fred and his 2x GTX295 PC, he couldn't let run Win7 without probs (CUDA errors, driver crashs).
So he's down to WinXP and everything is fine.

Microsoft Windows 7 ... Ultimate x64 Edition ...Nvida driver: 19562

Pelase look at here http://setiathome.berkeley.edu/result.php?resultid=1483726484
and tell me if there is some problem with 3 GPU in SLI mode or in NO SLI mode.

Franz

[Raistmer]

Your app instance crashed badly on that task.
Try to replace drivers with 191.* ones.

[Raistmer]

"Total GPU memory 939524096    free GPU memory 256024576"
And where other ~700MB of GPU memory

[Sutaru Tsureku]

Franz, this is a known BUG of the opt._CUDA_app.
Raistmer inserted a BUG detection, which should detect and display the BUG of the CUDA BUG.
Sometimes it fail and show this 'funny/strange' output.
Normally it should display the -12 error with BUG report.
But it show sometimes (very rarely) an 'Out Of Memory' error.

Raistmer, you can't remember, we both together found/discovered this..

You should not have enabled SLI for CUDA. The new driver should disable SLI automatically if CUDA.


Raistmer, in the SETI@home forum I saw a member also with Win7.
He have 2x GTX295 and ALL GPUs had only ~ 400 or ~ 200 MB free GPU RAM before CUDA load.
Sometimes too less and then the CUDA WU was crunched on CPU (falling back to CPU processing...).
I guess it's a Win7 or nVIDIA_driver BUG.

[Sutaru Tsureku]

Franz, BTW.
This Win7 PC have very much 1 errors.
It's like the other member I helped with his Win7 and 2x GTX295 PC.

Also Fred said, he couldn't let run well CUDA on his Win7 and 2x GTX295.
Not 190.x , 191.x and not 195.x . He continue with WinXP.

So I recommended the member to install WinXP and since then no error.

It could be a BUG in Win7 or the current available nVIDIA_drivers.
So the time will tell if with a new nVIDIA_driver it will be better.

The easiest would be to install WinXP.

[Raistmer]

Raistmer, you can't remember, we both together found/discovered this..

Ah, good that you remind me. Yes, sometimes memories fall

[Devaster]

i am using W7 on my machine with 9600GT and 8500GT for 4 monts with always latest drivers (beta or not) and NEVER had problems low mem on any CUDA project

[Raistmer]

i am using W7 on my machine with 9600GT and 8500GT for 4 monts with always latest drivers (beta or not) and NEVER had problems low mem on any CUDA project

x86 or x64 OS ?