error code 2 (0x2) & other issues

Message boards : SETI@home Enhanced : error code 2 (0x2) & other issues
Message board moderation

To post messages, you must log in.

AuthorMessage
AMDave
Volunteer tester

Send message
Joined: 12 Jan 16
Posts: 38
Credit: 289,647
RAC: 0
United States
Message 59453 - Posted: 5 Sep 2016, 19:15:24 UTC

Had a problem re-initiating Beta.  It was suspended for a month, so I thought I fire it up again.  I downloaded r3525 from Raistmer's cloud storage.  I archived just about everything in the project folder (it was cluttered with 200+ files).  I used the aistub file for app_info, and resumed beta.  Downloaded 50 WUs, then my attempt to open Event Viewer prompted the Connecting to client window to appear and remain for several minutes.  Upon reaching the EV, well, look:

05-Sep-2016 10:53:59 [SETI@home Beta Test] project resumed by user
05-Sep-2016 10:54:04 [SETI@home Beta Test] work fetch resumed by user
05-Sep-2016 10:54:09 [SETI@home Beta Test] Sending scheduler request: To fetch work.
05-Sep-2016 10:54:09 [SETI@home Beta Test] Requesting new tasks for NVIDIA GPU
05-Sep-2016 10:54:13 [SETI@home Beta Test] Scheduler request completed: got 50 new tasks
05-Sep-2016 10:54:15 [SETI@home Beta Test] Started download of blc7_2bit_guppi_57403_HIP11048_0004.2249.0.21.51.121.vlar
05-Sep-2016 10:54:15 [SETI@home Beta Test] Started download of 27jl16aa.3814.159685.6.40.71
05-Sep-2016 10:54:18 [SETI@home Beta Test] Finished download of 27jl16aa.3814.159685.6.40.71
05-Sep-2016 10:54:18 [SETI@home Beta Test] Started download of 27jl16aa.3814.159685.6.40.79
.
.
.
05-Sep-2016 10:55:36 [SETI@home Beta Test] Process creation failed: The system cannot find the file specified. (0x2) - error code 2 (0x2)
05-Sep-2016 10:55:36 [SETI@home Beta Test] Process creation failed: The system cannot find the file specified. (0x2) - error code 2 (0x2)
05-Sep-2016 10:55:36 [SETI@home Beta Test] Process creation failed: The system cannot find the file specified. (0x2) - error code 2 (0x2)
05-Sep-2016 10:55:37 [SETI@home Beta Test] Process creation failed: The system cannot find the file specified. (0x2) - error code 2 (0x2)
05-Sep-2016 10:55:37 [SETI@home Beta Test] Process creation failed: The system cannot find the file specified. (0x2) - error code 2 (0x2)
05-Sep-2016 10:55:37 [SETI@home Beta Test] Computation for task 27jl16aa.3814.159685.6.40.81_1 finished
05-Sep-2016 10:55:37 [SETI@home Beta Test] Output file 27jl16aa.3814.159685.6.40.81_1_r1003546493_0 for task 27jl16aa.3814.159685.6.40.81_1 absent
05-Sep-2016 10:55:37 [SETI@home Beta Test] Process creation failed: The system cannot find the file specified.
.
.
.
05-Sep-2016 10:57:41 [SETI@home Beta Test] Computation for task blc7_2bit_guppi_57403_HIP11048_0004.2249.0.21.51.121.vlar_2 finished
05-Sep-2016 10:57:41 [SETI@home Beta Test] Output file blc7_2bit_guppi_57403_HIP11048_0004.2249.0.21.51.121.vlar_2_r1980244307_0 for task blc7_2bit_guppi_57403_HIP11048_0004.2249.0.21.51.121.vlar_2 absent


Here is the Stderr output:

<core_client_version>7.6.22</core_client_version>
<![CDATA[
<message>
couldn't start app: CreateProcess() failed - The system cannot find the file specified.
 (0x2)
</message>
]]>


I suspended Beta, shutdown BOINC, and compared the app_info with the version I used for r3500.  I noticed this was not present in the aistub:

   <file_info>
      <name>MultiBeam_Kernels_r3525.cl</name>
   </file_info>


and this line did not have a corresponding exe file in the folder:

   <app_version>
      <app_name>setiathome_v8</app_name>
      <version_num>818</version_num>
   </app_version>


So, I renamed app_info, started BOINC, and resumed Beta.  Additional files were downloaded, including
mb_cmdline-8.17_windows_intel__opencl_nvidia_SoG.txt.  I suspended Beta, shut down BOINC, then changed the <version_num>818</version_num> to 817.  Started and resumed, only to get:

9/5/2016 2:19:45 PM | SETI@home Beta Test | Found app_info.xml; using anonymous platform
9/5/2016 2:19:45 PM | SETI@home Beta Test | [error] No application found for task: windows_intelx86 816 opencl_nvidia_sah; discarding
9/5/2016 2:19:45 PM | SETI@home Beta Test | [error] No application found for task: windows_intelx86 816 opencl_nvidia_sah; discarding
9/5/2016 2:19:45 PM | SETI@home Beta Test | [error] No application found for task: windows_intelx86 816 opencl_nvidia_sah; discarding
.
.
.
9/5/2016 2:20:34 PM | SETI@home Beta Test | Task postponed: Can't read CL file


I discovered that Beta had overwrittin MultiBeam_Kernels_r3525.cl with r3500.cl.  I copied r3525.cl back, resumed and received this:

9/5/2016 2:32:28 PM | SETI@home Beta Test | Message from server: Your app_info.xml file doesn't have a usable version of SETI@home v8


Well, let me shorten this.  Currently, I have 10 WUs "Waiting to run", with elapsed times of 3 sec and remaining times of 1:03:35 - 1:03:48, 1 WU running, and a quota of 1 WU.

I've learned that when resuming Beta after a substantial period of suspension, you must do so prior to implementing a app_info file.  I found what an error (0x5) is, but not "Process creation failed: The system cannot find the file specified.  (0x2) - error code 2 (0x2)".

One more thing, my task list displays the application as SETI@home v8 v8.17 (opencl_nvidia_SoG)windows_intelx86, so I'm guessing the app_info isn't being used, although it was found.

Any enlightenment towards what I could have done to avoid any of the above would be appreciated.
ID: 59453 · Report as offensive
Profile Raistmer
Volunteer tester
Avatar

Send message
Joined: 18 Aug 05
Posts: 2423
Credit: 15,878,738
RAC: 0
Russia
Message 59472 - Posted: 7 Sep 2016, 16:09:59 UTC

Could you just suspend beta project. Delete all in it, reset beta project in boinc and then allow new work?
News about SETI opt app releases: https://twitter.com/Raistmer
ID: 59472 · Report as offensive
AMDave
Volunteer tester

Send message
Joined: 12 Jan 16
Posts: 38
Credit: 289,647
RAC: 0
United States
Message 59483 - Posted: 7 Sep 2016, 19:52:38 UTC - in response to Message 59472.  
Last modified: 7 Sep 2016, 19:57:54 UTC

Could you just suspend beta project. Delete all in it, reset beta project in boinc and then allow new work?

Event Log:
9/7/2016 3:01:37 PM | SETI@home Beta Test | update requested by user
9/7/2016 3:01:39 PM | SETI@home Beta Test | Sending scheduler request: Requested by user.
9/7/2016 3:01:39 PM | SETI@home Beta Test | Reporting 18 completed tasks
9/7/2016 3:01:39 PM | SETI@home Beta Test | Not requesting tasks: suspended via Manager
9/7/2016 3:01:41 PM | SETI@home Beta Test | Scheduler request completed
9/7/2016 3:02:05 PM | SETI@home Beta Test | Resetting project
9/7/2016 3:02:51 PM | SETI@home Beta Test | work fetch resumed by user
9/7/2016 3:02:54 PM | SETI@home Beta Test | project resumed by user
9/7/2016 3:02:58 PM | SETI@home Beta Test | Master file download succeeded
9/7/2016 3:03:03 PM | SETI@home Beta Test | Sending scheduler request: To fetch work.
9/7/2016 3:03:03 PM | SETI@home Beta Test | Requesting new tasks for NVIDIA GPU
9/7/2016 3:03:05 PM | SETI@home Beta Test | Scheduler request completed: got 50 new tasks
.
.
.
9/7/2016 3:03:15 PM | SETI@home Beta Test | Sending scheduler request: To fetch work.
9/7/2016 3:03:15 PM | SETI@home Beta Test | Requesting new tasks for NVIDIA GPU
9/7/2016 3:03:16 PM | SETI@home Beta Test | Finished download of 27jl16aa.15988.166638.6.40.175.vlar
9/7/2016 3:03:16 PM | SETI@home Beta Test | Finished download of 27jl16aa.15988.166638.6.40.134.vlar
9/7/2016 3:03:16 PM | SETI@home Beta Test | Started download of 27jl16aa.15988.166638.6.40.174.vlar
9/7/2016 3:03:16 PM | SETI@home Beta Test | Started download of 27jl16aa.15988.166638.6.40.127.vlar
9/7/2016 3:03:16 PM | SETI@home Beta Test | Scheduler request completed: got 0 new tasks
9/7/2016 3:03:16 PM | SETI@home Beta Test | No tasks sent
9/7/2016 3:03:16 PM | SETI@home Beta Test | No tasks are available for SETI@home v8
9/7/2016 3:03:16 PM | SETI@home Beta Test | Tasks for CPU are available, but your preferences are set to not accept them
9/7/2016 3:03:16 PM | SETI@home Beta Test | Tasks for AMD/ATI GPU are available, but your preferences are set to not accept them
9/7/2016 3:03:16 PM | SETI@home Beta Test | Tasks for Intel GPU are available, but your preferences are set to not accept them
9/7/2016 3:03:16 PM | SETI@home Beta Test | This computer has reached a limit on tasks in progress

>>  Tasks were downloaded, then

9/7/2016 3:17:14 PM | SETI@home Beta Test | Sending scheduler request: To fetch work.
9/7/2016 3:17:14 PM | SETI@home Beta Test | Requesting new tasks for NVIDIA GPU
9/7/2016 3:17:16 PM | SETI@home Beta Test | Scheduler request completed: got 0 new tasks
9/7/2016 3:17:16 PM | SETI@home Beta Test | No tasks sent
9/7/2016 3:17:16 PM | SETI@home Beta Test | No tasks are available for SETI@home v8
9/7/2016 3:17:16 PM | SETI@home Beta Test | Tasks for CPU are available, but your preferences are set to not accept them
9/7/2016 3:17:16 PM | SETI@home Beta Test | Tasks for AMD/ATI GPU are available, but your preferences are set to not accept them
9/7/2016 3:17:16 PM | SETI@home Beta Test | Tasks for Intel GPU are available, but your preferences are set to not accept them
9/7/2016 3:17:16 PM | SETI@home Beta Test | This computer has reached a limit on tasks in progress

>>  WU crunched, then

9/7/2016 3:27:03 PM | SETI@home Beta Test | Message from task: 0
9/7/2016 3:27:03 PM | SETI@home Beta Test | Computation for task 27jl16aa.15988.166638.6.40.19.vlar_2 finished
9/7/2016 3:27:03 PM | SETI@home Beta Test | Starting task 27jl16aa.15988.166638.6.40.138.vlar_1
9/7/2016 3:27:05 PM | SETI@home Beta Test | Started upload of 27jl16aa.15988.166638.6.40.19.vlar_2_r1663897445_0
9/7/2016 3:27:09 PM | SETI@home Beta Test | Finished upload of 27jl16aa.15988.166638.6.40.19.vlar_2_r1663897445_0
9/7/2016 3:27:13 PM | SETI@home Beta Test | Sending scheduler request: To fetch work.
9/7/2016 3:27:13 PM | SETI@home Beta Test | Reporting 1 completed tasks
9/7/2016 3:27:13 PM | SETI@home Beta Test | Requesting new tasks for NVIDIA GPU
9/7/2016 3:27:15 PM | SETI@home Beta Test | Scheduler request completed: got 0 new tasks
9/7/2016 3:27:15 PM | SETI@home Beta Test | No tasks sent
9/7/2016 3:27:15 PM | SETI@home Beta Test | No tasks are available for SETI@home v8
9/7/2016 3:27:15 PM | SETI@home Beta Test | Message from server: Your app_info.xml file doesn't have a usable version of SETI@home v8.

9/7/2016 3:27:15 PM | SETI@home Beta Test | Tasks for CPU are available, but your preferences are set to not accept them
9/7/2016 3:27:15 PM | SETI@home Beta Test | Tasks for AMD/ATI GPU are available, but your preferences are set to not accept them
9/7/2016 3:27:15 PM | SETI@home Beta Test | Tasks for Intel GPU are available, but your preferences are set to not accept them
9/7/2016 3:27:15 PM | SETI@home Beta Test | This computer has finished a daily quota of 2 tasks
9/7/2016 3:27:03 PM | SETI@home Beta Test | Message from task: 0
9/7/2016 3:27:03 PM | SETI@home Beta Test | Computation for task 27jl16aa.15988.166638.6.40.19.vlar_2 finished
9/7/2016 3:27:03 PM | SETI@home Beta Test | Starting task 27jl16aa.15988.166638.6.40.138.vlar_1
9/7/2016 3:27:05 PM | SETI@home Beta Test | Started upload of 27jl16aa.15988.166638.6.40.19.vlar_2_r1663897445_0
9/7/2016 3:27:09 PM | SETI@home Beta Test | Finished upload of 27jl16aa.15988.166638.6.40.19.vlar_2_r1663897445_0
9/7/2016 3:27:13 PM | SETI@home Beta Test | Sending scheduler request: To fetch work.
9/7/2016 3:27:13 PM | SETI@home Beta Test | Reporting 1 completed tasks
9/7/2016 3:27:13 PM | SETI@home Beta Test | Requesting new tasks for NVIDIA GPU
9/7/2016 3:27:15 PM | SETI@home Beta Test | Scheduler request completed: got 0 new tasks
9/7/2016 3:27:15 PM | SETI@home Beta Test | No tasks sent
9/7/2016 3:27:15 PM | SETI@home Beta Test | No tasks are available for SETI@home v8
9/7/2016 3:27:15 PM | SETI@home Beta Test | Message from server: Your app_info.xml file doesn't have a usable version of SETI@home v8.

9/7/2016 3:27:15 PM | SETI@home Beta Test | Tasks for CPU are available, but your preferences are set to not accept them
9/7/2016 3:27:15 PM | SETI@home Beta Test | Tasks for AMD/ATI GPU are available, but your preferences are set to not accept them
9/7/2016 3:27:15 PM | SETI@home Beta Test | Tasks for Intel GPU are available, but your preferences are set to not accept them
9/7/2016 3:27:15 PM | SETI@home Beta Test | This computer has finished a daily quota of 2 tasks
9/7/2016 3:49:58 PM | SETI@home Beta Test | Message from task: 0
9/7/2016 3:49:58 PM | SETI@home Beta Test | Computation for task 27jl16aa.15988.166638.6.40.138.vlar_1 finished
9/7/2016 3:49:58 PM | SETI@home Beta Test | Starting task 27jl16aa.15988.166229.6.40.175.vlar_0
9/7/2016 3:50:00 PM | SETI@home Beta Test | Started upload of 27jl16aa.15988.166638.6.40.138.vlar_1_r955245894_0
9/7/2016 3:50:05 PM | SETI@home Beta Test | Finished upload of 27jl16aa.15988.166638.6.40.138.vlar_1_r955245894_0
9/7/2016 3:50:05 PM | SETI@home Beta Test | Sending scheduler request: To fetch work.
9/7/2016 3:50:05 PM | SETI@home Beta Test | Reporting 1 completed tasks
9/7/2016 3:50:05 PM | SETI@home Beta Test | Requesting new tasks for NVIDIA GPU
9/7/2016 3:50:09 PM | SETI@home Beta Test | Scheduler request completed: got 0 new tasks
9/7/2016 3:50:09 PM | SETI@home Beta Test | No tasks sent
9/7/2016 3:50:09 PM | SETI@home Beta Test | No tasks are available for SETI@home v8
9/7/2016 3:50:09 PM | SETI@home Beta Test | Message from server: Your app_info.xml file doesn't have a usable version of SETI@home v8.
9/7/2016 3:50:09 PM | SETI@home Beta Test | Tasks for CPU are available, but your preferences are set to not accept them
9/7/2016 3:50:09 PM | SETI@home Beta Test | Tasks for AMD/ATI GPU are available, but your preferences are set to not accept them
9/7/2016 3:50:09 PM | SETI@home Beta Test | Tasks for Intel GPU are available, but your preferences are set to not accept them
9/7/2016 3:50:09 PM | SETI@home Beta Test | This computer has finished a daily quota of 4 tasks


Task 24739599 and Task 24739955 are identified as SETI@home v8, Anonymous platform (NVIDIA GPU).

Here is the app_info I created from the aistub file.  There are several lines which are commented out.  Any assistance is greatly appreciated.
<app_info> 
    <app>
        <name>setiathome_v8</name>
    </app>
    <file_info>
        <name>MB8_win_x86_SSE3_OpenCL_NV_SoG_r3525.exe</name>
        <executable/>
    </file_info>
    <file_info>
        <name>libfftw3f-3-3-4_x86.dll</name>
	<executable/>
    </file_info>
   <file_info>
      <name>MultiBeam_Kernels_r3525.cl</name>
   </file_info>


    <file_info>
        <name>mb_cmdline-8.17_windows_intel__opencl_nvidia_SoG.txt</name>
    </file_info>

    <!--
    <file_info>
       <name>mb_cmdline_win_x86_SSE3_OpenCL_NV_SoG.txt</name>
    </file_info>
   -->
    <app_version>
        <app_name>setiathome_v8</app_name>
        <version_num>817</version_num>
        <platform>windows_intelx86</platform>
        <avg_ncpus>0.04</avg_ncpus>
        <max_ncpus>0.2</max_ncpus>
        <plan_class>opencl_nvidia_SoG</plan_class>
        	<cmdline></cmdline>	
	<coproc>
            <type>CUDA</type>
            <count>1</count>
        </coproc>
        <file_ref>
            <file_name>MB8_win_x86_SSE3_OpenCL_NV_SoG_r3525.exe</file_name>
            <main_program/>
        </file_ref>
        <file_ref>
            <file_name>libfftw3f-3-3-4_x86.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>mb_cmdline-8.17_windows_intel__opencl_nvidia_SoG.txt</file_name>
            <open_name>mb_cmdline.txt</open_name>
        </file_ref>
    </app_version>
</app_info>


*EDIT*
I've suspended Beta again.  As an aside, WUs are taking over 50% longer than r3500.
ID: 59483 · Report as offensive
Richard Haselgrove
Volunteer tester

Send message
Joined: 3 Jan 07
Posts: 1451
Credit: 3,266,428
RAC: 1
United Kingdom
Message 59490 - Posted: 7 Sep 2016, 21:16:42 UTC - in response to Message 59483.  

By "reset and allow new work", Raistmer meant 'return to stock processing' - testing the app which will be downloaded automatically.

I'd recommend stopping and restarting the BOINC client between 'resetting project' and 'allowing new tasks', ensuring that app_info.xml is deleted before the restart.

When you re-create an app_info.xml file - more appropriate to the main project than here - think again about MultiBeam_Kernels_r3525.cl: be consistent.

Either (preferred):
Supply both a <file_info> and a <file_ref>

Or (for a quick and dirty test):
don't mention it at all.

At the moment, you're declaring the file, but - as far as BOINC knows - not using it. That would generate a compiler warning, at least, in traditional programming.
ID: 59490 · Report as offensive
Profile Raistmer
Volunteer tester
Avatar

Send message
Joined: 18 Aug 05
Posts: 2423
Credit: 15,878,738
RAC: 0
Russia
Message 59491 - Posted: 7 Sep 2016, 21:18:06 UTC - in response to Message 59483.  

app_info.xml mentioned means you not under stock, but under anonymous platform instead.
As I said, delete ALL from beta project then reset it. app_info.xml should not present!

(reset it twice, restart and reset, but such message should not appear in correctly cleaned project)
News about SETI opt app releases: https://twitter.com/Raistmer
ID: 59491 · Report as offensive
AMDave
Volunteer tester

Send message
Joined: 12 Jan 16
Posts: 38
Credit: 289,647
RAC: 0
United States
Message 59508 - Posted: 8 Sep 2016, 17:43:04 UTC - in response to Message 59491.  
Last modified: 8 Sep 2016, 17:44:14 UTC

reset it twice

Done

restart and reset

Done

9/8/2016 1:16:26 PM |  | Starting BOINC client version 7.6.22 for windows_x86_64
9/8/2016 1:16:26 PM |  | log flags: file_xfer, sched_ops, task
9/8/2016 1:16:26 PM |  | Libraries: libcurl/7.45.0 OpenSSL/1.0.2d zlib/1.2.8
9/8/2016 1:16:26 PM |  | Data directory: C:\ProgramData\BOINC
9/8/2016 1:16:26 PM |  | Running under account AMDave
9/8/2016 1:16:27 PM |  | CUDA: NVIDIA GPU 0: GeForce GTX 950 (driver version 359.00, CUDA version 7.5, compute capability 5.2, 2048MB, 1772MB available, 2081 GFLOPS peak)
9/8/2016 1:16:27 PM |  | OpenCL: NVIDIA GPU 0: GeForce GTX 950 (driver version 359.00, device version OpenCL 1.2 CUDA, 2048MB, 1772MB available, 2081 GFLOPS peak)
9/8/2016 1:16:27 PM | SETI@home Beta Test | [error] State file error: missing application file MB8_win_x86_SSE3_OpenCL_NV_SoG_r3525.exe
.
.
.
9/8/2016 1:16:48 PM | SETI@home Beta Test | Resetting project
9/8/2016 1:18:03 PM | SETI@home Beta Test | work fetch resumed by user
9/8/2016 1:18:08 PM | SETI@home Beta Test | project resumed by user
9/8/2016 1:18:14 PM | SETI@home Beta Test | Master file download succeeded
9/8/2016 1:18:19 PM | SETI@home Beta Test | Sending scheduler request: To fetch work.
9/8/2016 1:18:19 PM | SETI@home Beta Test | Requesting new tasks for NVIDIA GPU
9/8/2016 1:18:21 PM | SETI@home Beta Test | Scheduler request completed: got 50 new tasks
9/8/2016 1:18:23 PM | SETI@home Beta Test | Started download of setiathome_8.01_windows_intelx86__cuda50.exe
9/8/2016 1:18:23 PM | SETI@home Beta Test | Started download of cudart32_50_35.dll
9/8/2016 1:18:26 PM | SETI@home Beta Test | Finished download of cudart32_50_35.dll
9/8/2016 1:18:26 PM | SETI@home Beta Test | Started download of cufft32_50_35.dll
9/8/2016 1:18:31 PM | SETI@home Beta Test | Sending scheduler request: To fetch work.
9/8/2016 1:18:31 PM | SETI@home Beta Test | Requesting new tasks for NVIDIA GPU
9/8/2016 1:18:32 PM | SETI@home Beta Test | Scheduler request completed: got 0 new tasks
9/8/2016 1:18:37 PM | SETI@home Beta Test | Finished download of setiathome_8.01_windows_intelx86__cuda50.exe
9/8/2016 1:18:37 PM | SETI@home Beta Test | Started download of mbcuda-8.01-cuda50.cfg.sample
9/8/2016 1:18:38 PM | SETI@home Beta Test | Finished download of mbcuda-8.01-cuda50.cfg.sample
9/8/2016 1:18:38 PM | SETI@home Beta Test | Started download of mbcuda-8.01-cuda50.cfg
9/8/2016 1:18:39 PM | SETI@home Beta Test | Finished download of mbcuda-8.01-cuda50.cfg
9/8/2016 1:18:39 PM | SETI@home Beta Test | Started download of setiathome-8.01-cuda50_AUTHORS.txt
9/8/2016 1:18:40 PM | SETI@home Beta Test | Finished download of setiathome-8.01-cuda50_AUTHORS.txt
9/8/2016 1:18:40 PM | SETI@home Beta Test | Started download of setiathome-8.01-cuda50_COPYING.txt
9/8/2016 1:18:41 PM | SETI@home Beta Test | Finished download of setiathome-8.01-cuda50_COPYING.txt
9/8/2016 1:18:41 PM | SETI@home Beta Test | Started download of setiathome-8.01-cuda50_COPYRIGHT.txt
9/8/2016 1:18:42 PM | SETI@home Beta Test | Finished download of setiathome-8.01-cuda50_COPYRIGHT.txt
9/8/2016 1:18:42 PM | SETI@home Beta Test | Started download of setiathome-8.01-cuda50_README.txt
9/8/2016 1:18:44 PM | SETI@home Beta Test | Finished download of setiathome-8.01-cuda50_README.txt
9/8/2016 1:18:44 PM | SETI@home Beta Test | Started download of setiathome-8.01-cuda50_README_x41zc.txt
9/8/2016 1:18:45 PM | SETI@home Beta Test | Finished download of setiathome-8.01-cuda50_README_x41zc.txt

First WU completed is Task 24748280
Run time : 7 min 21 sec
CPU time : 1 min 47 sec

This is incredibly fast, but it is a VHAR.

I initially wanted to test Raistmer's MB8_win_x86_SSE3_OpenCL_NV_SoG_r3525.7z, but now MB8_win_x86_SSE3_OpenCL_NV_SoG_r3528.7z, as I did for r3500 (which ran well on my rig).  Presently, my cache is comprised of 50 8.01 (cuda50) of which 5 are VLARs.  I'm here for testing, please tell me how you would like me to proceed.
ID: 59508 · Report as offensive
Profile Raistmer
Volunteer tester
Avatar

Send message
Joined: 18 Aug 05
Posts: 2423
Credit: 15,878,738
RAC: 0
Russia
Message 59509 - Posted: 8 Sep 2016, 18:33:59 UTC - in response to Message 59508.  


I initially wanted to test Raistmer's MB8_win_x86_SSE3_OpenCL_NV_SoG_r3525.7z, but now MB8_win_x86_SSE3_OpenCL_NV_SoG_r3528.7z, as I did for r3500 (which ran well on my rig).  Presently, my cache is comprised of 50 8.01 (cuda50) of which 5 are VLARs.  I'm here for testing, please tell me how you would like me to proceed.


Well, your GTX 950 hardly will suffer from CL file issues nor from high-prec timer not set issue. So, r3525 should work exactly as r3528 on your host. Stay with default config and crunch with r3525 till next week when r3528 will be available for auto-download. You may abort CUDAxx work for now if you don't interested in speed/precision comparison between different builds.
News about SETI opt app releases: https://twitter.com/Raistmer
ID: 59509 · Report as offensive
AMDave
Volunteer tester

Send message
Joined: 12 Jan 16
Posts: 38
Credit: 289,647
RAC: 0
United States
Message 59510 - Posted: 8 Sep 2016, 19:20:22 UTC - in response to Message 59509.  

Well, your GTX 950 hardly will suffer from CL file issues nor from high-prec timer not set issue. So, r3525 should work exactly as r3528 on your host. Stay with default config and crunch with r3525 till next week when r3528 will be available for auto-download. You may abort CUDAxx work for now if you don't interested in speed/precision comparison between different builds.


My cache has two 8.18 (opencl_nvidia_SoG).  I aborted 41 cuda50s, and Beta sent me 42 8.01 (cuda42).  Aborted those, now I have a full cache of r3525.

Task 24748253 is my first 8.18 opencl r3525 completed.

When testing r3525 & r3528, don't you want different cmdline options to be used?  Won't that require an app_info file?
ID: 59510 · Report as offensive
Profile Raistmer
Volunteer tester
Avatar

Send message
Joined: 18 Aug 05
Posts: 2423
Credit: 15,878,738
RAC: 0
Russia
Message 59513 - Posted: 9 Sep 2016, 7:23:14 UTC - in response to Message 59510.  


When testing r3525 & r3528, don't you want different cmdline options to be used?  Won't that require an app_info file?

1) No, app_info.xml not required for all kinds of testing for already deployed for distribution stock binaries.
2) Command line options can be passes via MB_cmdline*.txt files or (and I would call this more preferable way now) via app_config.xml file in its <cmdline> tag.
3) What to test:
a) How app works (speed + GUI usability) at pure default config
b) What best tuning line for particular host setup, that is, with what optional parameter settings app performs better than at default config and with acceptable GUI lags still.
c) Validness of its results.

Cause kernels file remained the same as for r3500 I put validness only third. For modifications that touch "meat" of processing chain it should be a) of course.
News about SETI opt app releases: https://twitter.com/Raistmer
ID: 59513 · Report as offensive

Message boards : SETI@home Enhanced : error code 2 (0x2) & other issues


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