Advanced search

Message boards : Graphics cards (GPUs) : New BOINC client 6.6.3 for testing.

Author Message
Neil A
Send message
Joined: 9 Oct 08
Posts: 50
Credit: 12,676,739
RAC: 0
Level
Pro
Scientific publications
watwatwatwatwatwatwatwat
Message 6150 - Posted: 29 Jan 2009 | 3:02:37 UTC

The following fixes are included in this BOINC client software version released earlier today for testing...

Mac client: fix bug in build script so that curl-7.19.2 actually

does build with c-ares 1.6.0. Fixes #830. (Checked into

boinc_core_release_6_6_2 tag and boinc_core_release_6_6a branch.)

- client: fix messages

- client: fetch work from non-CPU-intensive projects

- client: compile fix, remove spurious message

- MGR: Make sure the UI thread doesn't call a GUI RPC

that uses the SET_LOCALE class.

- MGR: fix compile error.

- client: if an app has avg_ncpus < 1, run it at above-idle priority

even if it doesn't use a coprocessor.

- scheduler: added an "nci" (non CPU intensive) plan class

to sched_plan.cpp. It declares the use of 1% of a CPU.



The above two changes are intended to allow the QCN app to

run at above_idle priority, which it needs in order to do 500Hz polling.



- API: the std::string version of boinc_resolve_filename()

acts the same as the char[] version.

- client sandbox: add details in switcher_exec "execv failed" message.

- MGR: Work around bug in generic list control GetSelectedItemCount()

which caused incorrect update of buttons in Projects tab after

detching from a project; remove redundant UpdateSelection() call.

- MGR: Remove override of GetSelectedItemCount() introduced yesterday;

instead, call DeleteItem() rather than SetItemCount() when number of

rows has been reduced, to allow virtual ListCtrl adjust its list of

selected rows (and thus keep its count in sync with reality.)

- MGR: Don't use wxT() to describe parameters passed to GUI RPCs.

- MGR: In CBOINCClientManager::StartupBOINCCore() allow time for Client

to start up, to avoid repeated attempts which put spurious messages

"Another instance Another instance of BOINC is running" in

stderrdae.txt.

- client: simplify message describing scheduler request;

to get work request details, use <sched_op_debug>

- client: when preempting a process, remove it from memory if:

1) it uses a coprocessor

2) it has checkpointed since the client started

3) it's being preempted because of a user action

(suspend job, project, or all processing)

or user preference (time of day, computer in use)

- client: clear debts when reset project

- client: respect work-fetch backoff for non-CPU-intensive projects

- client: for non-CPU-intensive project, fetch new job

if no currently running jobs

- client: skip non-CPU-intensive projects in debt calculations

- manager: show resource backoff times correctly

- client: if we're doing an RPC (for whatever reason)

to a non-CPU-intensive project without a job, ask for one.

- client: change the LTD policy so that

1) net adjustment for eligible projects is zero;

2) max LTD is zero



____________
Crunching for the benefit of humanity and in memory of my dad and other family members.

Profile Paul D. Buck
Send message
Joined: 9 Jun 08
Posts: 1050
Credit: 37,321,185
RAC: 0
Level
Val
Scientific publications
watwatwatwatwatwatwatwatwatwat
Message 6156 - Posted: 29 Jan 2009 | 6:30:00 UTC

Has anyone tired it?

Profile Beyond
Avatar
Send message
Joined: 23 Nov 08
Posts: 1112
Credit: 6,162,416,256
RAC: 0
Level
Tyr
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 6158 - Posted: 29 Jan 2009 | 6:36:23 UTC - in response to Message 6156.
Last modified: 29 Jan 2009 | 6:37:10 UTC

Has anyone tired it?

http://www.gpugrid.net/forum_thread.php?id=684&nowrap=true#6154

naja002
Avatar
Send message
Joined: 25 Sep 08
Posts: 111
Credit: 10,352,599
RAC: 0
Level
Pro
Scientific publications
watwatwatwatwatwatwatwat
Message 6165 - Posted: 29 Jan 2009 | 12:05:56 UTC
Last modified: 29 Jan 2009 | 12:47:09 UTC

Just installed it on Vista x64 + 2x 8800GS--It aborted all current tasks (WCG and GPUGrid) and re-DLed new ones. Currently it has only DLed 2x GPUGrid WUs--it has always been 4x WUs in every previous version. Cpu usage is 0-2%.

Time to Completion is ~ 1hr 13mins....I doubt that is correct, but that's what it's showing for both WUs. Time to Completion is steadily ticking upward, but Cpu usage moves up 1sec for evey ~23secs of realtime.


It's only been installed for ~10mins, so we'll see how it goes....


Manual update retrieves no new WUs on WCG or GPUGrid. I should have a larger cache on both projects, but things are running atm.

Updated driver from 180.48 to 181.22....no noticeable difference....

Neil A
Send message
Joined: 9 Oct 08
Posts: 50
Credit: 12,676,739
RAC: 0
Level
Pro
Scientific publications
watwatwatwatwatwatwatwat
Message 6168 - Posted: 29 Jan 2009 | 13:57:30 UTC

I installed BOINC 6.6.3 on two home computers last night and no significant problems so far, though I did see something similar to naja's, where I tried to fetch GPUGrid work and didn't the first time, but forced a second update and it did get some work.

N
____________
Crunching for the benefit of humanity and in memory of my dad and other family members.

Profile Dieter Matuschek
Avatar
Send message
Joined: 28 Dec 08
Posts: 58
Credit: 231,884,297
RAC: 0
Level
Leu
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 6169 - Posted: 29 Jan 2009 | 14:05:28 UTC - in response to Message 6165.
Last modified: 29 Jan 2009 | 14:05:59 UTC

Yesterday I upgraded BOINC 6.4.5 to 6.6.3 without any problems on an Intel Quad Q6600 with WinXP SP3.
Although it requests very often new work units, it doesn't get too much work (in contrast to a BOINC 6.2.2 install I had tried before).

naja002
Avatar
Send message
Joined: 25 Sep 08
Posts: 111
Credit: 10,352,599
RAC: 0
Level
Pro
Scientific publications
watwatwatwatwatwatwatwat
Message 6174 - Posted: 29 Jan 2009 | 16:18:23 UTC - in response to Message 6168.

I installed BOINC 6.6.3 on two home computers last night and no significant problems so far, though I did see something similar to naja's, where I tried to fetch GPUGrid work and didn't the first time, but forced a second update and it did get some work.

N


Agreed, Mine has picked up 2 more WUs since my last post. Cpu usage is still the same 0-2%. So far everything seems good, except losing all of the work and WUs during the change-over....

naja002
Avatar
Send message
Joined: 25 Sep 08
Posts: 111
Credit: 10,352,599
RAC: 0
Level
Pro
Scientific publications
watwatwatwatwatwatwatwat
Message 6175 - Posted: 29 Jan 2009 | 16:28:02 UTC
Last modified: 29 Jan 2009 | 17:20:07 UTC

Just installed 6.6.3 into another rig. It did not abort the WUs, etc. Started up, benchmarked and went to work--NP. But this machine is coming from 6.3.21, so I would say that's the difference.

The other rig was updated from 6.4.5.

Edit: Cpu usage is high on this rig....~25%, but I am willing to assume atm that it's because of the older WUs.

Phoneman1
Send message
Joined: 25 Nov 08
Posts: 51
Credit: 980,186
RAC: 0
Level
Gly
Scientific publications
watwat
Message 6176 - Posted: 29 Jan 2009 | 16:38:25 UTC - in response to Message 6174.

So far everything seems good, except losing all of the work and WUs during the change-over....


I upgraded about 6 hours ago on both machines with no problems so far.

I've had problems with the installer not stopping the GPU task cleanly in the past so I suspended all activity before running the installer. I let the installer shut down the boinc client and the boinc manager though. I didn't loose any work units doing it that way, but then I am using the Win 32 bit variant and you are on the Win 64 bit.

Phoneman1

naja002
Avatar
Send message
Joined: 25 Sep 08
Posts: 111
Credit: 10,352,599
RAC: 0
Level
Pro
Scientific publications
watwatwatwatwatwatwatwat
Message 6177 - Posted: 29 Jan 2009 | 16:42:55 UTC - in response to Message 6176.

So far everything seems good, except losing all of the work and WUs during the change-over....


I upgraded about 6 hours ago on both machines with no problems so far.

I've had problems with the installer not stopping the GPU task cleanly in the past so I suspended all activity before running the installer. I let the installer shut down the boinc client and the boinc manager though. I didn't loose any work units doing it that way, but then I am using the Win 32 bit variant and you are on the Win 64 bit.

Phoneman1


I lost all WUs when I went to 6.4.2 or 6.4.5 (I think I installed 6.4.2 on both though). I switched the 1 rig back to 6.3.21 and the other to 6.4.5. Today when I switched from 6.4.5-I lost all WUs, but not switching from 6.3.21.

Going into 6.4.? I lost all WUs and coming out of it--same thing.

Profile X-Files 27
Avatar
Send message
Joined: 11 Oct 08
Posts: 95
Credit: 68,023,693
RAC: 0
Level
Thr
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 6178 - Posted: 29 Jan 2009 | 17:04:01 UTC

It can't seem to download any WU.
____________

Profile Beyond
Avatar
Send message
Joined: 23 Nov 08
Posts: 1112
Credit: 6,162,416,256
RAC: 0
Level
Tyr
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 6180 - Posted: 29 Jan 2009 | 17:20:57 UTC - in response to Message 6177.

I lost all WUs when I went to 6.4.2 or 6.4.5 (I think I installed 6.4.2 on both though). I switched the 1 rig back to 6.3.21 and the other to 6.4.5. Today when I switched from 6.4.5-I lost all WUs, but not switching from 6.3.21.

Going into 6.4.? I lost all WUs and coming out of it--same thing.

Interesting, I wonder why this is happening to you? I've switched many times between various versions of BOINC 6.xx (both forward & backward & even 5.xx & including 6.4.1, 6.4.2, 6.4.5, 6.3.21) and have never lost any WUs in any project.

Profile Bender10
Avatar
Send message
Joined: 3 Dec 07
Posts: 167
Credit: 8,368,897
RAC: 0
Level
Ser
Scientific publications
watwatwatwatwatwatwat
Message 6185 - Posted: 29 Jan 2009 | 17:45:26 UTC - in response to Message 6180.

I've switched many times between various versions of BOINC 6.xx (both forward & backward & even 5.xx & including 6.4.1, 6.4.2, 6.4.5, 6.3.21) and have never lost any WUs in any project.


The loss of GPUgrid Wu's has been a hit or miss thing with many people. It depends on OS, Client, how you shutdown the client, upgrading or downgrading etc. Many have not been 'Bit' by this, some have... I try to suspend "non-running" Wu's and run down my "Active Wu's" just in case, then upgrade. I hate losing 'half crunched' Wu's....in the name of science...
____________


Consciousness: That annoying time between naps......

Experience is a wonderful thing: it enables you to recognize a mistake every time you repeat it.

Rabinovitch
Avatar
Send message
Joined: 25 Aug 08
Posts: 143
Credit: 64,937,578
RAC: 0
Level
Thr
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwat
Message 6203 - Posted: 30 Jan 2009 | 4:40:13 UTC

Everything is OK with WUs during upgrade, as usually. But it doesn't request work for gpugrid automatically! I am forced to make it by my hands again!!! Aggghhhrrrrr.... Is it so difficult for NORMAL programmer to fix this bug?!
____________
From Siberia with love!

Profile Paul D. Buck
Send message
Joined: 9 Jun 08
Posts: 1050
Credit: 37,321,185
RAC: 0
Level
Val
Scientific publications
watwatwatwatwatwatwatwatwatwat
Message 6206 - Posted: 30 Jan 2009 | 7:01:24 UTC - in response to Message 6203.

Everything is OK with WUs during upgrade, as usually. But it doesn't request work for gpugrid automatically! I am forced to make it by my hands again!!! Aggghhhrrrrr.... Is it so difficult for NORMAL programmer to fix this bug?!


Well, the good news is that there was only one major bug in 6.6.3 in calculating LTD ... which may very well mean that you will have trouble getting work ... :)

were it me, I would down level again until 6.6.4 ...

Rabinovitch
Avatar
Send message
Joined: 25 Aug 08
Posts: 143
Credit: 64,937,578
RAC: 0
Level
Thr
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwat
Message 6207 - Posted: 30 Jan 2009 | 7:11:36 UTC - in response to Message 6156.
Last modified: 30 Jan 2009 | 7:12:33 UTC

Has anyone tired it?


Yes, I tired... Tired of waiting for NORMAL version of BOINC, which could automatically get work for gpugrid (CUDA s@h, CUDA e@h in future)... :-)
____________
From Siberia with love!

STE\/E
Send message
Joined: 18 Sep 08
Posts: 366
Credit: 268,386,907
RAC: 1,296
Level
Asn
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwat
Message 6208 - Posted: 30 Jan 2009 | 9:10:21 UTC

I couldn't get any new work GPU units on 2 different Box's using 6.6.3 ...

Profile Kokomiko
Avatar
Send message
Joined: 18 Jul 08
Posts: 190
Credit: 24,093,690
RAC: 0
Level
Pro
Scientific publications
watwatwatwatwatwatwatwatwatwat
Message 6209 - Posted: 30 Jan 2009 | 9:30:24 UTC
Last modified: 30 Jan 2009 | 9:30:55 UTC

The 6.6.3 is running fine , but there are some changes I don't like. I can't see the amount of called work and had on one PC the situation, that he crunched all WUs and would not call new work 'til the last WU had less than 2 hours to work.

I don't like it, if the BM works like a black box and I get no information. I've described this on the Boinc dev forum
____________

Phoneman1
Send message
Joined: 25 Nov 08
Posts: 51
Credit: 980,186
RAC: 0
Level
Gly
Scientific publications
watwat
Message 6210 - Posted: 30 Jan 2009 | 10:19:56 UTC - in response to Message 6206.


Well, the good news is that there was only one major bug in 6.6.3 in calculating LTD ... which may very well mean that you will have trouble getting work ... :)


According to Boincview GPU's LTD is now zero on both of my machines. My other project, Cosmology, shows -4.8 million on one and -11.2 million on the other.

It does not seem to have afftected getting work for either project. On both machines 1 GPU is running and 2 are queued ready. Three of those queued were downloaded today, I upgraded to 6.6.3 this time yesterday.

There are 4 Cosmology tasks running on each machine and the normal number (half a day's worth) queued ready to run.

I'm going to stop Boinc and reset all the LTDs to zero and see what happens.

I think the fact that GPU LTD is zero now is by design and not a bug. I am not sure what it would be if I was running another GPU project. It looks to me like they are separating the work fetch mechanisms for CPU and GPU type projects.

Phoneman1

Profile Paul D. Buck
Send message
Joined: 9 Jun 08
Posts: 1050
Credit: 37,321,185
RAC: 0
Level
Val
Scientific publications
watwatwatwatwatwatwatwatwatwat
Message 6211 - Posted: 30 Jan 2009 | 11:56:12 UTC - in response to Message 6210.

I think the fact that GPU LTD is zero now is by design and not a bug. I am not sure what it would be if I was running another GPU project. It looks to me like they are separating the work fetch mechanisms for CPU and GPU type projects.

Phoneman1


Yes, that is the intent. Also making minor changes for non-CPU projects ...

If you are attached to lots of projects JM VII found issues that indicate that you can run dry of work with 6.6.3 ... YMMV

STE\/E
Send message
Joined: 18 Sep 08
Posts: 366
Credit: 268,386,907
RAC: 1,296
Level
Asn
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwat
Message 6212 - Posted: 30 Jan 2009 | 12:10:00 UTC - in response to Message 6211.

I think the fact that GPU LTD is zero now is by design and not a bug. I am not sure what it would be if I was running another GPU project. It looks to me like they are separating the work fetch mechanisms for CPU and GPU type projects.

Phoneman1


Yes, that is the intent. Also making minor changes for non-CPU projects ...

If you are attached to lots of projects JM VII found issues that indicate that you can run dry of work with 6.6.3 ... YMMV


I had to go back to v6.3.21 because 6.6.3 Wouldn't give me any more GPU WU's no matter what I did. I tried 6.4.5 but that Version would let me run 4&1 on a Quad or 8&2 on my i7. Version 6.3.21 is the only Version so far that gives me more GPU Work & lets me run 4&1 and 8&2 ...

Profile asb2106
Send message
Joined: 24 Dec 08
Posts: 17
Credit: 10,751,419
RAC: 0
Level
Pro
Scientific publications
watwatwatwatwatwatwatwat
Message 6215 - Posted: 30 Jan 2009 | 15:52:24 UTC

SAME PROBLEMS HERE!

6.6.3 will not get new work from GPUGRID for me.

Went back to 6.4.5 and instantly it got 2 new WU's for me.

They just cannot get this right can they!

Phoneman1
Send message
Joined: 25 Nov 08
Posts: 51
Credit: 980,186
RAC: 0
Level
Gly
Scientific publications
watwat
Message 6217 - Posted: 30 Jan 2009 | 16:23:50 UTC - in response to Message 6215.

SAME PROBLEMS HERE!


Is this a problem with the x64 variant - I wonder....

Anyone having problems getting GPU tasks on Win 32 bit or Linux 32 bit with 6.6.3???

Phoneman1

ExtraTerrestrial Apes
Volunteer moderator
Volunteer tester
Avatar
Send message
Joined: 17 Aug 08
Posts: 2705
Credit: 1,311,122,549
RAC: 0
Level
Met
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 6220 - Posted: 30 Jan 2009 | 17:36:11 UTC - in response to Message 6212.

Version 6.3.21 is the only Version so far that gives me more GPU Work & lets me run 4&1 and 8&2 ...


Did you try 6.5.0? I found it to be surprisingly well-behaved.

MrS
____________
Scanning for our furry friends since Jan 2002

Profile Dieter Matuschek
Avatar
Send message
Joined: 28 Dec 08
Posts: 58
Credit: 231,884,297
RAC: 0
Level
Leu
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 6221 - Posted: 30 Jan 2009 | 17:53:06 UTC - in response to Message 6217.

Anyone having problems getting GPU tasks on Win 32 bit or Linux 32 bit with 6.6.3???
Phoneman1

No probs so far with WinXP 32 bit (BOINC 6.6.3 installed two days ago).

Neil A
Send message
Joined: 9 Oct 08
Posts: 50
Credit: 12,676,739
RAC: 0
Level
Pro
Scientific publications
watwatwatwatwatwatwatwat
Message 6222 - Posted: 30 Jan 2009 | 19:28:36 UTC

I am experiencing GPUGrid work fetch problems under BOINC client 6.6.3 after upgrading several days ago. I have run out of work and with repeated attempts to get work manually including resetting the project without success.

There is definitely something wrong in the BOINC client work fetch logic that allows the PC to run dry and not fetch work when there are 2 graphics cards and only one active WU being processed and none in queue.

At 2:25 PM EST today, it is trying to download work by requesting new tasks, but nothing is being returned....this could be a GPUgrid.net work availablity problem again? Or BOINC...not sure.

Neil
____________
Crunching for the benefit of humanity and in memory of my dad and other family members.

Profile Paul D. Buck
Send message
Joined: 9 Jun 08
Posts: 1050
Credit: 37,321,185
RAC: 0
Level
Val
Scientific publications
watwatwatwatwatwatwatwatwatwat
Message 6225 - Posted: 30 Jan 2009 | 19:38:12 UTC

There is a major bug in 6.6.3 which Dr. Anderson fixed related to the calculation of LTD. There are varying and different problems with all the 6.6.x versions from dot zero to dot three ...

I warned you below to be wary of 6.6.3 ... :)

I actually did look at the code and there was an initialization error that though I cannot predict the exact ways that it would bite you, will eventually bite you ...

Neil A
Send message
Joined: 9 Oct 08
Posts: 50
Credit: 12,676,739
RAC: 0
Level
Pro
Scientific publications
watwatwatwatwatwatwatwat
Message 6226 - Posted: 30 Jan 2009 | 20:17:04 UTC

Thanks Paul.

I've been watching this forum as well I'm on the alpha dist list at BOINC and like to test new releases when they come out. I'd love to get my hands on a new build to see if the fix(es) to 6.6.3 work for me. In the mean time I guess I'll have to go back to an earlier BOINC client release for now.

Neil

Milford
Send message
Joined: 17 Jul 07
Posts: 14
Credit: 9,618,510
RAC: 0
Level
Ser
Scientific publications
watwatwatwatwatwatwatwatwat
Message 6227 - Posted: 30 Jan 2009 | 20:41:23 UTC - in response to Message 6226.

Works ok for me on two machines, vista64 and xp32; no problems

Profile Dieter Matuschek
Avatar
Send message
Joined: 28 Dec 08
Posts: 58
Credit: 231,884,297
RAC: 0
Level
Leu
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 6230 - Posted: 30 Jan 2009 | 21:24:36 UTC

I just had to downgrade from 6.6.3 because it fetched way too much WUs of a CPU intense project. :-(

Profile asb2106
Send message
Joined: 24 Dec 08
Posts: 17
Credit: 10,751,419
RAC: 0
Level
Pro
Scientific publications
watwatwatwatwatwatwatwat
Message 6232 - Posted: 30 Jan 2009 | 22:37:47 UTC - in response to Message 6227.
Last modified: 30 Jan 2009 | 22:40:06 UTC

I thought it was OK at first also. But there was no way I could get more work to fill the queue.

6.6.3 downloaded 300 321LLR PG WU's overnight when my cache was set to 1 day.
Even after detaching from PG and reseting GPUGRID, still no new work.


Switched to 6.5.0 and its been perfect all day. It grabs GPU's no problem, and it runs 4+1 & 4.2 w/o issue so far.

naja002
Avatar
Send message
Joined: 25 Sep 08
Posts: 111
Credit: 10,352,599
RAC: 0
Level
Pro
Scientific publications
watwatwatwatwatwatwatwat
Message 6236 - Posted: 31 Jan 2009 | 0:56:19 UTC
Last modified: 31 Jan 2009 | 0:58:06 UTC

Just a quick up date: No problems here. 2 rigs: Vista 64 3x 8800GS (total). Unless something changes....I'm going to stick with this for a while....

Profile Paul D. Buck
Send message
Joined: 9 Jun 08
Posts: 1050
Credit: 37,321,185
RAC: 0
Level
Val
Scientific publications
watwatwatwatwatwatwatwatwatwat
Message 6238 - Posted: 31 Jan 2009 | 4:11:08 UTC

Initialization problems in code are usually the hardest to find because the system under many conditions can appear to be running correctly. In this case, the testing variable is not set with the initial value of the first project as the scanning loop begins. Now, it is entirely possible that the value that the variable has at the beginning of the loop is "close" enough so that it will do a proper scan ... but in other cases the first project in the list should be the value in the testing variable ... and it is never set ...

What that means, of course, is that you can run into trouble immediately, or more likely after running for a bit. What disappoints me the most is that no new build was made because aside this bug the build might have been the leap forward we were hoping for that finally started to address the issues we have with the GPU / CPU loads ...

MarkJ
Volunteer moderator
Volunteer tester
Send message
Joined: 24 Dec 08
Posts: 738
Credit: 200,909,904
RAC: 0
Level
Leu
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 6241 - Posted: 31 Jan 2009 | 7:33:29 UTC - in response to Message 6238.

Initialization problems in code are usually the hardest to find because the system under many conditions can appear to be running correctly. In this case, the testing variable is not set with the initial value of the first project as the scanning loop begins. Now, it is entirely possible that the value that the variable has at the beginning of the loop is "close" enough so that it will do a proper scan ... but in other cases the first project in the list should be the value in the testing variable ... and it is never set ...

What that means, of course, is that you can run into trouble immediately, or more likely after running for a bit. What disappoints me the most is that no new build was made because aside this bug the build might have been the leap forward we were hoping for that finally started to address the issues we have with the GPU / CPU loads ...


I don't recall you mentioning the initialize issue on the mailing list. Do you have a snippet of code you could provide where you think the issue is, or is that the LTD fix Dr A has done?

It seems the suspend/resume buttons is the only fix so far in 6.6.4. The fact they didn't want to build a new version suggests they may be aware of more bugs and want to include (or are working on) fixes for them. Or maybe they just want to give us the weekend to give 6.6.3 a shake down.
____________
BOINC blog

Phoneman1
Send message
Joined: 25 Nov 08
Posts: 51
Credit: 980,186
RAC: 0
Level
Gly
Scientific publications
watwat
Message 6245 - Posted: 31 Jan 2009 | 11:26:04 UTC - in response to Message 6238.

Initialization problems in code are usually the hardest to find because the system under many conditions can appear to be running correctly.


Absolutely. This version looked good for most of yesterday and the day before on my systems. On my final check of yesterday evening it hadn't replaced a completed GPU task but was running one with one in the queue - plenty of time to sort itself out I thought - Wrong!

I've just checked for the first time today and found the last GPU task had ended nearly 2 hours before and no request for work had been made. A manual update did not request any work so I suspended the other project and tried again. That brought two GPU tasks, it then automically asked for more work and got two more. Then again but this time it was refused because I had reached 1 per core!

Clearly 6.6.3 is not to be trusted even on Win 32 so I've gone back to 6.5.0.

Phoneman1

Profile Paul D. Buck
Send message
Joined: 9 Jun 08
Posts: 1050
Credit: 37,321,185
RAC: 0
Level
Val
Scientific publications
watwatwatwatwatwatwatwatwatwat
Message 6250 - Posted: 31 Jan 2009 | 14:04:34 UTC - in response to Message 6241.

I don't recall you mentioning the initialize issue on the mailing list. Do you have a snippet of code you could provide where you think the issue is, or is that the LTD fix Dr A has done?

It seems the suspend/resume buttons is the only fix so far in 6.6.4. The fact they didn't want to build a new version suggests they may be aware of more bugs and want to include (or are working on) fixes for them. Or maybe they just want to give us the weekend to give 6.6.3 a shake down.


The one Dr. Anderson found. However, I did look at the code change he made and in essence the first project visited should have its value stored in the scan variable. It isn't... Assuming C does initialize the value to zero, the scan value starts with this position to begin to discover the project with the largest value. If the first project has this value, it will never be discovered.

Thus, after a few days, the first project in the list will inevitably become the project with the largest value but this will not be established ... with that ... you get issues ... now I did not look at the whole set of code ... but so far I cannot recall anyone that has run 6.6.3 that has not back-leveled after a couple of days ...

Not putting up another version can suggest or imply what you said. However, this bug is so severe that you cannot use this version for testing at all ... thus you cannot check the operation of 6.6.3 and contrast it with the versions that came before ... it is too severely damaged for that ...

MarkJ
Volunteer moderator
Volunteer tester
Send message
Joined: 24 Dec 08
Posts: 738
Credit: 200,909,904
RAC: 0
Level
Leu
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 6287 - Posted: 1 Feb 2009 | 7:21:31 UTC - in response to Message 6250.

The one Dr. Anderson found. However, I did look at the code change he made and in essence the first project visited should have its value stored in the scan variable. It isn't... Assuming C does initialize the value to zero, the scan value starts with this position to begin to discover the project with the largest value. If the first project has this value, it will never be discovered.

Thus, after a few days, the first project in the list will inevitably become the project with the largest value but this will not be established ... with that ... you get issues ... now I did not look at the whole set of code ... but so far I cannot recall anyone that has run 6.6.3 that has not back-leveled after a couple of days ...

Not putting up another version can suggest or imply what you said. However, this bug is so severe that you cannot use this version for testing at all ... thus you cannot check the operation of 6.6.3 and contrast it with the versions that came before ... it is too severely damaged for that ...


I have 6.6.3 on three machines (non-cuda), but i'm sticking with 6.5.0 on the one cuda-capable machine for the time being. I will take the non-cuda ones back to 6.2.19.

There are a few reports of work-fetch issues popping up in boinc_alpha with the debug logging so there is a fair bit of information there for the guys to examine. I don't know if you subscribe to it or just boinc_dev? Maybe you should mention your concern with the code change.
____________
BOINC blog

Profile Paul D. Buck
Send message
Joined: 9 Jun 08
Posts: 1050
Credit: 37,321,185
RAC: 0
Level
Val
Scientific publications
watwatwatwatwatwatwatwatwatwat
Message 6297 - Posted: 1 Feb 2009 | 14:49:18 UTC - in response to Message 6287.

There are a few reports of work-fetch issues popping up in boinc_alpha with the debug logging so there is a fair bit of information there for the guys to examine. I don't know if you subscribe to it or just boinc_dev? Maybe you should mention your concern with the code change.


BOINC Dev and Projects ... I don't have a concern with the CHANGE ... just with the lack of 6.6.4 with the code change in it ...

Dr. Anderson suggested that if we wanted it we could compile our own ... which is not a really viable suggestion for most. Personally as a developer (past life) I find it a poor judgement that they would leave a version up for download with such a devastatingly subtle bug in it for people to download ...

And firing off a build in the background on their PCs that are set-up for it is not that difficult ...

ExtraTerrestrial Apes
Volunteer moderator
Volunteer tester
Avatar
Send message
Joined: 17 Aug 08
Posts: 2705
Credit: 1,311,122,549
RAC: 0
Level
Met
Scientific publications
watwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwatwat
Message 6358 - Posted: 3 Feb 2009 | 20:18:45 UTC - in response to Message 6297.

.. just don't forget that these are developer versions, not even alphas. Personally I'm not that keen on testing these new versions, as most of the time something is quite broken.

MrS
____________
Scanning for our furry friends since Jan 2002

Post to thread

Message boards : Graphics cards (GPUs) : New BOINC client 6.6.3 for testing.

//