Stalled Client & Stalled Workunits

Message boards : Number crunching : Stalled Client & Stalled Workunits
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile Karl Roos
Avatar

Send message
Joined: 19 Mar 01
Posts: 36
Credit: 206,258,788
RAC: 0
United States
Message 169029 - Posted: 17 Sep 2005, 22:41:09 UTC - in response to Message 168976.  

It might be better if you Identify which computer it is, so that people with similar cpu/os might be able to help, also say which BOINC version is running and which Seti client, especially if you are running optimised version.

Andy


Its an AMD FX-55 CPU running on Asus A8N-Sli DLX motherboard.....BOINC version 4.45, optimized client version 4.11 (YAOSCW-W-r7) running on Windows XP Pro SP2. I've been using the 4.11 YAOSCW-W-r8.1 client this afternoon and it seems to be running with no problems. Maybe the other client had a particular issue with this hardware.....I have an almost identical system at work - same CPU and motherboard chipset - and it has been running the YAOSCW-W-r7 optimized client for 5 days with no issues. Thanks.
ID: 169029 · Report as offensive
W-K 666 Project Donor
Volunteer tester

Send message
Joined: 18 May 99
Posts: 13795
Credit: 40,757,560
RAC: 151
United Kingdom
Message 168976 - Posted: 17 Sep 2005, 19:45:55 UTC

It might be better if you Identify which computer it is, so that people with similar cpu/os might be able to help, also say which BOINC version is running and which Seti client, especially if you are running optimised version. The only case I have read where a computer stalls is when the benchmark runs and then fails to restart unit, the benchmark happens every five days (or manually its under file tab), and is recorded in the messages tab of BOINC Manager.

Andy
ID: 168976 · Report as offensive
Profile Karl Roos
Avatar

Send message
Joined: 19 Mar 01
Posts: 36
Credit: 206,258,788
RAC: 0
United States
Message 168864 - Posted: 17 Sep 2005, 15:54:22 UTC

I have one computer that periodically "stalls" where it stops doing work, CPU goes to 0%, and if you open the Boinc manager it doesn't show a project attached or any workunits downloaded. On one or two of the other computers I've noticed the CPU at 0% once or twice, where a workunit is "in-progress" but stopped and not being completed. If I "suspend" the unit, and then "resume" it seems to pick back up and finish. Is this typical behavior for Seti Boinc? I only switched over from Classic Seti this week, so I'm new to it. On the machine that stalls I assumed needed to back off the overclock, but that didn't seem to help. I am running optimized clients, maybe will try the standard client but optomized is way faster.
ID: 168864 · Report as offensive

Message boards : Number crunching : Stalled Client & Stalled Workunits


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