Message boards :
Number crunching :
OpenCL NV MultiBeam v8 SoG edition for Windows
Message board moderation
Previous · 1 . . . 13 · 14 · 15 · 16 · 17 · 18 · Next
Author | Message |
---|---|
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14676 Credit: 200,643,578 RAC: 874 |
Actually, the error message is on line 232 of the current file. Are we using an outdated version of seti_header.cpp? Apart from Jason's provision for Android in 2014 (r2181), most of the file size growth was Eric's r3113 and r3212 for GBT - and the file does "Write a SETI work unit header to a file". Could the written file be missing some information, if we use an old version? |
jason_gee Send message Joined: 24 Nov 06 Posts: 7489 Credit: 91,093,184 RAC: 0 |
Actually, the error message is on line 232 of the current file. Are we using an outdated version of seti_header.cpp? Not sure what missing a parameter addition would do. Is that a possibility for this build? "Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions. |
William Send message Joined: 14 Feb 13 Posts: 2037 Credit: 17,689,662 RAC: 0 |
If that is Raistmer's file he'll have build from https://setisvn.ssl.berkeley.edu/trac/browser/branches/sah_v7_opt/AKv8/client/seti_header.cpp at revision 3377 changes from Urs. you'd have to diff that against vanilla seti and Jason's. edit i.e. https://setisvn.ssl.berkeley.edu/trac/browser/branches/sah_v7_opt/Xbranch/client/seti_header.cpp and https://setisvn.ssl.berkeley.edu/trac/browser/seti_boinc/client/seti_header.cpp A person who won't read has no advantage over one who can't read. (Mark Twain) |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14676 Credit: 200,643,578 RAC: 874 |
Searching this board for previous occurences of "Bad workunit header" - which date back to 2005 - reminds me that the -6 error code was triggered by Raistmer's old "VLAR Kill" workround in 2009. Now, that has no relationship to the current occurrence, except to suggest that interrupting any SETI app at that point in startup has the capability to trigger that exit route. We shouldn't be too literal minded and start peering at the workunit itself. |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14676 Credit: 200,643,578 RAC: 874 |
I think I wrote that better last time round, in message 1711911: SETI@home error -6 Bad workunit header |
Keith Myers Send message Joined: 29 Apr 01 Posts: 13164 Credit: 1,160,866,277 RAC: 1,873 |
It looks like we have a <no_opencl/> "KILL" in the latest client via a cc_config.xml flag. That ought to make a lot of people happy. Looks like a LOT of changes since the last stable release. Seti@Home classic workunits:20,676 CPU time:74,226 hours A proud member of the OFA (Old Farts Association) |
William Send message Joined: 14 Feb 13 Posts: 2037 Credit: 17,689,662 RAC: 0 |
well that was a dead end. Raistmer's last changes (before the extra lines for linux) exactly match Eric's and I've not had enough coffee to certify that Jason's internal switching matches that [@Jason rev. 3315 line 125 I assume you moved that into the temp variable at lines 227 ff. ?] So, unless it's reproducible - see Richard's comments on odd errors [or is that edd errors? ] A person who won't read has no advantage over one who can't read. (Mark Twain) |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14676 Credit: 200,643,578 RAC: 874 |
It looks like we have a <no_opencl/> "KILL" in the latest client via a cc_config.xml flag. That ought to make a lot of people happy. Looks like a LOT of changes since the last stable release. ROFL - I'd forgotten that. That was Jacob Klein's request for a way of preventing OpenCL applications from running, during a temporary period when an NVidia driver bug caused errors at PrimeGrid and POEM (only, so far as we know, and the bug is fixed at source now). I did suggest it was overkill, or ought to be matched with a <no_cuda/> tag as well - but since it exists now, there's nothing to stop people testing it. |
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121 |
Just got two bad work units with missing header information it looks like. Worth to run scandisk on affected partition. SETI apps news We're not gonna fight them. We're gonna transcend them. |
William Send message Joined: 14 Feb 13 Posts: 2037 Credit: 17,689,662 RAC: 0 |
Just got two bad work units with missing header information it looks like. Well I assumed that anybody who runs into an error that may be due to file damage does first check the integrity of the hard disc before taking it any further. A person who won't read has no advantage over one who can't read. (Mark Twain) |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14676 Credit: 200,643,578 RAC: 874 |
Just got two bad work units with missing header information it looks like. Especially after a BSOD. |
Keith Myers Send message Joined: 29 Apr 01 Posts: 13164 Credit: 1,160,866,277 RAC: 1,873 |
Correct assumption. I had run a full AV scan earlier in the day since I had moved to different software recently and needed to find out how it handled it. Also, had run integrity checks on the partition and done a /scannow. Nothing showed up. I just think I caught the manager and client in a bad spot at just the right time during program exit. I haven't had a BSOD on either of my crunchers in over a year if I remember correctly. Very solid machines. Or just crack the BSOD up to a case of cosmic ray impacts as Joe or Jason would suggest. Seti@Home classic workunits:20,676 CPU time:74,226 hours A proud member of the OFA (Old Farts Association) |
Rasputin42 Send message Joined: 25 Jul 08 Posts: 412 Credit: 5,834,661 RAC: 0 |
What exactly makes a SOG a SOG? Or what is the difference between: MB8_win_x86_SSE3_OpenCL_NV_r3430.exe and MB8_win_x86_SSE3_OpenCL_NV_r3430_SoG.exe? |
Keith Myers Send message Joined: 29 Apr 01 Posts: 13164 Credit: 1,160,866,277 RAC: 1,873 |
What exactly makes a SOG a SOG? That's exactly what I would like to know. Both operate within the <plan_class>opencl_nvidia_SoG</plan_class>. That is the only plan_class listed in their respective aistub files in their application 7z files. Seti@Home classic workunits:20,676 CPU time:74,226 hours A proud member of the OFA (Old Farts Association) |
Mike Send message Joined: 17 Feb 01 Posts: 34362 Credit: 79,922,639 RAC: 80 |
What exactly makes a SOG a SOG? From Raistmer: SoG build is more unique case cause it's first time implemented real parallel execution of different searches completely on GPU device. Progress marks embedded in CPU code and with high AR that CPU code does only non-blocking kernel enqueuing. This done very fast and then GPU process data w/o interaction with CPU code. So no more marks of progress going to BOINC - highly non-linear behavior on VHARs. non_SoG does process some signals on CPU instead of GPU. With each crime and every kindness we birth our future. |
Rasputin42 Send message Joined: 25 Jul 08 Posts: 412 Credit: 5,834,661 RAC: 0 |
Thanks, Mike. If they are so different, they probably should have given them different revision numbers. By not doing so indicates a strong similarity, as indicated by Keith Myers: Both operate within the <plan_class>opencl_nvidia_SoG</plan_class> |
Mike Send message Joined: 17 Feb 01 Posts: 34362 Credit: 79,922,639 RAC: 80 |
Thanks, Mike. The revision number just makes sure all app versions have same bug fixes and improved switches included. With each crime and every kindness we birth our future. |
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121 |
To be sure what flavor used one can look into result's stderr. It has lot of interesting info, including this line: Build features: SETI8 Non-graphics OpenCL USE_OPENCL_NV OCL_ZERO_COPY SIGNALS_ON_GPU OCL_CHIRP3 FFTW USE_SSE3 x86 SIGNALS_ON_GPU in this line means app build with SoG path enabled. So, it's SoG. SETI apps news We're not gonna fight them. We're gonna transcend them. |
Keith Myers Send message Joined: 29 Apr 01 Posts: 13164 Credit: 1,160,866,277 RAC: 1,873 |
OK, still really confused. I've gone through and looked at my completed tasks with both of the apps I've listed in this thread. Both of them have SIGNALS_ON_GPU listed in their respective stderr.txt files. So how is it you're still saying that MB8_win_x86_SSE3_OpenCL_NV_r3430.exe is not performing analysis with signals on GPU?? Seti@Home classic workunits:20,676 CPU time:74,226 hours A proud member of the OFA (Old Farts Association) |
Jimbocous Send message Joined: 1 Apr 13 Posts: 1856 Credit: 268,616,081 RAC: 1,349 |
Just wondering if any of the SoG stuff has hit a Lunatics build yet? Assuming no ... |
©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.