Posts by Bernie Vine

101) Message boards : Number crunching : Don't know where it should go? Stick it here! (Message 2004823)
Posted 29 Jul 2019 by Profile Bernie Vine
Post:
Just had a look, I have about 50 of these.

SETI@home	8.20 setiathome_v8 (opencl_nvidia_SoG)	blc32_2bit_guppi_58643_47587_HIP14472_0014.6284.818.24.47.81.vlar_1	- (-)	0.00	0.000	00:00:54	19/09/2019 11:41:31	0.04C + 1NV	Ready to start, Project suspended	BAV--LT	
SETI@home	8.20 setiathome_v8 (opencl_nvidia_SoG)	blc32_2bit_guppi_58643_47587_HIP14472_0014.6293.818.24.47.226.vlar_0	- (-)	0.00	0.000	00:00:54	19/09/2019 11:41:31	0.04C + 1NV	Ready to start, Project suspended	BAV--LT	
SETI@home	8.20 setiathome_v8 (opencl_nvidia_SoG)	blc32_2bit_guppi_58643_47587_HIP14472_0014.6284.818.24.47.56.vlar_1	- (-)	0.00	0.000	00:00:54	19/09/2019 11:41:31	0.04C + 1NV	Ready to start, Project suspended	BAV--LT	
SETI@home	8.20 setiathome_v8 (opencl_nvidia_SoG)	blc32_2bit_guppi_58643_55295_HIP6290_0037.6275.818.23.46.134.vlar_1	- (-)	0.00	0.000	00:00:54	19/09/2019 11:41:31	0.04C + 1NV	Ready to start, Project suspended	BAV--LT	
SETI@home	8.20 setiathome_v8 (opencl_nvidia_SoG)	blc32_2bit_guppi_58643_55295_HIP6290_0037.6275.818.23.46.104.vlar_1	- (-)	0.00	0.000	00:00:54	19/09/2019 11:41:31	0.04C + 1NV	Ready to start, Project suspended	BAV--LT	
SETI@home	8.20 setiathome_v8 (opencl_nvidia_SoG)	blc32_2bit_guppi_58643_47587_HIP14472_0014.5899.818.23.46.183.vlar_1	- (-)	0.00	0.000	00:00:54	19/09/2019 11:41:31	0.04C + 1NV	Ready to start, Project suspended	BAV--LT	
SETI@home	8.20 setiathome_v8 (opencl_nvidia_SoG)	blc32_2bit_guppi_58643_53021_HIP6080_0030.6220.818.24.47.226.vlar_1	- (-)	0.00	0.000	00:00:54	19/09/2019 11:41:31	0.04C + 1NV	Ready to start, Project suspended	BAV--LT	
SETI@home	8.20 setiathome_v8 (opencl_nvidia_SoG)	blc32_2bit_guppi_58643_53021_HIP6080_0030.12045.0.24.47.37.vlar_1	- (-)	0.00	0.000	00:00:54	19/09/2019 11:59:33	0.04C + 1NV	Ready to start, Project suspended	BAV--LT	
SETI@home	8.20 setiathome_v8 (opencl_nvidia_SoG)	blc32_2bit_guppi_58643_49753_HIP6481_0020.32608.818.24.47.118.vlar_0	- (-)	0.00	0.000	00:00:54	19/09/2019 13:19:15	0.04C + 1NV	Ready to start, Project suspended	BAV--LT	
SETI@home	8.20 setiathome_v8 (opencl_nvidia_SoG)	blc32_2bit_guppi_58643_49753_HIP6481_0020.32608.818.24.47.116.vlar_1	- (-)	0.00	0.000	00:00:54	19/09/2019 13:19:15	0.04C + 1NV	Ready to start, Project suspended	BAV--LT	
SETI@home	8.20 setiathome_v8 (opencl_nvidia_SoG)	blc32_2bit_guppi_58643_61823_HIP7078_0057.9656.818.23.46.214.vlar_1	- (-)	0.00	0.000	00:00:54	19/09/2019 14:02:51	0.04C + 1NV	Ready to start, Project suspended	BAV--LT	
SETI@home	8.20 setiathome_v8 (opencl_nvidia_SoG)	blc32_2bit_guppi_58643_54975_HIP6863_0036.20794.818.23.46.182.vlar_0	- (-)	0.00	0.000	00:00:54	19/09/2019 14:58:53	0.04C + 1NV	Ready to start, Project suspended	BAV--LT	
SETI@home	8.20 setiathome_v8 (opencl_nvidia_SoG)	blc32_2bit_guppi_58643_53021_HIP6080_0030.20711.818.24.47.93.vlar_1	- (-)	0.00	0.000	00:00:54	19/09/2019 14:58:53	0.04C + 1NV	Ready to start, Project suspended	BAV--LT	
SETI@home	8.20 setiathome_v8 (opencl_nvidia_SoG)	blc32_2bit_guppi_58643_53021_HIP6080_0030.27306.409.24.47.112.vlar_0	- (-)	0.00	0.000	00:00:54	19/09/2019 15:25:04	0.04C + 1NV	Ready to start, Project suspended	BAV--LT	
SETI@home	8.20 setiathome_v8 (opencl_nvidia_SoG)	blc32_2bit_guppi_58643_59523_HIP660_0050.6518.818.23.46.16.vlar_1	- (-)	0.00	0.000	00:00:55	19/09/2019 16:16:33	0.04C + 1NV	Ready to start, Project suspended	BAV--LT	
SETI@home	8.20 setiathome_v8 (opencl_nvidia_SoG)	blc32_2bit_guppi_58643_54015_HIP6290_0033.12582.818.23.46.19.vlar_0	- (-)	0.00	0.000	00:00:55	19/09/2019 16:36:14	0.04C + 1NV	Ready to start, Project suspended	BAV--LT	
SETI@home	8.20 setiathome_v8 (opencl_nvidia_SoG)	blc32_2bit_guppi_58643_54015_HIP6290_0033.12767.818.24.47.29.vlar_0	- (-)	0.00	0.000	00:00:55	19/09/2019 16:46:24	0.04C + 1NV	Ready to start, Project suspended	BAV--LT


Estimated runtime 54/55 seconds, then the rest are 37 minutes.

So what to do, I have Boinc suspended at the moment.
102) Message boards : Politics : Greatest Best Leader of ALL TIME Yep Dat BeeeZZZ Big BIg BIG Hands Golden Haired Long Black Coat Wearin; WINNING ALWAYS Prez #45 45ers Gots His Back. You, Not So Much.......Yap (Message 2004810)
Posted 29 Jul 2019 by Profile Bernie Vine
Post:
Or even Kingston SW London who may well not feel "united" under Boris.
103) Message boards : Number crunching : Don't know where it should go? Stick it here! (Message 2004786)
Posted 29 Jul 2019 by Profile Bernie Vine
Post:
OK Need a little assistance (again)

I have been running my laptop for the first time on SETI@Home, I never normally use my laptop here as I know it can be a bit much for the machine to handle.

The machine is here

https://setiathome.berkeley.edu/show_host_detail.php?hostid=8774216


It processed a full days tasks yesterday and then suddenly this afternoon all GPU tasks error with this;

<core_client_version>7.14.2</core_client_version>
<![CDATA[
<message>
exceeded elapsed time limit 1084.87 (43667.73G/40.25G)</message>
<stderr_txt>
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

Build features: SETI8	Non-graphics	OpenCL	USE_OPENCL_NV	OCL_ZERO_COPY	SIGNALS_ON_GPU	OCL_CHIRP3	FFTW	USE_SSE3	x86	
     CPUID: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz 

     Cache: L1=64K L2=256K

CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3 SSSE3 FMA3 SSE4.1 SSE4.2 AVX 
Low-performance GPU detected, default period_iterations_num set to 500
For low-performance GPU path use_sleep enabled with 1ms per iteration, high prec timer enabled
OpenCL-kernels filename : MultiBeam_Kernels_r3557.cl 
ar=0.007826  NumCfft=103215  NumGauss=0  NumPulse=33293837184  NumTriplet=46247668896
Currently allocated 201 MB for GPU buffers
In v_BaseLineSmooth: NumDataPoints=1048576, BoxCarLength=8192, NumPointsInChunk=32768

Windows optimized setiathome_v8 application
Based on Intel, Core 2-optimized v8-nographics V5.13 by Alex Kan
SSE3xj Win32 Build 3557 , Ported by : Raistmer, JDWhale

SETI8 update by Raistmer

OpenCL version by Raistmer, r3557

Number of OpenCL platforms:				 2


 OpenCL Platform Name:					 NVIDIA CUDA
Number of devices:				 1
  Max compute units:				 3
  Max work group size:				 1024
  Max clock frequency:				 1189Mhz
  Max memory allocation:			 1073741824
  Cache type:					 Read/Write
  Cache line size:				 128
  Cache size:					 49152
  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:				 Yes
  Name:						 GeForce 940MX
  Vendor:					 NVIDIA Corporation
  Driver version:				 418.91
  Version:					 OpenCL 1.2 CUDA
  Extensions:					 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_khr_fp64 cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll cl_nv_d3d10_sharing cl_khr_d3d10_sharing cl_nv_d3d11_sharing cl_nv_copy_opts cl_nv_create_buffer


 OpenCL Platform Name:					 Intel(R) OpenCL
Number of devices:				 1
  Max compute units:				 24
  Max work group size:				 256
  Max clock frequency:				 1150Mhz
  Max memory allocation:			 1561123226
  Cache type:					 Read/Write
  Cache line size:				 64
  Cache size:					 524288
  Global memory size:				 1561123226
  Constant buffer size:				 1561123226
  Max number of constant args:			 8
  Local memory type:				 Scratchpad
  Local memory size:				 65536
  Queue properties:				 
    Out-of-Order:				 Yes
  Name:						 Intel(R) UHD Graphics 620
  Vendor:					 Intel(R) Corporation
  Driver version:				 22.20.16.4691
  Version:					 OpenCL 2.1 
  Extensions:					 cl_intel_accelerator cl_intel_advanced_motion_estimation cl_intel_d3d11_nv12_media_sharing cl_intel_device_side_avc_motion_estimation cl_intel_driver_diagnostics cl_intel_dx9_media_sharing cl_intel_media_block_io cl_intel_motion_estimation cl_intel_planar_yuv cl_intel_packed_yuv cl_intel_required_subgroup_size cl_intel_simultaneous_sharing cl_intel_subgroups cl_intel_subgroups_short cl_khr_3d_image_writes cl_khr_byte_addressable_store cl_khr_d3d10_sharing cl_khr_d3d11_sharing cl_khr_depth_images cl_khr_dx9_media_sharing cl_khr_fp16 cl_khr_fp64 cl_khr_gl_depth_images cl_khr_gl_event cl_khr_gl_msaa_sharing cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_gl_sharing cl_khr_icd cl_khr_image2d_from_buffer cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_mipmap_image cl_khr_mipmap_image_writes cl_khr_spir cl_khr_subgroups cl_khr_throttle_hints 


Work Unit Info:
...............
Credit multiplier is :  2.85
WU true angle range is :  0.007826
Used GPU device parameters are:
	Number of compute units: 3
	Single buffer allocation size: 128MB
	Total device global memory: 4096MB
	max WG size: 1024
	local mem type: Real
	FERMI path used: yes
	LotOfMem path: yes
	LowPerformanceGPU path: yes
	HighPerformanceGPU path: no
period_iterations_num=500
Triplet: peak=9.827008, time=56.91, period=1.7, d_freq=2767421532.39, chirp=-0.050771, fft_len=2k
GPU device sync requested...  ...GPU device synched
Termination request detected or computations are finished. GPU device synched,  exiting...
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

Build features: SETI8	Non-graphics	OpenCL	USE_OPENCL_NV	OCL_ZERO_COPY	SIGNALS_ON_GPU	OCL_CHIRP3	FFTW	USE_SSE3	x86	
     CPUID: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz 

     Cache: L1=64K L2=256K

CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3 SSSE3 FMA3 SSE4.1 SSE4.2 AVX 
Low-performance GPU detected, default period_iterations_num set to 500
For low-performance GPU path use_sleep enabled with 1ms per iteration, high prec timer enabled
OpenCL-kernels filename : MultiBeam_Kernels_r3557.cl 
ar=0.007826  NumCfft=103215  NumGauss=0  NumPulse=33293837184  NumTriplet=46247668896
Currently allocated 201 MB for GPU buffers
In v_BaseLineSmooth: NumDataPoints=1048576, BoxCarLength=8192, NumPointsInChunk=32768
Restarted at 2.45 percent.
Used GPU device parameters are:
	Number of compute units: 3
	Single buffer allocation size: 128MB
	Total device global memory: 4096MB
	max WG size: 1024
	local mem type: Real
	FERMI path used: yes
	LotOfMem path: yes
	LowPerformanceGPU path: yes
	HighPerformanceGPU path: no
period_iterations_num=500
Autocorr: peak=18.1383, time=62.99, delay=3.006, d_freq=2767424312, chirp=4.7826, fft_len=128k
Triplet: peak=12.84841, time=10.93, period=5.76, d_freq=2767427428.73, chirp=-14.477, fft_len=128 
Spike: peak=24.06685, time=65.86, d_freq=2767420361.54, chirp=22.781, fft_len=64k
Pulse: peak=3.409772, time=45.84, period=6.146, d_freq=2767422224.81, score=1.028, chirp=-27.748, fft_len=512 
D:	threshold 0.1344776; unscaled peak power: 0.1373595 exceeds threshold for 2.143%
GPU device sync requested...  ...GPU device synched
Termination request detected or computations are finished. GPU device synched,  exiting...

</stderr_txt>
]]>


Any help would be appreciated.
104) Questions and Answers : Windows : curious video card question (Message 2004652)
Posted 28 Jul 2019 by Profile Bernie Vine
Post:
No they do not, however there is a way to recompile the Boinc software (it is open source) that allows a user to "spoof" the number of GPU's.

You will see it mostly used on Linux machines running the "special app" where a top range GPU, think RTX2080 can do a task in 60-90 seconds.

These users run out of work during the outage, due to the 100 work unit limit per GPU, and use this method to keep crunching 24/7

There is a thread on the Number Crunching forums where it is sort of explained.

It is not generally available, you need to download the Boinc software and make the alterations yourself.
105) Message boards : Number crunching : Don't know where it should go? Stick it here! (Message 2004522)
Posted 27 Jul 2019 by Profile Bernie Vine
Post:
Well after a lot of web browsing( some of the prices!!!) I decided on a GTX 1660 (not a Ti as those two letter push it out of my price range) ;-)

https://www.amazon.co.uk/gp/product/B07PNH3C4N/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1

I had to keep the size down as I found out when using the temporary 750ti, long cards foul the sata sockets!!

I decided as the MB is only 6 months old why not splash out on a new GPU as well.

I will be interested to see how it compares to the Ti in my other Win machine
106) Message boards : Cafe SETI : Word Link # 102 (Message 2004520)
Posted 27 Jul 2019 by Profile Bernie Vine
Post:
Luna
107) Message boards : Number crunching : Don't know where it should go? Stick it here! (Message 2004491)
Posted 27 Jul 2019 by Profile Bernie Vine
Post:
Today as most days one of the first things I did was to check Boinc Tasks, to find to my surprise that my 2nd Win machine (the one I put t new MB in earlier this year) was disconnected,

So switching on the screen I find that it has rebooted, and is waiting for me to sign in. This is odd because since the new MB and a total re-install of Windows it has not been a problem. I log in, and thinking it may have been a Windows update. I go to kook at the Win event log, before I can click on it, screen goes blank. Nothing I can do will restore it. A feeling of impending doom!! I restart it by holding in the power button, it reboots, I log in and almost immediately black screen. I try to remote in, which works, as it asks for and accepts my PW, but all I get is a black screen. It is then I notice that it is showing in Boinc Tasks, however whilst the two CPU tasks are progressing the GPU task is static not progressing, I then notice that there are 27 GPU tasks "waiting to run". It would seem my GTX 970 has died. Now I know that 5 year old GPU's subject to 24 hour heavy use do fail. However this card was special to me.

Back when the 900 series first came out I was looking for new GPU, so I asked on these forums how people rated the GTX950 and GTX960 in terms of value for money,. At the time I was watching the pennies so really a 950 was the best I could afford. That same day I got a PM from another setizen, who said he had a spare GTX970 and would I be interested. Well yes I was. I pm'd him back asking how much he wanted. His reply totally surprised me, he didn't want anything, he had updated his GPU's to 980 and would be happy that another cruncher could put it to good use. Which I did. This was late 2014 and it has been either gaming or crunching 24/7 since.

He sadly left SETI after a discussion on Nitpicker convinced him SETI@Home was a total waste of time. Sad

RIP GTX 970

So if you have read this far you will know I need a new GPU, question is , a 970 for nostalgia or a 1060 for an update?
108) Message boards : Number crunching : The spoofed client - Whatever about (Message 2004427)
Posted 26 Jul 2019 by Profile Bernie Vine
Post:
I’ve always been under the impression that the restrictions were put in place more as a precautionary measure in preventing a large amount of resends in the event that a host trashes its entire WU cache due to hardware or software issues on the host’s end. Combined with the developers feelings that you’d never need more than 100 anyway based on the processing rate of the time.

Do you have evidence or a source that says the restrictions were put into place specifically for the case of work returned after an outage?

I unfortunately don't have a link at the moment. So far I can not even find a mention of the limit let alone the reason

However if you think about it, your reason is a non starter as there are lots of hosts totally trashing almost every WU due to old/faulty or wrong driver GPU's and they just continue, the 100 WU limit has no effect. So re-sends stay high

Also I assume "the developers" refers to Boinc. This isn't a Boinc limit, this is a server side SETI@Home project limit. Other projects have their own or none.

Also think about it, the only time the 100 WU limit has any affect is during an outage. The rest of the time your GPU's can return work as quickly as they like and it makes no difference.

My fastest machine is around 2.5 mins a task, it never "runs out" during normal working so the 100 task limit has no affect and I don't notice it .

However hundreds of machines returning thousands of WU' after an outage can cause database instability, the longer the outage obviously the worse it becomes.

If it is possible to reduce A) The amount of work returned and B)The amount of replacement tasks asked for after an outage it will recover quicker.

I will see if I can find any prof of what I am saying but it may take a while.
109) Message boards : Number crunching : The spoofed client - Whatever about (Message 2004405)
Posted 26 Jul 2019 by Profile Bernie Vine
Post:
modern GPUs and app developments have over run the old restrictions that were put in place at a time when processing 1 WU took an entire day. now we have GPUs that can do the same task in less than 30 seconds.


These restrictions were put into place to stop huge amounts of data being returned after an outage as it caused database problems. That is it, no other reason.

Now if you know that these problems no longer exist then fine I expect to see the limit removed.

What has happened with spoofing is that unless the return rate from spoofed machines is controlled after an outage, then you are negating the whole reason for the 100 task limit and making things worse.

The 100 task limit was to specifically stop machines with large caches returning all the work at once. So in effect this could make recovery after an outage worse.

When I raised this point before I was assured that people who spoofed were aware of this fact and controlled their task return so as not to flood the servers. Is this still correct?
110) Message boards : Cafe SETI : Rutger Hauer Dead (Message 2004096)
Posted 24 Jul 2019 by Profile Bernie Vine
Post:
Hard to forget this scene:

"I've seen things you people wouldn't believe, attack ships on fire off the shoulder of Orion. I watched C-beams glitter in the dark near the Tannhäuser Gate. All those moments will be lost in time, like tears in rain. Time to die."

Which he apparently wrote himself to help explain his character

RIP.
111) Message boards : Cafe SETI : Don't know where it should go? Stick it here! Part VII (Message 2004086)
Posted 24 Jul 2019 by Profile Bernie Vine
Post:
but this one that lasts 2:10 is and I hope everyone can view it


Nope I can't view that, but hopefully people in the US can see it and people in the UK can see mine!!
112) Message boards : Cafe SETI : Don't know where it should go? Stick it here! Part VII (Message 2004080)
Posted 24 Jul 2019 by Profile Bernie Vine
Post:
I admit to not keeping up with things, but this was a total surprise.

Seems CBS and Amazon have teamed up to produce this:

https://www.youtube.com/watch?time_continue=128&v=YhBBXHwEsIo

Hopefully it is watchable in all countries
113) Message boards : Cafe SETI : TLPTPHW (The Last Person To Post Here Wins) #CCLXXXVI (Message 2003977)
Posted 23 Jul 2019 by Profile Bernie Vine
Post:
Or perhaps 124
114) Message boards : Number crunching : Setting up Linux to crunch CUDA90 and above for Windows users (Message 2003849)
Posted 22 Jul 2019 by Profile Bernie Vine
Post:
What kind of system is this that you need risers for only 2 GPUs?


Er a cheap and cheerful one, you know you might have seen them, ordinary PC boards, one full length PCIE 16 slot only.

This particular board was the only new one I brought for my Linux conversions.

Oh yes and my GPU's are all second hand as well.
115) Message boards : Number crunching : SETI@Home Wow!-Event 2019 (Message 2003838)
Posted 22 Jul 2019 by Profile Bernie Vine
Post:
Never heard a peep out of the general rabble until this year.


Well you obviously missed the posts last year, and I think the year before. Then it was mostly about people with access to hundreds of "work" machines should have a separate category

However it is likely to be worse this year because there is the "special app" and the "GPU spoofing" meaning some will be able to bunker 6400 task per machine if they wish.

For reasons I wont go into here, I spent money on my machines and GPU's got round Linux, installed the special app, really for the WOW event ,mostly for my team.

I currently have the time and money to do this, but there are many who do not and would feel totally overpowered by someone running high end CPU and GPU's in multiple rigs.

So lets not call other posters "rabble" it helps to made the divide bigger.
116) Message boards : Number crunching : Setting up Linux to crunch CUDA90 and above for Windows users (Message 2003817)
Posted 22 Jul 2019 by Profile Bernie Vine
Post:
Do you have the opencl drivers installed?


See the bottom of my first post, the answer is yes and I have already successfully completed AP's
117) Message boards : Number crunching : Setting up Linux to crunch CUDA90 and above for Windows users (Message 2003812)
Posted 22 Jul 2019 by Profile Bernie Vine
Post:
It is located at /home/{username}/.nv/ComputeCache


Sorry couldn't find that.

Looking at all the lines that Mike pointed out it looks like the problem with the riser again where it suddenly doesn't detect the card. Hence the 142 "waiting to run ".

I will see if there are any better risers around.
118) Message boards : Number crunching : Setting up Linux to crunch CUDA90 and above for Windows users (Message 2003801)
Posted 22 Jul 2019 by Profile Bernie Vine
Post:
A bit of help here, one of my Linux machines has just errored 5 AP, all with this error

<core_client_version>7.14.2</core_client_version>
<![CDATA[
<message>
process exited with code 193 (0xc1, -63)</message>
<stderr_txt>
Running on device number: 1
Maximum single buffer size set to:256MB
DATA_CHUNK_UNROLL set to:16
oclFFT plan class overrides requested: global radix 256; local radix 16;  max workgroup size 256
FFA thread block override value:2304
FFA thread fetchblock override value:1152
GPU not found: type=NVIDIA, opencl_device_index=1, device_num=-1
WARNING: boinc_get_opencl_ids failed with code -1
OpenCL platform detected: NVIDIA Corporation
WARNING: BOINC supplied wrong platform!
Number of OpenCL devices found : 1 
BOINC assigns slot on device #1.
WARNING: BOINC failed to provide OpenCL device, using own enumeration abilities
SIGSEGV: segmentation violation
Stack trace (7 frames):
../../projects/setiathome.berkeley.edu/astropulse_7.08_x86_64-pc-linux-gnu__opencl_nvidia_100(boinc_catch_signal+0x4d)[0x4c6fdd]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x12890)[0x7fdf554d2890]
/usr/lib/x86_64-linux-gnu/libnvidia-opencl.so.1(+0xf5315)[0x7fdf524e3315]
../../projects/setiathome.berkeley.edu/astropulse_7.08_x86_64-pc-linux-gnu__opencl_nvidia_100[0x485cf9]
../../projects/setiathome.berkeley.edu/astropulse_7.08_x86_64-pc-linux-gnu__opencl_nvidia_100[0x46a1df]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7fdf54387b97]
../../projects/setiathome.berkeley.edu/astropulse_7.08_x86_64-pc-linux-gnu__opencl_nvidia_100[0x40bd89]

Exiting...

</stderr_txt>
]]>


I am guessing this line is the problem

"WARNING: BOINC failed to provide OpenCL device, using own enumeration abilities"

Any assistance would be welcome, it also now has 142 tasks "waiting to start"

I have shut it down and checked the riser connections, and now rebooted OK and seem to be crunching OK

Yes it does detect OpenCL on startup

22/07/2019 17:09:20	Data directory: /home/bav/BOINC	
22/07/2019 17:09:20	CUDA: NVIDIA GPU 0: GeForce GTX 1060 3GB (driver version 418.56, CUDA version 10.1, compute capability 6.1, 3018MB, 2695MB available, 3936 GFLOPS peak)	
22/07/2019 17:09:20	CUDA: NVIDIA GPU 1: GeForce GTX 1060 3GB (driver version 418.56, CUDA version 10.1, compute capability 6.1, 3019MB, 2950MB available, 3936 GFLOPS peak)	
22/07/2019 17:09:20	OpenCL: NVIDIA GPU 0: GeForce GTX 1060 3GB (driver version 418.56, device version OpenCL 1.2 CUDA, 3018MB, 2695MB available, 3936 GFLOPS peak)	
22/07/2019 17:09:20	OpenCL: NVIDIA GPU 1: GeForce GTX 1060 3GB (driver version 418.56, device version OpenCL 1.2 CUDA, 3019MB, 2950MB available, 3936 GFLOPS peak)	
SETI@home	22/07/2019 17:09:20	Found app_info.xml; using anonymous platform	
22/07/2019 17:09:21	[libc detection] gathered: 2.27, Ubuntu GLIBC 2.27-3ubuntu1
119) Message boards : Number crunching : Data Chat (Message 2003787)
Posted 22 Jul 2019 by Profile Bernie Vine
Post:
The WOW event is just a bit of fun, it has leader-boards, so yes there is competition and no I do't expect to be able to compete with someone running 2080 Ti's on Linux with the special app.

However I will do my best and try and beat my total for last year, and fly the flag for my team, and my country.

And yes there are people who only crunch to compete, but if they leave WU's un-crunched and abandoned , then we will crunch them later.

We actually need more events like this as we are currently only processing 1% of the Breakthrough Listen Data.

Lets try and keep positive.
120) Message boards : Number crunching : Data Chat (Message 2003764)
Posted 22 Jul 2019 by Profile Bernie Vine
Post:
Yes you are all right, they have started this way to early.


Well not necessarily, if you start bunkering a week before the event chances are a lot of WU's may not valid straight away as they have not been completed by the wingman.

Now if you start three weeks before, the chances are that nearly all the WU's will validate straight away is higher. Logic really, if annoying for others.

However the unintended consequence of this is it also helps others as all their pending tasks validate at the same time as well

No I have not started bunkering, I may do a couple of machines on the day but that is all.


Previous 20 · Next 20


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