How is it at other BOINC projects, like Milkyway and Einstein?

Einstein users report consistent problems when trying to run 2 or more tasks concurrently on late-generation AMD cards - Hawaii and Fuji.

The best-developed discussion thread - Problem with a R9 390X when run 2 or more WUs at a time. - is named for R9 390X 'Hawaii', but R9 Fury ('Fuji') has been mentioned as well. That's part of the problem of being a pioneer - you're on your own, without many collaborators with the exact same hardware to compare notes with.

So far as I can tell, the problems reported so far all relate to running 2xSETI, or 2xEinstein, tasks on the same card at the same time with a recent (15.x) driver. People have run two tasks at the same time with older drivers, but so slowly that it isn't worth it. Nobody has tried (or clearly reported results) running 1xSETI plus 1xEinstein concurrently. Juan is suggesting running 2xEinstein under the control of two separate BOINC clients: that seems an unlikely solution, but the experiment might supply further clues.

Fundamentally, the failures when running multiple tasks on these card ranges appear to be inherent to this new hardware and driver combination. It's going to need somebody to engage some serious debugging skills, and to report the results back to AMD.

This is driver related.
What i found out is that all new GPU`s with GCN 1.2 have isuues running multiple tasks at once.
Those new chips are not yet fully supported by the drivers.
For R9 2xx cards it can get fixed by using older drivers ie Cat 14.4. or 14.9.
On 3xx and Fury cards this won`t work for now but i`m working on it.

---

With each crime and every kindness we birth our future.

You know, this problem doesn't exist in Ubuntu Linux. There is an AMD Radeon (TM) R9 390 Hawaii running 3 tasks at a time with driver AMD-APP (1800.11) here, http://setiathome.berkeley.edu/show_host_detail.php?hostid=7776868.
Seems to be working well.
Apparently this is a Winders only problem....

You know, this problem doesn't exist in Ubuntu Linux. There is an AMD Radeon (TM) R9 390 Hawaii running 3 tasks at a time with driver AMD-APP (1800.11) here, http://setiathome.berkeley.edu/show_host_detail.php?hostid=7776868.
Seems to be working well.
Apparently this is a Winders only problem....

No, no windows only problem.
Urs has confirmed he has the same issues on Linux.
Maybe new Linux drivers fixed it already.

---

With each crime and every kindness we birth our future.

You know, this problem doesn't exist in Ubuntu Linux. There is an AMD Radeon (TM) R9 390 Hawaii running 3 tasks at a time with driver AMD-APP (1800.11) here, http://setiathome.berkeley.edu/show_host_detail.php?hostid=7776868.
Seems to be working well.
Apparently this is a Winders only problem....

No, no windows only problem.
Urs has confirmed he has the same issues on Linux.
Maybe new Linux drivers fixed it already.

Some problems have been solved after reporting to driver maintainers, but not on every distro. And without owning a GCN 1.2 GPU (like Fiji or Tonga) i can't do any testing of what works and what not.

Going into detail here would be off topic

---

_\|/_
U r s

... my system has gone full tilt.

And what to look for on that picture to see "full tilt"?

It is running as hard as it can. It hasn't done that in a few weeks. The GPUs and CPU are running at very nearly 100% capacity vs. the 65 t0 75% it was running at before the last Windoze update. Admittedly, I had problems with Win 10 initially, it seems to have settled in though.

---

Louis, please open a new thread about your PC. (AMD Radeon R9 280X) If someone have the same VGA card, he could find the conversation easily. (This is now my second try.)

This here is about my PC. (AMD Radeon R9 Fury X)

Cool, cya. I'll keep an eye out though. Still quite interested in performance comparisons.

Peace!

---

Is this a BUG or wanted from AMD that just 1 WU/GPU run smoothly, now?

This will change with a new AMD Catalyst?
He will released in two months?

How is it at other BOINC projects, like Milkyway and Einstein?
There work also just 1 WU/GPU now?

Thanks.

Dirk, all questions but one answered by Richard belongs to AMD forum mostly. AFAIK nobody here has direct contact or being part of AMD driver group.
And regarding "bug vs feature" I tend to call anything that restricts user abilities w/o clear warning (and there were no warning about such driver restriction from AMD driver team) as bug.

Juan is suggesting running 2xEinstein under the control of two separate BOINC clients: that seems an unlikely solution, but the experiment might supply further clues.

Much easier is to start with 2 offline tasks in benchmark.
To run 2 tasks simultaneously offline sounds easier than to configure 2 BOINC clients...

Juan is suggesting running 2xEinstein under the control of two separate BOINC clients: that seems an unlikely solution, but the experiment might supply further clues.

Much easier is to start with 2 offline tasks in benchmark.
To run 2 tasks simultaneously offline sounds easier than to configure 2 BOINC clients...

This produces errors on my Tonga also.
So i fear it won`t work on the Fury X as well.

---

With each crime and every kindness we birth our future.

Mike wrote:

This is driver related.
What i found out is that all new GPU`s with GCN 1.2 have isuues running multiple tasks at once.
Those new chips are not yet fully supported by the drivers.
For R9 2xx cards it can get fixed by using older drivers ie Cat 14.4. or 14.9.
On 3xx and Fury cards this won`t work for now but i`m working on it.

You are working on it?
What does this mean?
Raistmer and you are working on the GPU app (or on the driver) that 2+WUs/GPU will be possible?

---

Raistmer and you are working on the GPU app (or on the driver) that 2+WUs/GPU will be possible?

On the driver AMD should work ;) Try to "activate" them via bug reporting/support.

Is there a way (without app_info.xml or app_config.xml) to adjust the following:

I have disabled the HT.
So the PC have 12 real CPU-Cores.

1 GPU app get 1 whole CPU-Core for support.
On the other 8 CPU-Cores project tasks.

If 1 GPU idle, it should not start a 9th WU on the CPU.

It should be fixed:
1 CPU-Core - 1 GPU (in whole 4 reserved CPU-Cores)
8 CPU-Cores for WUs.

Maybe in cc_config.xml file?

Thanks.

EDIT: I ask this because of 'secondary' stock (without app_info.xml) projects.

Raistmer and you are working on the GPU app (or on the driver) that 2+WUs/GPU will be possible?

On the driver AMD should work ;) Try to "activate" them via bug reporting/support.

Until now noone did this?

Maybe you have an URL to AMD (BUG report)?

Forum or E-Mail?

Thanks.

---

Is there a way (without app_info.xml or app_config.xml) to adjust the following:

I have disabled the HT.
So the PC have 12 real CPU-Cores.

1 GPU app get 1 whole CPU-Core for support.
On the other 8 CPU-Cores project tasks.

If 1 GPU idle, it should not start a 9th WU on the CPU.

It should be fixed:
1 CPU-Core - 1 GPU (in whole 4 reserved CPU-Cores)
8 CPU-Cores for WUs.

Maybe in cc_config.xml file?

Thanks.

EDIT: I ask this because of 'secondary' stock (without app_info.xml) projects.

Reserve needed number of cores through app_info.

Raistmer and you are working on the GPU app (or on the driver) that 2+WUs/GPU will be possible?

On the driver AMD should work ;) Try to "activate" them via bug reporting/support.

Until now noone did this?

Maybe you have an URL to AMD (BUG report)?

Forum or E-Mail?

Thanks.

https://community.amd.com/community/support-forums
https://community.amd.com/message/1307976#1307976

I found both just opening amd.com
Think someone should do smth too beside asking on this thread ;)

Is there a way (without app_info.xml or app_config.xml) to adjust the following:

I have disabled the HT.
So the PC have 12 real CPU-Cores.

1 GPU app get 1 whole CPU-Core for support.
On the other 8 CPU-Cores project tasks.

If 1 GPU idle, it should not start a 9th WU on the CPU.

It should be fixed:
1 CPU-Core - 1 GPU (in whole 4 reserved CPU-Cores)
8 CPU-Cores for WUs.

Maybe in cc_config.xml file?

Thanks.

EDIT: I ask this because of 'secondary' stock (without app_info.xml) projects.

Reserve needed number of cores through app_info.

I would like to enable this without app_info or app_config. ;-)

Raistmer and you are working on the GPU app (or on the driver) that 2+WUs/GPU will be possible?

On the driver AMD should work ;) Try to "activate" them via bug reporting/support.

Until now noone did this?

Maybe you have an URL to AMD (BUG report)?

Forum or E-Mail?

Thanks.

https://community.amd.com/community/support-forums
https://community.amd.com/message/1307976#1307976

I found both just opening amd.com
Think someone should do smth too beside asking on this thread ;)

I made a BUG report at AMD here: http://www.amd.com/report. Maybe more people should do it there?
(I mentioned the Einstein and this thread.)


I saw now, there is the Catalyst v15.10 Beta available.
But:
http://support.amd.com/en-us/kb-articles/Pages/latest-catalyst-windows-beta.aspx
Known Issues:
(...)
[77255] The secondary display adapter is missing in the Device Manager and the AMD Catalyst™ Control Center after installing the driver on a Microsoft® Windows® 8.1 system
(...)

So maybe I'll not upgrade, maybe BOINC will not see the 2nd, or maybe all other (#2 to #4) VGA cards?

---

Someone wrote also the BUG report?

Someone tested already the Catalyst v15.10 Beta (2+WUs/GPU possible)?

---

Someone wrote also the BUG report?

Someone tested already the Catalyst v15.10 Beta (2+WUs/GPU possible)?

Curious about that BETA myself. The Win 10 issue (black screen at start up) is holding me back. Also, would there be any worthwhile performance enhancements?
Wait and see I guess.

BTW, Kudos on the Fury rig, that thing is smokin'.

---