ATI app shows no progress after 1 hour
log in

Advanced search

Message boards : Number crunching : ATI app shows no progress after 1 hour

Author Message
Golden_Frog
Send message
Joined: 20 Jul 09
Posts: 1
Credit: 10,917,862
RAC: 0
Message 761 - Posted: 30 Aug 2009, 16:14:11 UTC
Last modified: 30 Aug 2009, 16:14:30 UTC

Milkyway@home is down so I am putting my ati4830 to use here. The app has been running for just over an hour and shows no progress. Is this normal? The CPU is running at 100% doing something but no movement in the progress bar.

Profile Logan
Avatar
Send message
Joined: 2 Jul 09
Posts: 124
Credit: 37,455,338
RAC: 0
Message 764 - Posted: 30 Aug 2009, 17:18:11 UTC - in response to Message 761.

Milkyway@home is down so I am putting my ati4830 to use here. The app has been running for just over an hour and shows no progress. Is this normal? The CPU is running at 100% doing something but no movement in the progress bar.

When you tell 'no progress..' read as 'waiting for GPU available'.

I think you have a drivers problem, and the app don't recognizes your ATI card...
____________
Logan.

BOINC FAQ Service (Ahora, también disponible en Español/Now available in Spanish)

Profile BarryAZ
Send message
Joined: 21 Aug 09
Posts: 251
Credit: 13,266,362,907
RAC: 23,628,322
Message 768 - Posted: 30 Aug 2009, 19:16:52 UTC - in response to Message 764.

I am seeing this with *some* of the Collatz work units, but not others. Some progress normally and complete, others go nowhere. Perhaps it isn't a driver problem entirely, but rather an interaction between specific workunits and the driver used. Vista 32 bit, the 8.12 ATI Catalyst version (as I've heard stories about later versions). Embedded ATI 3300.

Milkyway@home is down so I am putting my ati4830 to use here. The app has been running for just over an hour and shows no progress. Is this normal? The CPU is running at 100% doing something but no movement in the progress bar.

When you tell 'no progress..' read as 'waiting for GPU available'.

I think you have a drivers problem, and the app don't recognizes your ATI card...

PeteS
Send message
Joined: 17 Jul 09
Posts: 20
Credit: 54,228,605
RAC: 0
Message 813 - Posted: 31 Aug 2009, 19:24:42 UTC

I was also hoping to use both Collatz and MW on my ATI hosts. MW has been running 100% stable and nicely without any crashes for some time now, but with collatz ATI app I get driver VPU recoveries and stalled wu's (like the thread maker). CPU 100% and no progress on wu means the app / driver has crashed. Either kill the processes with taskmanager or restart BOINC manager (and apps if manager does not close them).

Gipsel/CP: How could the ATI app be improved so that it would work as fine as MW app does? At the moment I can't use collatz, because I get same crashes on all hosts.

1x4850 and 3x4870 on Win7 x64 and Catalyst 9.5.

Profile Gipsel
Volunteer moderator
Project developer
Project tester
Send message
Joined: 2 Jul 09
Posts: 279
Credit: 77,274,766
RAC: 78,139
Message 814 - Posted: 31 Aug 2009, 19:32:19 UTC - in response to Message 813.

Gipsel/CP: How could the ATI app be improved so that it would work as fine as MW app does? At the moment I can't use collatz, because I get same crashes on all hosts.

I hope the next release will be equivalent to MW as the whole GPU detection and scheduling stuff will be identical (if Slicker doesn't decide otherwise in the last minute). At least it ran absolutely flawless on my machines during some tests and Slicker has also not found any issues so far.

Profile Slicker
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Avatar
Send message
Joined: 11 Jun 09
Posts: 2525
Credit: 740,580,099
RAC: 1
Message 838 - Posted: 1 Sep 2009, 13:30:16 UTC - in response to Message 814.

Gipsel/CP: How could the ATI app be improved so that it would work as fine as MW app does? At the moment I can't use collatz, because I get same crashes on all hosts.

I hope the next release will be equivalent to MW as the whole GPU detection and scheduling stuff will be identical (if Slicker doesn't decide otherwise in the last minute). At least it ran absolutely flawless on my machines during some tests and Slicker has also not found any issues so far.


Nope. I'm not touching it.

If I ever get around to getting the server up on 6.10, we may want to pull all the mutex code and let BOINC handle all the scheduling, but until then, the code will remain exactly the same (except for the encoding of the output which doesn't affect the mutexes/semaphores).


Post to thread

Message boards : Number crunching : ATI app shows no progress after 1 hour


Main page · Your account · Message boards


Copyright © 2018 Jon Sonntag; All rights reserved.