Author |
Message |
GDFVolunteer moderator Project administrator Project developer Project tester Volunteer developer Volunteer tester Project scientist Send message
Joined: 14 Mar 07 Posts: 1957 Credit: 629,356 RAC: 0 Level
Scientific publications
|
Today we are going to update the Windows application as we did for Linux yesterday.
Main changes are:
1) Use of PLUMED plugin for metadynamics calculations
2) small bug fixes
gdf |
|
|
GDFVolunteer moderator Project administrator Project developer Project tester Volunteer developer Volunteer tester Project scientist Send message
Joined: 14 Mar 07 Posts: 1957 Credit: 629,356 RAC: 0 Level
Scientific publications
|
Updated.
gdf |
|
|
|
has rolled back to cuda2.2?
____________
|
|
|
GDFVolunteer moderator Project administrator Project developer Project tester Volunteer developer Volunteer tester Project scientist Send message
Joined: 14 Mar 07 Posts: 1957 Credit: 629,356 RAC: 0 Level
Scientific publications
|
For the time being. CUDA2.3 did not solve at all the FFT problem with 260 cards.
gdf |
|
|
|
Seems to have at least one bug - I just got this error message on my screen:
acemd_6.69_windows_intelx86_cuda.exe has
stopped working
A problem caused the program to stop working correctly.
Windows will close the program and notify you if a solution is
available.
(in a box:) Close program
I plan to suspend BOINC long enough to copy everything in that slot, then tell it to close the program and see if that does anything useful.
(some delay)
I did; the slot emptied, and the log then showed these messages:
9/22/2009 11:56:01 PM Suspending computation - user request
9/23/2009 12:00:23 AM GPUGRID Computation for task 865-GIANNI_BIND001-35-100-RND9374_3 finished
9/23/2009 12:00:23 AM GPUGRID Output file 865-GIANNI_BIND001-35-100-RND9374_3_0 for task 865-GIANNI_BIND001-35-100-RND9374_3 absent
9/23/2009 12:00:23 AM GPUGRID Output file 865-GIANNI_BIND001-35-100-RND9374_3_1 for task 865-GIANNI_BIND001-35-100-RND9374_3 absent
9/23/2009 12:00:23 AM GPUGRID Output file 865-GIANNI_BIND001-35-100-RND9374_3_2 for task 865-GIANNI_BIND001-35-100-RND9374_3 absent
9/23/2009 12:00:23 AM GPUGRID Output file 865-GIANNI_BIND001-35-100-RND9374_3_3 for task 865-GIANNI_BIND001-35-100-RND9374_3 absent
9/23/2009 12:00:52 AM GPUGRID update requested by user
9/23/2009 12:00:53 AM GPUGRID Sending scheduler request: Requested by user.
9/23/2009 12:00:53 AM GPUGRID Reporting 1 completed tasks, not requesting new tasks
9/23/2009 12:00:58 AM GPUGRID Scheduler request completed
9/23/2009 12:01:03 AM Resuming computation
and later these messages:
9/23/2009 12:03:00 AM GPUGRID Sending scheduler request: To fetch work.
9/23/2009 12:03:00 AM GPUGRID Requesting new tasks for CPU
9/23/2009 12:03:05 AM GPUGRID Scheduler request completed: got 0 new tasks
9/23/2009 12:03:05 AM GPUGRID Message from server: No work sent
9/23/2009 12:03:05 AM GPUGRID Message from server: ACEMD beta version is not available for your type of computer.
9/23/2009 12:03:05 AM GPUGRID Message from server: Full-atom molecular dynamics on Cell processor is not available for your type of computer.
9/23/2009 12:03:40 AM GPUGRID Sending scheduler request: To fetch work.
9/23/2009 12:03:40 AM GPUGRID Requesting new tasks for GPU
9/23/2009 12:03:45 AM GPUGRID Scheduler request completed: got 0 new tasks
9/23/2009 12:03:45 AM GPUGRID Message from server: No work sent
9/23/2009 12:03:45 AM GPUGRID Message from server: ACEMD beta version is not available for your type of computer.
9/23/2009 12:03:45 AM GPUGRID Message from server: Full-atom molecular dynamics on Cell processor is not available for your type of computer.
Looks like BOINC may have decided to try to get its next few GPU workunits from the other BOINC projects that computer participates in - never mind that it's already found several times that none of them have any at present.
Let me know if sending you what I copied would be helpful.
By the way, I saw something over at World Community Grid saying that, starting with BOINC 6.10.5, it will be possible for projects to tell clients to wait longer than usual (several days) before asking for any more CPU workunits, or if appropriate, any more GPU workunits instead.
You may want to check if the load on your server is enough that you need this feature soon.
This machine uses BOINC 6.6.36 under Vista SP2.
An idea to consider: in any future threads about new application versions, include the program name and version number in the title, so that participants can easily tell whether that thread applies to a version they have run lately. |
|
|
|
(duplicate) |
|
|
|
The last news says that Boinc 6.10.3 is the recommended version. But 6.10.3 is no more available for download on boinc website.
What's the recommended version ?
Regards,
Bill |
|
|
GDFVolunteer moderator Project administrator Project developer Project tester Volunteer developer Volunteer tester Project scientist Send message
Joined: 14 Mar 07 Posts: 1957 Credit: 629,356 RAC: 0 Level
Scientific publications
|
http://www.gpugrid.net/join.php for the recommended version of BOINC.
gdf |
|
|
GDFVolunteer moderator Project administrator Project developer Project tester Volunteer developer Volunteer tester Project scientist Send message
Joined: 14 Mar 07 Posts: 1957 Credit: 629,356 RAC: 0 Level
Scientific publications
|
New application for windows uploaded 6.71.
gdf |
|
|
MarkJ Volunteer moderator Volunteer tester Send message
Joined: 24 Dec 08 Posts: 738 Credit: 200,909,904 RAC: 0 Level
Scientific publications
|
The last news says that Boinc 6.10.3 is the recommended version. But 6.10.3 is no more available for download on boinc website.
What's the recommended version ?
Regards,
Bill
Sure its available, along with all the older ones and the alpha test ones. Follow this link
____________
BOINC blog |
|
|
MarkJ Volunteer moderator Volunteer tester Send message
Joined: 24 Dec 08 Posts: 738 Credit: 200,909,904 RAC: 0 Level
Scientific publications
|
By the way, I saw something over at World Community Grid saying that, starting with BOINC 6.10.5, it will be possible for projects to tell clients to wait longer than usual (several days) before asking for any more CPU workunits, or if appropriate, any more GPU workunits instead.
You may want to check if the load on your server is enough that you need this feature soon.
The release notes for 6.10.6 mention the optional backoff in the scheduler reply. You can find the release notes here. The backoff can be specified for CPU, ATI and Cuda.
____________
BOINC blog |
|
|
|
Seems to have at least one bug - I just got this error message on my screen:
acemd_6.69_windows_intelx86_cuda.exe has
stopped working
A problem caused the program to stop working correctly.
Windows will close the program and notify you if a solution is
available.
(in a box:) Close program
I plan to suspend BOINC long enough to copy everything in that slot, then tell it to close the program and see if that does anything useful.
(some delay)
I did; the slot emptied, and the log then showed these messages:
9/22/2009 11:56:01 PM Suspending computation - user request
9/23/2009 12:00:23 AM GPUGRID Computation for task 865-GIANNI_BIND001-35-100-RND9374_3 finished
9/23/2009 12:00:23 AM GPUGRID Output file 865-GIANNI_BIND001-35-100-RND9374_3_0 for task 865-GIANNI_BIND001-35-100-RND9374_3 absent
9/23/2009 12:00:23 AM GPUGRID Output file 865-GIANNI_BIND001-35-100-RND9374_3_1 for task 865-GIANNI_BIND001-35-100-RND9374_3 absent
9/23/2009 12:00:23 AM GPUGRID Output file 865-GIANNI_BIND001-35-100-RND9374_3_2 for task 865-GIANNI_BIND001-35-100-RND9374_3 absent
9/23/2009 12:00:23 AM GPUGRID Output file 865-GIANNI_BIND001-35-100-RND9374_3_3 for task 865-GIANNI_BIND001-35-100-RND9374_3 absent
9/23/2009 12:00:52 AM GPUGRID update requested by user
9/23/2009 12:00:53 AM GPUGRID Sending scheduler request: Requested by user.
9/23/2009 12:00:53 AM GPUGRID Reporting 1 completed tasks, not requesting new tasks
9/23/2009 12:00:58 AM GPUGRID Scheduler request completed
9/23/2009 12:01:03 AM Resuming computation
and later these messages:
9/23/2009 12:03:00 AM GPUGRID Sending scheduler request: To fetch work.
9/23/2009 12:03:00 AM GPUGRID Requesting new tasks for CPU
9/23/2009 12:03:05 AM GPUGRID Scheduler request completed: got 0 new tasks
9/23/2009 12:03:05 AM GPUGRID Message from server: No work sent
9/23/2009 12:03:05 AM GPUGRID Message from server: ACEMD beta version is not available for your type of computer.
9/23/2009 12:03:05 AM GPUGRID Message from server: Full-atom molecular dynamics on Cell processor is not available for your type of computer.
9/23/2009 12:03:40 AM GPUGRID Sending scheduler request: To fetch work.
9/23/2009 12:03:40 AM GPUGRID Requesting new tasks for GPU
9/23/2009 12:03:45 AM GPUGRID Scheduler request completed: got 0 new tasks
9/23/2009 12:03:45 AM GPUGRID Message from server: No work sent
9/23/2009 12:03:45 AM GPUGRID Message from server: ACEMD beta version is not available for your type of computer.
9/23/2009 12:03:45 AM GPUGRID Message from server: Full-atom molecular dynamics on Cell processor is not available for your type of computer.
Looks like BOINC may have decided to try to get its next few GPU workunits from the other BOINC projects that computer participates in - never mind that it's already found several times that none of them have any at present.
Let me know if sending you what I copied would be helpful.
By the way, I saw something over at World Community Grid saying that, starting with BOINC 6.10.5, it will be possible for projects to tell clients to wait longer than usual (several days) before asking for any more CPU workunits, or if appropriate, any more GPU workunits instead.
You may want to check if the load on your server is enough that you need this feature soon.
This machine uses BOINC 6.6.36 under Vista SP2.
An idea to consider: in any future threads about new application versions, include the program name and version number in the title, so that participants can easily tell whether that thread applies to a version they have run lately.
Same error for me. I said that since few mounth \o/
I Have 1 260 (216) and 1 8800 GT on vista 64 sp2, and driver 182.5. If i install any other driver I have always this pb.
With 182.5, I have this pb 5% of time. |
|
|
|
Well in my case, the new app did not even solve the computation errors at all.
the only difference is that it now takes a couple hrs before it crashes.
In comparsion to other Boinc projects, GPU Grid is -that is my opinion- just a big waste of GPU Time for me.
By the way, is there any way that i can completly cancel my account here?
I mean in a way that each and every account Data will be completly removed from this project? |
|
|
GDFVolunteer moderator Project administrator Project developer Project tester Volunteer developer Volunteer tester Project scientist Send message
Joined: 14 Mar 07 Posts: 1957 Credit: 629,356 RAC: 0 Level
Scientific publications
|
Hi,
the problem is not directly us, but the fact that Nvidia libraries are bugged for your card.
gdf |
|
|
|
By the way, is there any way that i can completly cancel my account here?
I mean in a way that each and every account Data will be completly removed from this project?
No!
____________
Radio Caroline, the world's most famous offshore pirate radio station.
Great music since April 1964. Support Radio Caroline Team -
Radio Caroline |
|
|
|
Well... I can now confirm that on GTX260 WUs still can't be processed. There are only new bugs appears:
24.09.2009 20:11:43 GPUGRID [error] Can't rename output file 29-GIANNI_VIL-0-100-RND2120_2_5 to projects/www.gpugrid.net/29-GIANNI_VIL-0-100-RND2120_2_5: Error 2
24.09.2009 20:11:48 GPUGRID [error] Can't rename output file 29-GIANNI_VIL-0-100-RND2120_2_6 to projects/www.gpugrid.net/29-GIANNI_VIL-0-100-RND2120_2_6: Error 2
24.09.2009 20:11:48 GPUGRID Computation for task 29-GIANNI_VIL-0-100-RND2120_2 finished
24.09.2009 20:11:48 GPUGRID Output file 29-GIANNI_VIL-0-100-RND2120_2_1 for task 29-GIANNI_VIL-0-100-RND2120_2 absent
24.09.2009 20:11:48 GPUGRID Output file 29-GIANNI_VIL-0-100-RND2120_2_2 for task 29-GIANNI_VIL-0-100-RND2120_2 absent
24.09.2009 20:11:48 GPUGRID Output file 29-GIANNI_VIL-0-100-RND2120_2_3 for task 29-GIANNI_VIL-0-100-RND2120_2 absent
24.09.2009 20:11:52 GPUGRID Started upload of 29-GIANNI_VIL-0-100-RND2120_2_0
24.09.2009 20:11:52 GPUGRID Started upload of 29-GIANNI_VIL-0-100-RND2120_2_4
24.09.2009 20:12:00 GPUGRID Finished upload of 29-GIANNI_VIL-0-100-RND2120_2_0
24.09.2009 20:12:00 GPUGRID Started upload of 29-GIANNI_VIL-0-100-RND2120_2_7
24.09.2009 20:12:04 GPUGRID Finished upload of 29-GIANNI_VIL-0-100-RND2120_2_7
24.09.2009 20:15:57 GPUGRID Finished upload of 29-GIANNI_VIL-0-100-RND2120_2_4
____________
From Siberia with love!
|
|
|
dataman Send message
Joined: 18 Sep 08 Posts: 36 Credit: 100,352,867 RAC: 0 Level
Scientific publications
|
Well... I can now confirm that on GTX260 WUs still can't be processed.
Not true. I have 7 GTX260's running and I have not had an error since 6.71 came out.
This is my config if it is any help to anyone:
Win7 64-bit, BOINC 6.10.6, nVidia 190.62, CUDA 2.3; Q6600 (standard clock), GTX260 (standard clock), 8 gig memory.
I am using the same config on XP SP3 (Pentium D) 32-bit and Vista 64-bit (Q6600)
Hope this helps. Cheers!
____________
|
|
|
GDFVolunteer moderator Project administrator Project developer Project tester Volunteer developer Volunteer tester Project scientist Send message
Joined: 14 Mar 07 Posts: 1957 Credit: 629,356 RAC: 0 Level
Scientific publications
|
This problem with the 260 cards affects most but bot all users.
Go figure out why...
gdf |
|
|
JetSend message
Joined: 14 Jun 09 Posts: 25 Credit: 5,835,455 RAC: 0 Level
Scientific publications
|
I do not have any problems with fft "bug" on GTX 260, not now, not previously. But I should state, that after update I've noticed constant & consequental processing time increasing & some kind of sudden WU amount limitation message from BOINC manager:
24/09/2009 05:37:46 GPUGRID Message from server: No work sent
24/09/2009 05:37:46 GPUGRID Message from server: (reached limit of 6 GPU tasks)
Usually I was able to proceed 9 WU's a day...
Something is going wrong :-(
____________
|
|
|
|
A recent version of acemd from GPUGRID and a recent version of rosetta_beta from Rosetta@home may have a compatibility problem; if not, the rosetta_beta graphics portion appears to have frozen by itself.
9/24/2009 4:39:22 PM CUDA device: GeForce 9800 GT (driver version 19038, compute capability 1.1, 1024MB, est. 60GFLOPS)
9/24/2009 4:39:35 PM rosetta@home Restarting task Rossmann2X3_002_14911_14657_0 using rosetta_beta version 598
9/24/2009 4:39:38 PM GPUGRID Restarting task PMEno54-OTTO_HERG4-10-40-RND5579_0 using acemd version 671
Today, I saw the graphics portion of a rosetta_beta workunit freeze in a way that kept it from ending its screensaver function when I used the keyboard and mouse.
Some information above about which workunits resumed after I rebooted the computer.
The rosetta_beta workunit resumed at essentially the same point shown in the frozen graphics before the reboot.
No info yet on if the calculations portions of the two workunits were affected.
Currently using Nvidia driver version 190.38; haven't seen any word yet on whether the 190.62 version now available is likely to be more reliable.
64-bit Vista SP2
BOINC version 6.6.36 |
|
|
|
I have 2 GTX 260 216 190.62, 6.6.38 Vista 64 and things have been perfect since update. |
|
|
MarkJ Volunteer moderator Volunteer tester Send message
Joined: 24 Dec 08 Posts: 738 Credit: 200,909,904 RAC: 0 Level
Scientific publications
|
I allowed my machine with dual GTX260's to pickup a couple of work units now we have the acemd 6.71 app. I will report how it goes.
I noticed that it uses plan class cuda now and the cuda 2.2 dll's instead of the cuda23 plan class (along with appropiate dll's). Is this an intended part of the update?
____________
BOINC blog |
|
|
GDFVolunteer moderator Project administrator Project developer Project tester Volunteer developer Volunteer tester Project scientist Send message
Joined: 14 Mar 07 Posts: 1957 Credit: 629,356 RAC: 0 Level
Scientific publications
|
yes,
cuda2.3 did not solve any real bug of cuda fft.
gdf |
|
|
MarkJ Volunteer moderator Volunteer tester Send message
Joined: 24 Dec 08 Posts: 738 Credit: 200,909,904 RAC: 0 Level
Scientific publications
|
yes,
cuda2.3 did not solve any real bug of cuda fft.
gdf
It doesn't seem that 2.2 does either. I had a 50% success rate. One worked and one failed.
____________
BOINC blog |
|
|
GDFVolunteer moderator Project administrator Project developer Project tester Volunteer developer Volunteer tester Project scientist Send message
Joined: 14 Mar 07 Posts: 1957 Credit: 629,356 RAC: 0 Level
Scientific publications
|
no, cuda2.2 does not. At the end is probably a driver issue.
We will see if one day they decide to solve it or we have to wait for gtx260 to phase out...
gdf |
|
|
|
no, cuda2.2 does not. At the end is probably a driver issue.
We will see if one day they decide to solve it or we have to wait for gtx260 to phase out...
gdf
4-5 years wait ... I mean they may stop selling them in a year, but they are likely to be about in people's systems for far longer ...
Heck, I am kinda waiting for the next generation to come out so that the 260 cards and the like get pushed down to replace the 9800 series which seemed to be about the low end card that Frys was selling this weekend ... |
|
|
w42Send message
Joined: 12 Jun 09 Posts: 1 Credit: 739,539 RAC: 0 Level
Scientific publications
|
Looks like the new application version also broke GTS250 support for me. Now every work unit fails with "Cuda error: Kernel [pme_fill_charges_overflow] failed in file 'fillcharges.cu' in line 97 : unknown error." or some other unknown error after few hours runtime. Only thing that changed was the application version.
Oh well, I guess I disable this project until your application gets fixed or there's a stable version out for the recommended BOINC version (assuming that'll help). :( |
|
|
zpm Send message
Joined: 2 Mar 09 Posts: 159 Credit: 13,639,818 RAC: 0 Level
Scientific publications
|
i will admit, 190XX+ are unstable for public use... |
|
|
|
no, cuda2.2 does not. At the end is probably a driver issue.
We will see if one day they decide to solve it or we have to wait for gtx260 to phase out...
gdf
4-5 years wait ... I mean they may stop selling them in a year, but they are likely to be about in people's systems for far longer ...
Heck, I am kinda waiting for the next generation to come out so that the 260 cards and the like get pushed down to replace the 9800 series which seemed to be about the low end card that Frys was selling this weekend ...
Expect the next generation to start being available in the next few weeks, at least for the basic chip (GT300), although in rather small numbers. I've seen guesses that it will be early next year before many cards using it are available.
Nvidia has announced that they plan to start offering some new compilers at about the same time, including some for C++ and Fortran, so expect some competition from other BOINC projects that decided to wait until compilers for those languages were available. I haven't seen a clear statement yet on whether those new compilers will also work for the older chips they already sell.
|
|
|
|
A recent version of acemd from GPUGRID and a recent version of rosetta_beta from Rosetta@home may have a compatibility problem; if not, the rosetta_beta graphics portion appears to have frozen by itself.
9/24/2009 4:39:22 PM CUDA device: GeForce 9800 GT (driver version 19038, compute capability 1.1, 1024MB, est. 60GFLOPS)
9/24/2009 4:39:35 PM rosetta@home Restarting task Rossmann2X3_002_14911_14657_0 using rosetta_beta version 598
9/24/2009 4:39:38 PM GPUGRID Restarting task PMEno54-OTTO_HERG4-10-40-RND5579_0 using acemd version 671
Today, I saw the graphics portion of a rosetta_beta workunit freeze in a way that kept it from ending its screensaver function when I used the keyboard and mouse.
Have now seen essentially the same problem with a second rosetta_beta workunit, and also with a workunit from QMC@home.
A new guess on what the problem is: The newer versions of BOINC come with a screensaver that automatically displays graphics from one of the workunits that are running, waits a while, then moves those graphics to a different place on the screen. So far, the three times I've seen this problem, it's been while showing graphics that cover the whole screen, leaving no place to move them to. Therefore I'll guess that the new screensaver is unable to deal with situations when it is time to move the graphics, but the graphics are too big to leave anywhere else to move them.
If this is correct, Docking@home is yet another project likely to trigger this problem, even though I haven't seen any Docking@home workunit trigger it yet. Also, many of the GPUGRID participants who also participate in any of these three other BOINC projects are likely to need instructions on how to keep the new screensaver from running at all. |
|
|