Seti@Home optimized science apps and information
Optimized Seti@Home apps => Windows => GPU crunching => Topic started by: PatrickV2 on 21 Nov 2009, 05:45:40 am
-
Hi there,
I recently installed Win7-64bits on a Q6600/8800GTX machine of mine, and installed BOINC 6.10.18. GPU was recognized, and apparantly specific WU's are downloaded for cuda. So I'm still running the stock executables, and I like the way it behaves.
I also downloaded from Lunatics, the installer: "Lunatics_Win64v0.2_(SSE3+)_AP505r168_AKv8bx64_CudaV12.exe", but am not sure what happens after I install it.
I know from experience the CPU-executables will increase crunching throughput, but looking through the forums, and looking at terms like 'VLAR-Kill', 'rebranding', etc, I'm wondering what happens with the GPU-part of my crunching activities? Will the new GPU/CUDA executables still only crunch the 'cuda'-marked WU's, or will something change? Will the 'Use GPU only when machine is idle'-option also still work after installing the updated executables?
Best regards amd thanks in advance for any answers,
Patrick.
-
with 8800 and win7 my experience is that you don't have enought GPU memory and you need to disable some AERO features.
Franz
-
with 8800 and win7 my experience is that you don't have enought GPU memory and you need to disable some AERO features.
Franz
No problems here, Aero was working fine when I had the GPU crunching always enabled. Problems were games, which were running very slowly with the cuda app active. As could be expected. Which is why I set the option to only enable GPU crunching when my computer is idle. Works quite nicely.
Anyway, we're about 1.5 days along, and about 65 views along... If the verdict is that nothing will change (except the crunch-times will go down even further) afer installing the Lunatics pack, I'm all for it. But I'm not 100% sure, so that's why I ask here....
TIA, Regards,
Patrick.
-
Well, still no authoritative response here, so I made a backup of my BOINC & BOINC_Data directories and installed the Lunatics pack, installing the SSSE3 and the CUDA apps.
After restarting BOINC, all existing cuda WUs were deleted and since I had no CPU tasks, that list was empty too. And, because the servers are apparently down, I could not get any new work.
So I restored my backup, and am now back to the original situation.
The question still stands: how do I install the optimized apps while still retaining the original behaviour? Why did BOINC delete the cuda-specific WUs it had already downloaded?
Will I get the wanted behaviour if I only install the SSSE3_x64 apps, and leave the cuda app in the original state?
Anyone?
Update: Nope, only installing the SSSE3 CPU apps also results in ALL cuda WUs being deleted and all CPU WUs also being deleted because their state file is incorrect.
So, what do I do? Empty the current cache, and only then install the new apps? And, again, how will that setup behave itself?
Regards, Patrick.
-
What exactly did Boinc say when it deleted your tasks?
Claggy
-
What exactly did Boinc say when it deleted your tasks?
Claggy
I don't have the exact logging anymore, but the cuda tasks were deleted because there was no app in the app_info.xml file to process them.
The CPU tasks were deleted with a notice about an incorrect state or something.
If you want the precise text, I'd have to redo the installation and nuke of the WUs.
Regards, Patrick.
-
OK, I just re-did the re-install and blowing up of my BOINC install, the relevant logging right after having done the install, and restarting the client is:
26-Nov-09 00:36:14 Starting BOINC client version 6.10.18 for windows_x86_64
26-Nov-09 00:36:14 log flags: file_xfer, sched_ops, task
26-Nov-09 00:36:14 Libraries: libcurl/7.19.4 OpenSSL/0.9.8l zlib/1.2.3
26-Nov-09 00:36:14 Data directory: D:\WinApps\BOINC_Data
26-Nov-09 00:36:14 Running under account Patrick
26-Nov-09 00:36:14 Processor: 4 GenuineIntel Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz [Intel64 Family 6 Model 15 Stepping 11]
26-Nov-09 00:36:14 Processor: 4.00 MB cache
26-Nov-09 00:36:14 Processor features: fpu tsc pae nx sse sse2 pni
26-Nov-09 00:36:14 OS: Microsoft Windows 7: Ultimate x64 Edition, (06.01.7600.00)
26-Nov-09 00:36:14 Memory: 4.00 GB physical, 8.00 GB virtual
26-Nov-09 00:36:14 Disk: 426.70 GB total, 282.43 GB free
26-Nov-09 00:36:14 Local time is UTC +1 hours
26-Nov-09 00:36:14 NVIDIA GPU 0: GeForce 8800 GTX (driver version 19107, CUDA version 2030, compute capability 1.0, 768MB, 346 GFLOPS peak)
26-Nov-09 00:36:14 SETI@home Found app_info.xml; using anonymous platform
26-Nov-09 00:36:14 SETI@home [error] No application found for task: windows_intelx86 608 cuda; discarding
26-Nov-09 00:36:14 SETI@home [error] No application found for task: windows_intelx86 608 cuda; discarding
26-Nov-09 00:36:14 SETI@home [error] No application found for task: windows_intelx86 608 cuda; discarding
26-Nov-09 00:36:14 SETI@home [error] No application found for task: windows_intelx86 608 cuda; discarding
26-Nov-09 00:36:14 SETI@home [error] No application found for task: windows_intelx86 608 cuda; discarding
26-Nov-09 00:36:14 SETI@home [error] No application found for task: windows_intelx86 608 cuda; discarding
26-Nov-09 00:36:14 SETI@home [error] No application found for task: windows_intelx86 608 cuda; discarding
26-Nov-09 00:36:14 SETI@home [error] No application found for task: windows_intelx86 608 cuda; discarding
26-Nov-09 00:36:14 SETI@home [error] No application found for task: windows_intelx86 608 cuda; discarding
26-Nov-09 00:36:14 SETI@home [error] No application found for task: windows_intelx86 608 cuda; discarding
26-Nov-09 00:36:14 SETI@home [error] No application found for task: windows_intelx86 608 cuda; discarding
26-Nov-09 00:36:14 SETI@home [error] No application found for task: windows_intelx86 608 cuda; discarding
26-Nov-09 00:36:14 SETI@home [error] No application found for task: windows_intelx86 608 cuda; discarding
26-Nov-09 00:36:14 SETI@home [error] No application found for task: windows_intelx86 608 cuda; discarding
26-Nov-09 00:36:14 SETI@home [error] No application found for task: windows_intelx86 608 cuda; discarding
26-Nov-09 00:36:14 SETI@home [error] No application found for task: windows_intelx86 608 cuda; discarding
26-Nov-09 00:36:14 SETI@home [error] No application found for task: windows_intelx86 608 cuda; discarding
26-Nov-09 00:36:14 SETI@home [error] No application found for task: windows_intelx86 608 cuda; discarding
26-Nov-09 00:36:14 SETI@home [error] No application found for task: windows_intelx86 608 cuda; discarding
26-Nov-09 00:36:14 SETI@home [error] No application found for task: windows_intelx86 608 cuda; discarding
26-Nov-09 00:36:14 SETI@home [error] No application found for task: windows_intelx86 608 cuda; discarding
26-Nov-09 00:36:14 SETI@home [error] No application found for task: windows_intelx86 608 cuda; discarding
26-Nov-09 00:36:14 SETI@home [error] No application found for task: windows_intelx86 608 cuda; discarding
26-Nov-09 00:36:14 SETI@home [error] No application found for task: windows_intelx86 608 cuda; discarding
26-Nov-09 00:36:14 SETI@home [error] No application found for task: windows_intelx86 608 cuda; discarding
26-Nov-09 00:36:14 SETI@home [error] No application found for task: windows_intelx86 608 cuda; discarding
26-Nov-09 00:36:14 SETI@home [error] No application found for task: windows_intelx86 608 cuda; discarding
26-Nov-09 00:36:14 SETI@home [error] No application found for task: windows_intelx86 608 cuda; discarding
26-Nov-09 00:36:14 SETI@home [error] No application found for task: windows_intelx86 608 cuda; discarding
26-Nov-09 00:36:14 SETI@home [error] No application found for task: windows_intelx86 608 cuda; discarding
26-Nov-09 00:36:14 SETI@home [error] No application found for task: windows_intelx86 608 cuda; discarding
26-Nov-09 00:36:14 SETI@home [error] No application found for task: windows_intelx86 608 cuda; discarding
26-Nov-09 00:36:14 SETI@home [error] No application found for task: windows_intelx86 608 cuda; discarding
26-Nov-09 00:36:14 SETI@home [error] No application found for task: windows_intelx86 608 cuda; discarding
26-Nov-09 00:36:14 SETI@home [error] No application found for task: windows_intelx86 608 cuda; discarding
26-Nov-09 00:36:14 SETI@home [error] No application found for task: windows_intelx86 608 cuda; discarding
26-Nov-09 00:36:14 SETI@home [error] No application found for task: windows_intelx86 608 cuda; discarding
26-Nov-09 00:36:14 SETI@home [error] No application found for task: windows_intelx86 608 cuda; discarding
26-Nov-09 00:36:14 SETI@home [error] No application found for task: windows_intelx86 608 cuda; discarding
26-Nov-09 00:36:14 SETI@home [error] No application found for task: windows_intelx86 603 ; discarding
26-Nov-09 00:36:14 SETI@home [error] No application found for task: windows_intelx86 603 ; discarding
26-Nov-09 00:36:14 SETI@home [error] No application found for task: windows_intelx86 603 ; discarding
26-Nov-09 00:36:14 SETI@home [error] No application found for task: windows_intelx86 603 ; discarding
26-Nov-09 00:36:14 SETI@home [error] No application found for task: windows_intelx86 603 ; discarding
26-Nov-09 00:36:14 SETI@home [error] State file error: result 11oc06aa.7629.890.13.10.62_1 not found for task
26-Nov-09 00:36:14 SETI@home [error] State file error: result 11oc06aa.30821.890.12.10.85_1 not found for task
26-Nov-09 00:36:14 SETI@home [error] State file error: result 11oc06aa.30821.1299.12.10.236_1 not found for task
26-Nov-09 00:36:14 SETI@home [error] State file error: result 02se09ab.14973.4975.14.10.93_2 not found for task
26-Nov-09 00:36:14 SETI@home [error] State file error: result 03mr07ab.2677.20522.15.10.248_1 not found for task
26-Nov-09 00:36:14 Not using a proxy
and then it continues 'as expected' requesting new work.
Regards, Patrick.
-
If you still have the unchanged copy of your Boinc Backup, you still might be okay.
In the copy you have a file called client_state.xml under the section for Seti It tells what Applications are supposed to be present. That is what is needed.
The trick, is to add a section to the app_info.xml that gives the name of the Stock MB Cuda application that points to the optimized application. You can even make a copy of the optimized app and rename the same as the stock app. Then run work down to ZERO and removed the cludged information form the app_info.xml
So without seeing your app_info.xml it makes it very tough to "guess" Your log shows something does not compare between the client_state.xml and the app_info.xml
Please post a copy of your app_info.xml
Regards
-
If you still have the unchanged copy of your Boinc Backup, you still might be okay.
In the copy you have a file called client_state.xml under the section for Seti It tells what Applications are supposed to be present. That is what is needed.
The trick, is to add a section to the app_info.xml that gives the name of the Stock MB Cuda application that points to the optimized application. You can even make a copy of the optimized app and rename the same as the stock app. Then run work down to ZERO and removed the cludged information form the app_info.xml
So without seeing your app_info.xml it makes it very tough to "guess" Your log shows something does not compare between the client_state.xml and the app_info.xml
Please post a copy of your app_info.xml
Regards
Here it is.
Regards,
Patrick.
[attachment deleted by admin]
-
OK, I just re-did the re-install and blowing up of my BOINC install, the relevant logging right after having done the install, and restarting the client is:
26-Nov-09 00:36:14 Starting BOINC client version 6.10.18 for windows_x86_64
26-Nov-09 00:36:14 log flags: file_xfer, sched_ops, task
26-Nov-09 00:36:14 Libraries: libcurl/7.19.4 OpenSSL/0.9.8l zlib/1.2.3
26-Nov-09 00:36:14 Data directory: D:\WinApps\BOINC_Data
26-Nov-09 00:36:14 Running under account Patrick
26-Nov-09 00:36:14 Processor: 4 GenuineIntel Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz [Intel64 Family 6 Model 15 Stepping 11]
26-Nov-09 00:36:14 Processor: 4.00 MB cache
26-Nov-09 00:36:14 Processor features: fpu tsc pae nx sse sse2 pni
26-Nov-09 00:36:14 OS: Microsoft Windows 7: Ultimate x64 Edition, (06.01.7600.00)
26-Nov-09 00:36:14 Memory: 4.00 GB physical, 8.00 GB virtual
26-Nov-09 00:36:14 Disk: 426.70 GB total, 282.43 GB free
26-Nov-09 00:36:14 Local time is UTC +1 hours
26-Nov-09 00:36:14 NVIDIA GPU 0: GeForce 8800 GTX (driver version 19107, CUDA version 2030, compute capability 1.0, 768MB, 346 GFLOPS peak)
26-Nov-09 00:36:14 SETI@home Found app_info.xml; using anonymous platform
26-Nov-09 00:36:14 SETI@home [error] No application found for task: windows_intelx86 608 cuda; discarding
snip
26-Nov-09 00:36:14 SETI@home [error] State file error: result 11oc06aa.7629.890.13.10.62_1 not found for task
26-Nov-09 00:36:14 SETI@home [error] State file error: result 11oc06aa.30821.890.12.10.85_1 not found for task
26-Nov-09 00:36:14 SETI@home [error] State file error: result 11oc06aa.30821.1299.12.10.236_1 not found for task
26-Nov-09 00:36:14 SETI@home [error] State file error: result 02se09ab.14973.4975.14.10.93_2 not found for task
26-Nov-09 00:36:14 SETI@home [error] State file error: result 03mr07ab.2677.20522.15.10.248_1 not found for task
26-Nov-09 00:36:14 Not using a proxy
and then it continues 'as expected' requesting new work.
Regards, Patrick.
The Problem is you're changed from a 32bit version of Windows/Boinc to the 64 bit version, and they are different platforms,
putting a platform tag of 'windows_intelx86' in you're app_info should fix it for now,
but you might want to run down your tasks, detach/reattach (to clear the x86 platform from your client_state.xml),
then reinstall the optimised apps.
Edit: Here's a modified app_info, try it:
<app_info>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AK_v8b_win_x64_SSSE3x.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>528</version_num>
<file_ref>
<file_name>AK_v8b_win_x64_SSSE3x.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<file_ref>
<file_name>AK_v8b_win_x64_SSSE3x.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>astropulse_v5</name>
</app>
<file_info>
<name>ap_5.03r112_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v5</app_name>
<version_num>503</version_num>
<file_ref>
<file_name>ap_5.03r112_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>astropulse_v505</name>
</app>
<file_info>
<name>ap_5.05r168_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v505</app_name>
<version_num>505</version_num>
<file_ref>
<file_name>ap_5.05r168_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>MB_6.08_CUDA_V12_VLARKill_FPLim2048.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart.dll</name>
<executable/>
</file_info>
<file_info>
<name>cufft.dll</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3-1-1a_upx.dll</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</version_num>
<plan_class>cuda</plan_class>
<platform>windows_intelx86</platform>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>MB_6.08_CUDA_V12_VLARKill_FPLim2048.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
</app_version>
</app_info>
Claggy
-
The Problem is you're changed from a 32bit version of Windows/Boinc to the 64 bit version, and they are different platforms,
putting a platform tag of 'windows_intelx86' in you're app_info should fix it for now,
but you might want to run down your tasks, detach/reattach (to clear the x86 platform from your client_state.xml),
then reinstall the optimised apps.
<app_info>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AK_v8b_win_x64_SSSE3x.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>528</version_num>
<file_ref>
<file_name>AK_v8b_win_x64_SSSE3x.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<file_ref>
<file_name>AK_v8b_win_x64_SSSE3x.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>astropulse_v5</name>
</app>
<file_info>
<name>ap_5.03r112_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v5</app_name>
<version_num>503</version_num>
<file_ref>
<file_name>ap_5.03r112_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>astropulse_v505</name>
</app>
<file_info>
<name>ap_5.05r168_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v505</app_name>
<version_num>505</version_num>
<file_ref>
<file_name>ap_5.05r168_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>MB_6.08_CUDA_V12_VLARKill_FPLim2048.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart.dll</name>
<executable/>
</file_info>
<file_info>
<name>cufft.dll</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3-1-1a_upx.dll</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</version_num>
<plan_class>cuda</plan_class>
<platform>windows_intelx86</platform>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>MB_6.08_CUDA_V12_VLARKill_FPLim2048.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
</app_version>
</app_info>
Claggy
But, but, I installed the following BOINC package on this machine:
boinc_6.10.18_windows_x86_64.exe
(downloaded from the official site). Is this a known problem with this package?
Regards,
Patrick.
-
But, but, I installed the following BOINC package on this machine:
boinc_6.10.18_windows_x86_64.exe
(downloaded from the official site). Is this a known problem with this package?
Regards,
Patrick.
But What Windows / Boinc combination was your backup running prevously?
Claggy
-
But, but, I installed the following BOINC package on this machine:
boinc_6.10.18_windows_x86_64.exe
(downloaded from the official site). Is this a known problem with this package?
Regards,
Patrick.
But What Windows / Boinc combination was your backup running prevously?
Claggy
I do not understand your question? The machine is a fresh install, with a fresh install of the mentioned BOINC package. It also got a new ID when I attached the machine to setiathome....
Regards,
Patrick.
-
But, but, I installed the following BOINC package on this machine:
boinc_6.10.18_windows_x86_64.exe
(downloaded from the official site). Is this a known problem with this package?
Regards,
Patrick.
But What Windows / Boinc combination was your backup running prevously?
Claggy
I do not understand your question? The machine is a fresh install, with a fresh install of the mentioned BOINC package. It also got a new ID when I attached the machine to setiathome....
Regards,
Patrick.
Sorry, i thought you had saved your Boinc and your Boinc Data folder's from a prevous installation of windows.
Try restoring your backup folder's again, do a repair installation of Boinc, install the optimised apps again, then replace the app_info with the one i posted above.
Claggy
-
Sorry, i thought you had saved your Boinc and your Boinc Data folder's from a prevous installation of windows.
Try restoring your backup folder's again, do a repair installation of Boinc, install the optimised apps again, then replace the app_info with the one i posted above.
Claggy
No sorry necessary, I was perhaps not clear enough in my OP. I did what you described, just restarted BOINC, and it now at least did not throw away the entire set of WUs. However, since BOINC is down and I had set the caches pretty low, I have no CPU work left. Anyway, cuda seems to be restarting, so we'll see how it goes.
Now, should I use this setup to empty the cache, or should I let it start fetching WUs again?
Regards,
Patrick.
-
Probably just leave it as it is for now,
i had problems with the different platform tags when the first multi app app_info's were posted,
you couldn't just remove the platform tag from the app_info, as it would still be in the client_state.xml,
and i don't think things worked properly, a detach/reattach would clear the platform tag from the client_state.xml
and set the seti portion of it back to normal.
Claggy
-
Probably just leave it as it is for now,
i had problems with the different platform tags when the first multi app app_info's were posted,
you couldn't just remove the platform tag from the app_info, as it would still be in the client_state.xml,
and i don't think things worked properly, a detach/reattach would clear the platform tag from the client_state.xml
and set the seti portion of it back to normal.
Claggy
Well, the machine just finished the last few, cuda-only, WU's it still had (about 10 or so) but 4 of these ended with a 'Calculation error'. *sigh*
So, err, without trying to downscale your efforts, how do I run the optimized CPU-apps, but keep the official setiathome cuda app, since that seems to be a bit more stable?
Regards,
Patrick.
-
So, err, without trying to downscale your efforts, how do I run the optimized CPU-apps, but keep the official setiathome cuda app, since that seems to be a bit more stable?
Regards,
Patrick.
More stable ??
Did you bother to look on stderr for reason of computation error?
-
So, err, without trying to downscale your efforts, how do I run the optimized CPU-apps, but keep the official setiathome cuda app, since that seems to be a bit more stable?
Regards,
Patrick.
More stable ??
Did you bother to look on stderr for reason of computation error?
I tried to find the reason yes, but couldn't find anything. Where is the stderr output located?
Regards, Patrick.
-
Look at result page on website.
-
Look at result page on website.
Aha, all 4 we-re VLAR-kills:
<core_client_version>6.10.18</core_client_version>
<![CDATA[
<message>
- exit code -6 (0xfffffffa)
</message>
<stderr_txt>
VLAR WU (AR: 0.010757 )detected... autokill initialised
SETI@home error -6 Bad workunit header
File: ..\worker.cpp
Line: 144
</stderr_txt>
]]>
What would the 'regular' cuda app have done with these? Started the calculation and barfed out in-flight?
Regards,
Patrick.
-
Look at result page on website.
Aha, all 4 we-re VLAR-kills:
<core_client_version>6.10.18</core_client_version>
<![CDATA[
<message>
- exit code -6 (0xfffffffa)
</message>
<stderr_txt>
VLAR WU (AR: 0.010757 )detected... autokill initialised
SETI@home error -6 Bad workunit header
File: ..\worker.cpp
Line: 144
</stderr_txt>
]]>
What would the 'regular' cuda app have done with these? Started the calculation and barfed out in-flight?
Regards,
Patrick.
The stock Cuda app would have done the work, but would have done it at close to CPU speed,
on my 9800GTX+ they take over an hour to do, against 15 to 20 mins on mid range AR's.
Claggy
-
Look at result page on website.
Aha, all 4 we-re VLAR-kills:
<core_client_version>6.10.18</core_client_version>
<![CDATA[
<message>
- exit code -6 (0xfffffffa)
</message>
<stderr_txt>
VLAR WU (AR: 0.010757 )detected... autokill initialised
SETI@home error -6 Bad workunit header
File: ..\worker.cpp
Line: 144
</stderr_txt>
]]>
What would the 'regular' cuda app have done with these? Started the calculation and barfed out in-flight?
Regards,
Patrick.
The stock Cuda app would have done the work, but would have done it at close to CPU speed,
on my 9800GTX+ they take over an hour to do, against 15 to 20 mins on mid range AR's.
Claggy
I would not really mind having such units take the same time as on the CPU really; abandoning/'killing' them seems also rather harsh? Or does that have little impact on Seti@Home? Will my machine not be 'marked' as being unreliable in the seti database when it kills off units on a regular basis?
Also, I finally got some work for my machine, but the 8800GTX is taking about 5 to 7 minutes per cuda unit. That is as to be expected?
EDIT: Oh wait, that's not the 'real' time, as I just watched the counter going up. I suppose I could get the real time from the errlog from the seti website?
Same question for the CPU units: ~2 hours / unit on a non-overclocked Q6600?
Regards, Patrick.
-
Use the rebranding program to move the VLAR Wu's to the CPU.
Claggy
-
Use the rebranding program to move the VLAR Wu's to the CPU.
Claggy
OK, thread has 18 pages, and I see a V2 and V3 being posted on the first page. Checked the last 2 pages, no updates. Public beta and GPU areas do not contain it.
What's the most up-to-date rebranding tool, and how should this be run? Daily? Hourly?
Regards,
Patrick.
-
The latest version is on Page 13:
Re: CPU <-> GPU rebranding (http://lunatics.kwsn.net/12-gpu-crunching/cpu-gpu-rebranding-perl-script.msg19454.html#msg19454)
How often you run the rescheduling tool depends on your cache size, if you're got a larger cache you'll have a bit more time to reschedule any VLAR's,
with a smaller cache you'll need to run it more often to make sure any VLAR's don't get to the top of the cache and onto the GPU,
Claggy
-
The latest version is on Page 13:
Re: CPU <-> GPU rebranding (http://lunatics.kwsn.net/12-gpu-crunching/cpu-gpu-rebranding-perl-script.msg19454.html#msg19454)
How often you run the rescheduling tool depends on your cache size, if you're got a larger cache {ou'll have a bit more time to reschedule any VLAR's,
with a smaller cache you'll need to run it more often to make sure any VLAR's don't get to the top of the cache and onto the GPU,
Claggy
Thanks for point me in the right direction (towards the right page would be the better term ;)). Isn't it perhaps an option to put the rebranding tool in a more obvious place; this would also lessen the chances of someone downloading an old/outdated version of the tool?
However, I currently have another, non-Lunatics-related probably, problem with BOINC on the aforementioned machine:
It does not want to download WUs after it has been running for a while. I get the following errors (a small copy-paste selection):
01-Dec-09 18:38:54 SETI@home Started download of 16no06ac.7279.1299.11.10.3
01-Dec-09 18:38:54 SETI@home Started download of 16no06ab.22684.25021.16.10.224
01-Dec-09 18:38:56 SETI@home Temporarily failed download of 16no06ac.7279.1299.11.10.3: connect() failed
01-Dec-09 18:38:56 SETI@home Backing off 1 min 0 sec on download of 16no06ac.7279.1299.11.10.3
01-Dec-09 18:38:56 SETI@home Temporarily failed download of 16no06ab.22684.25021.16.10.224: connect() failed
01-Dec-09 18:38:56 SETI@home Backing off 1 min 0 sec on download of 16no06ab.22684.25021.16.10.224
01-Dec-09 18:39:20 Project communication failed: attempting access to reference site
01-Dec-09 18:39:21 Internet access OK - project servers may be temporarily down.
01-Dec-09 18:39:57 SETI@home Started download of 16no06ac.7279.1299.11.10.1
01-Dec-09 18:39:57 SETI@home Started download of 16no06ac.7279.1299.11.10.7
01-Dec-09 18:39:59 Project communication failed: attempting access to reference site
01-Dec-09 18:39:59 SETI@home Temporarily failed download of 16no06ac.7279.1299.11.10.1: connect() failed
01-Dec-09 18:39:59 SETI@home Backing off 1 min 9 sec on download of 16no06ac.7279.1299.11.10.1
01-Dec-09 18:39:59 SETI@home Temporarily failed download of 16no06ac.7279.1299.11.10.7: connect() failed
01-Dec-09 18:39:59 SETI@home Backing off 1 min 0 sec on download of 16no06ac.7279.1299.11.10.7
01-Dec-09 18:40:00 Internet access OK - project servers may be temporarily down.
01-Dec-09 18:43:39 SETI@home Started download of 16no06ac.4594.72.12.10.245
01-Dec-09 18:43:39 SETI@home Started download of 12se09ad.10017.19290.10.10.89
01-Dec-09 18:43:41 Project communication failed: attempting access to reference site
01-Dec-09 18:43:41 SETI@home Temporarily failed download of 16no06ac.4594.72.12.10.245: connect() failed
01-Dec-09 18:43:41 SETI@home Backing off 22 min 41 sec on download of 16no06ac.4594.72.12.10.245
01-Dec-09 18:43:41 SETI@home Temporarily failed download of 12se09ad.10017.19290.10.10.89: connect() failed
01-Dec-09 18:43:41 SETI@home Backing off 25 min 9 sec on download of 12se09ad.10017.19290.10.10.89
01-Dec-09 18:43:42 Internet access OK - project servers may be temporarily down.
However, the servers are not down, since other machines on my network (or the same machine running WinXP32 from another HD) have no problems downloading WUs. Uploading finished WUs also goes fine. Quitting/restarting BOINC (I run it in a cmd window) does not fix this. However, if I reboot the machine, and then start BOINC, it suddely starts downloading WUs again. But when I check back a day or so later, it has saved up another bunch of failed downloads.
I've tried disabling the Win7 firewall, but no change.
Any ideas here? People noticing something similar on their home-network?
Regards,
Patrick.
-
Hi PatrickV2,
this is also been discussed in the seti at home forum.
solution is add the two following entries to your file hosts
usually you find it in C:\Windows\System32\drivers\etc
208.68.240.18 boinc2.ssl.berkeley.edu
208.68.240.13 boinc2.ssl.berkeley.edu
execute editor as admin, if you running Vista or W7.
hint: Don't forget to remove it when the issue in Berkeley is solved.
;)
-
DON'T add the .13 address - that's the bad one.
The idea is to fix the reference to use .18 only - that was the good one last weekend.
But it's probably all historic now - I expect the rogue server will be rebooted before the end of maintenance.
-
DON'T add the .13 address - that's the bad one.
The idea is to fix the reference to use .18 only - that was the good one last weekend.
But it's probably all historic now - I expect the rogue server will be rebooted before the end of maintenance.
OK, so I guess it's a problem at Seti's site (I was afraid my Win7 machine was misbehaving on my local network).
Should I now add the .18 to my hosts file, or leave it as is, and hope things clear up sometime tonight/tomorrow (local time)?
EDIT: Retried manually a few minutes ago, and WUs are, somewhat hesitantly, downloading again, so it looks like seti cleared the problem at their side...
Regards,
Patrick.