@Mike: sorry, don't know much about how to handle this in Linux. Could it have anything to do with your distro being rather *old*?

@Pat: the different WU sizes are not causing these problems. And when you close and restart BOINC manager, do you also shut down BOINC? Or just the manager? Seems like you're on of the few who can still reproduce the issue on a regular basis, so you may have the chance to find the cause ;)

MrS

---

Scanning for our furry friends since Jan 2002

Frank, have you tried the 180.84 driver yet? It seems to have solved all my 64bit issues. It's only been a day, but no problems since :)
Fish

180.84 has been running fine for some days - in the middle of PG-challenge boinc suddenly wasn't able to get fresh work from GPU.

@Mike: sorry, don't know much about how to handle this in Linux. Could it have anything to do with your distro being rather *old*?

@Pat: the different WU sizes are not causing these problems. And when you close and restart BOINC manager, do you also shut down BOINC? Or just the manager? Seems like you're on of the few who can still reproduce the issue on a regular basis, so you may have the chance to find the cause ;)

MrS

6.04 is a typing mistake by me it is actually;

Ubuntu 8.04LTS isn't outdated, there is another release 8.10. Both are reliable os's.

There is some other issue, because yesterday it worked for a couple of hours.

I guess I will put this project on the back burner for awhile. Good science but difficult [for me] to set up and run with out babysitting it.

mike

You're right, 8.04 is surely not causing this problem.

MrS

---

Scanning for our furry friends since Jan 2002

MrS:

Seems that both rigs are responding properly (knock on wood) but will keep an eye on it.

When I shut BOINCmgr down I also selected "Stop running science applications when exiting the Manager".

Pat

Mike,
do you have installed boinc for Linux x86_64 or 32 bit?

gdf

64 bit with ia32-libs

mike

edit; I just tried again and got 2 work units and it is working one. I did not change anything.....let's see how long it will work.

edit; I just tried again and got 2 work units and it is working one. I did not change anything.....let's see how long it will work.

I just got up a little bit ago and my machine had completed one task and I reported it in and got another. Just like it is supposed to work ... :)

Now, was it a one time miracle or will it repeat?

About half way through the next task and I have two in queue ... so, theory says I should be keeping about that many locally ...

Fingers crossed ...

My two units will run about 8 hours and then go to "waiting on memory". I re boot and then it will pick one back up and crunch????? When it goes to waiting on memory, it does a constant write to hard drive. I will try 180.06 drivers later today or after it finishes these units and see if it will behave:)

mike

Sounds like the memory leak in the linux app. See also:
http://www.gpugrid.net/forum_thread.php?id=571

It's back!!!

12/24/2008 11:47:25 AM|GPUGRID|Sending scheduler request: Requested by user. Requesting 387007 seconds of work, reporting 0 completed tasks
12/24/2008 11:47:30 AM|GPUGRID|Scheduler request completed: got 0 new tasks
12/24/2008 11:47:30 AM|GPUGRID|Message from server: No work sent
12/24/2008 11:47:30 AM|GPUGRID|Message from server: Full-atom molecular dynamics for Cell processor is not available for your type of computer.
12/24/2008 11:47:30 AM|GPUGRID|Message from server: Full-atom molecular dynamics on Cell processor is not available for your type of computer.

Simply server was out of work.

More workunits now and many more in the next few days.

gdf

My bad!!! Thanks GDF!!! I guess the next time I cry wolf, I'll check the server first. Thanks again to you and all of your staff (if any) for all of your hard & dedicated work to correct these problems and listening to all of us complain.

GDF,

A little cheer maybe. The one machine I am running at the moment seemed to have auto-magically obtained another task on the 24th at about 1400 and my last 2.56 task is nearing completion. So ... encouraging news and I am getting tempted to fire up the other machine and let it rip! :)

But, it is looking like, at least for me, that I am in the "normal" group now (about the only thing normal about me).