Posts by Ross*

1) Message boards : Graphics cards (GPUs) : why can"t I get new tasks (Message 40168) Posted 14 Feb 2015 by Ross* Post: Hi reduced cache to 1 day and everything works. the software must have had a confused problem that the if I got 10 days of tasks I would not be able to complete them in time. I was not doing other projects. I now get 2 tasks in reserve most of the time. the long 24hr tasks take 7hrs Cheers Ross*
2) Message boards : Graphics cards (GPUs) : why can"t I get new tasks (Message 40157) Posted 12 Feb 2015 by Ross* Post: Hi 13/02/2015 12:30:43 p.m. \| GPUGRID \| Sending scheduler request: Requested by user. 13/02/2015 12:30:43 p.m. \| GPUGRID \| Requesting new tasks for NVIDIA GPU 13/02/2015 12:30:47 p.m. \| GPUGRID \| Scheduler request completed: got 0 new tasks 13/02/2015 12:30:47 p.m. \| GPUGRID \| No tasks sent 13/02/2015 12:30:47 p.m. \| GPUGRID \| Tasks won't finish in time: BOINC runs 75.1% of the time; computation is enabled 100.0% of that Have increased my cache to 10 days . What setting do I change to get ride of this error ? Boinc 4.2.36 no other projects running , using 780 TI Kingpins try using Titan Z but could only get 1 task at a time. Thanks for any info Ross*
3) Message boards : Number crunching : FYI to all Nvidia Crunches out there... Clock speed Problems (Message 21250) Posted 25 May 2011 by Ross* Post: As I've posted in reply to your identical post at SETI: This problem has recently been drawn to the attention of the SETI CUDA developers, and is in the process of being reported onwards to other CUDA-enabled BOINC projects. It seems to be related specifically to the release of nVidia drivers which will support the forthcoming v4 release of the CUDA run-time support files. The central BOINC library code isn't yet fully compatible with CUDA v4: the problem has been overcome with test programs, and should go away with the next round of application releases. Unfortunately, v3 and earlier nVidia drivers aren't available for the very latest generation of nVidia cards, but if you have a card which can run with nVidia driver 266.58, that should avoid the problem. @ project devs: It's been isolated to a CUDA task exit handling problem in the BOINC API library code. Eric Korpela (SETI@home) has a copy of the proposed (and tested) solution for evaluation, and is considering checking it in following testing and evaluation. I can put you in touch with the developer concerned, or pass messages, if you wish. Hi I have had the same problem with various cards . the new beta 270 driver seems to have fixed the problem. [I hope ] Cheers Ross*
4) Message boards : Number crunching : Energies have become nan (Message 21036) Posted 22 Apr 2011 by Ross* Post: The following happened to several Wus with this driver on 2 boxes A198-TONI_AGG1-8-100-RND4916_0 Workunit 2448115 Created 21 Apr 2011 19:47:36 UTC Sent 21 Apr 2011 19:52:50 UTC Received 21 Apr 2011 23:20:56 UTC Server state Over Outcome Client error Client state Compute error Exit status 98 (0x62) Computer ID 95964 Report deadline 26 Apr 2011 19:52:50 UTC Run time 8796.666317 CPU time 1981.4 stderr out <core_client_version>6.10.58</core_client_version> <![CDATA[ <message> - exit code 98 (0x62) </message> <stderr_txt> # Using device 0 # There are 2 devices supporting CUDA # Device 0: "GeForce GTX 570" # Clock rate: 1.56 GHz # Total amount of global memory: 1275658240 bytes # Number of multiprocessors: 15 # Number of cores: 120 # Device 1: "GeForce GTX 570" # Clock rate: 1.56 GHz # Total amount of global memory: 1275789312 bytes # Number of multiprocessors: 15 # Number of cores: 120 MDIO ERROR: cannot open file "restart.coor" ERROR: file deven.cpp line 879: # Energies have become nan called boinc_finish </stderr_txt> ]]> Validate state Invalid Claimed credit 35140.0810185185 Granted credit 0 application version Long runs (8-12 hours on fastest card) v6.13 (cuda31) Also these A560r5-TONI_AB1-21-100-RND5976_1 Workunit 2447770 Created 21 Apr 2011 15:12:33 UTC Sent 21 Apr 2011 22:50:47 UTC Received 22 Apr 2011 0:06:48 UTC Server state Over Outcome Client error Client state Compute error Exit status 98 (0x62) Computer ID 96625 Report deadline 26 Apr 2011 22:50:47 UTC Run time 1046.854 CPU time 272.0657 stderr out <core_client_version>6.10.58</core_client_version> <![CDATA[ <message> - exit code 98 (0x62) </message> <stderr_txt> # Using device 0 # There are 2 devices supporting CUDA # Device 0: "GeForce GTX 580" # Clock rate: 1.59 GHz # Total amount of global memory: 1543045120 bytes # Number of multiprocessors: 16 # Number of cores: 128 # Device 1: "GeForce GTX 580" # Clock rate: 1.59 GHz # Total amount of global memory: 1543176192 bytes # Number of multiprocessors: 16 # Number of cores: 128 MDIO ERROR: warning: redefined atom parameters for ht MDIO ERROR: warning: redefined atom parameters for ot MDIO ERROR: warning: redefined atom parameters for cph1 MDIO ERROR: warning: redefined atom parameters for cph2 MDIO ERROR: warning: redefined atom parameters for nr1 MDIO ERROR: warning: redefined atom parameters for nr2 MDIO ERROR: warning: redefined atom parameters for hr3 MDIO ERROR: warning: redefined atom parameters for hr1 MDIO ERROR: warning: redefined bond parameters for ht ht MDIO ERROR: warning: redefined bond parameters for ht ot MDIO ERROR: warning: redefined bond parameters for nr1 cph1 MDIO ERROR: warning: redefined bond parameters for nr1 cph2 MDIO ERROR: warning: redefined bond parameters for nr2 cph1 MDIO ERROR: warning: redefined bond parameters for nr2 cph2 MDIO ERROR: warning: redefined bond parameters for cph1 cph1 MDIO ERROR: warning: redefined bond parameters for hr1 cph2 MDIO ERROR: warning: redefined bond parameters for hr3 cph1 MDIO ERROR: warning: redefined angle parameters for cph2 nr1 cph1 MDIO ERROR: warning: redefined angle parameters for cph2 nr2 cph1 MDIO ERROR: warning: redefined angle parameters for nr1 cph1 cph1 MDIO ERROR: warning: redefined angle parameters for nr1 cph2 nr2 MDIO ERROR: warning: redefined angle parameters for nr2 cph1 cph1 MDIO ERROR: warning: redefined angle parameters for nr1 cph2 hr1 MDIO ERROR: warning: redefined angle parameters for nr2 cph2 hr1 MDIO ERROR: warning: redefined angle parameters for hr3 cph1 cph1 MDIO ERROR: warning: redefined angle parameters for nr1 cph1 hr3 MDIO ERROR: warning: redefined angle parameters for nr2 cph1 hr3 MDIO ERROR: warning: redefined angle parameters for ht ot ht MDIO ERROR: warning: redefined dihedral parameters for d cph2 nr1 cph1 cph1 MDIO ERROR: warning: redefined dihedral parameters for d cph2 nr2 cph1 cph1 MDIO ERROR: warning: redefined dihedral parameters for d nr1 cph1 cph1 hr3 MDIO ERROR: warning: redefined dihedral parameters for d nr1 cph2 nr2 cph1 MDIO ERROR: warning: redefined dihedral parameters for d nr2 cph1 cph1 nr1 MDIO ERROR: warning: redefined dihedral parameters for d nr2 cph2 nr1 cph1 MDIO ERROR: warning: redefined dihedral parameters for d hr1 cph2 nr1 cph1 MDIO ERROR: warning: redefined dihedral parameters for d hr1 cph2 nr2 cph1 MDIO ERROR: warning: redefined dihedral parameters for d hr3 cph1 cph1 hr3 MDIO ERROR: warning: redefined dihedral parameters for d hr3 cph1 nr1 cph2 MDIO ERROR: warning: redefined dihedral parameters for d hr3 cph1 nr2 cph2 MDIO ERROR: warning: redefined dihedral parameters for d nr2 cph1 cph1 hr3 MDIO ERROR: warning: redefined improper parameters for i hr1 nr1 nr2 cph2 MDIO ERROR: warning: redefined improper parameters for i hr1 nr2 nr1 cph2 MDIO ERROR: warning: redefined improper parameters for i hr3 cph1 nr1 cph1 MDIO ERROR: warning: redefined improper parameters for i hr3 cph1 nr2 cph1 MDIO ERROR: warning: redefined improper parameters for i hr3 nr1 cph1 cph1 MDIO ERROR: warning: redefined improper parameters for i hr3 nr2 cph1 cph1 MDIO ERROR: cannot open file "restart.coor" # Using device 0 # There are 2 devices supporting CUDA # Device 0: "GeForce GTX 580" # Clock rate: 1.59 GHz # Total amount of global memory: 1543045120 bytes # Number of multiprocessors: 16 # Number of cores: 128 # Device 1: "GeForce GTX 580" # Clock rate: 1.59 GHz # Total amount of global memory: 1543176192 bytes # Number of multiprocessors: 16 # Number of cores: 128 MDIO ERROR: warning: redefined atom parameters for ht MDIO ERROR: warning: redefined atom parameters for ot MDIO ERROR: warning: redefined atom parameters for cph1 MDIO ERROR: warning: redefined atom parameters for cph2 MDIO ERROR: warning: redefined atom parameters for nr1 MDIO ERROR: warning: redefined atom parameters for nr2 MDIO ERROR: warning: redefined atom parameters for hr3 MDIO ERROR: warning: redefined atom parameters for hr1 MDIO ERROR: warning: redefined bond parameters for ht ht MDIO ERROR: warning: redefined bond parameters for ht ot MDIO ERROR: warning: redefined bond parameters for nr1 cph1 MDIO ERROR: warning: redefined bond parameters for nr1 cph2 MDIO ERROR: warning: redefined bond parameters for nr2 cph1 MDIO ERROR: warning: redefined bond parameters for nr2 cph2 MDIO ERROR: warning: redefined bond parameters for cph1 cph1 MDIO ERROR: warning: redefined bond parameters for hr1 cph2 MDIO ERROR: warning: redefined bond parameters for hr3 cph1 MDIO ERROR: warning: redefined angle parameters for cph2 nr1 cph1 MDIO ERROR: warning: redefined angle parameters for cph2 nr2 cph1 MDIO ERROR: warning: redefined angle parameters for nr1 cph1 cph1 MDIO ERROR: warning: redefined angle parameters for nr1 cph2 nr2 MDIO ERROR: warning: redefined angle parameters for nr2 cph1 cph1 MDIO ERROR: warning: redefined angle parameters for nr1 cph2 hr1 MDIO ERROR: warning: redefined angle parameters for nr2 cph2 hr1 MDIO ERROR: warning: redefined angle parameters for hr3 cph1 cph1 MDIO ERROR: warning: redefined angle parameters for nr1 cph1 hr3 MDIO ERROR: warning: redefined angle parameters for nr2 cph1 hr3 MDIO ERROR: warning: redefined angle parameters for ht ot ht MDIO ERROR: warning: redefined dihedral parameters for d cph2 nr1 cph1 cph1 MDIO ERROR: warning: redefined dihedral parameters for d cph2 nr2 cph1 cph1 MDIO ERROR: warning: redefined dihedral parameters for d nr1 cph1 cph1 hr3 MDIO ERROR: warning: redefined dihedral parameters for d nr1 cph2 nr2 cph1 MDIO ERROR: warning: redefined dihedral parameters for d nr2 cph1 cph1 nr1 MDIO ERROR: warning: redefined dihedral parameters for d nr2 cph2 nr1 cph1 MDIO ERROR: warning: redefined dihedral parameters for d hr1 cph2 nr1 cph1 MDIO ERROR: warning: redefined dihedral parameters for d hr1 cph2 nr2 cph1 MDIO ERROR: warning: redefined dihedral parameters for d hr3 cph1 cph1 hr3 MDIO ERROR: warning: redefined dihedral parameters for d hr3 cph1 nr1 cph2 MDIO ERROR: warning: redefined dihedral parameters for d hr3 cph1 nr2 cph2 MDIO ERROR: warning: redefined dihedral parameters for d nr2 cph1 cph1 hr3 MDIO ERROR: warning: redefined improper parameters for i hr1 nr1 nr2 cph2 MDIO ERROR: warning: redefined improper parameters for i hr1 nr2 nr1 cph2 MDIO ERROR: warning: redefined improper parameters for i hr3 cph1 nr1 cph1 MDIO ERROR: warning: redefined improper parameters for i hr3 cph1 nr2 cph1 MDIO ERROR: warning: redefined improper parameters for i hr3 nr1 cph1 cph1 MDIO ERROR: warning: redefined improper parameters for i hr3 nr2 cph1 cph1 MDIO ERROR: cannot open file "restart.coor" ERROR: file deven.cpp line 879: # Energies have become nan called boinc_finish </stderr_txt> ]]> Validate state Invalid Claimed credit 38584.7222222222 Granted credit 0 application version Long runs (8-12 hours on fastest card) v6.13 (cuda31) I have since gone back the 266.58 and had no issues. Cheers Ross*
5) Message boards : Graphics cards (GPUs) : check sum and signature errors (Message 20743) Posted 21 Mar 2011 by Ross* Post: Hi Thanks for the info, Tried your suggestions, so far so good. Reseting the project just lossed 8 hrs of crunching [my fault ] Just a little concerned I have 10 Wus working/ready to run at this time but 14 in progress on the website. Can I delete those that are now on my active list? Cheers Ross*
6) Message boards : Graphics cards (GPUs) : check sum and signature errors (Message 20723) Posted 19 Mar 2011 by Ross* Post: Hi after about a week of no errors re downloading I have had 9 in the last 2 days. All are <core_client_version>6.10.58</core_client_version> <![CDATA[ <message> WU download error: couldn't get input files: <file_xfer_error> <file_name>p34-IBUCH_7_mutEGFR_110315-1-p34-IBUCH_7_mutEGFR_110315-0-10-RND5046_3</file_name> <error_code>-119</error_code> <error_message>MD5 check failed</error_message> </file_xfer_error> all are on my Vista 64 boxes so far. I have rebooted both boxes this morning to see if that makes a difference, but there are all on the same network and there all running on NV 266.58 GTX 580s Is there any other settings that I need to look at? Cheers Ross*
7) Message boards : Number crunching : New acemdlong workunits (Message 20635) Posted 8 Mar 2011 by Ross* Post: [ I've sent a batch of 700 WUs named "AB", which should be 8-12h on the fastest cards] Hi When can I get some more? 17000sec for 11k credits standard, 27000secs for the long [7.5hrs] for the long ones 57k credits. I love them. Cheers Ross
8) Message boards : Graphics cards (GPUs) : check sum and signature errors (Message 20628) Posted 7 Mar 2011 by Ross* Post: You have 2 tasks in progress now. Did you upgrade from Vista to Win7? Hi same box running Win7 home 64 i7980x chip with 1 GTX 580 running at stock that I have been using for the last 6 months. Was running Nvidia 266.37beta but I downloaded 266.58 today. Seems to have fixed the problem ???? I have had 12 failed downloads and one error a couple of mintes after start. I will be montioring the next 24 hrs to see if I get any more. If I get more I will consder going back to older drivers. Cheers Ross*
9) Message boards : Graphics cards (GPUs) : check sum and signature errors (Message 20626) Posted 7 Mar 2011 by Ross* Post: 07/03/2011 1:51:23 p.m. GPUGRID [error] MD5 check failed for F270-TONI_KKAL2-12-F270-TONI_KKAL2-11-100-RND9694_3 07/03/2011 1:51:23 p.m. GPUGRID [error] expected 78ae4b727ac681841c20a8edc19bf5f5, got 872e47a2b17f9baf4680fd91cb89aba5 07/03/2011 1:51:23 p.m. GPUGRID [error] Checksum or signature error for F270-TONI_KKAL2-12-F270-TONI_KKAL2-11-100-RND9694_3 Hi have tried serveral times to get new WUs but only get these that fail. No long run WUs available Cheers Ross*
10) Message boards : Graphics cards (GPUs) : New nvidia beta application (Message 14892) Posted 1 Feb 2010 by Ross* Post: [Within 2 months 6core systems with 12 threads will be available. You will even be able to get dual socket versions. Look to the future, it has dense core populations with multithreading being the norm.] Hi to add to this debate. I have 2 i7 920 boxes with a ATI 5970 each plus running WCGrid on 8 threads each as well. Whatever is planned, my view is that the app should be able to run the GPU apps with a CPU app running as well, without any micro management. I will be running 6 core CPUs in a couple of months hopefully with a new nivida GPU card. I agree with the use of preferences to fine tune how the box manages its resources. My future is to 2 gulftowns per MB and 2 double GPUs per box. Cheers Ross, New Zealand
11) Message boards : Graphics cards (GPUs) : GPUGRID and ATI (Message 13777) Posted 3 Dec 2009 by Ross* Post: We are working on the optimization now. We will not put the application out until it delivers what a 5870 should deliver in terms of performance. Be patient. gdf Great, I will be patient! Ross
12) Message boards : Graphics cards (GPUs) : GPUGRID and ATI (Message 13755) Posted 2 Dec 2009 by Ross* Post: We could not find a 5870, but we got a 5850 that should be good enough. I have just installed now, removing the old 8800gt. gdf I find this interesting that in the USA there is no ATI 5800/5900 GPUs Even in far distant New Zealand I can get ATI 5970 in 3 days. I would love to crunch GPUGRID again but had to give up with a 295. I am cruching Collatz now because a 5790 can rip though the WUs 2 every 7 mins. So come get a optiz - app for ATI cards . You are missing out on so much Computer Power Ross
13) Message boards : Graphics cards (GPUs) : Video Card Longevity (Message 11466) Posted 29 Jul 2009 by Ross* Post: Hi that WU is not showing up in my tasks list . it and other were the cause of all the problems early this week . has July 30th expire date on it. normaly I can crunch a WU in 7.5 hrs but now takes 9hrs. As it does not show up in tasks how do I abort or kill it? Thanks Ross my 295 freaks at over 73c smartdoctor alarm goes off new fan etc using good airflow Ross
14) Message boards : Graphics cards (GPUs) : Video Card Longevity (Message 11461) Posted 29 Jul 2009 by Ross* Post: A question to you I have a inprogress WU 19-KASHIF_HIVPR_dim_ba4-28-100-RND7953_0 running but not in my tasks. How do i get rid of it ? It is putting strain on my 295 to the extent that I have had to go back to 1 WU at a time. tempertures have going over 65C Thanks Ross
15) Message boards : Server and website : http error with HIV workunits (Message 11373) Posted 27 Jul 2009 by Ross* Post: have 2 WUS almosted completed test will be when they are replaced hopefully the Ge Fouce will conqueror Cheers Ross
16) Message boards : Server and website : http error with HIV workunits (Message 11363) Posted 27 Jul 2009 by Ross* Post: We'll try to cancel them server-side asap, thanks for your patience. I also have had 20 WUs errors in download , stuck in mid download , error in computation E.T.C Typical of is below 27/07/2009 10:44:29 a.m. GPUGRID Finished download of 91-KASHIF_HIVPR_sub_so_ba1-5-91-KASHIF_HIVPR_sub_so_ba1-4-100-RND7343_2 27/07/2009 10:44:29 a.m. GPUGRID Started download of 91-KASHIF_HIVPR_sub_so_ba1-5-91-KASHIF_HIVPR_sub_so_ba1-4-100-RND7343_3 27/07/2009 10:45:17 a.m. GPUGRID Finished download of 91-KASHIF_HIVPR_sub_so_ba1-5-91-KASHIF_HIVPR_sub_so_ba1-4-100-RND7343_3 27/07/2009 10:45:17 a.m. GPUGRID Started download of 91-KASHIF_HIVPR_sub_so_ba1-5-pdb_file 27/07/2009 10:46:44 a.m. GPUGRID Finished download of 77-GIANNI_BINDX119-29-par_file 27/07/2009 10:46:44 a.m. GPUGRID Started download of 91-KASHIF_HIVPR_sub_so_ba1-5-psf_file 27/07/2009 10:46:44 a.m. GPUGRID [error] MD5 check failed for 77-GIANNI_BINDX119-29-par_file 27/07/2009 10:46:44 a.m. GPUGRID [error] expected c2605a4451ad8240f29215f84cb6de7e, got d8298542b27b3e9c7a3396c23444223c 27/07/2009 10:46:44 a.m. GPUGRID [error] Checksum or signature error for 77-GIANNI_BINDX119-29-par_file plus other strange behavoiur. is it all sorted out now? Ross
17) Message boards : Number crunching : ATI GPUs (Message 10910) Posted 29 Jun 2009 by Ross* Post: I have 2 computers qx9650 with a 295 doing GPUGRD i7 920 with a ATI 4870x2 doing MW I avg 20000 a day with GPUGRD I am now avg 50000 a day with Milkyway I was only doing 4000 a day till I started using the new Gipsel 0.19f code with the ATI card I HAVE READ a lot about the diffences between the cards but is it not time someone though about doing some pararall programming. The MW jobs were taking 1 to 2 hrs now are taking 2 to 3 mins I hear a lot about the No of shaders per card but if you read below perhaps ATI ?? cards may have a case. <core_client_version>6.6.36</core_client_version> <![CDATA[ <stderr_txt> Running Milkyway@home ATI GPU application version 0.19f by Gipsel CPU: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz (8 cores/threads) 3.39998 GHz (392ms) CAL Runtime: 1.4.317 Found 2 CAL devices Device 0: ATI Radeon HD 4800 (RV770) 1024 MB local RAM (remote 2047 MB cached + 2047 MB uncached) GPU core clock: 750 MHz, memory clock: 900 MHz 800 shader units organized in 10 SIMDs with 16 VLIW units (5-issue), wavefront size 64 threads supporting double precision Device 1: ATI Radeon HD 4800 (RV770) 1024 MB local RAM (remote 2047 MB cached + 2047 MB uncached) GPU core clock: 750 MHz, memory clock: 900 MHz 800 shader units organized in 10 SIMDs with 16 VLIW units (5-issue), wavefront size 64 threads supporting double precision 0 WUs already running on GPU 0 0 WUs already running on GPU 1 Starting WU on GPU 0 main integral, 320 iterations predicted runtime per iteration is 191 ms (33.3333 ms are allowed), dividing each iteration in 6 parts borders of the domains at 0 272 536 800 1072 1336 1600 Calculated about 9.89542e+012 floatingpoint ops on GPU, 1.23583e+008 on FPU. Approximate GPU time 106.189 seconds. probability calculation (stars) Calculated about 3.05993e+009 floatingpoint ops on FPU. WU completed. CPU time: 4.61763 seconds, GPU time: 106.189 seconds, wall clock time: 323.25 seconds, CPU frequency: 3.4 GHz
18) Message boards : Graphics cards (GPUs) : nVidia WHQL 186.18 drivers available (Message 10819) Posted 24 Jun 2009 by Ross* Post: [quote][quote]got it the day it came out, no problems once so ever... Be warned will kill any WUs that are in progress ever if manager is turned off. Ross can't any new WUs at this time claims work request to big will moniter developments and if nessceary go back to old driver. Just a thought has anyone done a system restore to before the change of drivers? Ross
19) Message boards : Graphics cards (GPUs) : nVidia WHQL 186.18 drivers available (Message 10818) Posted 24 Jun 2009 by Ross* Post: got it the day it came out, no problems once so ever... Be warned will kill any WUs that are in progress ever if manager is turned off. Ross
20) Message boards : Number crunching : The influence of the CPU (Message 10750) Posted 21 Jun 2009 by Ross* Post: Point taken So do i7 machines e.g 920s only show up as 2.67 not what they are OC too? next week my i7 920 arrives OC to 3.4 but will have a 4870x2 so I mostly will be doing Milkyway@home or folding@home with that. It will be interesting to see who runs the first ASUS Mars 295 and the results they get. Thanks

Next 20