Posts by mr.mac52


log in
1) Message boards : Technical News : Status Update (Nov 19, 2014) (Message 1602920)
Posted 20 Nov 2014 by Profile mr.mac52
Thanks for keeping us updated, it is much appreciated from the trenches...
2) Message boards : Number crunching : Lunatics Windows Installer v0.43 Release Notes (Message 1586658)
Posted 14 Oct 2014 by Profile mr.mac52
I updated my three systems and only had a warning from Norton Internet Security that the file had not been downloaded very many times and I blew it off and installed without any problems.

All seems to be running fine and producing results as usual.

John
3) Message boards : Number crunching : Did the work unit limit change? (Message 1515004)
Posted 12 May 2014 by Profile mr.mac52
I noticed that my work unit numbers is above the 600 mark for the first time in a long time. I currently show 837 tasks in progress when my three systems are usually limited to 600.

I just checked again and I'm at 900 tasks.

What has changed or should I just keep my mouth shut???

John
4) Message boards : Technical News : May (May 08 2014) (Message 1513823)
Posted 8 May 2014 by Profile mr.mac52
Thanks for the update on things around the lab and I hope your travel plans include some fun as well.

John
5) Message boards : Number crunching : Intel GPU app hosts with failures - please post here (Message 1482770)
Posted 28 Feb 2014 by Profile mr.mac52
I checked my overnight runs and have successfully processed my first Intel GPU work unit.

Thanks to all who contributed to getting this going!

John
6) Message boards : Number crunching : Intel GPU app hosts with failures - please post here (Message 1482549)
Posted 27 Feb 2014 by Profile mr.mac52
Ok, I checked and I do have an dummy plug in the motherboard VGA port. So I followed HAL9000 and extended the desktop to that VGA adapter and restarted BOINC. My log file now has two lines about the Intel GPU:

2/27/2014 4:32:24 PM | | OpenCL: Intel GPU 0: Intel(R) HD Graphics 4600 (driver version 9.18.10.3257, device version OpenCL 1.2, 1624MB, 1624MB available, 208 GFLOPS peak)
2/27/2014 4:32:24 PM | | OpenCL CPU: Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz (OpenCL driver vendor: Intel(R) Corporation, driver version 1.2, device version OpenCL 1.2 (Build 66956))

I did go to the Intel web site and down loaded 15.31.17.64.3257 version, file name: Win64_153117 which I believe is the correct one. The internal date in the file is: August 2, 2013. However the device manager is reporting a version of: 9.18.10.3257 which I can not explain.

So I'll wait until I see another error show up or if anyone has any other ideas as to what else is wrong...

I do appreciate everyone's assistance on this!

John
7) Message boards : Number crunching : Intel GPU app hosts with failures - please post here (Message 1482518)
Posted 27 Feb 2014 by Profile mr.mac52
OK, I'll bite, tell me what I'm doing wrong. I know it is something stupid but I'm not seeing it at this time. Also sorry that I don't recall how to make links active any more.

The host is 5409093, BIGmac, an i7-4770K

http://setiathome.berkeley.edu/show_host_detail.php?hostid=5409093

NVIDIA GeForce GTX 670 (2048MB) driver: 331.65 OpenCL: 1.01, INTEL Intel(R) HD Graphics 4600 (1624MB) OpenCL: 1.02

All my errors show up like this workunit: 1438660832

http://setiathome.berkeley.edu/workunit.php?wuid=1438660832

<core_client_version>7.2.39</core_client_version>
<![CDATA[
<message>
too many boinc_temporary_exit()s
</message>
<stderr_txt>
Running on device number: 0
Priority of worker thread raised successfully
Priority of process adjusted successfully, below normal priority class used
WARNING: boinc_get_opencl_ids failed with code -1
OpenCL platform detected: NVIDIA Corporation
OpenCL platform detected: Intel(R) Corporation
WARNING: BOINC supplied wrong platform!
ERROR: OpenCL kernel/call 'clGetDeviceIDs' call failed (-1) in file ..\..\..\src\GPU_lock.cpp near line 672.
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
WARNING: boinc_get_opencl_ids failed with code -1
OpenCL platform detected: NVIDIA Corporation
OpenCL platform detected: Intel(R) Corporation
WARNING: BOINC supplied wrong platform!
ERROR: OpenCL kernel/call 'clGetDeviceIDs' call failed (-1) in file ..\..\..\src\GPU_lock.cpp near line 672.
.
.
.

app_info.xml
<app_info>
<app>
<name>setiathome_v7</name>
</app>
<file_info>
<name>setiathome_7.03_windows_intelx86__opencl_intel_gpu_sah.exe</name>
<executable/>
</file_info>
<file_info>
<name>MultiBeam_Kernels_r2061_windows_intel_gpu.cl</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3.dll</name>
<executable/>
</file_info>
<file_info>
<name>mb_cmdline-7.03-opencl_intel_gpu_sah.txt</name>
</file_info>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>703</version_num>
<platform>windows_intelx86</platform>
<coproc>
<type>intel_gpu</type>
<count>1</count>
</coproc>
<plan_class>opencl_intel_gpu_sah</plan_class>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.04</max_ncpus>
<file_ref>
<file_name>setiathome_7.03_windows_intelx86__opencl_intel_gpu_sah.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r2061_windows_intel_gpu.cl</file_name>
<open_name>MultiBeam_Kernels_r2061.cl</open_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>mb_cmdline-7.03-opencl_intel_gpu_sah.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
</app_version>
<app>
<name>setiathome_v7</name>
</app>
<file_info>
<name>AKv8c_Bb_r1846_winx86_AVXx.exe</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3.dll</name>
<executable/>
</file_info>
<file_info>
<name>AKv8c_Bb_r1846_winx86_AVXx.txt</name>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<platform>windows_x86_64</platform>
<file_ref>
<file_name>AKv8c_Bb_r1846_winx86_AVXx.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>AKv8c_Bb_r1846_winx86_AVXx.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>700</version_num>
<platform>windows_x86_64</platform>
<file_ref>
<file_name>AKv8c_Bb_r1846_winx86_AVXx.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>AKv8c_Bb_r1846_winx86_AVXx.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AKv8c_Bb_r1846_winx86_AVXx.exe</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3.dll</name>
<executable/>
</file_info>
<file_info>
<name>AKv8c_Bb_r1846_winx86_AVXx.txt</name>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<platform>windows_x86_64</platform>
<file_ref>
<file_name>AKv8c_Bb_r1846_winx86_AVXx.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>AKv8c_Bb_r1846_winx86_AVXx.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
</app_version>
<app>
<name>astropulse_v6</name>
</app>
<file_info>
<name>AP6_win_x86_SSE2_OpenCL_NV_r1843.exe</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3.dll</name>
<executable/>
</file_info>
<file_info>
<name>ap_cmdline_win_x86_SSE2_OpenCL_NV.txt</name>
</file_info>
<file_info>
<name>AstroPulse_Kernels_r1843.cl</name>
</file_info>
<app_version>
<app_name>astropulse_v6</app_name>
<version_num>604</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>cuda_opencl_100</plan_class>
<cmdline></cmdline>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>AP6_win_x86_SSE2_OpenCL_NV_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>ap_cmdline_win_x86_SSE2_OpenCL_NV.txt</file_name>
<open_name>ap_cmdline.txt</open_name>
</file_ref>
<file_ref>
<file_name>AstroPulse_Kernels_r1843.cl</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse_v6</app_name>
<version_num>604</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>opencl_nvidia_100</plan_class>
<cmdline></cmdline>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>AP6_win_x86_SSE2_OpenCL_NV_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>ap_cmdline_win_x86_SSE2_OpenCL_NV.txt</file_name>
<open_name>ap_cmdline.txt</open_name>
</file_ref>
<file_ref>
<file_name>AstroPulse_Kernels_r1843.cl</file_name>
</file_ref>
</app_version>
<app>
<name>astropulse_v6</name>
</app>
<file_info>
<name>AP6_win_x86_SSE_CPU_r1797.exe</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3.dll</name>
<executable/>
</file_info>
<file_info>
<name>ap_cmdline_win_x86_SSE_CPU.txt</name>
</file_info>
<app_version>
<app_name>astropulse_v6</app_name>
<version_num>601</version_num>
<platform>windows_x86_64</platform>
<cmdline></cmdline>
<file_ref>
<file_name>AP6_win_x86_SSE_CPU_r1797.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>ap_cmdline_win_x86_SSE_CPU.txt</file_name>
<open_name>ap_cmdline.txt</open_name>
</file_ref>
</app_version>
<app>
<name>setiathome_v7</name>
</app>
<file_info>
<name>Lunatics_x41zc_win32_cuda50.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart32_50_35.dll</name>
<executable/>
</file_info>
<file_info>
<name>cufft32_50_35.dll</name>
<executable/>
</file_info>
<file_info>
<name>mbcuda.cfg</name>
</file_info>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>700</version_num>
<platform>windows_x86_64</platform>
<plan_class>cuda50</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zc_win32_cuda50.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>mbcuda.cfg</file_name>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>Lunatics_x41zc_win32_cuda50.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart32_50_35.dll</name>
<executable/>
</file_info>
<file_info>
<name>cufft32_50_35.dll</name>
<executable/>
</file_info>
<file_info>
<name>mbcuda.cfg</name>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>610</version_num>
<platform>windows_x86_64</platform>
<plan_class>cuda_fermi</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zc_win32_cuda50.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>mbcuda.cfg</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</version_num>
<platform>windows_x86_64</platform>
<plan_class>cuda</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zc_win32_cuda50.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>mbcuda.cfg</file_name>
</file_ref>
</app_version>
</app_info>



From my BOINC Manager log file:

2/27/2014 3:14:21 PM | | cc_config.xml not found - using defaults
2/27/2014 3:14:21 PM | | Starting BOINC client version 7.2.39 for windows_x86_64
2/27/2014 3:14:21 PM | | log flags: file_xfer, sched_ops, task
2/27/2014 3:14:21 PM | | Libraries: libcurl/7.25.0 OpenSSL/1.0.1 zlib/1.2.6
2/27/2014 3:14:21 PM | | Data directory: M:\John McClelland Data\ProgramData\BOINC
2/27/2014 3:14:21 PM | | Running under account John McClelland
2/27/2014 3:14:21 PM | | CUDA: NVIDIA GPU 0: GeForce GTX 670 (driver version 331.65, CUDA version 6.0, compute capability 3.0, 2048MB, 1948MB available, 2915 GFLOPS peak)
2/27/2014 3:14:21 PM | | OpenCL: NVIDIA GPU 0: GeForce GTX 670 (driver version 331.65, device version OpenCL 1.1 CUDA, 2048MB, 1948MB available, 2915 GFLOPS peak)
2/27/2014 3:14:21 PM | | OpenCL CPU: Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz (OpenCL driver vendor: Intel(R) Corporation, driver version 1.2, device version OpenCL 1.2 (Build 66956))
2/27/2014 3:14:21 PM | SETI@home | Found app_info.xml; using anonymous platform
2/27/2014 3:14:21 PM | | app version refers to missing GPU type intel_gpu
2/27/2014 3:14:21 PM | SETI@home | [error] State file error: bad application name setiathome_enhanced
2/27/2014 3:14:21 PM | | app version refers to missing GPU type intel_gpu
2/27/2014 3:14:21 PM | SETI@home | Missing coprocessor for task 16my13ab.18736.7811.438086664208.12.184_1
2/27/2014 3:14:21 PM | SETI@home | Missing coprocessor for task 16my13ab.18736.7811.438086664208.12.188_0
2/27/2014 3:14:21 PM | SETI@home | Missing coprocessor for task 16my13ab.18736.7811.438086664208.12.186_0
2/27/2014 3:14:21 PM | SETI@home | Missing coprocessor for task 26au13aa.21194.15200.438086664204.12.77_2
2/27/2014 3:14:21 PM | | Host name: bigMAC
2/27/2014 3:14:21 PM | | Processor: 8 GenuineIntel Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz [Family 6 Model 60 Stepping 3]
2/27/2014 3:14:21 PM | | Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss htt tm pni ssse3 fma cx16 sse4_1 sse4_2 movebe popcnt aes syscall nx lm vmx tm2 pbe
2/27/2014 3:14:21 PM | | OS: Microsoft Windows 7: Ultimate x64 Edition, Service Pack 1, (06.01.7601.00)
2/27/2014 3:14:21 PM | | Memory: 7.89 GB physical, 15.78 GB virtual
2/27/2014 3:14:21 PM | | Disk: 1.82 TB total, 1.33 TB free
2/27/2014 3:14:21 PM | | Local time is UTC -7 hours
2/27/2014 3:14:21 PM | SETI@home | Found app_config.xml
2/27/2014 3:14:21 PM | SETI@home | URL http://setiathome.berkeley.edu/; Computer ID 5409093; resource share 5000
2/27/2014 3:14:21 PM | SETI@home | General prefs: from SETI@home (last modified 08-Jun-2013 18:38:46)
2/27/2014 3:14:21 PM | SETI@home | Computer location: home
2/27/2014 3:14:21 PM | SETI@home | General prefs: no separate prefs for home; using your defaults
2/27/2014 3:14:21 PM | | Reading preferences override file
2/27/2014 3:14:21 PM | | Preferences:
2/27/2014 3:14:21 PM | | max memory usage when active: 7675.05MB
2/27/2014 3:14:21 PM | | max memory usage when idle: 8079.00MB
2/27/2014 3:14:21 PM | | max disk usage: 500.00GB
2/27/2014 3:14:21 PM | | (to change preferences, visit a project web site or select Preferences in the Manager)
2/27/2014 3:14:21 PM | | Not using a proxy
2/27/2014 3:14:24 PM | | Running CPU benchmarks
2/27/2014 3:14:24 PM | | Suspending computation - CPU benchmarks in progress
[/url]
8) Message boards : Number crunching : Change Request:Let Client Assign Work to GPU or CPU as needed (Message 1475907)
Posted 12 Feb 2014 by Profile mr.mac52
Jason, Thanks for such a great overview of the direction the project is moving. If not for you and the others we see every day in this forum, we'd be totally in the dark. Great job!

John
9) Message boards : Number crunching : Logmein.com (Message 1467073)
Posted 21 Jan 2014 by Profile mr.mac52
I have been using TeamViewer for 4 or 5 years now and have never had a problem that I could not solve. If they stop the free personal use I'll be really bummed out.

John
10) Message boards : Number crunching : Haswell CPU Question (Message 1465305)
Posted 17 Jan 2014 by Profile mr.mac52
My understanding on Haswell is that Intel redesigned the internal heat spreader and rather than soldering it, they are now using a thermal paste. There are lots of online postings about 'delidding' Haswell and using alternative TIM products. I have not done this on my i7-4770K as of yet but am considering it. Typical benefit is a lowering of core temperatures by roughly 20°C. YMMV

John
11) Message boards : Number crunching : Heads up on NVIDIA driver 331.82 (Message 1444554)
Posted 20 Nov 2013 by Profile mr.mac52
I had the same experience with 331.65 and a second clean install with manual reboot solved it for me.

John
12) Message boards : News : Berkeley SETI at California Academy of Sciences (Message 1426754)
Posted 10 Oct 2013 by Profile mr.mac52
+1
13) Message boards : Number crunching : Observation of CreditNew Impact (2) (Message 1403450)
Posted 15 Aug 2013 by Profile mr.mac52
Eric, thanks for the details in your posting, I actually think I understand it! I know, that's a scary thought...

John
14) Message boards : Technical News : Emergence (Aug 13 2013) (Message 1402831)
Posted 13 Aug 2013 by Profile mr.mac52
Thanks Matt, nice to hear from you and some of what is going on down home.

John
15) Message boards : Technical News : Spring Cleaning (Jun 19 2013) (Message 1382845)
Posted 19 Jun 2013 by Profile mr.mac52
Understanding the backstory about SETI@home helps make sense of what we volunteers experience on a daily basis.

Thanks for keeping this line of communications open and functional Matt!

John
16) Message boards : Number crunching : Lunatic's app_info cleanup (Message 1379079)
Posted 9 Jun 2013 by Profile mr.mac52
Thanks Richard!

I have looked at the application page before but I didn't recall the relationships documented there, makes it much clearer now.

On my small-seti system I got down to the last two tasks before I 'cleaned up' my app_info.xml file and restarted BOINC, blowing those two off. After that everything started downloading and rebuilding my work cache.

Thanks for pointing me to the answer of my silly questions.

John
17) Message boards : Number crunching : Lunatic's app_info cleanup (Message 1379041)
Posted 9 Jun 2013 by Profile mr.mac52
In the <name>setiathome_enhanced</name> section, the <plan_class> has a couple of differences in my case than the other similar entries in the other sections.

In the <version_num>610</version_num>, the <plan_class> is cuda_fermi which I think maybe cuda42.

In the <version_num>608</version_num>, the <plan_class> is just plain cuda which I think could be cuda50.

Anyone know for sure or have the secret decoder ring?

Thanks for all the hard work on getting the new app_info info out!

John
18) Message boards : Number crunching : VLAR's to Kepler cards. (Message 1376234)
Posted 3 Jun 2013 by Profile mr.mac52
Thanks Fred, I'll take your advice and not move the GPU VLAR's to the CPU any more. The rescheduler was a very handy tool back in the day!

John
19) Message boards : Number crunching : VLAR's to Kepler cards. (Message 1374876)
Posted 1 Jun 2013 by Profile mr.mac52
When I started seeing a lot of .VLARs I went digging for my copy of the old BOINCrescheduler64 and tried it with no success. I can't even recall where I got it or who's project it was but I wonder if it could be updated to shift all the CUDA .VLARs to the CPU in today's environment.

John
20) Message boards : Technical News : Colo! (Mar 28 2013) (Message 1351953)
Posted 29 Mar 2013 by Profile mr.mac52
I am always amazed about how much you do with so little gear. Best wishes and hope you don't have to pull any all nighters getting it up and running on the flip side.

John


Next 20

Copyright © 2014 University of California