You are not logged in.

#26 2023-08-06 11:51:59

trougnouf
Member
Registered: 2022-12-03
Posts: 5

Re: Opencl error (may be PHI node, LLVM problem)

I got darktable/ansel to work properly with ROCm OpenCL using the opencl-amd aur package instead of the official rocm-opencl-runtime package.

Somehow it shows a slightly higher version (3581 vs 3570 in the official package).

Unfortunately that means uninstalling a lot of packages including python-pytorch-opt-rocm.

Offline

#27 2023-08-07 11:55:44

Libert
Member
From: S_Korea
Registered: 2023-03-09
Posts: 15
Website

Re: Opencl error (may be PHI node, LLVM problem)

Thank you for your interest and for proposing solutions so far.
It has been very helpful.

Last edited by Libert (2023-08-07 11:57:12)


May there be a rightful result for your efforts...
Home / Git

Offline

#28 2023-08-08 10:29:41

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 11,814

Re: Opencl error (may be PHI node, LLVM problem)

Happy to Help.

Please prepend [Workedaround] (or similar) to the thread title (edit first post. there's a character limit so you may have to remove some stuff to make it fit).


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

#29 2023-08-26 13:14:20

Fabi0_Z
Member
Registered: 2019-02-05
Posts: 13

Re: Opencl error (may be PHI node, LLVM problem)

Libert wrote:

ohh....   Thanks!!!


❯ LC_ALL=C RUSTICL_ENABLE=radeonsi darktable -d opencl

     0.0691 [dt_get_sysresource_level] switched to 1 as `default'
     0.0691   total mem:       15833MB
     0.0691   mipmap cache:    1979MB
     0.0691   available mem:   7916MB
     0.0691   singlebuff:      123MB
     0.0691   OpenCL tune mem: OFF
     0.0691   OpenCL pinned:   OFF
[opencl_init] opencl related configuration options:
[opencl_init] opencl: ON
[opencl_init] opencl_scheduling_profile: 'default'
[opencl_init] opencl_library: 'default path'
[opencl_init] opencl_device_priority: '*/!0,*/*/*/!0,*'
[opencl_init] opencl_mandatory_timeout: 400
[opencl_init] opencl library 'libOpenCL' found on your system and loaded
[opencl_init] found 1 platform
[opencl_init] found 1 device

[dt_opencl_device_init]
   DEVICE:                   0: 'AMD Radeon Pro W6600 (navi23, LLVM 15.0.7, DRM 3.49, 6.1.39-3-lts)', NEW
   PLATFORM NAME & VENDOR:   rusticl, Mesa/X.org
   CANONICAL NAME:           rusticlamdradeonprow6600
   DRIVER VERSION:           23.1.5
   DEVICE VERSION:           OpenCL 3.0 
   DEVICE_TYPE:              GPU
   GLOBAL MEM SIZE:          8192 MB
   MAX MEM ALLOC:            2048 MB
   MAX IMAGE SIZE:           16384 x 16384
   MAX WORK GROUP SIZE:      1024
   MAX WORK ITEM DIMENSIONS: 3
   MAX WORK ITEM SIZES:      [ 1024 1024 1024 ]
   ASYNC PIXELPIPE:          NO
   PINNED MEMORY TRANSFER:   NO
   MEMORY TUNING:            NO
   FORCED HEADROOM:          400
   AVOID ATOMICS:            NO
   MICRO NAP:                250
   ROUNDUP WIDTH:            16
   ROUNDUP HEIGHT:           16
   CHECK EVENT HANDLES:      128
   TILING ADVANTAGE:         0.000
   DEFAULT DEVICE:           NO
   KERNEL BUILD DIRECTORY:   /usr/share/darktable/kernels
   KERNEL DIRECTORY:         /home/libert/.cache/darktable/cached_v1_kernels_for_rusticlAMDRadeonProW6600_2315
   CL COMPILER OPTION:       -cl-fast-relaxed-math
   KERNEL LOADING TIME:       1.6686 sec
[opencl_init] OpenCL successfully initialized. Internal numbers and names of available devices:
[opencl_init]		0	'rusticl AMD Radeon Pro W6600'
[opencl_init] FINALLY: opencl is AVAILABLE and ENABLED.
[opencl_init] set scheduling profile to default.
[dt_opencl_update_priorities] these are your device priorities:
[dt_opencl_update_priorities] 		image	preview	export	thumbspreview2
[dt_opencl_update_priorities]		0	-1	0	0	-1
[dt_opencl_update_priorities] show if opencl use is mandatory for a given pixelpipe:
[dt_opencl_update_priorities] 		image	preview	export	thumbspreview2
[dt_opencl_update_priorities]		0	0	0	0	0
[opencl_synchronization_timeout] synchronization timeout set to 200
[dt_opencl_update_priorities] these are your device priorities:
[dt_opencl_update_priorities] 		image	preview	export	thumbspreview2
[dt_opencl_update_priorities]		0	-1	0	0	-1
[dt_opencl_update_priorities] show if opencl use is mandatory for a given pixelpipe:
[dt_opencl_update_priorities] 		image	preview	export	thumbspreview2
[dt_opencl_update_priorities]		0	0	0	0	0
[opencl_synchronization_timeout] synchronization timeout set to 200
ioctl (GFEATURE): Invalid argument
ioctl (GFEATURE): Invalid argument
ioctl (GFEATURE): Invalid argument
ioctl (GFEATURE): Broken pipe
ioctl (GFEATURE): Broken pipe
ioctl (GFEATURE): Broken pipe
    11.6604 [_gamepad_open_devices] opened game controller 'ASUS ROG Kunai 3 Gamepad'
[dt_opencl_update_priorities] these are your device priorities:
[dt_opencl_update_priorities] 		image	preview	export	thumbspreview2
[dt_opencl_update_priorities]		0	-1	0	0	-1
[dt_opencl_update_priorities] show if opencl use is mandatory for a given pixelpipe:
[dt_opencl_update_priorities] 		image	preview	export	thumbspreview2
[dt_opencl_update_priorities]		0	0	0	0	0
[opencl_synchronization_timeout] synchronization timeout set to 200
[dt_opencl_update_priorities] these are your device priorities:
[dt_opencl_update_priorities] 		image	preview	export	thumbspreview2
[dt_opencl_update_priorities]		0	-1	0	0	-1
[dt_opencl_update_priorities] show if opencl use is mandatory for a given pixelpipe:
[dt_opencl_update_priorities] 		image	preview	export	thumbspreview2
[dt_opencl_update_priorities]		0	0	0	0	0
[opencl_synchronization_timeout] synchronization timeout set to 200
[dt_opencl_update_priorities] these are your device priorities:
[dt_opencl_update_priorities] 		image	preview	export	thumbspreview2
[dt_opencl_update_priorities]		0	-1	0	0	-1
[dt_opencl_update_priorities] show if opencl use is mandatory for a given pixelpipe:
[dt_opencl_update_priorities] 		image	preview	export	thumbspreview2
[dt_opencl_update_priorities]		0	0	0	0	0
[opencl_synchronization_timeout] synchronization timeout set to 200
[dt_opencl_update_priorities] these are your device priorities:
[dt_opencl_update_priorities] 		image	preview	export	thumbspreview2
[dt_opencl_update_priorities]		0	-1	0	0	-1
[dt_opencl_update_priorities] show if opencl use is mandatory for a given pixelpipe:
[dt_opencl_update_priorities] 		image	preview	export	thumbspreview2
[dt_opencl_update_priorities]		0	0	0	0	0
[opencl_synchronization_timeout] synchronization timeout set to 200
[dt_opencl_update_priorities] these are your device priorities:
[dt_opencl_update_priorities] 		image	preview	export	thumbspreview2
[dt_opencl_update_priorities]		0	-1	0	0	-1
[dt_opencl_update_priorities] show if opencl use is mandatory for a given pixelpipe:
[dt_opencl_update_priorities] 		image	preview	export	thumbspreview2
[dt_opencl_update_priorities]		0	0	0	0	0
[opencl_synchronization_timeout] synchronization timeout set to 200
 [opencl_summary_statistics] device 'rusticl AMD Radeon Pro W6600' (0): 30 out of 31 events were successful and 0 events lost. max event=30
❯ darktable
ioctl (GFEATURE): 부적절한 인수
ioctl (GFEATURE): 부적절한 인수
ioctl (GFEATURE): 부적절한 인수
ioctl (GFEATURE): 파이프가 깨어짐
ioctl (GFEATURE): 파이프가 깨어짐
ioctl (GFEATURE): 파이프가 깨어짐
     0.9917 [_gamepad_open_devices] opened game controller 'ASUS ROG Kunai 3 Gamepad'

OpenCL also works. Thank you!!

Is Darktable correctly rendering images with opencl-rusticl-mesa? I'm in the same situation, DT recognize both the driver and the device, but when I'm in the darkroom the preview always looks total black

I've tried using instead opencl-clover-mesa and works fine, Radeon 5700XT

Offline

#30 2023-09-16 18:33:46

glenjo
Member
From: Pacific NW
Registered: 2020-06-09
Posts: 36

Re: Opencl error (may be PHI node, LLVM problem)

I ended up with the same problem, and this thread has been very helpful in fixing the problem. I did find that it was easier to go into the darktablerc file and turn off the implementations of opencl which were causing the problem. I can provide some details on that if there is any interest.

Offline

Board footer

Powered by FluxBB