Invalid WU.

Message boards : Number crunching : Invalid WU.
Message board moderation

To post messages, you must log in.

AuthorMessage
Grant (SSSF)
Volunteer tester

Send message
Joined: 19 Aug 99
Posts: 13727
Credit: 208,696,464
RAC: 304
Australia
Message 1500311 - Posted: 5 Apr 2014, 22:07:07 UTC

Has anyone seen this before?

1466308336


From my computer,
Stderr output
<core_client_version>7.0.64</core_client_version>
<![CDATA[
<stderr_txt>

</stderr_txt>
]]>


From another computer,
Stderr output
<core_client_version>7.2.42</core_client_version>
<![CDATA[
<stderr_txt>

</stderr_txt>
]]>


And from a 3rd computer an Inconclusive,
Stderr output
<core_client_version>7.2.42</core_client_version>
<![CDATA[
<stderr_txt>
setiathome_CUDA: Found 1 CUDA device(s):
Device 1: GeForce 9800 GT, 512 MiB, regsPerBlock 8192
computeCap 1.1, multiProcs 14
clockRate = 1500 MHz
In cudaAcc_initializeDevice(): Boinc passed DevPref 1
setiathome_CUDA: CUDA Device 1 specified, checking...
Device 1: GeForce 9800 GT is okay
SETI@home using CUDA accelerated device GeForce 9800 GT
pulsefind: blocks per SM 1 (Pre-Fermi default)
pulsefind: periods per launch 100 (default)
Priority of process set to BELOW_NORMAL (default) successfully
Priority of worker thread set successfully

setiathome enhanced x41zc, Cuda 2.30

Detected setiathome_enhanced_v7 task. Autocorrelations enabled, size 128k elements.
Work Unit Info:
...............
WU true angle range is : 0.448007
re-using dev_GaussFitResults array for dev_AutoCorrIn, 4194304 bytes
re-using dev_GaussFitResults+524288x8 array for dev_AutoCorrOut, 4194304 bytes
cudaAcc_free() called...
cudaAcc_free() running...
cudaAcc_free() PulseFind freed...
cudaAcc_free() Gaussfit freed...
cudaAcc_free() AutoCorrelation freed...
cudaAcc_free() DONE.
Cuda sync'd & freed.
Preemptively acknowledging a safe Exit. ->
SETI@Home Informational message -9 result_overflow
NOTE: The number of results detected equals the storage space allocated.

Flopcounter: 17361877896.476398

Spike count: 26
Autocorr count: 0
Pulse count: 4
Triplet count: 0
Gaussian count: 0
Worker preemptively acknowledging an overflow exit.->
called boinc_finish
Exit Status: 0
boinc_exit(): requesting safe worker shutdown ->
boinc_exit(): received safe worker shutdown acknowledge ->
Cuda threadsafe ExitProcess() initiated, rval 0

</stderr_txt>
]]>
Grant
Darwin NT
ID: 1500311 · Report as offensive
Josef W. Segur
Volunteer developer
Volunteer tester

Send message
Joined: 30 Oct 99
Posts: 4504
Credit: 1,414,761
RAC: 0
United States
Message 1500446 - Posted: 6 Apr 2014, 0:17:40 UTC - in response to Message 1500311.  

Has anyone seen this before?

1466308336
...

Yes, the Strange Invalid MB Overflow tasks with truncated Stderr outputs... thread discusses that issue.
                                                                   Joe
ID: 1500446 · Report as offensive
Grant (SSSF)
Volunteer tester

Send message
Joined: 19 Aug 99
Posts: 13727
Credit: 208,696,464
RAC: 304
Australia
Message 1500475 - Posted: 6 Apr 2014, 1:16:11 UTC - in response to Message 1500446.  

Ah, one of the those randomly occurring, yet to be sorted issues.
Grant
Darwin NT
ID: 1500475 · Report as offensive

Message boards : Number crunching : Invalid WU.


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