Linux beta application uploaded.
gdf

I have got two workunits (1 for GTX275 and 1 for GTX260 (192sp)).
Let's crunch it.

Reboot after every driver-crash!

If the problems do not disappear:

Deinstall old drivers via windows, then boot into safe-mode, run Guru3d driver sweeper, reboot, and install the new drivers.

Driver works fine.

And... I using linux. Should I install windows in order to reinstall driver? lol

---

Reboot after every driver-crash!

If the problems do not disappear:

Deinstall old drivers via windows, then boot into safe-mode, run Guru3d driver sweeper, reboot, and install the new drivers.

Driver works fine.

And... I using linux. Should I install windows in order to reinstall driver? lol

Then forget "driver sweeper" - and I replace "driver-crash" by "WU-crash".
It is a common advice to reboot after every failed WU.

(I am running dual-boot sytems (Win/Linux) on my whole "farm".)

It can be good advice to reboot after a failed WU; where a failure is not common! If a Beta fails, or a task fails after a few seconds, this is probably not the case, as some Betas are expected to fail, and some tasks can crash (bad batch) when running under some conditions.
So, if you do not normally get failures, and certainly if you get two or three, it is a good idea to reboot. This eliminates some possibilities of system or application errors causing a problem, and removes the possibility of runaway failures from such problems.

The longer a system is on, the more likely an odd or random problem with the operating system will occur. Many network, driver and application problems are solved by a simple reboot.

8% of cpu utilization for gpu calculation is great with this ACEMD beta version v6.09 (cuda) Linux version.

8% of cpu utilization for gpu calculation is great with this ACEMD beta version v6.09 (cuda) Linux version.

Here, my first wu calculated without problems.

The beta is running great here on 4 different types of cards: GTX 260, GT 240, 8800 GT and 9600GSO.
My BIG problem is having to abort a boatload of v6.71 WUs in order to get the v6.08 ones.
Any chance of making this easier on us?

Now up to 33 successful v6.08 WUs on 5 cards (GTX 260, GT 240, 8800 GT, 9600GSO and another GT 240). Still only the single error mentioned above and I think that was caused by something not related to GPUGRID (another project had put out some bad WUs and the bad CPU WU crashed pretty much everything including the GPUGRID WU). I think v6.08 is more stable than v6.71, and that wasn't bad.

Up to 50 successful v6.08 with only the one failure mentioned above :-)
That's on a varied mix of GPUs. Older cards seem to benefit as much as the G200 series.

It can be good advice to reboot after a failed WU; where a failure is not common! If a Beta fails, or a task fails after a few seconds, this is probably not the case, as some Betas are expected to fail, and some tasks can crash (bad batch) when running under some conditions.
So, if you do not normally get failures, and certainly if you get two or three, it is a good idea to reboot. This eliminates some possibilities of system or application errors causing a problem, and removes the possibility of runaway failures from such problems.

The longer a system is on, the more likely an odd or random problem with the operating system will occur. Many network, driver and application problems are solved by a simple reboot.

You are completely right. I only add the information that a slowdown of computation is a known "runaway failure" from cuda failures.

Look here for example.

I only add the information that a slowdown of computation is a known "runaway failure" from cuda failures.

you meant that the reason for massive slowdown of 6.09 app happened to me to be fixed by restarting computer?

I don't so coz after I aborted 6.09 WUs I've got 6.70 ones. And u know what? they worked w/o any slowdown: 6 hours and the job done (as usual). And furthermore - to complete 10% of 6.09 WU took me 3 hours, so I need 30 hours to complete the whole WU, i.e. 6.09 WU is 5 times slower. Taking in consideration that new app is 1.6 time faster, my card was 8 time slower then it should be.


I think that smth wrong with linux app, i.e. 6.09

---

the main change for Linux is that now the new app uses the same driver mechanism to reduce CPU usage of Windows. Maybe the problem is in your driver or Linux kernel. The application under Linux does normally work as expected, fast.

gdf

GDF,
system: ubuntu 9.10 x64,
kernel - at that time - 2.6.31-19,
driver - 195.30
cuda 2.3

what's necessary to change?

BTW, I tried to "catch" 6.09 - no luck :(

---

Completed. Is such a run time OK?!

---

From Siberia with love!

No, it's too slow.
Are you sure that your card is running at full speed during these runs?

gdf

141-IBUCH_1000smd_pYEEI_100202-2-10-RND7134_1 was the first ACEMD beta version v6.09 (cuda)that I ran on a Linux PC (Ubuntu/Mint64bit). Damn it took forever! http://www.gpugrid.net/result.php?resultid=1835513

---

Maybe there is a specific problem with Ubuntu.
We have run fine on CentOS and Fedora.

We can reintroduce the same mechanism as before for Linux.

gdf

"Maximum performance", as usually... But it's really SLOWWW.....

Ohhh, that diversity of Linuxes!.. Ohh, that Ubuntu!..

Crunch3r said: "Any Linux Distribution is better than Ubuntu and all it's derivates since it causes to many trouble due their weired kernel experiments.

Personally i use Gentoo and am running openSuSE on production servers.
Fedora is a good choice as well."

Fedora's ISO is waiting the Ubuntu's first full crash to take it's place...

Or may be I'll switch back to Debian.

---

From Siberia with love!

looks I'm not alone facing the slowdown with 6.09 ...

I don't think hat the problem is ubuntu kernel, otherwise why 6.70 works just fine???

update.
I've just got new app - "acemd2_6.02_x86_64-pc-linux-gnu__cuda"

There is progress in comparison with 6.09 - 18.5-19 hours against 30 hours (6.09), but still worse then 6.70.

BUT: CPU usage - ZERO :-) That's awesome :-)

---

6.70 and 6.09 are exactly different in the use of CPU. So it could be the kernel.

gdf

I put "No' to "run test apps" option, but I'm still getting 6.02 apps. I aborted 2 of them and now
"Fri 12 Feb 2010 10:22:03 AM EST GPUGRID Message from server: Project has no jobs available"

and again: 0h59m and 2.3% only...

---

I'm still receiving 6.02... How I can avoid this?

---