I detached and reattached my PC, with the AGP HD3850, to run the WUs on it's CPUs.

I now have 12 _3s_2_ WUs to crunch. So, there may be a few of thse around still.

I only moved to this about an hour ago, so when this picks up new work I will look see if I only get the _1s_2's and the _2s_1s and _2s_2's first before moving back to the GPU.

---

Go away, I was asleep

Gipsel got it fixed with version 0.19f:

http://www.file-upload.net/download-1684038/Milkyway_0.19f_ATI.zip.html


Vielen Dank Gipsel !

Unrelated to the 3s workunits, I've noticed some odd behavior since updating my BOINC client to version 6.6.31. When I get some work from here on the ATI app it sits at ready to start instead of beginning immediately as it used to. I have to pause / resume the other project in progress for it to begin working GPU tasks in parallel with other CPU project work. Re-installing the ATI app did not fix the problem. I'll watch how it behaves for a little while and may have to roll back to an earlier BOINC version. I've left the supplied app_info.xml as default and it's worked fine in the past. Perhaps it may be necessary to specify some values now.

Gipsel got it fixed with version 0.19f

I will make a link out of it.
Version 0.19f of the ATI GPU application
is ready for download. Besides the fix for the three stream WUs it reports now the GPU time as WU time.

It was a really absurd bug, a missing line break in the GPU assembly (I edited the assembly after protyping it in a high level language). Because offline tools compiled it without problem (the compiler embedded to the graphics driver is obviously pickier) it was a bit hard to track that down in about 40kB assembly. But it works now.

Gipsel got it fixed with version 0.19f:

http://www.file-upload.net/download-1684038/Milkyway_0.19f_ATI.zip.html


Vielen Dank Gipsel !

Yes! thank you.
You guys are just great and second to non in the BOINC community.
Apparently you and the guys at Stanford are the only ones that know how to make programs that can put the ATI card to good use.

  "booger"                     

:p that run of comics is great!

---

Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.

Gipsel got it fixed with version 0.19f:

http://www.file-upload.net/download-1684038/Milkyway_0.19f_ATI.zip.html


Vielen Dank Gipsel !

Yes! thank you.
You guys are just great and second to non in the BOINC community.
Apparently you and the guys at Stanford are the only ones that know how to make programs that can put the ATI card to good use.

Aah. Not crap anymore then?

Gipsel got it fixed with version 0.19f

I will make a link out of it.
Version 0.19f of the ATI GPU application
is ready for download. Besides the fix for the three stream WUs it reports now the GPU time as WU time.

It was a really absurd bug, a missing line break in the GPU assembly.

THANK YOU ! Cluster Physik, you are doing a Great job with the ATI Apps !

I wish my other projects like Einstein would implement ATI instead of this
focus on Cuda only nonsense.

Bill

I just had an odd one. I updated to the new version. I finished ok but it got 0 credit. Here it is The odd thing it was a ps_sgr_208_2s_2 unit.

---

4870 GPU
4870 GPU

I just had an odd one. I updated to the new version. I finished ok but it got 0 credit. Here it is The odd thing it was a ps_sgr_208_2s_2 unit.

If you look in the result, it shows it as Invalid. Why, I don't know.

---

Calm Chaos Forum...Join Calm Chaos Now

Me either, I'm keeping an eye on it for a while to see if any others do the same. That's the first invalid unit i've had here.

---

4870 GPU
4870 GPU

I've just had another one on a diffrent system. Here it is, I'm not sure what's happening. Both are very stable systems.

---

4870 GPU
4870 GPU

Here's another

---

4870 GPU
4870 GPU

Someone mentioned that the new 0.19f app runs the GPU a little harder and a little hotter. Are your fans clean?

---

Calm Chaos Forum...Join Calm Chaos Now

Aah. Not crap anymore then?

That was related to the new wu's and the fact that 2 months have gone
after the message "Almost there!" on the 'Milkyway@Home for GPUs' page
where the GPU application and discussions regarded that should take place.

Someone mentioned that the new 0.19f app runs the GPU a little harder and a little hotter. Are your fans clean?

Yes! Very much so.

Last week I was suffering overheating, and stripped down, removed PCs to outside and compressor cleaned all machines and the dust bunnies. The only PC with a MW compliant GPU had the GPU removed from the socket and separately cleaned.

Interestingly, the PC is running just as heavily loaded now (98%), but the GPU temperature has dropped back to a normal (65C from 72C) and the GPU fan load has dropped to 47% from 55%.

Perhaps it's the cooler weather.

---

Go away, I was asleep

Yes, the fans are clean. One is a recent build and the other was just changed over into a new case and everything was cleaned before installing. Under load the cards are reporting temps of ~75C. Neither card is overclocked. Both systems are in Antec900 cases. Plenty of airflow there :-).
I had several more return as invalid overnight. I didn't do a reboot after going to 19f yesterday at 2230. I just rebooted both systems at 1400 UTC today. I'm going to watch them for a bit and see if that makes any difference.

<edit>
Reboot made no difference. Still getting the occasional invalid result. Is anybody else having the same problem? I might suspect it was a computer issue if it wasn't happening on both systems.

---

4870 GPU
4870 GPU

Yes, the fans are clean. One is a recent build and the other was just changed over into a new case and everything was cleaned before installing. Under load the cards are reporting temps of ~75C. Neither card is overclocked. Both systems are in Antec900 cases. Plenty of airflow there :-).
I had several more return as invalid overnight. I didn't do a reboot after going to 19f yesterday at 2230. I just rebooted both systems at 1400 UTC today. I'm going to watch them for a bit and see if that makes any difference.

<edit>
Reboot made no difference. Still getting the occasional invalid result. Is anybody else having the same problem? I might suspect it was a computer issue if it wasn't happening on both systems.

KWSN imcrazynow

You made me look at my only GPU driven rig, and I am getting the odd invalid results as well. Three to be precise since UK lunchtime (13.30 - UTC+1). The successful WUs between them seem to be getting fewer before the next invalid result.

I wonder what ti is?

---

Go away, I was asleep

I didn't have any last night, but now I just looked and have 6 out of almost 600 results on two machines.

---

Calm Chaos Forum...Join Calm Chaos Now

I've had a few between my two GPU boxes. But *maybe* 1 in 50 or less. Example:

Task ID 74360632
Name ps_sgr_235_2s_1_674470_1244317010_0
Workunit 73253956
Created 6 Jun 2009 19:36:53 UTC
Sent 6 Jun 2009 19:39:25 UTC
Received 6 Jun 2009 19:52:15 UTC
Server state Over
Outcome Success
Client state Done
Exit status 0 (0x0)
Computer ID 24918
Report deadline 9 Jun 2009 19:39:25 UTC
CPU time 84.34375
stderr out

<core_client_version>6.4.6</core_client_version>
<![CDATA[
<stderr_txt>
Running Milkyway@home ATI GPU application version 0.19f by Gipsel
CPU: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz (4 cores/threads) 2.40002 GHz (259ms)

CAL Runtime: 1.3.145
Found 1 CAL device

Device 0: ATI Radeon HD 3800 (RV670) 512 MB local RAM (remote 28 MB cached + 512 MB uncached)
GPU core clock: 669 MHz, memory clock: 829 MHz
320 shader units organized in 4 SIMDs with 16 VLIW units (5-issue), wavefront size 64 threads
supporting double precision

3 WUs already running on GPU 0
No free GPU! Waiting ... 461.688 seconds.
Starting WU on GPU 0

main integral, 160 iterations
predicted runtime per iteration is 408 ms (33.3333 ms are allowed), dividing each iteration in 13 parts
borders of the domains at 0 128 248 376 496 616 744 864 984 1112 1232 1360 1480 1600
Calculated about 3.70012e+012 floatingpoint ops on GPU, 6.34181e+007 on FPU. Approximate GPU time 84.3438 seconds.

probability calculation (stars)
Calculated about 1.20373e+009 floatingpoint ops on FPU.

WU completed.
CPU time: 19.9844 seconds, GPU time: 84.3438 seconds, wall clock time: 716.234 seconds, CPU frequency: 2.40012 GHz

</stderr_txt>
]]>

Validate state Invalid
Claimed credit 0.364573240852738
Granted credit 0
application version 0.19

-----

-jim