Problem with a R9 390X when run 2 or more WUs at a time.

juan BFP
juan BFP
Joined: 18 Nov 11
Posts: 839
Credit: 421,443,712
RAC: 0

Hi Bill Yes i´m in Panama

Hi Bill

Yes i´m in Panama now due my job and realy miss my big battleships with his big guns (690´s). LOL

I have some more info about the problem, seems like is a general problem of the 390/290 series. The same happening in Seti@home. For what i could dig it´s something related to the GPU processor and the driver.

Hope the AMD team could fint the cure vary fast.

I was thinking about bild a new host here with 4 or more big guns and the performance of the 390 it´s realy amazing when you compare agaist similar priced NV stuff.

lHj2ixL.jpg

 

Keith Myers
Keith Myers
Joined: 11 Feb 11
Posts: 1,062
Credit: 1,172,629,336
RAC: 2,756,160

I think Tom* might have

I think Tom* might have figured out where the tasks are failing. I looked at several of your invalids and saw what he noticed, inordinately high values of sumspec pages. If I understand what little of what the application is doing, the number of sumspec is related to memory allocation for processing the task. I looked at a lot of your wingmates until I found similar hosts using a Hawaii chip and looked for their invalids. Without knowing whether those hosts tried running more than one task at a time, I saw high values of sumspec pages on some of those invalids too. I still think setting the memory_debug and coproccessor_debug would be enlightening. I haven't followed any of the 290/390X SETI discussions so far. Maybe the SETI folks have already got a good handle on the issue already?

 

Keith Myers
Keith Myers
Joined: 11 Feb 11
Posts: 1,062
Credit: 1,172,629,336
RAC: 2,756,160

Another thing to try is the

Another thing to try is the beta 1.52 BRP4G application and see if there is any difference.

 

Floyd1
Floyd1
Joined: 29 Jun 14
Posts: 14
Credit: 590,463,278
RAC: 0

I can confirm that the

I can confirm that the problem remains with the beta 1.52 BRP4G tasks as well.

hotze33
hotze33
Joined: 10 Nov 04
Posts: 100
Credit: 363,440,607
RAC: 76,667

Hi, I´m a little late to the

Hi,
I´m a little late to the party as I just recently switched from my GTX470 to a R9 290.
First I was using the catalyst 15.7 driver and run only single wu as two at the same time were failing. The runtime was around 3300s for the Parkes PMPS XT v1.52 BRP6-opencl-ati app (6500s for two wus at the same time but invalid) and 1150s for the Arecibo, GPU v1.52 BRP4G-Beta-opencl-ati app (1800s for two wus, but invalid).

After reading through many posts, I stumbled upon one at the anandtech forums.
http://forums.anandtech.com/showthread.php?t=2355452&page=2
So I switched to catalyst 14.4 and now I´m able to run two wus at the same time. However, the efficiency is not so good and two wus now need 7600s. I haven´t crunched any BRP4 units yet, so no data there.

Sasa Jovicic
Sasa Jovicic
Joined: 17 Feb 09
Posts: 75
Credit: 42,495,326
RAC: 3,788

Try Catalyst 13.12. It is

Try Catalyst 13.12. It is just slightly slower than 15.7 but it is significant faster than Catalyst 14.xx.

chase1902
chase1902
Joined: 13 Aug 11
Posts: 37
Credit: 1,264,094,642
RAC: 0

I found the 13.~~ driver so

I found the 13.~~ driver so slow, that it was faster to do just 1 work task at a time with the later driver.
I didn't try 13.12 though, would be interesting to see how that one does.
I'm running that card in my linux system now, so no more playing with drivers (just content for the moment that it all works O,K)

hotze33
hotze33
Joined: 10 Nov 04
Posts: 100
Credit: 363,440,607
RAC: 76,667

I have now switched

I have now switched successfully to catalyst 14.8. Productivity is now up and running two Parkes PMPS XT wus takes ca. 5000s. No invalids so far, besides one from switching the driver.

astrocrab
astrocrab
Joined: 28 Jan 08
Posts: 208
Credit: 429,202,534
RAC: 0

i've got the same problem on

i've got the same problem on my new R9 nano. all completed tasks are invalid. any solution to fix this?

woohoo
woohoo
Joined: 28 Jul 14
Posts: 20
Credit: 250,230,330
RAC: 0

one solution would be to only

one solution would be to only run one wu at a time on that card

i know it's a much older driver, but if i had that card i would at least try to see if i could get catalyst 14.8 to work on it

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.