Here is just a sample of the tasks which are failing.

597677568 449500025 30 Oct 2013, 6:39:49 UTC 30 Oct 2013, 8:40:00 UTC Error while computing 9.23 1.01 --- MilkyWay@Home v1.02 (opencl_amd_ati)
597677567 449500024 30 Oct 2013, 6:39:49 UTC 30 Oct 2013, 8:40:00 UTC Error while computing 11.39 0.99 --- MilkyWay@Home v1.02 (opencl_amd_ati)
597677565 449500022 30 Oct 2013, 6:39:49 UTC 30 Oct 2013, 8:40:00 UTC Error while computing 9.25 1.02 --- MilkyWay@Home v1.02 (opencl_amd_ati)
597677559 449500016 30 Oct 2013, 6:39:49 UTC 30 Oct 2013, 8:40:00 UTC Error while computing 9.25 1.17 --- MilkyWay@Home v1.02 (opencl_amd_ati)
597677558 449500015 30 Oct 2013, 6:39:49 UTC 30 Oct 2013, 8:40:00 UTC Error while computing 9.25 1.02 --- MilkyWay@Home v1.02 (opencl_amd_ati)
597677557 449500014 30 Oct 2013, 6:39:49 UTC 30 Oct 2013, 8:40:00 UTC Error while computing 9.33 0.99 --- MilkyWay@Home v1.02 (opencl_amd_ati)
597677553 449500010 30 Oct 2013, 6:39:49 UTC 30 Oct 2013, 8:40:00 UTC Error while computing 10.24 1.03 --- MilkyWay@Home v1.02 (opencl_amd_ati)
597673627 449497069 30 Oct 2013, 6:32:08 UTC 30 Oct 2013, 8:40:00 UTC Error while computing 9.19 0.90 --- MilkyWay@Home v1.02 (opencl_amd_ati)
597673626 449497068 30 Oct 2013, 6:32:08 UTC 30 Oct 2013, 8:40:00 UTC Error while computing 9.18 0.87 --- MilkyWay@Home v1.02 (opencl_amd_ati)
597673623 449497065 30 Oct 2013, 6:32:08 UTC 30 Oct 2013, 8:40:00 UTC Error while computing 9.20 0.86 --- MilkyWay@Home v1.02 (opencl_amd_ati)
597673622 449497064 30 Oct 2013, 6:32:08 UTC 30 Oct 2013, 8:40:00 UTC Error while computing 9.55 0.89 --- MilkyWay@Home v1.02 (opencl_amd_ati)
597673616 449497058 30 Oct 2013, 6:32:08 UTC 30 Oct 2013, 8:40:00 UTC Error while computing 9.18 0.89 --- MilkyWay@Home v1.02 (opencl_amd_ati)
597673615 449497057 30 Oct 2013, 6:32:08 UTC 30 Oct 2013, 8:40:00 UTC Error while computing 9.14 0.85 --- MilkyWay@Home v1.02 (opencl_amd_ati)
597673614 449497056 30 Oct 2013, 6:32:08 UTC 30 Oct 2013, 8:40:00 UTC Error while computing 9.17 0.91 --- MilkyWay@Home v1.02 (opencl_amd_ati)
597543714 449397094 30 Oct 2013, 2:05:38 UTC 30 Oct 2013, 6:39:49 UTC Error while computing 7.84 0.82 --- MilkyWay@Home v1.02 (opencl_amd_ati)
597543713 449393898 30 Oct 2013, 2:05:38 UTC 30 Oct 2013, 6:39:49 UTC Error while computing 8.76 0.85 --- MilkyWay@Home v1.02 (opencl_amd_ati)
597543712 449393502 30 Oct 2013, 2:05:38 UTC 30 Oct 2013, 6:39:49 UTC Error while computing 8.35 0.86 --- MilkyWay@Home v1.02 (opencl_amd_ati)
597543711 449388712 30 Oct 2013, 2:05:38 UTC 30 Oct 2013, 6:39:49 UTC Error while computing 8.72 0.88 --- MilkyWay@Home v1.02 (opencl_amd_ati)
597543710 449384068 30 Oct 2013, 2:05:38 UTC 30 Oct 2013, 6:39:49 UTC Error while computing 10.60 0.89 --- MilkyWay@Home v1.02 (opencl_amd_ati)

So I adjusted this setting to "no" hoping to pick them off before I get them. Correct?

MilkyWay@Home: no
MilkyWay@Home N-Body Simulation: yes
Milkyway@Home Separation: yes
Milkyway@Home Separation (Modified Fit): yes

Milkyway@Home Separation (Modified Fit) v1.28 (opencl_amd_ati) tasks are working fine. I only crunch Milkyway@home on my GPU. The CPU does Seti@home.

Thanks.

---

-mpyusko

AMD FX-8350 @ 4.3GHz
AMD Radeon RX 480 8GB @ 1342MHz/2000MHz

Here is just a sample of the tasks which are failing.

So I adjusted this setting to "no" hoping to pick them off before I get them. Correct?

MilkyWay@Home: no
MilkyWay@Home N-Body Simulation: yes
Milkyway@Home Separation: yes
Milkyway@Home Separation (Modified Fit): yes

Milkyway@Home Separation (Modified Fit) v1.28 (opencl_amd_ati) tasks are working fine. I only crunch Milkyway@home on my GPU. The CPU does Seti@home.

Thanks.

It is not a unit problem as several units that you had problems with were crunched just fine on other gpu's.

But yes the units you have excluded seem to be the ones having the problems. Do you leave a cpu core free for the gpu to use? How much cpu is each gpu unit using? When looking at my own 6950 I see "running(0.784 cpu +1 ATI GPU)". This means that each gpu unit is using just over 75% of a cpu core to keep it fed and running at full speed. Since gpu's can crank out much more work then a cpu can it makes sense to leave one cpu core free just to keep it running at full speed.

Right now it's running .945 CPUs + 1 GPU (@ 95% usage). (That's a CPU clocked at 3.504GHz/core and 820MHz GPU Clock) Seti@Home uses the remaining of Both. (I actually tried running Seti@home on my GPU and it was a waste of time. Only used <20% of my GPU)

By the way, You do know what killed the Pilsbury Doughboy right?

---

-mpyusko

AMD FX-8350 @ 4.3GHz
AMD Radeon RX 480 8GB @ 1342MHz/2000MHz

Right now it's running .945 CPUs + 1 GPU (@ 95% usage). (That's a CPU clocked at 3.504GHz/core and 820MHz GPU Clock) Seti@Home uses the remaining of Both. (I actually tried running Seti@home on my GPU and it was a waste of time. Only used <20% of my GPU)

By the way, You do know what killed the Pilsbury Doughboy right?

Yup old age!!!

As for only using 20% of the gpu at Seti did you try running more then one unit at a time?

http://funnybizblog.com/funny-stuff/pillsbury-doughboy-obituary

Anyway.... No I only ever had it try one WU at a time for Seti on the GPU. Out of the few computers I have crunching, I have 1x 4 threads of Seti, 1x 2 threads of seti, 1x 1 thread of seti, 1x 4 threads seti and GPU Primgrid (SP), 1x 2 threads seti and GPU milkyway (DP). (I also have an old K62-400 that runs on WU of Seti every 358 hours.)

So with that 'much' computing power dedicated to Seti@home, I don't feel so bad dedicating my GPU to Milkway.... as long as they complete without errors.

My one computer is a Dual-CPU Xeon but the mobo only has PCI of assorted flavors and PCI-E x8 on it. Right now it has a Voodoo 3 200PCI in it because it's way better than the RAGE/XL integrated, but I thought about picking up a PCI-E 1x 5450 to slap in there so it can crunch with the GPU. Maybe on Primegrid or something.

Since I adjusted:

MilkyWay@Home: no

I have been seeing a much higher success rate.

I just noticed this error in the logs:


Thu 07 Nov 2013 06:31:58 PM EST | Milkyway@Home | Message from server: Catalyst driver version is not OK for CAL application with this GPU

I'm using 13.11 Beta 6 for Linux. About to upgrade to 13.11 beta 8 later today. Thoughts?

---

-mpyusko

AMD FX-8350 @ 4.3GHz
AMD Radeon RX 480 8GB @ 1342MHz/2000MHz

http://funnybizblog.com/funny-stuff/pillsbury-doughboy-obituary

Anyway.... No I only ever had it try one WU at a time for Seti on the GPU. Out of the few computers I have crunching, I have 1x 4 threads of Seti, 1x 2 threads of seti, 1x 1 thread of seti, 1x 4 threads seti and GPU Primgrid (SP), 1x 2 threads seti and GPU milkyway (DP). (I also have an old K62-400 that runs on WU of Seti every 358 hours.)

So with that 'much' computing power dedicated to Seti@home, I don't feel so bad dedicating my GPU to Milkway.... as long as they complete without errors.

My one computer is a Dual-CPU Xeon but the mobo only has PCI of assorted flavors and PCI-E x8 on it. Right now it has a Voodoo 3 200PCI in it because it's way better than the RAGE/XL integrated, but I thought about picking up a PCI-E 1x 5450 to slap in there so it can crunch with the GPU. Maybe on Primegrid or something.

Since I adjusted:

MilkyWay@Home: no

I have been seeing a much higher success rate.

I just noticed this error in the logs:


Thu 07 Nov 2013 06:31:58 PM EST | Milkyway@Home | Message from server: Catalyst driver version is not OK for CAL application with this GPU

I'm using 13.11 Beta 6 for Linux. About to upgrade to 13.11 beta 8 later today. Thoughts?

Thanks of the link!! 8-))))

As far as using Beta drivers be careful, crunching is not what the drivers are made to enhance, it is gaming, so unless you are also gaming it might be best to avoid the latest and greatest gpu drivers. Nvidia just released two new versions and both made the crunching upto 20% SLOWER. It made the gaming better, but at the expense of crunching. Also I was running a set of Beta drivers for AMD for here a while back and kept getting errors from the project saying I was running unauthorized drivers. A reply from an Admin told me they do not support Beta drivers, just released versions. I did NOT change my drivers and just ignored the messages, but just be aware that you MAY get errors in the units.

I hear it was frosting on the morning of the service.

I game with Steam, so yes I update.

---

-mpyusko

AMD FX-8350 @ 4.3GHz
AMD Radeon RX 480 8GB @ 1342MHz/2000MHz

I hear it was frosting on the morning of the service.

I game with Steam, so yes I update.

That makes sense then, you gotta do what you gotta do.