Forum > GPU crunching
BOINC 6.10.x (Alpha) For Windows
Claggy:
--- Quote from: MarkJ on 04 Oct 2009, 05:34:21 am ---That must have been the .4 and .5 interations. We are now up to 6.10.11 which seems to be okay so far. There have been a couple of fixes since so expect a new version any day soon.
--- End quote ---
Boinc 6.10.12 is out:
boinc_6.10.12_windows_intelx86.exe
boinc_6.10.12_windows_x86_64.exe
Claggy
Edit:
Change Log:
Rom 2 October 2009
- client: fix crashing bug introduced in [18605]
Rom 5 october 2009
- client: if downloaded project list file is garbage, ignore it.
- all: accept <foo /> as an XML bool
- client: Apparently it is valid for the autoproxy to return successful API completeion but a null proxy list. Check for the null instead of crashing.
- client: only support one of the ati13* plan classes at a time. A couple users had not updated their amdcal* runtime libraries after upgrading catalyst drivers. This was leading to crashes of the project applications when work was supplied looking for the old DLL names.
- client: fix a handle leak I just introduced. (From: Andreas a.k.a Gipsel)
- lib: Fix memory/resource leak. (From Nicolás Alvarez)
- lib: Add additional ATI descriptions.
- lib: Fix some inaccurate ATI capabilities in certain cards. (From: Andreas a.k.a Gipsel)
- lib: Fix memory/resource leak. (From Nicolás Alvarez) (reprise)
- client: restore calDeviceGetInfo(), add its info to COPROC_ATI struct (some plan class might need to know this).
- Code cleanup.
- client: better behavior if a GPU goes away:
1) if an APP_VERSION is missing a coprocessor, don't delete it and its files. (If the coprocessor returns, we won't need to re-download)
2) if a RESULT uses an app version that is missing a coprocessor, abort it (rather than deleting it). The client will report the result on the next scheduler RPC, and the server will make a new instance.
- client: fix bug where if you change project "no CPU/NVIDIA/ATI" prefs and update, the change wouldn't take effect until client restart.
- client: fix bug in enforcement of "no CPU/NVIDIA/ATI" prefs
- client: make the order of the result vector consistent with the order used to select coproc jobs
- client: improve coproc_debug messages
- client: if a task is running, uses a GPU, and the system has >1 GPU, append text to its resource string saying which GPU it's using
- manager: tweak Task properties text
- DIAG: Suspend threads right before extracting their context and then resume them afterwards. Otherwise we could end up in a deadlock state where both the main thread and a support thread are attempting to use the same system resource. In the last situation it was way down in Winsock.
- DIAG: Don't resume after the thread has been suspended, otherwise the thread stack may be trashed after extracting the context. This should still be okay though as by the time the diagnostics framework has gotten here it has already downloaded all the symbols it'll need.
Tag for 6.10.12 release, all platforms boinc_core_release_6_10_12
Richard Haselgrove:
--- Quote from: Claggy on 05 Oct 2009, 05:53:58 pm ---
Claggy
- all: accept <foo /> as an XML bool
--- End quote ---
Claggy - your space - R.I.P. :'(
Raistmer:
--- Quote from: Claggy on 05 Oct 2009, 05:53:58 pm ---2) if a RESULT uses an app version that is missing a coprocessor, abort it (rather than deleting it). The client will report the result on the next scheduler RPC, and the server will make a new instance.
--- End quote ---
Welcome to lose work in progress as official BOINC's politics.
Claggy:
--- Quote from: Richard Haselgrove on 05 Oct 2009, 07:37:58 pm ---
--- Quote from: Claggy on 05 Oct 2009, 05:53:58 pm ---
Claggy
- all: accept <foo /> as an XML bool
--- End quote ---
Claggy - your space - R.I.P. :'(
--- End quote ---
Yes I'd noticed Claggy's Space was no more. :'(
Boinc 6.10.13 is released:
boinc_6.10.13_windows_intelx86.exe
boinc_6.10.13_windows_x86_64.exe
Claggy
Edit:
Change Log:
Rom 5 october 2009
- client: Fix crash that was introduced 7 months ago. (From Nicolás Alvarez)
- client: Fix a missed checkin that prevents a crash during autoproxy detection.
Tag for 6.10.13 release, all platforms boinc_core_release_6_10_13
Arnulf:
Hello Claggy!
Can you tell me if there is some coding that errors out WU's that runs for more than 24 hours?
I have tested the 6.10.12 version and that one reports errors when running over 86430 seconds.
When re-installing 6.10.3 the errors goes away.
Arnulf
Here are the results:
http://setiathome.berkeley.edu/beta/workunit.php?wuid=2321437
http://setiathome.berkeley.edu/beta/workunit.php?wuid=2321435
http://setiathome.berkeley.edu/beta/workunit.php?wuid=2321436
http://setiathome.berkeley.edu/beta/workunit.php?wuid=2321243
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version