Dear all, please give the new acemdbeta app, ver 845, a work out. This supports all GPUs now.
It's Windows only - if you don't get WUs, you'll need to update your driver.

Matt

Matt, is the 343.98 Driver accepted? I've been trying to get Beta tasks. 14/09/29 06:12:36 | GPUGRID | No tasks are available for ACEMD beta version

I have correct configure-- /run testing app/Beta app checked, not accepting other short or long. I never update to WHQL drivers, from being limited for certain functional areas, unlike Betas or Developer Driver.

Huh, yes. You should be getting something...
According to the logs your host #159309 got given work at 12:15 CEST.

14/09/29 06:48:02 | GPUGRID | No tasks are available for ACEMD beta version

Strange, I see no Beta tasks running on Boinc Manager. I just tried again. If driver is accepted, I will continue to try. Thanks for the help.

14/09/29 06:50:55 | GPUGRID | No tasks are available for ACEMD beta version

*Now* you should get something..

I did, indeed.

Update: unknown error) - exit code -97 (0xffffff9f)after 8s

The simulation has become unstable. Terminating to avoid lock-up (1)(this first time I've had this during my time at GPUGRID. GPU1 Temp was 58C.
If you don't mind errors, I will try again.

Update2: same error. GPU usage go's to 90% for seconds, after GPU usage to 0% then crashes.

On the first test unit, I got an error.

9/29/2014 7:13:41 AM | GPUGRID | Computation for task 21-MJHARVEY_TEST4000-0-10-RND0794_0 finished
9/29/2014 7:13:41 AM | GPUGRID | Output file 21-MJHARVEY_TEST4000-0-10-RND0794_0_1 for task 21-MJHARVEY_TEST4000-0-10-RND0794_0 absent
9/29/2014 7:13:41 AM | GPUGRID | Output file 21-MJHARVEY_TEST4000-0-10-RND0794_0_2 for task 21-MJHARVEY_TEST4000-0-10-RND0794_0 absent
9/29/2014 7:13:41 AM | GPUGRID | Output file 21-MJHARVEY_TEST4000-0-10-RND0794_0_3 for task 21-MJHARVEY_TEST4000-0-10-RND0794_0 absent



Name 21-MJHARVEY_TEST4000-0-10-RND0794_0
Workunit 10123268
Created 29 Sep 2014 | 9:50:11 UTC
Sent 29 Sep 2014 | 11:10:35 UTC
Received 29 Sep 2014 | 11:13:11 UTC
Server state Over
Outcome Computation error
Client state Compute error
Exit status -97 (0xffffffffffffff9f) Unknown error number
Computer ID 127986
Report deadline 4 Oct 2014 | 11:10:35 UTC
Run time 4.10
CPU time 3.48
Validate state Invalid
Credit 0.00
Application version ACEMD beta version v8.45 (cuda65)
Stderr output
<core_client_version>7.2.42</core_client_version>
<![CDATA[
<message>
(unknown error) - exit code -97 (0xffffff9f)
</message>
<stderr_txt>
# GPU [GeForce GTX 690] Platform [Windows] Rev [3212] VERSION [65]
# SWAN Device 2 :
# Name : GeForce GTX 690
# ECC : Disabled
# Global mem : 2048MB
# Capability : 3.0
# PCI ID : 0000:07:00.0
# Device clock : 1019MHz
# Memory clock : 3004MHz
# Memory width : 256bit
# Driver version : r343_98 : 34411
# GPU 0 : 67C
# GPU 1 : 42C
# GPU 2 : 69C
# GPU 3 : 70C
# The simulation has become unstable. Terminating to avoid lock-up (1)

</stderr_txt>
]]>

Update#3 I've received 5 Beta tasks- all have failed, but two caused a system hang ( no error files).

FATAL : Cuda driver error 702 in file 'swanlibnv2.cpp' in line 1965/ Simulation unstable. Flag 11 value 1
# The simulation has become unstable. Terminating to avoid lock-up
# The simulation has become unstable. Terminating to avoid lock-up (2)

Simulation unstable. Flag 11 value 1
# The simulation has become unstable. Terminating to avoid lock-up
# The simulation has become unstable. Terminating to avoid lock-up (2)

Update#4 Still failing on both cards with same error--

(unknown error) - exit code -97 (0xffffff9f)


[url] http://www.gpugrid.net/workunit.php?wuid=10099983 [/url]

This work unit has 3 Linux failures (all with GTX 780) and 2 Win8.1 failures.

Update#5 received 5 more beta for total of ten-- all failed with same error number. All Tasks have started fine (90+GPUusage/14%MCU) with progress .016 intervals, before failing. Wingman with Tesla K20c/GTX780 (c.c3.5, along C.C3.0 wingman, failed also.

Yes, looks like CUDA65 is bad on everything but GM204s. Ho hum.

-97 error here, on my GTX 460
# Simulation unstable. Flag 11 value 1
# The simulation has become unstable. Terminating to avoid lock-up
# The simulation has become unstable. Terminating to avoid lock-up (2)

=========================

http://www.gpugrid.net/result.php?resultid=13149151
Name 43-MJHARVEY_TEST1999-1-10-RND5744_2
Workunit 10123176
Created 29 Sep 2014 | 11:40:28 UTC
Sent 29 Sep 2014 | 12:54:10 UTC
Received 29 Sep 2014 | 13:17:01 UTC
Server state Over
Outcome Computation error
Client state Compute error
Exit status -97 (0xffffffffffffff9f) Unknown error number
Computer ID 153764
Report deadline 4 Oct 2014 | 12:54:10 UTC
Run time 2.56
CPU time 0.00
Validate state Invalid
Credit 0.00
Application version ACEMD beta version v8.45 (cuda65)
Stderr output

<core_client_version>7.4.22</core_client_version>
<![CDATA[
<message>
(unknown error) - exit code -97 (0xffffff9f)
</message>
<stderr_txt>
# GPU [GeForce GTX 460] Platform [Windows] Rev [3212] VERSION [65]
# SWAN Device 1 :
# Name : GeForce GTX 460
# ECC : Disabled
# Global mem : 1024MB
# Capability : 2.1
# PCI ID : 0000:07:00.0
# Device clock : 1526MHz
# Memory clock : 1900MHz
# Memory width : 256bit
# Driver version : r343_98 : 34411
# Simulation unstable. Flag 11 value 1
# The simulation has become unstable. Terminating to avoid lock-up
# The simulation has become unstable. Terminating to avoid lock-up (2)

</stderr_txt>
]]>

Yikes, I'm seeing these same errors on the Short Run queue -- I guess the Cuda65 app has been deployed there too?

It was on acemdshort briefly. It is no longer.

Matt

14/09/29 09:48:39 | GPUGRID | No tasks are available for ACEMD beta version

Has beta app been pulled for non-C.C 5.2 cards?

Has beta app been pulled for non-C.C 5.2 cards?

Yes, it's served its purpose there. The CUDA65 build is broken on non-5.2

Matt

846 on acemdbeta now. CUDA65 for sm 3.0 and higher.

Matt

My 2 GTX 660 Tis, and my GTX 460, in my main rig, are now successfully simultaneously crunching 3 ACEMD beta version 8.46 (cuda65) tasks.

Thank you!

So far, so good. .004% progress intervals-- 1.000% in four minutes. 24,000s est. time to complete.

Matt:

I even think the canary behavior works better for me now. I tried the scenario where it was failing on the 8.41 app, and now it worked fine without failure on the 8.46 beta app.

Can you please explain, in detail, how the canary behavior was changed? How exactly does behave in 8.46?

Thanks,
Jacob

Running fine after 25 minutes on a GTX 650 Ti. It will complete in 3 hours 16 minutes (344.11 driver, Win7 64-bit).

It completed OK on the GTX 650 Ti, but seems to be causing problems on some higher-end cards. But their versions of ACEMD probably have more changes than the one I got (8.46).
http://www.gpugrid.net/workunit.php?wuid=10123336

I will be trying my GTX 660 Ti next on the same machine to see what happens.