(In reply to Samuel Pitoiset from comment #20)
> Make sure to load the right version of libdrm (ie. 2.4.93 or more recent). I
> had this problem today because I was loading and old version of libdrm.
> Something was installed in the wrong place.

Doh!

Sorry!  Ugh. Development systems...

My latest AMDGPU-PRO OpenCL (amdgpu-pro-18.30-635379-sle-12.tar.xz)
installation broad me

/opt/amdgpu/lib64/
insgesamt 268
drwxr-xr-x 2 root root  4096 18. Aug 06:31 .
drwxr-xr-x 4 root root  4096 18. Aug 06:31 ..
lrwxrwxrwx 1 root root    22  8. Aug 18:33 libdrm_amdgpu.so.1 ->
libdrm_amdgpu.so.1.0.0
-rwxr-xr-x 1 root root 69192  8. Aug 18:33 libdrm_amdgpu.so.1.0.0
lrwxrwxrwx 1 root root    22  8. Aug 18:33 libdrm_radeon.so.1 ->
libdrm_radeon.so.1.0.1
-rwxr-xr-x 1 root root 68968  8. Aug 18:33 libdrm_radeon.so.1.0.1
lrwxrwxrwx 1 root root    15  8. Aug 18:33 libdrm.so.2 -> libdrm.so.2.4.0
-rwxr-xr-x 1 root root 99600  8. Aug 18:33 libdrm.so.2.4.0
lrwxrwxrwx 1 root root    15  8. Aug 18:33 libkms.so.1 -> libkms.so.1.0.0
-rwxr-xr-x 1 root root 22096  8. Aug 18:33 libkms.so.1.0.0

but the screen corruption appeared first around Aug 22, 2018.

So it worked 'halfway' with upstream _and_ AMDGPU-PRO libdrm.

Maybe the AMD developers could include a 'tag' or something like that to
differentiate both version?!

CONCLUSION

After deleting /opt/amdgpu/lib64/ ALL is fine, again.