Just had this 3s invalidate on my P4 cpu. So not just a gpu problem it seems.

---

And same here. I was thinking that it was related to my instalation of Folding@home so I removed it, to bad. This project used to be greate but now it's just crap with an alpha stus that seams to go on for ever.

Hi everyone!
Í've got same problem with my ATI 4850.
With any version of aplication.

And same here. I was thinking that it was related to my instalation of Folding@home so I removed it, to bad. This project used to be greate but now it's just crap with an alpha stus that seams to go on for ever.

The work runs fine with the stock application.
When people chose the anonymous platform, unforeseen things happen. Be patient, it'll get fixed.

But why wasn't it fixed yesterday! :)

---

Cheers,

PeterV

.

I've aborted 40-50 of the 3s units this morning to go along with the 100 or so of them last night. All GPU crunching grinds to a halt when these hang up. Please stop sending these things out until there is a fix. What happened to testing the work before sending it out to everybody?

---

4870 GPU
4870 GPU

Oh my god, Is anybody home hear. Stop sending out 3s wu's Now!!!!!

---

Like many others posting in to this thread I have a stalled ATI HD3850 due, I surmise, to the problem ps_sgr_208_3s_etc WUs.

Interestingly, the HD3850 seems to be getting lots of work, but cannot crunch them as the _3s_ cause the system to stall for some reason or other. When the GPU does crunch it ends up terminating as a computer error.

I am going to detach and reattach to allow Milkyway to do CPU crunching as I noticed there is no problem with these _3s_ WUs on them. I can continue this way, at 10% of the GPU RAC, until these _3s_ WUs stop.

I hope Travis or Dave can see a way to sort this problem out in this project soon. It has been at least 2 days now living (or not) with this problem.

:((

---

Go away, I was asleep

I didn't have any problems with the six 3s_2 I got. Is it only the 3s_1 giving problems? Could be some lingering still that need canceled.

---

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

The current workaround is to abort all the _3s_ WUs, close and restart boinc, and hope you get some _1s_ or _2s_ WUs next time. Its horribly manual and requires keeping an eye on boinc, which explains all the requests/demands in this thread for Travis to fix it.

---

Cheers,

PeterV

.

The current workaround is to abort all the _3s_ WUs, close and restart boinc, and hope you get some _1s_ or _2s_ WUs next time. Its horribly manual and requires keeping an eye on boinc, which explains all the requests/demands in this thread for Travis to fix it.

Come on guys, deep breaths :)
The problem isn't with the workunits, they're fine, so Travis can't fix it.
It's a bug in Cluster Physiks GPU application as he has already pointed out.
Give him a chance and he'll sort it

The current workaround is to abort all the _3s_ WUs, close and restart boinc, and hope you get some _1s_ or _2s_ WUs next time. Its horribly manual and requires keeping an eye on boinc, which explains all the requests/demands in this thread for Travis to fix it.

Come on guys, deep breaths :)
The problem isn't with the workunits, they're fine, so Travis can't fix it.
It's a bug in Cluster Physiks GPU application as he has already pointed out.
Give him a chance and he'll sort it

The real problem is that if a WU gets sent out to 2 GPU clients, and both abort it, the WU dies from too many errors, so the project suffers.

Just my $0.02.....

---

Click to help Seti City.

It's a bug in Cluster Physiks GPU application as he has already pointed out.

Didn't catch that when I read through. I only have a cpu, so no problems.

---

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

Hi John - agreed. However GPU users cannot choose their WUs - and once downloaded these WUs can't be run - therefore abort or leave stalled is the only option. Granted I'm sure that CP will get it sorted, but the project may be best suspending the generation of this type of WU until it is addressed ......... can't be good for the retruned data to have so may aborted WUs or project resets.

Hello MW@Home,

These *_3s_* runs are 3 stream runs that I started. I will tell Travis that there is a problem with them on the GPUs but not the CPUs and abort said run asap.

Sorry for the inconvenience,
John Vickers

Hello MW@Home,

These *_3s_* runs are 3 stream runs that I started. I will tell Travis that there is a problem with them on the GPUs but not the CPUs and abort said run asap.

Sorry for the inconvenience,
John Vickers

No probs...

Once CP gets the ATI app sorted out, we will burn thru these like nothing...

And thanks for posting...

---

Click to help Seti City.

Looks like the searches are stopped, we'll not do 3 stream runs until the ATI code is fixed :)

---

Looks like the searches are stopped, we'll not do 3 stream runs until the ATI code is fixed :)

Ahhhh,,

Just as I was really starting to enjoy them :)...

---

.

  "booger"                     

_________________
*** BOFH excuse #309:
firewall needs cooling

No 3s to be had, everything seems ok at present.

---