Cant start Darktable with openCL enabled

When I start Darktable with openCL enabled, it hangs. This is the output of darktable -d opencl

     0.0631 [dt_get_sysresource_level] switched to 1 as `default'
     0.0632   total mem:       15932MB
     0.0632   mipmap cache:    1991MB
     0.0632   available mem:   7966MB
     0.0632   singlebuff:      124MB
     0.0632   OpenCL tune mem: OFF
     0.0632   OpenCL pinned:   OFF
[opencl_init] opencl related configuration options:
[opencl_init] opencl: ON
[opencl_init] opencl_scheduling_profile: 'very fast GPU'
[opencl_init] opencl_library: 'default path'
[opencl_init] opencl_device_priority: '*/!0,*/*/*/!0,*'
[opencl_init] opencl_mandatory_timeout: 200
[opencl_init] opencl library 'libOpenCL' found on your system and loaded

These are the openCL libs installed:

/opt/cuda/targets/x86_64-linux/lib/libOpenCL.so
/opt/cuda/targets/x86_64-linux/lib/libOpenCL.so.1
/opt/cuda/targets/x86_64-linux/lib/libOpenCL.so.1.0
/opt/cuda/targets/x86_64-linux/lib/libOpenCL.so.1.0.0
/opt/intel/oneapi/compiler/2023.0.0/linux/lib/libOpenCL.so
/opt/intel/oneapi/compiler/2023.0.0/linux/lib/libOpenCL.so.1
/opt/intel/oneapi/compiler/2023.0.0/linux/lib/libOpenCL.so.1.2
/usr/lib/libOpenCL.so
/usr/lib/libOpenCL.so.1
/usr/lib/libOpenCL.so.1.0.0

I think this is an issue with olc-idc installed? I am using Arch for Darktable.
I have a Nvidia 3090 in this computer, which I have also installed opencl-nvidia for

Does dt start if openCL is disabled?

Did dt work previously with openCL?

What version of the nvidia driver?

There isn’t much we can do about bad openCL drivers, AFAIK

clinfo + darktable-cltest might have more insight. Having multiple devices / drivers can mess things up. AFAIK there is a way to limit which driver is loaded, in /etc/OpenCL/vendors/

Edit: OpenCL on Linux is a excellent write-up on the details.

Is this with an Arc GPU? You may have to use the newest kernel available (which provides i915.ko for Intel GPU).

If you attach to darktable process with strace, you may see, that it’s in an infinite loop. On Ubuntu, switching to a newer kernel from https://kernel.ubuntu.com fixes it. Not sure what’s available for Arch.