Message boards :
Number crunching :
Problem with AstroPulse v7
Message board moderation
Author | Message |
---|---|
IAN FRAIGUN Send message Joined: 24 Oct 12 Posts: 9 Credit: 6,907,275 RAC: 1 |
I am having an issue with Astro Pulse V7 7.04 tasks. I keep getting them downloaded, but always show them with properties stating Scheduler Wait: unsupported Open CL Runtime. I do not have any issues with V6 tasks and am currently running BOINC V7.2.42. What do I need to due to get these tasks to run. I have had to abort about 60 already as they seem to start, run for about 1-5 seconds then go back to a ready to start status. Appreciate Any Help. Ian Fraigun |
Wedge009 Send message Joined: 3 Apr 99 Posts: 451 Credit: 431,396,357 RAC: 553 |
It looks like quite a few users are encountering this issue with the switch to APv7. The most common recommendation I've seen is to update the Catalyst software. It looks to me as though you're using Catalyst 12.4. I should think the most recent release still supports HD 5000 series cards. Soli Deo Gloria |
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121 |
Version: OpenCL 1.1 AMD-APP-SDK-v2.5 (732.1) Upgrade your ATi drivers. Preferably with clean install. Cause you could have mixture of components from different Catalyst packs currently. |
HAL9000 Send message Joined: 11 Sep 99 Posts: 6534 Credit: 196,805,888 RAC: 57 |
The use of Display Driver Uninstaller to clean the current driver & SDK from your system would be a good idea. Then either Catalyst 14.9 or Catalyst 14.4 would probably be a good choice for your system. SETI@home classic workunits: 93,865 CPU time: 863,447 hours Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[ |
Wedge009 Send message Joined: 3 Apr 99 Posts: 451 Credit: 431,396,357 RAC: 553 |
No need to contact me privately for this, Ian. You look like you're using Win7, so this would be the most recent Catalyst release for that set-up. Soli Deo Gloria |
betreger Send message Joined: 29 Jun 99 Posts: 11361 Credit: 29,581,041 RAC: 66 |
since installing AP v7 on my very old XP box I have had these APs time out, very weird. 3782686765 1615604402 13 Oct 2014, 22:13:46 UTC 14 Oct 2014, 23:12:34 UTC Timed out - no response 0.00 0.00 --- SETI@home v7 Anonymous platform (NVIDIA GPU) 3782510914 1615520678 13 Oct 2014, 20:04:02 UTC 14 Oct 2014, 23:12:34 UTC Timed out - no response 0.00 0.00 --- SETI@home v7 Anonymous platform (NVIDIA GPU) 3782436162 1615485492 13 Oct 2014, 19:07:09 UTC 14 Oct 2014, 23:12:34 UTC Timed out - no response 0.00 0.00 --- SETI@home v7 Anonymous platform (NVIDIA GPU) 3782311098 1615425861 13 Oct 2014, 17:35:09 UTC 14 Oct 2014, 23:12:33 UTC Timed out - no response 0.00 0.00 --- SETI@home v7 Anonymous platform (NVIDIA GPU) 3780031044 1594754332 13 Oct 2014, 16:19:00 UTC 13 Oct 2014, 16:29:50 UTC Timed out - no response 0.00 0.00 --- AstroPulse v6 v6.04 (opencl_nvidia_100) 3780031052 1594754330 13 Oct 2014, 16:19:00 UTC 13 Oct 2014, 16:29:50 UTC Timed out - no response 0.00 0.00 --- AstroPulse v6 v6.04 (opencl_nvidia_100) 3777523676 1601539989 13 Oct 2014, 16:19:00 UTC 13 Oct 2014, 16:29:50 UTC Timed out - no response 0.00 0.00 --- AstroPulse v6 v6.04 (opencl_nvidia_100) 3777524700 1603337563 13 Oct 2014, 16:19:00 UTC 13 Oct 2014, 16:29:50 UTC Timed out - no response 0.00 0.00 --- AstroPulse v6 v6.04 (opencl_nvidia_100) 3777523677 1601963163 13 Oct 2014, 16:19:00 UTC 13 Oct 2014, 16:29:50 UTC Timed out - no response 0.00 0.00 --- AstroPulse v6 v6.04 (opencl_nvidia_100 |
Josef W. Segur Send message Joined: 30 Oct 99 Posts: 4504 Credit: 1,414,761 RAC: 0 |
since installing AP v7 on my very old XP box I have had these APs time out, very weird. Forced expiration by the "Resend lost tasks" mechanism is sometimes nearly impossible to figure out, but both the 5 stock AstroPulse v6 v6.04 (opencl_nvidia_100) tasks and 4 Anonymous platform (NVIDIA GPU) tasks show the early timeouts which indicate that's the cause. AP has nothing like the special .vlar exclusion, but still if the Scheduler tries to assign lost AP work to CPU it's quite likely the estimated completion would be past the deadline and not get sent on that basis. Joe |
betreger Send message Joined: 29 Jun 99 Posts: 11361 Credit: 29,581,041 RAC: 66 |
Well the old box seems to be running normally now so no harm done. |
Jim Wilkins Send message Joined: 11 Oct 99 Posts: 70 Credit: 1,658,376 RAC: 0 |
All of my AP7 Nvidia GPU WUs are failing on my iMac? How to diagnose this? Thanks, Jim |
Zalster Send message Joined: 27 May 99 Posts: 5517 Credit: 528,817,460 RAC: 242 |
There is a problem with the initial estimated time to complete that causes the NV app to error out with Exceeded Time. It is discussed here http://setiathome.berkeley.edu/forum_thread.php?id=75865&postid=1586389 and in 2 other threads. The most important thread is Raistmer's thread on APv7-related issues and errors here in Number Crunching where TBar describes the fix. That thread is linked as well in the above thread that I posted. If you have questions, just ask Zalster |
Jim Wilkins Send message Joined: 11 Oct 99 Posts: 70 Credit: 1,658,376 RAC: 0 |
I'm sorry, I forgot to specify the error. They are all computation errors. Thanks, Jim |
Zalster Send message Joined: 27 May 99 Posts: 5517 Credit: 528,817,460 RAC: 242 |
Jim, All your errors are exceeded time limit errors, you can look at the stderr report and see it listed there. Here is just 1 of all those that Errored. ap_01jl14aa_B6_P0_00029_20141017_02068.wu_0 Workunit 1618602819 Created 17 Oct 2014, 11:13:01 UTC Sent 17 Oct 2014, 13:05:03 UTC Report deadline 11 Nov 2014, 13:05:03 UTC Received 17 Oct 2014, 14:04:04 UTC Server state Over Outcome Computation error Client state Compute error Exit status 197 (0xc5) EXIT_TIME_LIMIT_EXCEEDED Computer ID 7126638 Run time 28 min 22 sec CPU time 4 min 25 sec Validate state Invalid Credit 0.00 Device peak FLOPS 1,207.31 GFLOPS Application version AstroPulse v7 v7.05 (opencl_nvidia_mac) Stderr output <core_client_version>7.2.42</core_client_version> <![CDATA[ <message> Maximum elapsed time exceeded </message> <stderr_txt> Running on device number: 0 OpenCL platform detected: Apple Number of OpenCL devices found : 1 BOINC assigns slot on device #0. Info: BOINC provided OpenCL device ID used DOUBLE_FP supported. cl_khr_fp64 supported. cl_APPLE_fp64_basic_ops supported. FERMI : true Used GPU device parameters are: Number of compute units: 8 Single buffer allocation size: 256MB Total device global memory: 4096MB max WG size: 1024 local mem type: Real FERMI path used: yes -unroll default value used: 8 -ffa_block default value used: 2048 -ffa_block_fetch default value used: 1024 AstroPulse v7.05 Darwin 10.7+ 64 bit, rel. Rev 2709, OpenCL version by Raistmer, GPU mode V7, by Raistmer ported to OS X by Lunatics.kwsn.net team. Build features: Non-graphics OpenCL USE_OPENCL_NV OPENCL_WRITE COMBINED_DECHIRP_KERNEL SMALL_CHIRP_TABLE TWIN_FFA FFTW BLANKIT USE_INCREASED_PRECISION SSE3 64bit System: Darwin x86_64 Kernel: 13.4.0 CPU : Intel(R) Core(TM) i5-4670 CPU @ 3.40GHz GenuineIntel x86, Family 6 Model 60 Stepping 3 Features : FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT PSE36 CLFSH DS ACPI MMX FXSR SSE SSE2 SS HTT TM PBE SSE3 PCLMULQDQ DTES64 MON DSCPL VMX SMX EST TM2 SSSE3 FMA CX16 TPR PDCM SSE4.1 SSE4.2 x2APIC MOVBE POPCNT AES PCID XSAVE OSXSAVE SEGLIM64 TSCTMR AVX1.0 RDRAND F16C Number of OpenCL platforms: 1 OpenCL Platform Name: Apple Number of devices: 1 Max compute units: 8 Max work group size: 1024 Max clock frequency: 784Mhz Max memory allocation: 1073741824 Cache type: None Cache line size: 0 Cache size: 0 Global memory size: 4294967296 Constant buffer size: 65536 Max number of constant args: 9 Local memory type: Scratchpad Local memory size: 49152 Queue properties: Out-of-Order: No Name: GeForce GTX 780M Vendor: NVIDIA Driver version: 8.26.28 310.40.55b01 Version: OpenCL 1.2 Extensions: cl_APPLE_SetMemObjectDestructor cl_APPLE_ContextLoggingFunctions cl_APPLE_clut cl_APPLE_query_kernel_names cl_APPLE_gl_sharing cl_khr_gl_event cl_khr_byte_addressable_store 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_APPLE_fp64_basic_ops cl_khr_fp64 cl_khr_3d_image_writes cl_khr_depth_images cl_khr_gl_depth_images cl_khr_gl_msaa_sharing cl_khr_image2d_from_buffer state.fold_buf_size_short=65536; state.fold_buf_size_long=262144 GPU device sync requested... ...GPU device synched Termination request detected or computations are finished. GPU device synched, exiting... </stderr_txt> ]]> HOME PARTICIPATE ABOUT COMMUNITY ACCOUNT STATISTICS Please read the links provide in previous post. I think they will help you. Zalster |
Jim Wilkins Send message Joined: 11 Oct 99 Posts: 70 Credit: 1,658,376 RAC: 0 |
Thanks... Thanks, Jim |
juan BFP Send message Joined: 16 Mar 07 Posts: 9786 Credit: 572,710,851 RAC: 3,799 |
Get this WU ended on an error after 1 hours 44 min 10 sec of processing time on a 670. http://setiathome.berkeley.edu/result.php?resultid=3792993814 <message> finish file present too long </message> I remember see that error before but at the time was on MB WU before de commode builds. |
Jeff Buck Send message Joined: 11 Feb 00 Posts: 1441 Credit: 148,764,870 RAC: 0 |
Get this WU ended on an error after 1 hours 44 min 10 sec of processing time on a 670. Did BOINC crash, or stop unexpectedly? My most recent thread on this is "Zombie" AP tasks - still alive in AP v7. There are links to 2 earlier threads in there. I just experienced another one this morning also. I'm still putting together the info to add to the thread. |
juan BFP Send message Joined: 16 Mar 07 Posts: 9786 Credit: 572,710,851 RAC: 3,799 |
Get this WU ended on an error after 1 hours 44 min 10 sec of processing time on a 670. No Boinc did not crash or stop, the WU simply crunch for a while (a little more than 1 hr and 44 secs) an the exit with the error pointed, the the next one crunch normaly. Exactly in the same way it´s happening with MB in the past and was solved by the Jason´s commode builds. Please note ´m not saying is the same error just looks like a similar behavior. |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.