MarkJ reported a hanging task similar to what you see / have seen and it also happened on his box with 2 GPUs.. could mean something.

MrS

---

Scanning for our furry friends since Jan 2002

@ Paul: Did you restart BOINC?

I did that on mine and that seemed to get them moving. Failing that try rebooting the machine.

---

BOINC blog

@ Paul: Did you restart BOINC?

I did that on mine and that seemed to get them moving. Failing that try rebooting the machine.

I did a restart, though not a cold start, between "sets" of these odd tasks. But the second pair just completed this afternoon.

With NO change to the system, and no restart, I have 4 in flight with all of them on track to complete in the normal 6 hours, for example the one at 25% done is 1:33 hours with 7 hours to run ...

Oh, now that is interesting ... one GPU task is in "Waiting" ... now why is that ...

Even more interesting is the fact that the task suspended has a deadline sooner than the task that is running ... Hmmm, two tasks where the time to complete is INCREASING 3 seconds for each runtime second ...

Ok, I just shot two of those tasks and down leveled to 6.5.0 to see what will happen (also did a re-boot) ...

{edit, add}

Anyone else having this issue, would you please note which version of BOINC are you using? This *MAY* be an issue with 6.6.x, assuming we were all running 6.6.15+ when we saw this issue. If we were all running 6.6.x, the next question is if you are running into this problem in a system with multiple GPU "cores" (more than one GPU task in progress at the same time.

I have a suspicion as to what might be happening and need this information to make a more coherent report to the Alpha mailing list ...

I have been watching since I down leveled to 6.5.0 and I don't seem to have the odd behavior of slowly increasing time to completion ...

I will also note that this increased time may NOT be correctly reflected in the data shown on the task page of GPU Grid after you report the task ...

I see the following from the Home page news:

A new batch of workunits out
April 3, 2009
We have just submitted a new batch of workunits which improve further the accuracy of the free energy calculations

Maybe this has something to do with it?

---

BOINC blog

I see the following from the Home page news:

A new batch of workunits out
April 3, 2009
We have just submitted a new batch of workunits which improve further the accuracy of the free energy calculations

Maybe this has something to do with it?

I don't think so, but it could...

The reason I don't think so is that I changed my version BACK down to 6.5.0 and the issue seems to have gone away. I have this suspicion as to what else may have happened. It could be one, or the other, or both ... but, when I first asked this question, GDF seemed to indicate that this was not the issue ...

At any rate ... if no one else has the issue, then it was just me, and in that case I would have to ascribe it to 6.6.20 ...

I picked up a GIANNI wu which locked up at 13%. Was sitting there when I got home tonight. No movement in %, just the times counting up. I restarted boinc which got it going again (now past 20%), but seems to be rather unusual. Might be a feature in boinc 6.6.20 which that machine is now running.

Its here, but I have yet to upload it. There goes my bonus credits.

---

BOINC blog

Occasionally lock-ups happen. Might be nice if the app could detect that it's not progressing any more and could initiate a restart of itself. But I guess this is not trivial to implement.. as a task which is stuck doesn't execute its code any more.

MrS

---

Scanning for our furry friends since Jan 2002

I picked up a GIANNI wu which locked up at 13%. Was sitting there when I got home tonight. No movement in %, just the times counting up. I restarted boinc which got it going again (now past 20%), but seems to be rather unusual. Might be a feature in boinc 6.6.20 which that machine is now running.

Its here, but I have yet to upload it. There goes my bonus credits.

The new version is supposed to be detecting stalled tasks that increase in time but not percentage... but like all new features, I don't know if it works yet or not ...

The new version of BOINC, not GPU-Grid itself?
Would be a cool feature, if it really worked. They'd have to take normal runtime / update intervals into account, though. Otherwise they might prevent very slow computers or huge WUs from running at all, because they seem to be stalled.

MrS

---

Scanning for our furry friends since Jan 2002

The new version of BOINC, not GPU-Grid itself?
Would be a cool feature, if it really worked. They'd have to take normal runtime / update intervals into account, though. Otherwise they might prevent very slow computers or huge WUs from running at all, because they seem to be stalled.

MrS

Supposedly in BOINC. But its only meant to work for cpu-intensive tasks, so it doesn't work with GPUgrid.

That GIANNI task locked up again at 87& this time. I have posted about it on the boinc alpha mailing list. Restarted BOINC and its progressing again now.

---

BOINC blog

The new version of BOINC, not GPU-Grid itself?
Would be a cool feature, if it really worked. They'd have to take normal runtime / update intervals into account, though. Otherwise they might prevent very slow computers or huge WUs from running at all, because they seem to be stalled.

MrS

Supposedly in BOINC. But its only meant to work for cpu-intensive tasks, so it doesn't work with GPUgrid.

According to the glossy advertising it is supposed to work with both ...

But, I have serious doubts about 6.6.20 for other reasons ...

Away for almost three weeks at F@H.

I'm going to give this a shot again...