Message boards : Graphics cards (GPUs) : New beta 6.22 for Windows (Fermi too)
Author | Message |
---|---|
We have tested locally and this version works for us. | |
ID: 16079 | Rating: 0 | rate: / Reply Quote | |
We have tested locally and this version works for us. Picked up 3 tonight. 2 out of 3 crashed after about 15 seconds. Third is still going. SWAN : FATAL : Failure executing kernel [mshake_position_kernel_1] [2] [10,1,1][64,1,1] Assertion failed: 0, file swanlib_nv.cpp, line 281 1st wu 2nd wu Both gave a windows pop-up saying task has stopped responding. BOINC 6.10.43, Win7 x64, Driver 196.21 ____________ BOINC blog | |
ID: 16082 | Rating: 0 | rate: / Reply Quote | |
Tried to crunch two tasks: <core_client_version>6.10.36</core_client_version> <![CDATA[ <message> The system cannot find the path specified. (0x3) - exit code 3 (0x3) </message> <stderr_txt> # Using device 0 # There is 1 device supporting CUDA # Device 0: "GeForce GTX 260" # Clock rate: 1.24 GHz # Total amount of global memory: 939196416 bytes # Number of multiprocessors: 27 # Number of cores: 216 MDIO ERROR: cannot open file "restart.coor" SWAN : FATAL : Failure executing kernel sync [reduce_kernel4] [702] Assertion failed: 0, file swanlib_nv.cpp, line 121 This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. </stderr_txt> ]]> 2. Host ID 38345 - Win XP x86, 9600 GT, driver 19562, a little OCed. No problem when crunchig 6.03 tasks. The task errored out after 230s. <core_client_version>6.10.18</core_client_version> <![CDATA[ <stderr_txt> # Using device 0 # There is 1 device supporting CUDA # Device 0: "GeForce 9600 GT" # Clock rate: 1.62 GHz # Total amount of global memory: 536543232 bytes # Number of multiprocessors: 8 # Number of cores: 64 MDIO ERROR: cannot open file "restart.coor" # Time per step (avg over 5000 steps): 45.297 ms # Approximate elapsed time for entire WU: 226.484 s called boinc_finish </stderr_txt> ]]> | |
ID: 16086 | Rating: 0 | rate: / Reply Quote | |
Tried to crunch two tasks: | |
ID: 16087 | Rating: 0 | rate: / Reply Quote | |
You are right GDF, claimed 18.73, granted 28.09 for 280s elapsed time. Very high credit for 9600 GT, nice. | |
ID: 16088 | Rating: 0 | rate: / Reply Quote | |
Picked up 3 tonight. 2 out of 3 crashed after about 15 seconds. Third is still going. Third one completed successfully. Link is here ____________ BOINC blog | |
ID: 16090 | Rating: 0 | rate: / Reply Quote | |
For what it's worth, | |
ID: 16091 | Rating: 0 | rate: / Reply Quote | |
1st beta 6.22 WU completed. ^^ | |
ID: 16092 | Rating: 0 | rate: / Reply Quote | |
cuda30 version is also out now. This should work on Fermi. | |
ID: 16094 | Rating: 0 | rate: / Reply Quote | |
Success. | |
ID: 16096 | Rating: 0 | rate: / Reply Quote | |
6.22 cuda 3.0 erroed out (both GTX260 and 9600GT). <core_client_version>6.10.18</core_client_version> <![CDATA[ <message> Incorrect function. (0x1) - exit code 1 (0x1) </message> <stderr_txt> # Using device 0 # There is 1 device supporting CUDA # Device 0: "GeForce GTX 260" # Clock rate: 1.24 GHz # Total amount of global memory: 939196416 bytes # Number of multiprocessors: 27 # Number of cores: 216 MDIO ERROR: cannot open file "restart.coor" </stderr_txt> ]]> ID 38345 <core_client_version>6.10.18</core_client_version> <![CDATA[ <message> - exit code -40 (0xffffffd8) </message> <stderr_txt> # Using device 0 # There is 1 device supporting CUDA # Device 0: "GeForce 9600 GT" # Clock rate: 1.62 GHz # Total amount of global memory: 536543232 bytes # Number of multiprocessors: 8 # Number of cores: 64 SWAN : Module load result [.fastfill.cu.] [200] SWAN: FATAL : Module load failed </stderr_txt> ]]> | |
ID: 16097 | Rating: 0 | rate: / Reply Quote | |
nenym wrote: 6.22 cuda 3.0 erroed out (both GTX260 and 9600GT). 6.22 cuda 3.0 works fine on GTX260 now, wow. The first task finished on my weird GTX260 after updating from 181.xx drivers. | |
ID: 16098 | Rating: 0 | rate: / Reply Quote | |
After updating 9600GT drivers to WHQL 197.13 6.22 cuda 3.0 runs fine. | |
ID: 16099 | Rating: 0 | rate: / Reply Quote | |
What's the oldest driver required for the CUDA 3.0 app? | |
ID: 16100 | Rating: 0 | rate: / Reply Quote | |
It gets shipped only if you have 197.13. | |
ID: 16101 | Rating: 0 | rate: / Reply Quote | |
6.22 cuda and cuda3.0 works fine although I'd like to test cuda3.0 on a full blown WU (not the shorties). | |
ID: 16106 | Rating: 0 | rate: / Reply Quote | |
It gets shipped only if you have 197.13. Cuda toolkit 3 was supported from 195.62 drivers onwards. You could give the cuda 3 DLL's to machines with this or later. ____________ BOINC blog | |
ID: 16108 | Rating: 0 | rate: / Reply Quote | |
Just finished my 1 WU | |
ID: 16114 | Rating: 0 | rate: / Reply Quote | |
It gets shipped only if you have 197.13. This is not correct. My computer downloaded 2 of these units and I am running version 195.62. They both crashed after about 2 seconds. | |
ID: 16123 | Rating: 0 | rate: / Reply Quote | |
It gets shipped only if you have 197.13. If you read a couple of posts further up I mentioned that according to to nvidia 195.62 supports cuda toolkit 3. Its likely the guys changed it so we get the the cuda 3 DLL's and beta app. It may be that the latest cuda 3 toolkit doesn't work properly with 195.62, but it may with later drivers. I have 196 drivers, but haven't picked up any beta work since the cuda 3 version came out. I will see if I can get one. Its also possible its a bug with the beta app and nothing to do with the driver version. ____________ BOINC blog | |
ID: 16125 | Rating: 0 | rate: / Reply Quote | |
4 success and 2 failed on cuda30 2087571 1314084 2 Apr 2010 9:37:39 UTC 2 Apr 2010 15:34:03 UTC Completed and validated 1,108.61 164.94 187.28 280.92 ACEMD beta version v6.22 (cuda30) ____________ | |
ID: 16141 | Rating: 0 | rate: / Reply Quote | |
In the last 2 days I've had 12 failures against 12 successes. All using 197.13 driver. | |
ID: 16142 | Rating: 0 | rate: / Reply Quote | |
Updated drivers on one machine to 197.13 and managed to get one 6.22 beta which promptly crashed. Link to wu is here | |
ID: 16143 | Rating: 0 | rate: / Reply Quote | |
WU 1314836 died on my Intel quad/GTS250 after 2.39sec ET. I notice it had already crashed on 3 other hosts. Maybe not quite ready for prime time;) | |
ID: 16153 | Rating: 0 | rate: / Reply Quote | |
Updated drivers on one machine to 197.13 and managed to get one 6.22 beta which promptly crashed. Link to wu is here Make that 2 crashed straight away. Link to 2nd wu is here Card is a GTX275. ____________ BOINC blog | |
ID: 16155 | Rating: 0 | rate: / Reply Quote | |
Got another one that also died immediately. Different machine this time. Everybody who has received it has bombed out too. Link to wu is here | |
ID: 16157 | Rating: 0 | rate: / Reply Quote | |
I removed the CUDA3 application. Let's see if it's just the problem of CUDA3 not being ready. The CUDA2 application should be working as before. | |
ID: 16158 | Rating: 0 | rate: / Reply Quote | |
If all goes well would we see 3 plan classes (cuda,cuda23,cuda30)? maybe 2? | |
ID: 16181 | Rating: 0 | rate: / Reply Quote | |
No errors here, running cuda2. | |
ID: 16200 | Rating: 0 | rate: / Reply Quote | |
Two just completed without error. | |
ID: 16216 | Rating: 0 | rate: / Reply Quote | |
I think I did 30 WUs with Completed and validated, 7 WUs with Error while computing but most of them were under a few seconds. The beta application runs pretty smooth, only thing is if I restart boinc while it processes an WU, the WU restarts. Apart from that, it's stable. | |
ID: 16232 | Rating: 0 | rate: / Reply Quote | |
I think I did 30 WUs with Completed and validated, 7 WUs with Error while computing but most of them were under a few seconds. The beta application runs pretty smooth, only thing is if I restart boinc while it processes an WU, the WU restarts. Apart from that, it's stable. Yes, there is a small mistake in the WU itself. I think that next week we may deploy the beta application as the normal application. gdf | |
ID: 16233 | Rating: 0 | rate: / Reply Quote | |
I have had 2 and both errored and everyone else who did these units also errored. | |
ID: 16235 | Rating: 0 | rate: / Reply Quote | |
Does the ACEMD beta version v6.22 (cuda) application crunch the same WU as the ACEMD - GPU molecular dynamics v6.03 (cuda) application? That would be a powerful speedup. | |
ID: 16246 | Rating: 0 | rate: / Reply Quote | |
Received yesterday evening 1 WU (1350013). No errors - time 9 min 43 sec. | |
ID: 16248 | Rating: 0 | rate: / Reply Quote | |
Today's test was a success (5 WU) without a hitch. | |
ID: 16293 | Rating: 0 | rate: / Reply Quote | |
Received yesterday evening 1 WU (1350013). No errors - time 9 min 43 sec. Yes, they are small, just for testing. gdf | |
ID: 16295 | Rating: 0 | rate: / Reply Quote | |
Did 4 today. 2 failed. Everybody else who got the 1st failure wu also crashed. Link to 1st wu here | |
ID: 16297 | Rating: 0 | rate: / Reply Quote | |
Would love to be able to test my fermi cards on linux. nudge nudge. | |
ID: 16318 | Rating: 0 | rate: / Reply Quote | |
Message boards : Graphics cards (GPUs) : New beta 6.22 for Windows (Fermi too)