Bugreport: boinc reported success but has failed


log in

Advanced search

Questions and Answers : GPU applications : Bugreport: boinc reported success but has failed

Author Message
Profile juko
Send message
Joined: 27 Feb 10
Posts: 1
Credit: 45,560
RAC: 0
Germany
Message 986286 - Posted: 3 Apr 2010, 9:10:02 UTC

Hello,

I have seen it twice, that boinc has reported a successfull outcome. But stderr output looks like this:


<core_client_version>6.6.36</core_client_version>
<![CDATA[
<stderr_txt>
setiathome_CUDA: Found 1 CUDA device(s):
Device 1 : GeForce 9600 GT
totalGlobalMem = 536543232
sharedMemPerBlock = 16384
regsPerBlock = 8192
warpSize = 32
memPitch = 262144
maxThreadsPerBlock = 512
clockRate = 1625000
totalConstMem = 65536
major = 1
minor = 1
textureAlignment = 256
deviceOverlap = 1
multiProcessorCount = 8
setiathome_CUDA: CUDA Device 1 specified, checking...
Device 1: GeForce 9600 GT is okay
SETI@home using CUDA accelerated device GeForce 9600 GT
setiathome_enhanced 6.09 Visual Studio/Microsoft C++
libboinc: 6.3.22

Work Unit Info:
...............
WU true angle range is : 0.007596
Optimal function choices:
-----------------------------------------------------
name
-----------------------------------------------------
v_BaseLineSmooth (no other)
v_GetPowerSpectrum 0.00019 0.00000
v_ChirpData 0.01334 0.00000
v_Transpose4 0.00370 0.00000
FPU opt folding 0.00742 0.00000
SETI@Home Informational message -9 result_overflow
NOTE: The number of results detected exceeds the storage space allocated.

Flopcounter: 331369304.000000

Spike count: 30
Pulse count: 0
Triplet count: 0
Gaussian count: 0
called boinc_finish

</stderr_txt>
]]>


The above doesn't look like an successfull run.
My question is, what happens if two machines with the same bug compute the same workunit?
In a bad case they deliver both the same false result.
And the validation process can't detect it. Is this correct?


Greetings
Juergen

Profile BilBg
Volunteer tester
Avatar
Send message
Joined: 27 May 07
Posts: 2806
Credit: 6,330,234
RAC: 7,430
Bulgaria
Message 986301 - Posted: 3 Apr 2010, 11:10:54 UTC - in response to Message 986286.
Last modified: 3 Apr 2010, 11:18:55 UTC

Absolutely normal - no error

SETI@Home Informational message -9 result_overflow

Means - the WU is considered too noisy if too many "signals" are found
and after max 30 "signals" of one kind is aborted by purpose/design
by SETI@Home app, not by BOINC

Credit is given for the effort (time, FLOPS) till abort
e.g. if the WU processing is discontinued after 77% -
then about 77% of the credit for the full to-the-end computation is given

.
____________



- ALF - "Find out what you don't do well ..... then don't do it!" :)

Profile ignorance is no excuse
Avatar
Send message
Joined: 4 Oct 00
Posts: 9529
Credit: 44,433,321
RAC: 0
Korea, North
Message 986332 - Posted: 3 Apr 2010, 14:11:13 UTC - in response to Message 986301.

If you see this happening in multiple WU's then you probably need to restart. Sometimes the GPU gets glitchy or overheats and starts throwing bad results out. In that case just restart your computer
____________
In a rich man's house there is no place to spit but his face.
Diogenes Of Sinope

End terrorism by building a school

Questions and Answers : GPU applications : Bugreport: boinc reported success but has failed

Copyright © 2014 University of California