New drivers today, but don't expect a fix.

https://www.reddit.com/r/Amd/comments/ebz5vk/radeon_software_19123_tomorrow_december_18_2019/fb84hpx/?utm_source=share&utm_medium=web2x

tmakedon
Director of AMD Software Strategy

Does this reply prove to you that we are monitoring Reddit? ;-) Yes this will show up as a known issue and we are investigating it.

As promised, it's on the known issues (finally):
https://www.amd.com/en/support/kb/release-notes/rn-rad-win-19-12-3

---

As promised, it's on the known issues (finally):
https://www.amd.com/en/support/kb/release-notes/rn-rad-win-19-12-3

made clickable
bottom of the known issues list

---

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

A proud member of the OFA (Old Farts Association)

what a cop out too. SETI isnt the only project having issues with these cards. Instead of naming SETI specifically, they should have said something like some OpenCL compute applications will provide incorrect results.

---

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

what a cop out too. SETI isnt the only project having issues with these cards. Instead of naming SETI specifically, they should have said something like some OpenCL compute applications will provide incorrect results.

. . Exactly there is NO maybe about it ... they are giving out nothing but rubbish ...

Stephen

:(

A new 1 decided to pester me, along with the usual culprits. :-(

JohnDoe 9166075

Cheers.

I was either very very lucky yesterday (UTC time) as only 2 regulars were of a very minor annoyance to me, or more have shut their GPU's down (or have they been finally locked out?).

Cheers.

I was either very very lucky yesterday (UTC time) as only 2 regulars were of a very minor annoyance to me, or more have shut their GPU's down (or have they been finally locked out?).

Cheers.

I think it's working.. between my pestering (JohnDoe 9166075 is the latest and thank you) and word getting out. [AfZ]TomServo1 is the latest to reply and indicate the GPU is now disabled.

---

I've made a change to the validator that raises the effective quorum for overflow results. The should limit the number of successful cross validations for these GPUs.

That change is still missing a few, so I need to check the overflow detection mechanism. No, my mistake. It is working. The results I was looking at were before the change.

---

@SETIEric@qoto.org (Mastodon)

I've made a change to the validator that raises the effective quorum for overflow results. The should limit the number of successful cross validations for these GPUs.

That change is still missing a few, so I need to check the overflow detection mechanism. No, my mistake. It is working. The results I was looking at were before the change.

Thank you for that.
That should also help reduce the server load.

---

Grant
Darwin NT

That should also help reduce the server load.

Not be so sure about that. Will take more time to clear the quorum for overflow results.

But sure will reduce the pollution of the DB giving more time to they fix the driver.

---

I've made a change to the validator that raises the effective quorum for overflow results. The should limit the number of successful cross validations for these GPUs.

That change is still missing a few, so I need to check the overflow detection mechanism. No, my mistake. It is working. The results I was looking at were before the change.

. . Many thanks, hope all this does not spoil your Christmas too much.

Stephen

:)

I must of just been lucky yesterday as today I can report 3 new culprits with 1 being a Linux job so it's certainly not just Windows thing. :-(

fredi 7913572 Linux
Recedham 954834
TomasFraus 8445239

Cheers.

I must of just been lucky yesterday as today I can report 3 new culprits with 1 being a Linux job so it's certainly not just Windows thing. :-(

fredi 7913572 Linux
Recedham 954834
TomasFraus 8445239

Cheers.

Good find. I thought there was the same issue with the Linux hosts. But rare to find one using the 5700 on the Seti project.

---

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

A proud member of the OFA (Old Farts Association)

That latest AMD driver update 19.12.2 was garbage. Caused my system to crash. That running 1 wu on a Radeon VII. I reverted back to 19.9.2 and it's been stable since.

---

That latest AMD driver update 19.12.2 was garbage. Caused my system to crash. That running 1 wu on a Radeon VII. I reverted back to 19.9.2 and it's been stable since.

But at least your cards, so long as you stay with your current drivers, are not effected by the huge problem that effects the newer RX pose just out of the box and so far no solution is in site (other than AMD now stating that their RX cards are not "SETI Friendly").

But I would be very wary about newer drivers on their older kits now. ;-)

Cheers.

That is good info. Looks like fredi's computer 8867025 is running the PAL OpenCL driver for Linux (probably from the AMDGPU-Pro package). As ROCm driver cards still aren't chosen in the ATI multibeam client's plan class, the only results we'd get from those will be from anonymous hosts, and that's only when ROCm finally gets Navi support.

So the big question is how this continues to work on the macOS OpenCL runtime according to observations posted to this thread. My guesses are one of these:
- There's an issue with Navi support at the PAL layer. Both the Windows driver and AMDGPU-Pro use the PAL layer provided by device drivers.
- Both the Windows and AMDGPU-Pro OpenCL compilers are shipped with the same GCN bitcode mistakes.

I don't know if the Apple stack uses PAL at all.

---

Since yesterday, we've fallen back to the old server so anonymous platform apps should be able to get work. Since this morning we should have had the validator that requires 3 results for overflow results. Merry Christmas!

Now I just need to explain why some workunits like this one are sneaking through.

Problem found and fixed....

---

@SETIEric@qoto.org (Mastodon)

Since yesterday, we've fallen back to the old server so anonymous platform apps should be able to get work. Since this morning we should have had the validator that requires 3 results for overflow results. Merry Christmas!

Thanks for all your efforts.

We're just very curious as to how the Scheduler from Beta ended up on main, after all the complaints about it's issues over at Beta about it?

---

Grant
Darwin NT

Since yesterday, we've fallen back to the old server so anonymous platform apps should be able to get work. Since this morning we should have had the validator that requires 3 results for overflow results. Merry Christmas!

Now I just need to explain why some workunits like this one are sneaking through.

<edit>Problem found and fixed....</edit>

+42

---

A proud member of the OFA (Old Farts Association).

Since yesterday, we've fallen back to the old server so anonymous platform apps should be able to get work. Since this morning we should have had the validator that requires 3 results for overflow results. Merry Christmas!

Now I just need to explain why some workunits like this one are sneaking through.

<edit>Problem found and fixed....</edit>

. . Thanks for all the hard work, and I hope whoever was responsible buys you guys a nice dinner out (and wine) :)

. . Have a happy New Year!

Stephen

:)