Questions and Answers :
GPU applications :
weird error on GPU job - looks like result was too long but says aborted
Message board moderation
Author | Message |
---|---|
David Ball Send message Joined: 31 Oct 02 Posts: 9 Credit: 1,111,658 RAC: 0 |
Vista 32 bit with all patches and 4gb ram, C2D E6420 (Conroe, 2.13 ghz, 4 MB L2 cache). nVidia GT 630 (fermi version of 630 - basically GT440 with 2 GB of ddr3) Boinc client 7.2.39 Boinc manager said it got a compute error but when I turned it in to Seti, it says computation error in some places but exit status is 194 (0xc2) EXIT_ABORTED_BY_CLIENT. I did not abort it. It ran for the normal amount of time (about 40 minutes run time with the usual small amount of CPU time) The stderr output says something about "finish file present too long". http://setiathome.berkeley.edu/result.php?resultid=3417116829 What really happened here? |
BilBg Send message Joined: 27 May 07 Posts: 3720 Credit: 9,385,827 RAC: 0 |
EXIT_ABORTED_BY_CLIENT. I did not abort it You are the User, not the 'CLIENT' (CLIENT = boinc.exe) "finish file" = the boinc_finish_called file (appears (created by app) in a slot (...\<BOINC-Data>\slots\) when app is finished the task) "present too long" = more than 10 sec (if app is still in memory 10 sec after the file boinc_finish_called was created by the app (considered by BOINC as app-hang)) Stupid new BOINC 'feature' which kills (aborts, deletes) perfectly well finished tasks. 194 (0xc2) EXIT_ABORTED_BY_CLIENT - "finish file present too long": http://setiathome.berkeley.edu/forum_thread.php?id=73704 Â - ALF - "Find out what you don't do well ..... then don't do it!" :) Â |
©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.