Posts by |MatMan|

1) Message boards : Number crunching : cuda_opend failed (Message 44989)
Posted 13 Dec 2010 by |MatMan|
Post:

I get these errors (WU):

<core_client_version>6.10.58</core_client_version>
<![CDATA[
<message>
 - exit code -1073741819 (0xc0000005)
</message>
<stderr_txt>
<search_application> milkywayathome separation 0.50 Windows x86 double OpenCL </search_application>
Found 1 platforms
Platform 0 information:
  Platform name:       NVIDIA CUDA
  Platform version:    OpenCL 1.0 CUDA 3.2.1
  Platform vendor:     
  Platform profile:    
  Platform extensions: cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_d3d9_sharing cl_nv_d3d10_sharing cl_khr_d3d10_sharing cl_nv_d3d11_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll 
Using device 1 on platform 0
Found 3 CL devices
Device GeForce GTX 295 (NVIDIA Corporation:0x10de)
Type:                CL_DEVICE_TYPE_GPU
Driver version:      265.90
Version:             OpenCL 1.0 CUDA
Compute capability:  1.3
Little endian:       CL_TRUE
Error correction:    CL_FALSE
Image support:       CL_TRUE
Address bits:        32
Max compute units:   30
Clock frequency:     1075 Mhz
Global mem size:     911605760
Max mem alloc:       227901440
Global mem cache:    0
Cacheline size:      0
Local mem type:      CL_LOCAL
Local mem size:      16384
Max const args:      9
Max const buf size:  65536
Max parameter size:  4352
Max work group size: 512
Max work item dim:   3
Max work item sizes: { 512, 512, 64 }
Mem base addr align: 2048
Min type align size: 128
Timer resolution:    1000 ns
Double extension:    MW_CL_KHR_FP64
Extensions:          cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_d3d9_sharing cl_nv_d3d10_sharing cl_khr_d3d10_sharing cl_nv_d3d11_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll  cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_fp64 
Found a compute capability 1.3 device. Using -cl-nv-maxrregcount=32 

Compiler flags:
-cl-mad-enable -cl-no-signed-zeros -cl-strict-aliasing -cl-finite-math-only -DUSE_CL_MATH_TYPES=0 -DUSE_MAD=1 -DUSE_FMA=0 -cl-nv-verbose  -cl-nv-maxrregcount=32  -DDOUBLEPREC=1 -DMILKYWAY_MATH_COMPILATION -DNSTREAM=3 -DFAST_H_PROB=1 -DAUX_BG_PROFILE=0 -DUSE_IMAGES=1 -DI_DONT_KNOW_WHY_THIS_DOESNT_WORK_HERE=0  

Build status: CL_BUILD_ERROR


Unhandled Exception Detected...

- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x02B40A20 read attempt to address 0x00000000

Windows 7 64bit, one GTX295 + one 9600GSO

2) Message boards : Number crunching : CUDA Application Updated (Message 31665)
Posted 28 Sep 2009 by |MatMan|
Post:

Anyway, the new CUDA app looks quite nice: 200s for a GTX280 is only 4 times slower than a 110€ ATI. That's better than expected ;)

If I'm not wrong the theoretical DP performance of a 4870 (is this the card you meant?) vs a GTX280 is 240 GFLOPS vs 78 GFLOPS = ~3 : 1.
So a factor of 4 is nice but we should get to a factor of 3... :P

I know it's just a comparison of theoretical numbers...

3) Message boards : Number crunching : CUDA Application for 32 bit Windows (Message 31342)
Posted 22 Sep 2009 by |MatMan|
Post:

So I cant use opti app to Run CPU? I was hoping to run cpu and gpu, but cpu is too slow without opti app.If I rename file will it still run opti app?

If I understand you correctly you want to run the optimized CPU app and the CUDA app in parallel.

Here is an app_info.xml which should just do that (adapted from lunatics). You have to change the name of the CPU app to the one which you are actually using (in my case this is the 64bit SSE3 version)! Stop Boinc, create an empty text file in your milkyway project directory (this is were also the optimized app is located), copy everything from below in it, rename the file to "app_info.xml", start Boinc (previously downloaded CUDA workunits will be discarded). Absolutely no guarantee that it will work - it works for me though...

<app_info>
 <app>
  <name>milkyway</name>
 </app>
 <file_info>
  <name>astronomy_0.20_x64_SSE3.exe</name>
  <executable/>
 </file_info>

 <app_version>
  <app_name>milkyway</app_name>
  <version_num>19</version_num>
  <file_ref>
   <file_name>astronomy_0.20_x64_SSE3.exe</file_name>
   <main_program/>
  </file_ref>
 </app_version>

 <app_version>
  <app_name>milkyway</app_name>
  <version_num>20</version_num>
  <file_ref>
   <file_name>astronomy_0.20_x64_SSE3.exe</file_name>
   <main_program/>
  </file_ref>
 </app_version>

 <app>
    <name>milkyway</name>
    </app>
    <file_info>
        <name>milkyway_0.20_windows_intelx86__cuda23.exe</name>
        <executable/>
    </file_info>
    <file_info>
        <name>cudart.dll</name>
        <executable/>
    </file_info>
    <file_info>
        <name>cutil32.dll</name>
        <executable/>
    </file_info>
    <app_version>
        <app_name>milkyway</app_name>
        <version_num>20</version_num>
        <plan_class>cuda23</plan_class>
        <avg_ncpus>0.040000</avg_ncpus>
        <max_ncpus>0.040000</max_ncpus>
        <coproc>
            <type>CUDA</type>
            <count>1</count>
        </coproc>
        <file_ref>
            <file_name>milkyway_0.20_windows_intelx86__cuda23.exe</file_name>
            <main_program/>
         </file_ref>
        <file_ref>
	       <file_name>cudart.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>cutil32.dll</file_name>
        </file_ref>        
    </app_version>

</app_info>