Created attachment 133896 [details] Kernel config Trying to couple mainline amdgpu driver with opencl from amdgpu-pro (installed via Gentoo dev-libs/amdgpu-pro-opencl package) to make darktable use opencl again. Clinfo and apps see the opencl but when trying to create a command queue driver returns CL_OUT_OF_HOST_MEMORY. The same behavior is reported on Ubuntu 16.04.3 as seen here https://redmine.darktable.org/issues/11702 kernel 4.12.0-pf7 xorg-server-1.19.3 libdrm-2.4.82 xorg-1.19.3 x11-drivers/xf86-video-amdgpu-1.3.0 dev-libs/amdgpu-pro-opencl-17.30.465504
Created attachment 133897 [details] Dmesg output
Created attachment 133898 [details] Clinfo output
Created attachment 133899 [details] darktable-cltest output
Created attachment 133900 [details] lspci -k output
I managed to make it work somehow, but it's still unusable due to producing artifacts on images processed using opencl on darktable and few other programs I tried. So probably the title should be changed. However, CL_OUT_OF_HOST_MEMORY error may be removed via envitonment var setting, namely export GPU_FORCE_64BIT_PTR=1 also export GPU_USE_SYNC_OBJECTS=1 export GPU_MAX_ALLOC_PERCENT=100 export GPU_SINGLE_ALLOC_PERCENT=100 export GPU_MAX_HEAP_SIZE=100 are recommended but I haven't noticed any difference. What I've noticed, however, is that the driver reports the different amount of available GPU memory each time darktable is started...
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/13.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.