AstroPulse V77.10 Task Not Running Correctly

Questions and Answers : GPU applications : AstroPulse V77.10 Task Not Running Correctly
Message board moderation

To post messages, you must log in.

AuthorMessage
James Bradshaw

Send message
Joined: 9 Mar 01
Posts: 11
Credit: 35,457,279
RAC: 238
United States
Message 1760168 - Posted: 29 Jan 2016, 2:08:44 UTC

PC is running two each SETI V88.0 without a problem. Also one each AstroPulse V77.10. However, if SETI files are being processed the AstroPulse file shows suspended because PC is in use. If I suspend both SETI files the AstroPulse shows as running, however, even though elapsed time runs, the percent completed and the estimated remaining time does not change. What have I mangled or should I just drop AstroPulse? Thanks. JB
ID: 1760168 · Report as offensive
Profile BilBg
Volunteer tester
Avatar

Send message
Joined: 27 May 07
Posts: 3720
Credit: 9,385,827
RAC: 0
Bulgaria
Message 1760200 - Posted: 29 Jan 2016, 3:34:12 UTC - in response to Message 1760168.  

You seem to like DDouble NNumbers ;)
There are no SETI V88.0 or AstroPulse V77.10

They are at SETI@home v8 and AstroPulse v7
http://setiathome.berkeley.edu/apps.php

I guess this is the computer:
http://setiathome.berkeley.edu/show_host_detail.php?hostid=7748105

You have now 2 SETI@home v8 tasks for CPU and 1 AstroPulse v7 v7.10 (opencl_nvidia_cc1) task for GPU
http://setiathome.berkeley.edu/results.php?hostid=7748105

1) "suspended because PC is in use" means your Setting is (by default or you set it):
"Suspend GPU computing when computer is in use"
Computing preferences
(but you may feel lag if GPU tasks run while you work or especially if you game or watch videos)

You may also want to set:
"Suspend when non-BOINC CPU usage is above" to 0 (zero)

2) "even though elapsed time runs" - for how long? - wait at least 2-5 minutes (AstroPulse don't update progress often, only every 0.901 %) (also the first ever task will do some additional "work" (compile .cl to .bin files) at start - may take a few minutes)


I really don't understand this: "If I suspend both SETI (CPU) files the AstroPulse (GPU) shows as running"
It should not happen this way - I see no reason
(unless both SETI@home and AstroPulse tasks are for GPU - but on web page I don't see currently for your computer SETI@home for GPU)

Can you check again?
After you now know what runs on CPU and what runs on GPU -
Shown on the "Tasks" tab - columns "Application" and "Status"

https://boinc.berkeley.edu/wiki/Advanced_view#The_Tasks_tab
 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 
ID: 1760200 · Report as offensive
James Bradshaw

Send message
Joined: 9 Mar 01
Posts: 11
Credit: 35,457,279
RAC: 238
United States
Message 1760405 - Posted: 29 Jan 2016, 16:55:01 UTC - in response to Message 1760200.  

Thank you for your response. Sorry about the double numbers. The SETI task display shows, for example, v77.10, not 7.7.10 so I really don't know how to respond to that. The one AstroPulse task (AstroPulse v77.10 (opencl_nvidia_ccl)) I was referring to never went beyond 12.612% complete and has been in the working queue for weeks. Submission deadline is 1/29/2016. The SETI tasks would be completed and submitted and new tasks downloaded, but when SETI tasks were working the AstroPulse task would not work, always showing suspended-computer is in use, regardless of how I set up computer work time. This particular task has been hung up ever since I download SETI@home V8.[/b] Interestingly, NEW AstroPulse tasks downloaded show AstroPulse v 77.03 (sse) are being processed just fine as are SETI@hom v88.00. Because it is obvious the one task will not be completed by today's deadline, I aborted the problem task and now the newly downloaded AstroPulse and SETI tasks are working fine. I am not enough of a tech to give further details why the opencl NVidia ccl task was hung up, but I appreciate your effort to assist me. Perhaps the root cause is my lack of understanding of the difference between running on CPU and/or GPU. Sorry for the bandwidth, but again, thanks. JB
ID: 1760405 · Report as offensive
Profile Jord
Volunteer tester
Avatar

Send message
Joined: 9 Jun 99
Posts: 15183
Credit: 4,362,181
RAC: 3
Netherlands
Message 1760415 - Posted: 29 Jan 2016, 17:16:03 UTC - in response to Message 1760405.  

The SETI task display shows, for example, v77.10, not 7.7.10

https://setiathome.berkeley.edu/results.php?hostid=7748105 and https://setiathome.berkeley.edu/result.php?resultid=4649590685 show:
AstroPulse v7 v7.10 (opencl_nvidia_cc1) 
windows_intelx86

Even in BOINC Manager I bet it says something of the same name, else the project cannot send out the correct applications, as shown numbered on the applications page.
The applications and their numbers showing there aren't added by a human, but by the database.

In your case, you ran an Astropulse version 7, v7.10 and it tried to run on your Nvidia GeForce 9500 GT.
You also have an Astropulse for on the CPU:
AstroPulse v7 v7.03 (sse)
windows_intelx86

ID: 1760415 · Report as offensive
Profile BilBg
Volunteer tester
Avatar

Send message
Joined: 27 May 07
Posts: 3720
Credit: 9,385,827
RAC: 0
Bulgaria
Message 1760548 - Posted: 30 Jan 2016, 3:18:46 UTC - in response to Message 1760405.  

This particular task has been hung up ever since I download SETI@home V8

There is no connection between this AstroPulse v7 v7.10 (opencl_nvidia_cc1) task and that the new SETI@home v8 apps were deployed.
(unless some previously run CUDA SETI@home v8 task left the NVIDIA driver in "bad state" (or even crashed driver?) - reboot computer if needed)


Your "hang" AstroPulse v7 v7.10 (opencl_nvidia_cc1) task:
http://setiathome.berkeley.edu/result.php?resultid=4649590685

ERROR: OpenCL kernel/call 'clEnqueueReadBuffer->CPU_result' call failed (-5) in file ..\..\ap_fold.cpp near line 6766.
Waiting 30 sec before restart...
Running on device number: 0
Priority of worker thread raised successfully
Priority of process adjusted successfully, below normal priority class used
OpenCL platform detected: NVIDIA Corporation
BOINC assigns device 0
Info: BOINC provided OpenCL device ID used
Used GPU device parameters are:
Number of compute units: 4
Single buffer allocation size: 256MB
Total device global memory: 1024MB
max WG size: 512
local mem type: Real
FERMI path used: no
-unroll default value used: 4
-ffa_block default value used: 1024
-ffa_block_fetch default value used: 512

Build features: Non-graphics BLANKIT OpenCL USE_OPENCL_NV TWIN_FFA OCL_ZERO_COPY COMBINED_DECHIRP_KERNEL FFTW USE_INCREASED_PRECISION USE_SSE2 x86
CPUID: Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz

Cache: L1=64K L2=4096K

CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3 SSSE3
### Restart at 11.71 percent.



* I don't know why this ERROR happened or what it means - I may ask the dev to look at this info.
Did you have a driver crash or did you update NVIDIA driver and didn't reboot?


Interestingly, NEW AstroPulse tasks downloaded show AstroPulse v 77.03 (sse) are being processed just fine

This is task sent for the CPU, this task is done by different app (different .exe)
If the tasks are for your GPU they will have NVIDIA or CUDA or OpenCL in ( ) like "(opencl_nvidia_cc1)"


The one AstroPulse task (AstroPulse v77.10 (opencl_nvidia_ccl)) I was referring to ...

If you Copy/Paste (from your tasks web-pages) and not type you will get:
AstroPulse v7 v7.10 (opencl_nvidia_cc1)

"AstroPulse v7" is the user_friendly_name of the app, the real name (used internally) is astropulse_v7
This is name and not number - you may think of it as if it was AstroPulse_Seven

v7.10 is the version_num of the particular app - e.g. if they find a bug in the current .exe and want to deploy new .exe (for the same "AstroPulse v7" tasks) they will need to set this on server to higher number (7.11) so to make the new app Download to your (any) local BOINC
opencl_nvidia_cc1 is the plan_class - list of rules used by server to determine what exact app to send to your GPU/driver combination

You can see all the variants here:
(many apps with different version_num and plan_class can do the same tasks on different Hardware/OS)
http://setiathome.berkeley.edu/apps.php


P.S.
Please write in paragraphs - this raw text is hard to read
 
 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 
ID: 1760548 · Report as offensive
Profile Bernie Vine
Volunteer moderator
Volunteer tester
Avatar

Send message
Joined: 26 May 99
Posts: 9949
Credit: 103,452,613
RAC: 328
United Kingdom
Message 1760647 - Posted: 30 Jan 2016, 8:53:08 UTC

I think the naming confusion results from the way Boinc display the tasks



Whilst there is a space in v7 7.10 and v8 8.00 it is not obvious.

For someone not familiar with things it does look like v77 and v88
ID: 1760647 · Report as offensive
Profile Raistmer
Volunteer developer
Volunteer tester
Avatar

Send message
Joined: 16 Jun 01
Posts: 6324
Credit: 106,370,077
RAC: 121
Russia
Message 1760700 - Posted: 30 Jan 2016, 11:53:12 UTC
Last modified: 30 Jan 2016, 12:00:17 UTC

Well, such (-5) error happens time to time on nvidia hardware indeed.
The reason not well understood but seems the probability of such error increases with longer/bigger chunks of data to be processed.

So, try to play with -unroll N and -ffa_block N options to get rid of it.

EDIT: in cited case error happened in this call:

{//R: use driver inner sync mechanisms and perform sync readback
  clFlush(cq);
  err=clEnqueueReadBuffer(cq, gpu_results,CL_TRUE,0,sizeof(cl_uint),&CPU_result,0, NULL, NULL);OCL_LOG_ERR("clEnqueueReadBuffer->CPU_result");
}

and hence try to change -ffa_block N option. But it such error occurs not too often it can be ignored.
ID: 1760700 · Report as offensive
James Bradshaw

Send message
Joined: 9 Mar 01
Posts: 11
Credit: 35,457,279
RAC: 238
United States
Message 1766235 - Posted: 19 Feb 2016, 4:26:28 UTC - in response to Message 1760700.  

Thank all of you! JB
ID: 1766235 · Report as offensive

Questions and Answers : GPU applications : AstroPulse V77.10 Task Not Running Correctly


 
©2022 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.