1)
Message boards :
Number crunching :
All work Units giving "Computational Error"
(Message 53190)
Posted 15 Feb 2012 by Grutte Pier [Wa Oars]~MAB The Frisian Post: Atm it seems it's working fine. Installed 6.10.60 again and afterwards http://www.arkayn.us/forum/index.php?PHPSESSID=f0483088d797862abe1bbb0a1b6bd4a2&action=downloads;sa=view;down=60 on my XP64 GTX 460 FTW 1GB (1.075V > 1.012V / 850MHz > 890MHz) / 6.10.60 / 275.33 XP32 OK GTX 460 SC 768MB (763MHz > 820MHz) / 6.10.60 / 285.58 XP64 OK Will change some things in nearby future such as drivers, voltages and speed and watch what happens. |
2)
Message boards :
Number crunching :
All work Units giving "Computational Error"
(Message 53125)
Posted 13 Feb 2012 by Grutte Pier [Wa Oars]~MAB The Frisian Post: It seems it's OK at the moment, now I'm having Collatz-problems with that specific card (can't find mem-errors) ?????, and I let that card crunch on MW@H for a while. |
3)
Message boards :
Number crunching :
All work Units giving "Computational Error"
(Message 53061)
Posted 10 Feb 2012 by Grutte Pier [Wa Oars]~MAB The Frisian Post: Had installed 275.33 to see everything keeps crunching so will check it soon. |
4)
Message boards :
Number crunching :
All work Units giving "Computational Error"
(Message 53021)
Posted 10 Feb 2012 by Grutte Pier [Wa Oars]~MAB The Frisian Post: Perhaps I'll start MW@H again if I know which driver is most stable. Atm no probs with Collatz so ......... |
5)
Message boards :
Number crunching :
All work Units giving "Computational Error"
(Message 52936)
Posted 9 Feb 2012 by Grutte Pier [Wa Oars]~MAB The Frisian Post: And which are stable enough for MW@H and other boinc projects. Not playing any games just folding. XP 64, Asrock 870 xtreme, 8GB Kingston 1600 and a Phenom II X4 945 |
6)
Message boards :
Number crunching :
All work Units giving "Computational Error"
(Message 52913)
Posted 9 Feb 2012 by Grutte Pier [Wa Oars]~MAB The Frisian Post: Stopped boinc and repaired it but still get : http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=99049735 even on the machine which had it xp32 replaced by xp64 and fresh install of drivers 266.58 and boinc 6.10.60, so MW@H is exit for the moment. |
7)
Message boards :
Number crunching :
CL_INVALID_COMMAND_QUEUE
(Message 52354)
Posted 10 Jan 2012 by Grutte Pier [Wa Oars]~MAB The Frisian Post: Could be bug or driver issue. You might try updating your drivers; 266.58 is almost a year old. I know and have tried several but they were slower than the one I installed. I've had some problems before with nv4_disp and now that OK I hope. I have repaired boinc and it seems OK at the moment (fingers crossed). |
8)
Message boards :
Number crunching :
CL_INVALID_COMMAND_QUEUE
(Message 52335)
Posted 9 Jan 2012 by Grutte Pier [Wa Oars]~MAB The Frisian Post: Suddenly a lot of CL_INVALID_COMMAND_QUEUE errors. Anyone any idea ? <core_client_version>6.10.60</core_client_version> <![CDATA[ <message> Onjuiste functie. (0x1) - exit code 1 (0x1) </message> <stderr_txt> Error loading Lua script 'astronomy_parameters.txt': [string "number_parameters: 4..."]:1: '<name>' expected near '4' Error reading astronomy parameters from file 'astronomy_parameters.txt' Trying old parameters file Using SSE2 path Found 1 platform(s) Platform 0 information: Name: NVIDIA CUDA Version: OpenCL 1.0 CUDA 3.2.1 Vendor: NVIDIA Corporation Extensions: cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_d3d9_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll Profile: FULL_PROFILE Using device 0 on platform 0 Found 1 CL device(s) Device GeForce GTX 460 (NVIDIA Corporation:0x10de) (CL_DEVICE_TYPE_GPU) Driver version: 266.58 Version: OpenCL 1.0 CUDA Compute capability: 2.1 Image support: CL_TRUE Max compute units: 7 Clock frequency: 1640 Mhz Global mem size: 804847616 Local mem size: 49152 Max const buf size: 65536 Double extension: MW_CL_KHR_FP64 Compiler flags: -cl-mad-enable -cl-no-signed-zeros -cl-strict-aliasing -cl-finite-math-only -cl-nv-verbose -DDOUBLEPREC=1 -DFAST_H_PROB=1 -DAUX_BG_PROFILE=0 -DNSTREAM=2 -DCONVOLVE=120 -DR0=27.411997116918361 -DSUN_R0=8.500000000000000 -DQ_INV_SQR=1.000000000000000 -DUSE_IMAGES=0 Build status: CL_BUILD_SUCCESS Build log: : Considering profile 'compute_20' for gpu='sm_21' in 'cuModuleLoadDataEx_4' : Retrieving binary for 'cuModuleLoadDataEx_4', for gpu='sm_21', usage mode=' --verbose ' : Considering profile 'compute_20' for gpu='sm_21' in 'cuModuleLoadDataEx_4' : Control flags for 'cuModuleLoadDataEx_4' disable search path : Ptx binary found for 'cuModuleLoadDataEx_4', architecture='compute_20' : Ptx compilation for 'cuModuleLoadDataEx_4', for gpu='sm_21', ocg options=' --verbose ' ptxas info : Compiling entry function 'mu_sum_kernel' for 'sm_21' ptxas info : Function properties for mu_sum_kernel 256 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads ptxas info : Used 49 registers, 8+0 bytes lmem, 80 bytes cmem[0], 22 bytes cmem[2], 20 bytes cmem[16] Kernel work group info: Work group size = 640 Kernel local mem size = 0 Compile work group size = { 0, 0, 0 } Keeping chunk boundaries as multiples of 448 Range: { nu_steps = 640, mu_steps = 1600, r_steps = 1400 } Iteration area: 2240000 Chunk estimate: 79 Num chunks: 79 Added area: 0 Effective area: 2240000 Failed to finish: CL_INVALID_COMMAND_QUEUE Failed to run nu step: CL_INVALID_COMMAND_QUEUE Integral 0 time = 2.817866 s Failed to calculate integral 0 07:10:26 (2712): called boinc_finish </stderr_txt> ]]> |
9)
Message boards :
Number crunching :
Doesn't run on 2 cores from a Phenom II X4 945
(Message 52196)
Posted 3 Jan 2012 by Grutte Pier [Wa Oars]~MAB The Frisian Post: Is it possible you have forgotten a </app_version> at the end ? I'm getting a "parse error in app_info.xml; check XML syntax". And I saw in the app you already added the lines for gpu ? It looks as if cpu wu's will not download if gpu is running and also I don't get anymore gpu wu's while trying to download cpu wu's. |
10)
Message boards :
Number crunching :
Doesn't run on 2 cores from a Phenom II X4 945
(Message 52195)
Posted 3 Jan 2012 by Grutte Pier [Wa Oars]~MAB The Frisian Post: Thanks ! Can you give me also the needed lines for adding GPU-crunching for if I want to use cpu and gpu to do MW@H ? And what if I want my gpu's to crunch on SETI and Milkyway simultaniously ? Are gpu-crunching M@H at the moment but would like to start S@H again also. |
11)
Message boards :
Number crunching :
Doesn't run on 2 cores from a Phenom II X4 945
(Message 52182)
Posted 2 Jan 2012 by Grutte Pier [Wa Oars]~MAB The Frisian Post: I use 2 cores to run Malariacontrol and wanted to use 2 cores for M@H but it doesn't run on 2 cores, only on 4 cores although I set the preferences on 2 cores and 50%. And what about "On multiprocessors, use at most 2 processors" ? It seems to me that if you use the above on a certain project it should only use those 2 cores and no more. And thus leaving 2 cores to use somewhere else. |
12)
Message boards :
Number crunching :
Doesn't run on 2 cores from a Phenom II X4 945
(Message 52173)
Posted 2 Jan 2012 by Grutte Pier [Wa Oars]~MAB The Frisian Post: And where to find ? I'm a N00B programming. |
13)
Message boards :
Number crunching :
Doesn't run on 2 cores from a Phenom II X4 945
(Message 52165)
Posted 1 Jan 2012 by Grutte Pier [Wa Oars]~MAB The Frisian Post: I use 2 cores to run Malariacontrol and wanted to use 2 cores for M@H but it doesn't run on 2 cores, only on 4 cores although I set the preferences on 2 cores and 50%. Normal ? Update : It wil run on two cores but only if no other project is running. Found on the SETI site it uses all cores or none (or less cores but the other cores are useles). So I can't run it besides another project and it delivers not enough WU's to run day after day and also it won't start even if I set resource share to 100% and 1% at MC. |
©2024 Astroinformatics Group