- User Since
- Wed, Jul 31, 4:48 PM (2 w, 3 d)
Fri, Aug 2
Thanks, that's quite likely. I'm trying to debug further issues with this OpenCL runtime and Blender upstream and it does sound like having a slightly unexpected LLVM or Clang version can lead to such wild issues: https://github.com/intel/compute-runtime/issues/195
Instead of this patch we should update python for 2.81
Thu, Aug 1
I stumbled on this diff while trying to make my AMD Radeon RX Vega M work with Blender 2.80 / 2.81 alpha on Linux (T68009).
While the above file shows that the OpenCL capabilities of the AMD GPU seem fine (confirmed by opencl), it is not listed as recognized in Edit > Settings > System.
Intel upstream bug report: https://github.com/intel/compute-runtime/issues/194
Updated backtrace with debug symbols:
Note that the bug may very well be in https://github.com/intel/compute-runtime
It's my first Blender patch so I'm not sure I cross-referenced things properly.
I found that it fails the first time you click the link, but seems to work on subsequent calls. (It's also not only related to Help > Report a Bug but any link meant to open in the browser). I'll send a patch that retries once on error.
I'm not very familiar with Python's release cycle but it seems fixes were merged in the 3.7 branch in July 2018 and November 2018, so I assume the bug might be fixed with 3.7.2 and later.
Wed, Jul 31
I found that this might be related to https://developer.blender.org/D2171 since my AMD GPU does use Mesa's Clover OpenCL implementation:
$ ./clinfo --list Platform #0: Clover `-- Device #0: AMD VEGAM (DRM 3.30.0, 5.1.20-desktop-2.mga7, LLVM 8.0.0) Platform #1: Intel(R) OpenCL HD Graphics `-- Device #0: Intel(R) Gen9 HD Graphics NEO
I just tested 2.81-5359b7a03307 (2019-07-30) and the bug is reproducible too.