New client gets stuck at 0%

First of all many thanks to Vincenzo for the new client. I am running it on an Athlon XP 3000+, and it really is
much faster than the "old" one.

However, there seems to be a problem when the client begins processing a new workunit. Sometimes (very
often, in fact) it happens that the "fraction done" remains at 0.00%, even after hours. Usually there is no
error message when this happens, and always the cpu load is at 100% as normal, but the client doesn't make
any progress. Sometimes I can resolve this by stopping and restarting the client several times, but
sometimes I also have to reboot the machine completely.

I never saw this problem directly after a reboot, and so far it never happend when the client was continuing
work on a workunit previously already partially done. It doesn't happen only when the (boinc-) client is
started, but also when the seti-client has finished a workunit and is beginning to process a new one.

Yesterdady I got a trap for the first time. This happened directly after starting the boinc-client:

06-30-2009  14:16:32  SYS3171  PID 006c  TID 0001  Slot 00ae
*************\BIN\SLOTS\0\SETIATHOME-6.10.I386-PC-OS2-EMX.EXE
c0000005
ffffffff
P1=00000008  P2=00000008  P3=XXXXXXXX  P4=XXXXXXXX  
EAX=00000053  EBX=0b24dff4  ECX=0b24c1ee  EDX=00000000
ESI=00000053  EDI=0000150b  
DS=0000  DSACC=****  DSLIM=********  
ES=0000  ESACC=****  ESLIM=********  
FS=0000  FSACC=****  FSLIM=********
GS=0001  GSACC=****  GSLIM=********
CS:EIP=000a:ffffe1f9  CSACC=****  CSLIM=********
SS:ESP=005b:000fa974  SSACC=f0df  SSLIM=ffffffff
EBP=0000001b  FLG=00012642

Re: New client gets stuck at 0%

--- In seti-warp <at> yahoogroups.com, "miprinzing" <mipri <at> ...> wrote:
>
> First of all many thanks to Vincenzo for the new client. I am running it on an Athlon XP 3000+, and it really is
much faster than the "old" one.
> 
> However, there seems to be a problem when the client begins processing a new workunit. Sometimes (very
often, in fact) it happens that the "fraction done" remains at 0.00%, even after hours. Usually there is no
error message when this happens, and always the cpu load is at 100% as normal, but the client doesn't make
any progress. Sometimes I can resolve this by stopping and restarting the client several times, but
sometimes I also have to reboot the machine completely.
> 
> I never saw this problem directly after a reboot, and so far it never happend when the client was continuing
work on a workunit previously already partially done. It doesn't happen only when the (boinc-) client is
started, but also when the seti-client has finished a workunit and is beginning to process a new one.
> 
> Yesterdady I got a trap for the first time. This happened directly after starting the boinc-client:
> 
> 06-30-2009  14:16:32  SYS3171  PID 006c  TID 0001  Slot 00ae
> *************\BIN\SLOTS\0\SETIATHOME-6.10.I386-PC-OS2-EMX.EXE
> c0000005
> ffffffff
> P1=00000008  P2=00000008  P3=XXXXXXXX  P4=XXXXXXXX  
> EAX=00000053  EBX=0b24dff4  ECX=0b24c1ee  EDX=00000000
> ESI=00000053  EDI=0000150b  
> DS=0000  DSACC=****  DSLIM=********  
> ES=0000  ESACC=****  ESLIM=********  
> FS=0000  FSACC=****  FSLIM=********
> GS=0001  GSACC=****  GSLIM=********
> CS:EIP=000a:ffffe1f9  CSACC=****  CSLIM=********
> SS:ESP=005b:000fa974  SSACC=f0df  SSLIM=ffffffff

Re: Re: New client gets stuck at 0%