Another Xmas present has made a nuisance of itself here.

Tanis 10773581

Cheers.

Tanis, Richard and AMD Jesus (edit: and George Ko) pestered. stogdan and Richard Hartland also replied and indicated they are disabling their affected GPUs... yay!

The list is two pages back or more so here's a repost of it:

李溪伦 9302807
[AfZ]TomServo1 1483720
achimbln 138625
Alexandr Galushchenko 9609912
alffrommars 9024750
AMD Jesus 70887
antoi 10856207
aridhol 10288747
Arnab 10093567
Baldarov 9438496
Bigthor 480399
Borktron 10682716
Brandon 8198367
calendir 9663884
Camiron 7449359
Carl 914781
Christopher 9894096
CoffeeSloth 10266313
Crisu 7833612
dalex 10881818
Daniel Conrad Broom 8059986
Daniel frederikson 9813817
Daniel Penz 91581
Dank 49802
Derrek 219419
Doc_Jebus 10863878
dsharbour 10858679
Dzsozi 8002127
Earendil 146007
egon.sauter 494566
Eirikafh 10883218
Eric 9157146
eryndel 10878567
Esta 10624508
Foaming Mad Cow Industries 219464
fred 1935325
fredi 7913572
George Ko 639539
ghostbuster 564989
gunsnammo 137399
Haiko_N 9198068
HawkMedic 10838738
higemayuge 10790664
HMZ 9079227
Jeff 10639246
Jeffrey A. Smith 38247
Jerjes 1291426
JohnDoe 9166075
Jorge Barrera 9650295
Juraxell 10864786
Kekke 46817
knutella 9880098
lastsworder 10878688
lupaslupas 10002927
MadMikeDelta 8221690
Maulwurf 1516335
MaximusPrometheus 10240426
mgg 279419
mnelsonx 272885
Niflhuem 113140
No Name@Extraterrestrial Intelligence 8116
NYX.consulting 10503661
Oriah 9838773
Otosan 8547502
PantherJon 9801065
Peter Furlong 7965665
phoenix7477 10773411
Rafael 8249913
rame 10738
rAttmAniA 9002301
Recedham 954834
rgeens 10740140
Richard 8565733
Richard Hartland 9781177
Rocky 270621
Saint123 159425
Stephen Diem 36679
stogdan 10865456
StrayCat 177967
Strickland 34273
suhail ahmad 9878177
Swagstergo 10882690
T66 3336343
Tanis 10773581
toby 9442798
TomasFraus 8445239
Tomik 8972653
Trezy 10367889
Tristan 9778349
vleermuis 1295921
VMS Software Inc 45538
werewolf_007 10880222
xakei 10823091
Zac 100334866

Italicized names have replied and indicated they are disabling their affected GPUs.
Struck-through names are confirmed to no longer be producing these bad results, ie via disabling GPU computing.

---

It's been a while, but I've been ripped off again, https://setiathome.berkeley.edu/workunit.php?wuid=3820918292. :-(

And a new culprit, George Ko 639539.

Cheers.

Another new rig on the block. :-(

unbound 10885610

Cheers.

new one: Hozer https://setiathome.berkeley.edu/show_host_detail.php?hostid=8878385

his prime card shows a R9 390, but his secondary card is a 5700XT.

also, for AMD cards, it appears that the level of double precision performance is the main/first factor for ranking the cards in BOINC.

also interesting, and I just noticed, that the seti apps only report half of the number of compute units on these new cards.
5700's report as 18 CU, when in reality they have 36
5700XTs report as 20 CU, when in reality they have 40
but the older cards seem to report correctly, eg. the R9 390 correctly reports 40 CUs

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

Richard and DA need to update coproc.cpp again to handle the Navi cards by adding code for cores_per_proc = parameter.

They had to change the code to properly handle the new Turing cards where the cores_per_proc value was half of Pascal.https://github.com/BOINC/boinc/pull/2707
Looks like they need to double the value for Navi.

https://github.com/BOINC/boinc/commit/20af3e90ce165c23edb700ecc21ec729dd36dff8

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

I'm a little hesitant about submitting this change, because I've never personally worked with AMD cards or with the developer of an AMD app. From what I understand, the process for deriving the card geometry from the API is rather different from the NV situation. Also, the only effect of the NV patch I submitted was the correct calculation of GFlops Peak, which helps in runtime estimation - it doesn't affect the actual calculations at all.

Having said that, I'm perfectly happy to submit a patch if we can work out exactly what is needed. I can speak with Ray Hinchliffe (author of SIV) to see how he handles those cards: we cross checked the NV results before submitting the last change. I'll also hunt through the Wiki reports, which are usually pretty comprehensive. There may even be manufacturer documentation... ? Anyone? ;-)

Edit - the ATI code (and comments) are at https://github.com/BOINC/boinc/blob/master/lib/coproc.cpp#L841

There don't seem to be any 'magic numbers' for cores_per_proc, like we have to use for NV - anybody really knowledgeable about ATI hardware willing to help?

If it helps, I cross-referenced my recent inconclusives with the list posted earlier and these three are candidates all running RX 5700 hosts that are not yet listed:

dcox https://setiathome.berkeley.edu/show_user.php?userid=10884993
iinkabob https://setiathome.berkeley.edu/show_user.php?userid=102908
Simgiov https://setiathome.berkeley.edu/show_user.php?userid=8796082

---

While Strickland gave me another mauling another new comer also joined in. :-(

killerepicprofurrygamer6969 10885981

Cheers.

New one: BigDaddyDave - https://setiathome.berkeley.edu/show_host_detail.php?hostid=8874591

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

Well I've been ripped off again and it certainly doesn't look like Eric's fix is working. :-(

https://setiathome.berkeley.edu/workunit.php?wuid=3823542361

And another new culprit came with it, teargasm 10886461.

Cheers.

Mr. Kevvy could you check your list please as you have some unclosed tags in it I've just noticed as calendir 9663884 is still using their GPU.

Other than the usual culprits 4 new names turned up here.

AshlandPony 9004257
cprince1977 10886783
Illyria 10845292
jcr 3428

Cheers.

From what I understand, the process for deriving the card geometry from the API is rather different from the NV situation.

What isn't to say the API itself is incorrectly reporting the number of SM's on the newer cards. After neither Khronos nor AMD has fixed the drivers yet for this threads problem, I wouldn't bet either way.
It would be good to check with Ray and see if SIV reports the correct number of SM's or whether he had to modify/fudge SIV to fix what the API reports to jibe with what AMD says the architecture actually has.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

User Capizzi #10504781
computer #8860521

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

firecrypt https://setiathome.berkeley.edu/show_host_detail.php?hostid=8869537

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

https://setiathome.berkeley.edu/workunit.php?wuid=3827527607

Two ATI cards validated, my Nvidia invalid.

ATI hosts;
https://setiathome.berkeley.edu/show_host_detail.php?hostid=8867611
https://setiathome.berkeley.edu/show_host_detail.php?hostid=8875643

Just 1 new 1 for me today to report.

Adam Tadian 9295811

Cheers.

I am still keeping my AMD GPU firmly switched off despite regular messages from SETI@home app to fix this! :) I quote:

SETI@home: Notice from BOINC
Your settings do not allow fetching tasks for AMD/ATI GPU. To fix this, you can change Project Preferences on the project's web site.
Thu 09 Jan 2020 16:13:08 GMT

Perhaps it would help if SETI@home could send a different notification to those of us who have AMD GPUs until such time this OpenCL issue is resolved.

Ta
Aravah 10852549

---

I am still keeping my AMD GPU firmly switched off despite regular messages from SETI@home app to fix this! :) I quote:
SETI@home: Notice from BOINC
Your settings do not allow fetching tasks for AMD/ATI GPU. To fix this, you can change Project Preferences on the project's web site.
Thu 09 Jan 2020 16:13:08 GMT
Perhaps it would help if SETI@home could send a different notification to those of us who have AMD GPUs until such time this OpenCL issue is resolved.
Ta
Aravah 10852549

. . You make a good point ...

Stephen

. .

Just got apprised that AMD released new Adrenaline drivers for Windows 10 today. One of the fixed issues is with Seti@home result overflows.

Fixed result overflows that can be experienced with Radeon RX 5700 series when using SETI@Home.

https://www.amd.com/en/support/kb/release-notes/rn-rad-win-20-1-1
Need to have some of the known 5700XT users that have responded to PM's give the new drivers a test run.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)