Computation Error 197 on 8.22 SETI@home v8 (opencl_nvidia_SoG)

Message boards : Number crunching : Computation Error 197 on 8.22 SETI@home v8 (opencl_nvidia_SoG)
Message board moderation

To post messages, you must log in.

AuthorMessage
droople
Avatar

Send message
Joined: 18 Aug 08
Posts: 11
Credit: 3,604,996
RAC: 19
China
Message 2024280 - Posted: 22 Dec 2019, 3:38:50 UTC

Dear All,
I got some computation error 197 on 8.22 SETI@home v8 (opencl_nvidia_SoG)

Here is the detail of the task
8.22 SETI@home v8 (opencl_nvidia_SoG) 15fe13ab.19056.15095.5.32.205_1

Name 26mr08ac.15063.37553.14.41.247_1

Created 14 Dec 2019, 2:50:31 UTC
Sent 14 Dec 2019, 7:29:11 UTC
Report deadline 3 Jan 2020, 18:38:53 UTC
Received 17 Dec 2019, 3:45:35 UTC
Server state Over
Outcome Computation error
Client state Compute error
Exit status 197 (0x000000C5) EXIT_TIME_LIMIT_EXCEEDED

Run time 43 min 25 sec
CPU time 7 sec
Validate state Invalid
Credit 0.00
Device peak FLOPS 1,993.50 GFLOPS
Application version SETI@home v8 v8.22 (opencl_nvidia_SoG)
windows_intelx86
Peak working set size 106.44 MB
Peak swap size 131.12 MB
Peak disk usage 0.02 MB

Here is the Stderr output
<core_client_version>7.14.2</core_client_version>
<![CDATA[
<message>
exceeded elapsed time limit 2560.36 (1414546.15G/552.48G)</message>
<stderr_txt>
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

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-9700KF CPU @ 3.60GHz

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
OpenCL-kernels filename : MultiBeam_Kernels_r3584.cl
ar=3.800778 NumCfft=99351 NumGauss=0 NumPulse=28028404807 NumTriplet=28028404807
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 3584 , Ported by : Raistmer, JDWhale

SETI8 update by Raistmer

OpenCL version by Raistmer, r3584

Number of OpenCL platforms: 1


OpenCL Platform Name: NVIDIA CUDA
Number of devices: 1
Max compute units: 36
Max work group size: 1024
Max clock frequency: 1440Mhz
Max memory allocation: 2147483648
Cache type: Read/Write
Cache line size: 128
Cache size: 1179648
Global memory size: 8589934592
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 RTX 2070
Vendor: NVIDIA Corporation
Driver version: 441.66
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 cl_khr_int64_base_atomics cl_khr_int64_extended_atomics


Work Unit Info:
...............
Credit multiplier is : 2.85
WU true angle range is : 3.800778
Used GPU device parameters are:
Number of compute units: 36
Single buffer allocation size: 128MB
Total device global memory: 8192MB
max WG size: 1024
local mem type: Real
FERMI path used: yes
LotOfMem path: yes
LowPerformanceGPU path: no
HighPerformanceGPU path: no
period_iterations_num=50
Triplet: peak=8.737766, time=98.7, period=0.4465, d_freq=1419908447.27, chirp=0, fft_len=16

</stderr_txt>
]]>

Cheers
ID: 2024280 · Report as offensive
juan BFP Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 16 Mar 07
Posts: 9786
Credit: 572,710,851
RAC: 3,799
Panama
Message 2024283 - Posted: 22 Dec 2019, 3:48:19 UTC

This is a well know issue look at: https://setiathome.berkeley.edu/forum_thread.php?id=84694

Revert the Nvidia to the 431.60 and all will be OK
ID: 2024283 · Report as offensive
Grant (SSSF)
Volunteer tester

Send message
Joined: 19 Aug 99
Posts: 13760
Credit: 208,696,464
RAC: 304
Australia
Message 2024284 - Posted: 22 Dec 2019, 3:48:51 UTC

Mentioned in multiple other threads- your video driver is the problem.
Driver version: 441.66

Only drivers 431.60 or earlier can be used without causing issues on some Arecibo WUs.
Grant
Darwin NT
ID: 2024284 · Report as offensive
droople
Avatar

Send message
Joined: 18 Aug 08
Posts: 11
Credit: 3,604,996
RAC: 19
China
Message 2024356 - Posted: 22 Dec 2019, 13:25:07 UTC - in response to Message 2024283.  

This is a well know issue look at: https://setiathome.berkeley.edu/forum_thread.php?id=84694

Revert the Nvidia to the 431.60 and all will be OK


Thank you so much,
ID: 2024356 · Report as offensive

Message boards : Number crunching : Computation Error 197 on 8.22 SETI@home v8 (opencl_nvidia_SoG)


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