Welcome to MilkyWay@home

Posts by MarkJ

1) Message boards : Number crunching : Development BOINC 6.10.29 released (Message 36000)
Posted 24 Jan 2010 by MarkJ
Post:
Don't you think that this is getting out of hand now ?

Almost every project message board is full with your ALPHA BOINC posts, which do not belong here or elsewhere at all, except the boinc alpha test or boinc message board.

Don't you think that we already have enough trouble here with "stable" releases of the client and the server software and getting things sorted out ?


Just because you may not be interested in the alpha versions doesn't mean others aren't. They are clearly labeled in the subject line as to being development versions, so you can ignore the message thread if you wish.
2) Message boards : Number crunching : Development BOINC 6.10.29 released (Message 35713)
Posted 17 Jan 2010 by MarkJ
Post:
Another new one to test.

REMINDER TO ALL ALPHA TESTERS:
It's far easier for us to fix problems if you send message logs with the appropriate flags set. The main flags are:

<cpu_sched_debug>: problems involving the choice of applications to run.
<work_fetch_debug>: problems involving work fetch (which projects are asked for work, and how much).
<rr_simulation>: problems involving jobs being run in high-priority mode.

Use these flags from the cc_config.xml file.

Report any problems you get with it to the Alpha email list. This list needs registration.

The change logs since 6.10.25...

Change Log:

6.10.26

- client: add missing dlsym of cuMemGetInfo() on non_Windows platforms.

- MGR: fix another bug due to changes for Snow Leopard compatibility: on OS 10.4.11 (Tiger) and perhaps others, when Automatic Login is set, getlogin() returns "root" for a time after the system is first booted, causing the Manager to think the user is not a member of group boinc_master. So check "USER" environment variable instead.

- Mac MGR: Call Mac accessibility calls GetViewDisplayName() instead of GetViewName() to announce localized tab names.

- client: Eliminate x86_64 Mac client; i386 client determines if system supports x86_64 applications and sets HOSTTYPE and platform accordingly. This allows us to link with the 32-bit CUDA libraries. The one other effect is that the benchmarks are run in 32-bit mode even on a 64-bit capable Mac.

- client: Async get_state RPC was not updating state.have_ati field.

- MGR: Rebuild Advanced Menu and Taskbar Menu after connecting to client, so GPU Activity and Snooze GPU items are displayed if needed.

- Mac: Fix bug in backtrace code which showed up only under OS 10.6.

- Mac installer: Add CUDA information to Mac ReadMe files.


6.10.27

- client (Mac): it's DYLD_LIBRARY_PATH, not DYLIB_LIBRARY_PATH

- client: ATI available RAM wasn't being detected correctly


6.10.28

- client sandbox: set LD_LIBRARY_PATH and DYLD_LIBRARY_PATH in switcher.

For unknown reasons, the these 2 environment variables are not passed in to switcher, though all other environment variables do get propagated.


6.10.29

- client (Mac): append /usr/local/cuda/lib to LD_LIBRARY_PATH and DYLD_LIBRARY_PATH

- client: show <cpu_sched> message when suspend/resume GPU activity

- client: there are oddball cases where the client has an app for which avg_ncpus > ncpus. Allow such jobs to run; otherwise nothing runs.

- client: in computing "anticipated" STD, scale by ninstances (from John McLeod)

- MGR: Deconflict menu item IDs.

- manager/client: show PID in task properties; add PID to RESULT structure in GUI RPC

- client: when parsing cc_config.xml, clear vectors so we don't end up with duplicates

- client: divide LTD deltas by ninstances, same as for STD.

This is cosmetic - it won't affect work fetch, but it will prevent LTD from changing faster than real time

- client: add logic to work fetch so that each project will have enough jobs to use its share of resource instances.

This avoids situations where e.g. on a 2-CPU system a project has 75% resource share and 1 CPU job, and its STD increases without bound.

Did a general cleanup of the logic for computing work request sizes (seconds and instances).

- client: Unix: if can't create client lock file,
report ERR_OPEN rather than ERR_ALREADY_RUNNING. fixes #970

- client: fix format strings for ninstances (can be fraction now)

- client: scheduling problem:

- a project overestimates job FLOP counts

- the client starts jobs in EDF mode

- as job progresses and fraction done increases, its completion time estimate decreases until it's no longer a deadline miss.

- job gets preempted by other job from that project; you end up with lots of partly completed jobs.

Solution (I hope): if an app version has running jobs, compute a "temp DCF" for the app version, which is the min of dynamic/static estimates for its jobs.

Apply this scaling factor to completion time estimates for unstarted jobs in RR simulation

- client: the estimation of remaining time of running jobs was wrong (how did this bug survive so long?)

- client: bug in ACTIVE_TASK::est_dur()

- client: work fetch fix: avoid sending null request in certain cases.

- client: add <stderr_head> config option; sends the first rather than last 64KB of stderr to server.

This doesn't belong here; this choice should come from the server. I may take this out later.

- client: small tweak to work fetch: if project has crazy DCF, don't automatically request 1 sec; only request work if there's a shortfall.
3) Message boards : Number crunching : Development BOINC 6.10.17 released (Message 33164)
Posted 9 Nov 2009 by MarkJ
Post:
I did a reinstall and swapped to Windows 7 yesterday, also updating my BOINC from 6.10.13 to this new one, tranferring my WUs to the new install. Now my machine has decided that it is only going to run one CPU WU at a time(I run an i7 specified to use 6 core in my prefs). :P GPU is working fine, but it kinda sucks having all those cores idling. gonna let it crunch thru the WUs I had in cache when i swapped OSes and see if it gets its head out of its rar then. ;)


You haven't been running Aqua MT work have you? There seems to be a problem with it resuming use of all cores after an Aqua multi-thread wu finishes. Apparently 6.10.13 is better behaved with multi-thread apps, so I am told. I don't run Aqua though.

6.10.18 is now out. Only revised language packs and a couple of minor tweaks supposedly.
4) Message boards : Number crunching : Development BOINC 6.10.17 released (Message 32887)
Posted 31 Oct 2009 by MarkJ
Post:
Now its the "official" version. From the BOINC Alpha email list...

We are pleased to announce that 6.10 is now ready for public use.

This release of BOINC contains the following enhancements:

1. Support for ATI GPUs

2. Support for detecting proxy configurations within companies

3. Improvements to the CPU/GPU scheduler

4. A new default screen saver

I would like to thanks everybody who has used a pre-release version of 6.10 over the last couple of months, for providing feedback and helping us make the BOINC system even better.

Release Notes: Release_Notes

System Requirements: System_Requirements

Download: Download

----- Rom

BOINC Development Team
5) Message boards : Number crunching : Development BOINC 6.10.17 released (Message 32862)
Posted 29 Oct 2009 by MarkJ
Post:
Another new one to test. This is likely to become the official version next week unless "showstopper" bugs are found.

REMINDER TO ALL ALPHA TESTERS:
It's far easier for us to fix problems if you send message logs with the appropriate flags set. The main flags are:

<cpu_sched_debug>: problems involving the choice of applications to run.
<work_fetch_debug>: problems involving work fetch (which projects are asked for work, and how much).
<rr_simulation>: problems involving jobs being run in high-priority mode.

Use these flags from the cc_config.xml file.

Report any problems you get with it to the Alpha email list. This list needs registration.

The offical change log:

- WINSETUP: Remove the 'SeDebugPrivilege' prev from the list of privs the installer sets for the BOINC client itself.

- MGR: Change the shortcut key for switching to the simple view.

- client: If an administrator has deployed proxy settings at runtime or during a VPN connection allow the client to read the new proxy configuration from the registry.

- MGR: Add View menu with Cmd+Shift+A to Mac Simple GUI for disabled users because Mac manager cannot eliminate menu bar or detect active screen reader. On Windows, manager prevents switch to Simple GUI if screen reader is active.

- WININSTALL: Abort install if Win9x detected
6) Message boards : Number crunching : BOINC 6.10.14 (Message 32574)
Posted 20 Oct 2009 by MarkJ
Post:
6.10.15 is out for Windows. Doesn't really warrant its own topic as the only change seems to be an important fix for remote desktop users whose hosts are also contributing GPU resources, a combination I expect is pretty rare.
- client: Use is_remote_desktop() instead of the various GPU functions
. . . . . to determine when the client software has been switched into Remote
. . . . . Desktop mode and shutsdown GPU apps.  This will prevent App crashes.


Well there is a little bit more to it. From the BOINC forum...

Rom Walton wrote:
Howdy Folks,

Major fixes for this release are:

1. Startup problems on reboot should be fixed. Everybody should reboot at least once and verify that the manager can start the client at logon.

2. The introduction of a limbo state when the GPU disappears. Task instances should error out if they go past deadline.

3. We introduced some code to detect Remote Desktop and to move GPU jobs into limbo until the user signs back into the console. The original detection code is where the .13 client was crashing, the new code doesn't appear to work correctly. If I can figure out what is going wrong I'll do another release for that.

Please give items 1 and 2 a few tries. Changing driver versions and that should trigger #2.


Charlie 16 October 2009
- MGR: Fix build break on Mac

Rom 19 October 2009
- client: Use is_remote_desktop() instead of the various GPU functions to determine when the client software has been switched into Remote Desktop mode and shutsdown GPU apps. This will prevent App crashes.
7) Message boards : Number crunching : Server s/w update? (Message 32385)
Posted 15 Oct 2009 by MarkJ
Post:
If you look at Your Account -> Your computers you will notice the GPU column is blank. On Seti it picks up ATI and Nvidia GPU's because the server s/w has been updated to store that information.

As the guys above have said we await Travis talking the network engineers into putting the latest version on. The question is when that may be.

I notice that GPUgrid is now showing the BOINC version with the computer details, on their site. It wasn't there 2 days ago so its a recent addition.
8) Message boards : Number crunching : Server s/w update? (Message 32358)
Posted 14 Oct 2009 by MarkJ
Post:
I understand the server s/w has been updated to support the ATI gpu's being reported. It does over at Seti.

Probably a question for Travis. Are there plans to update the server s/w here to also support the ATI gpus? If so, when?
9) Message boards : Number crunching : v0.20 issues win32 (Message 32214)
Posted 10 Oct 2009 by MarkJ
Post:
I managed to crash the driver about 5 times after I posted this. I will try 8.12 which I saw recommended in another thread. Oh and the later BOINC version made no difference.


Well 8.12 seems to be much better so far. I am also running two wu at a time and nothing for <cmdline>. Current setup is an i7-920 under WinXP. HD4850 at stock speed, BOINC 6.10.13 and Catalyst 8.12 (and none of the ATI add-ons).

I've had it running for a couple of days without any issues yet (touch wood). Its also mentioned in the readme file about Cat 8.12 :-)
10) Message boards : Number crunching : v0.20 issues win32 (Message 32132)
Posted 8 Oct 2009 by MarkJ
Post:
Try rolling back to 9.2 or forward to the latest WHQL version


Well I tried catalyst's 9.1, 9.2 (previously had 9.8 installed from shop) and now on 9.9 (latest and greatest). The 9.9 seems to be a bit more stable as I have only killed the driver once, and despite trying it seems to keep working now.

Seeing as I am in experimental s/w mode I guess I might try BOINC 6.10.13 as well :-)


I take it back!

I managed to crash the driver about 5 times after I posted this. I will try 8.12 which I saw recommended in another thread. Oh and the later BOINC version made no difference.
11) Message boards : Number crunching : v0.20 issues win32 (Message 32074)
Posted 7 Oct 2009 by MarkJ
Post:
Try rolling back to 9.2 or forward to the latest WHQL version


Well I tried catalyst's 9.1, 9.2 (previously had 9.8 installed from shop) and now on 9.9 (latest and greatest). The 9.9 seems to be a bit more stable as I have only killed the driver once, and despite trying it seems to keep working now.

Seeing as I am in experimental s/w mode I guess I might try BOINC 6.10.13 as well :-)
12) Message boards : Number crunching : v0.20 issues win32 (Message 32024)
Posted 6 Oct 2009 by MarkJ
Post:
My 1st post. I've recently joined as I now have a system with an ATI card in it. I have been getting a few VDU errors with the driver restarting. My setup:

HD4850 card (1Gb)
BOINC 6.10.11
Cat 9.8
Running 0.20 with a single wu.
Win XP (32 bit)

Did the copy of the ATI*.dll's as advised in the readme. Is this still required with BOINC 6.10.11?

I have tried running 2 and 3 wu at a time (changed <coproc> in app_info to 0.5 or 0.33) but they seem to take the same time as doing them one at a time.

My VDU errors usually occur when I click on one of the tabs in BOINC and then it does the popup about reporting the error. Only happens if I have some MW work units running at the same time on GPU. The wu running at the time will proceed up to 100% and then gets a computation error. Do I need to put an entry in the <cmdline> in app_info?

Any help appreciated.
Thanks




©2024 Astroinformatics Group