Ever since I upgraded all my BOINC Clients to V4.13, I'm experiencing an odd Problem once a while, which seems to affect only the SETI Client :

Symptom :
- when Client is Paused/Suspended (due to timeslicing) while very close to WorkUnit completion (e.g. 99.x%), Client stalls without any further progress when Running again (after timeslicing back to it)

- due to that Problem, the entire Timeslicing process is interrupted (the hanging Client does not get any CPU Cycles), thus the entire computing Process is stalled effectively

Appearance :
- BOINC GUI or remote monitoring Utilites show the Client as "Running" just short of completion or even at 100.0% complete, but no further Progress is made. System and BOINC still operate and react normal to issued Commands, but is effectively not processing any data anymore.

Solution :
- manually or Remote via GUI_RPC (e.g. BOINCview Utility) momentarily toggle the BOINC Client's Run Mode to "Suspend" (vs. "Always run" or "Run based on Preferences"), then back to normal Run Mode again...

After this toggling, the Client correctly completes the stalled WorkUnit, and proceeds with normal workflow again.

-=-=-=-=-=-=-=-=-=-=-
Just this morning, I found 2 Linux machines stalled at 99.9% and 100.0% respectively, without progressing anymore. Not knowing any better, those 2 Units I manually aborted, before I found out the Run -> Suspend -> Run again Trick to save them :p

Just keep an eye on this bug, seems I'm just unlucky enough to have my SETI Clients being timesliced just one step before completion :P

---