cancel
Showing results for 
Search instead for 
Did you mean: 

OpenCL

G_0_M
Journeyman III

20.45-1188099-rhel-8.2 OpenCL bug

I am the package maintainer of darktable.org photo editing software on Fedora/CentOS/RHEL.

I need to report this OpenCL bug of driver AMDGPU-Pro 20.45-1188099-rhel-8.2. The GPU is a RX480
```

https://github.com/darktable-org/darktable/issues/7641#issuecomment-757386750

0 Likes
5 Replies
dipak
Big Boss

Thank you for reporting this.

 

#8 0x00007f61cb7f5865 in ?? () from /home/user/amdgpu-pro-20.45-1188099-rhel-8.2/opt/amdgpu-pro/lib64/libamdocl-orca64.so
#9 0x00007f61cb7e126b in clBuildProgram () from /home/user/amdgpu-pro-20.45-1188099-rhel-8.2/opt/amdgpu-pro/lib64/libamdocl-orca64.so #10 0x00007f622582514d in dt_opencl_build_program (dev=dev@entry=0, prog=prog@entry=2, binname=binname@entry=0x55b33a1e40d0 "/home/user/.cache/darktable/cached_kernels_for_Ellesmere_31884/basic.cl.bin", cachedir=cachedir@entry=0x55b33a292f00 "/home/user/.cache/darktable/cached_kernels_for_Ellesmere_31884", md5sum=md5sum@entry=0x7ffdc82cd320 "6a7ac27a0a07a40e4f9c782096beabee", loaded_cached=1) at /usr/src/debug/darktable-3.4.0-3.fc33.x86_64/src/common/opencl.c:1716

From the above backtrace information, it looks like clBuildProgram() API is the last OpenCL runtime API that was called. As I can see, the "#10" line points to the kernel or device binary that was used to call clBuildProgram(). It would be helpful if you can provide us that kernel or device binary which triggered the issue. If device binary was used, please confirm whether the device binary was generated with the same driver.  If not, please generate the binary with the latest driver and then try.

 

Thanks.

 

0 Likes

By looking at the timestamp of the kernel directory and the timestamp of the amdgpu-pro drivers I am using, I really think the kernel have been generated by using lastest driver (the one in thread title). I attach the entire directory here

0 Likes

As I can see, there are a number of binary files. Could you please point to any particular binary file which reproduces the issue?

By the way, may we assume that the issue only occurs when clBuildProgram() is used to build the program from the device binary, not from the source file?

 

Thanks.

0 Likes

I don't know, because I have no knowledge about how OpenCL works.

I can just tell you that we Fedora users are forced to use propertary amdgpu-pro OpenCL drivers by unpacking them and starting darktable with command

OCL_ICD_VENDORS=/home/user/amdgpu-pro-20.45-1188099-rhel-8.2/etc/OpenCL/vendors/  LD_LIBRARY_PATH=/home/user/amdgpu-pro-20.45-1188099-rhel-8.2/opt/amdgpu-pro/lib64/ darktable

I tried to retrieve infos you need in darktable developers mailing list, but I received no reply: https://www.mail-archive.com/darktable-dev@lists.darktable.org/msg06057.html

0 Likes

To reproduce the issue using the package, please share the download link and provide the detailed steps to build and run it. I'll report the issue to the appropriate team.

Meanwhile, if you get any feedback from the darktable team, please share with us. 

 

Thanks.

0 Likes