6.1.14 don't count CPU time on Vista

Message boards : BOINC client : 6.1.14 don't count CPU time on Vista
Message board moderation

To post messages, you must log in.

AuthorMessage
barney-s

Send message
Joined: 16 Apr 08
Posts: 2
Germany
Message 16687 - Posted: 16 Apr 2008, 20:37:01 UTC

Hello,

I write this, because I didn't fount a notice to my events.

I am running 6.1.14 on WinXP SP2 without Problems.
Now trying out 6.1.14 on my Vista Lappi it is number crunching Seti and Cosmo, but not counting the CPU Time.
But also the WU is finished with success.
You can see here:http://setiathome.berkeley.edu/result.php?resultid=815424248

I moved back to 5.10.45 on Vista
regards, Barney

---
Yes I know: Vista sucks ... you dont need to mention it...
ID: 16687 · Report as offensive
Pepo
Avatar

Send message
Joined: 3 Apr 06
Posts: 547
Slovakia
Message 16697 - Posted: 17 Apr 2008, 14:41:11 UTC - in response to Message 16687.  

I write this, because I didn't fount a notice to my events.

The only evil note I can see in your result is "Can't set up shared mem: -1", but I have no solution. Did you possibly try to reboot and start crunching again?

But also the WU is finished with success.

You should ask this on Seti forum. While the results really validated (the tasks' details suggest so) and Seti is using flop counting instead of CPU time, then your zero time should be ignored. IMO a validator (or some similar process) issue - either the result was not really valid, or it should have been granted a credit.

Peter
ID: 16697 · Report as offensive
Chris
Avatar

Send message
Joined: 1 Jun 07
Posts: 36
Message 16699 - Posted: 17 Apr 2008, 16:34:46 UTC

On Windows Server 2008 RC was the same problem, progress bar did not work while running 6.1.14 as a single-user installation.

The WCG HPF2 applications always popped up their grafic windows, manualy closing caused an error message. I did not save logs late at night, sorry for that. Service installation works fine. But I should not work with an old operating System...
ID: 16699 · Report as offensive
barney-s

Send message
Joined: 16 Apr 08
Posts: 2
Germany
Message 16703 - Posted: 17 Apr 2008, 20:47:15 UTC - in response to Message 16697.  


The only evil note I can see in your result is "Can't set up shared mem: -1", but I have no solution. Did you possibly try to reboot and start crunching again?

Yes sure I had a reboot - in fact was some vanilla install of 6.1.4

But also the WU is finished with success.

You should ask this on Seti forum. While the results really validated (the tasks' details suggest so) and Seti is using flop counting instead of CPU time, then your zero time should be ignored. IMO a validator (or some similar process) issue - either the result was not really valid, or it should have been granted a credit.

As I wrote before, was the same with cosmology.
And similar as Chris wrote for his 2008 Server, I had no progressbar. Also allways the Graphics for Spinhedge, and not able to disable.
Well, on the reboot of the maschine, I lost the WU for Spinhedge - sorry

Regards, Barney
ID: 16703 · Report as offensive
John McLeod VII
Avatar

Send message
Joined: 29 Aug 05
Posts: 147
Message 17171 - Posted: 4 May 2008, 4:19:40 UTC - in response to Message 16962.  

Well, moved a testbox this morning from 6.1.14 to 6.1.16 without loss of work, wink wink.... why? Because twice now caught it out as somehow having moved into power saving mode. 20 minutes after last keyboard/mouse operation it went into Suspending Computation only to notice this morning that the CPU temps were rather low. Sure enough, on touch of mouse it went off again. Went to do something else and again, 20 minutes.... The CPU use was set to use the prefs which were set to work when machine in use.

The line in the global_prefs read:

<suspend_if_no_recent_input>0.0</suspend_if_no_recent_input>

It's not in the global_prefs_override.xml or in the client options, so manually added the line, just to be sure, if i could be.

Figure that?

The problem you having is the power saving feature of your computer. This turns down the CPU, turns off the HD and Monitor. Turning off the HD and turning down the CPU cause BOINC projects to halt.

BOINC WIKI
ID: 17171 · Report as offensive

Message boards : BOINC client : 6.1.14 don't count CPU time on Vista

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.