dri-devel September 2019

dri-devel@lists.freedesktop.org

315 participants
2278 discussions

[Bug 110405] No successful install of amdgpu 18.30 on Ubuntu 18.04.02 LTS
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=110405 Bug ID: 110405 Summary: No successful install of amdgpu 18.30 on Ubuntu 18.04.02 LTS Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: arnonym123yt(a)gmail.com Created attachment 143941 --> https://bugs.freedesktop.org/attachment.cgi?id=143941&action=edit Logs, as described in https://amdgpu-install.readthedocs.io/en/latest/install-bugrep.html Standard Gnome-session not starting, after login it goes directly back to login prompt. Ubuntu with wayland is working. Cinnamon is not working. After purge of amdgpu, everything is back to normal. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 109923] Chromium shows blackscreen on sketchfab like sites (WebGL?) (rx460, 18.50-725072, 7/2/2019)
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=109923 Bug ID: 109923 Summary: Chromium shows blackscreen on sketchfab like sites (WebGL?) (rx460, 18.50-725072, 7/2/2019) Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: DRM/AMDgpu-pro Assignee: dri-devel(a)lists.freedesktop.org Reporter: mihailov-d-v(a)mail.ru Steps to Reproduce: Open sketchfab.com, while loading chromium shows something, but then everything gets black. It is happening on 18.50-725072 amdgpu-pro drivers, while on 18.40-697810 chromium doesn't show blackscreen. I use Lubuntu 18.04. Some outputs (there is one comment after dmesg): $uname -a Linux user 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:33:07 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ dmesg | grep amdgpu [ 6.246244] [drm] amdgpu kernel modesetting enabled. [ 6.246246] [drm] amdgpu version: 18.50.1.418 [ 6.257297] fb: switching to amdgpudrmfb from VESA VGA [ 6.257997] amdgpu 0000:01:00.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0xffff [ 6.263289] amdgpu 0000:01:00.0: VRAM: 2048M 0x000000F400000000 - 0x000000F47FFFFFFF (2048M used) [ 6.263292] amdgpu 0000:01:00.0: GART: 256M 0x000000FF00000000 - 0x000000FF0FFFFFFF [ 6.267778] [drm] amdgpu: 2048M of VRAM memory ready [ 6.267780] [drm] amdgpu: 13014M of GTT memory ready. [ 6.633726] fbcon: amdgpudrmfb (fb0) is primary device [ 6.694025] amdgpu 0000:01:00.0: fb0: amdgpudrmfb frame buffer device [ 6.711472] [drm] Initialized amdgpu 3.27.0 20150101 for 0000:01:00.0 on minor 0 [ 203.253903] amdgpu 0000:01:00.0: GPU fault detected: 146 0x0378770c for process chromium-browse pid 2365 thread chromium-browse pid 2365 [ 203.253910] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x0011306F [ 203.253912] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0807700C [ 203.253915] amdgpu 0000:01:00.0: VM fault (0x0c, vmid 4, pasid 32771) at page 1126511, read from 'SDM0' (0x53444d30) (119) [ 579.809297] amdgpu 0000:01:00.0: GPU fault detected: 146 0x0378770c for process chromium-browse pid 2365 thread chromium-browse pid 2365 [ 579.809305] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x0011306F [ 579.809307] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0E07700C [ 579.809310] amdgpu 0000:01:00.0: VM fault (0x0c, vmid 7, pasid 32771) at page 1126511, read from 'SDM0' (0x53444d30) (119) (The comment:) The error messages after point [ 203.253903] are typical for 18.40-697810 too, but chromium seems work not so bad. Render artifacts doesn't count. (End of comment) chrome://version tab: Chromium 72.0.3626.119 (Official Build) Built on Ubuntu , running on Ubuntu 18.04 (64-bit) Revision 9a65993e2cde1b5797ec98da4cd9abcea464cd7b-refs/branch-heads/3626@{#876} OS Linux JavaScript V8 7.2.502.26 Flash 32.0.0.142 /usr/lib/adobe-flashplugin/libpepflashplayer.so User Agent Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/72.0.3626.119 Chrome/72.0.3626.119 Safari/537.36 Command Line /usr/lib/chromium-browser/chromium-browser --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so --ppapi-flash-version=32.0.0.142 --enable-pinch --enable-native-gpu-memory-buffers --enable-features=CheckerImaging --flag-switches-begin --autoplay-policy=no-user-gesture-required --enable-gpu-rasterization --enable-offline-auto-reload-visible-only --disable-offline-auto-reload --enable-tcp-fastopen --enable-zero-copy --ignore-gpu-blacklist --num-raster-threads=3 --enable-features=CheckerImaging,DrawOcclusion,ExpensiveBackgroundTimerThrottling,OptimizationHints,ParallelDownloading,UseSurfaceLayerForVideo --disable-features=AutofillExpandedPopupViews,MemoryCoordinator,WebPayments,fill-on-account-select --flag-switches-end Executable Path /usr/lib/chromium-browser/chromium-browser If it's not the right place for this bug please tell me where can I report it, if you know. -- You are receiving this mail because: You are the assignee for the bug.

1 12

[Bug 109499] amdgpu 4k modes not working
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=109499 Bug ID: 109499 Summary: amdgpu 4k modes not working Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu-pro Assignee: dri-devel(a)lists.freedesktop.org Reporter: snorkellingcactus(a)gmail.com Hi. We have an AMD W7100. We are trying to use two DisplayPort at 3840x2160. Firstly, those modes are not listed by xrandr Second, adding and setting a new xrandr mode may work only after replugging DisplayPort cables on other DisplayPort (for example, disconnecting DP0 and DP1 and connecting to DP2 and DP3). Then, fix will not persist across reboots. EDID seems to behave flaky by some reason (EDID invalid messages from dmesg) We however have a vendor provided EDID which we forced to be loaded on boot. That only changed available modes to a max of 1920x1080 but symptoms kept being the same. (edid-decode info shows 3840x2160 modes however) We tried thousands of options/configs. We are on Ubuntu 16.04. We tried amdgpu-pro 18.30 and 18.10 version of the driver, with kernel 4.15 and kernel 4.13, using amdgpu.dc=0 and amdgpu.dc=1, using amdgpu and modesetting as driver on xorg. The errors dmesg throws when adding/setting the 3840x2160 with xrandr are like: X Error of failed request: BadName (named color or font does not exist) Major opcode of failed request: 140 (RANDR) Minor opcode of failed request: 16 (RRCreateMode) Serial number of failed request: 43 Current serial number in output stream: 43 [241317.628306] [drm:drm_crtc_helper_set_config [drm_kms_helper]] *ERROR* failed to set mode on [CRTC:37:crtc-0] xrandr: Configure crtc 0 failed xrandr: Configure crtc 1 failed [241317.940299] [drm:drm_crtc_helper_set_config [drm_kms_helper]] *ERROR* failed to set mode on [CRTC:39:crtc-1] On some setup, with drm debug enabled on kernel and when trying to set the 3840x2160 mode with xrandr dmesg trhow: [ 7.638690] [drm:drm_mode_prune_invalid [drm]] Not using 3840x2160 mode: CLOCK_HIGH When using amdgpu.dc=1 that changed to something like: X Error of failed request: BadName (named color or font does not exist) Major opcode of failed request: 140 (RANDR) Minor opcode of failed request: 16 (RRCreateMode) Serial number of failed request: 39 Current serial number in output stream: 39 [ 4482.053606] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] amdgpu_crtc id:0 crtc_state_flags: enable:0, active:0, planes_changed:0, mode_changed:0,active_changed:0,connectors_changed:0 [ 4482.056191] [drm:drm_mode_setcrtc [drm]] [CRTC:43:crtc-0] [ 4482.056232] [drm:drm_mode_setcrtc [drm]] [CONNECTOR:55:DP-1] [ 4482.056390] [drm:best_encoder [amdgpu]] Finding the best encoder [ 4482.056530] [drm:best_encoder [amdgpu]] Finding the best encoder [ 4482.056661] [drm:best_encoder [amdgpu]] Finding the best encoder [ 4482.056839] [drm:dm_update_crtcs_state [amdgpu]] amdgpu_crtc id:0 crtc_state_flags: enable:1, active:1, planes_changed:0, mode_changed:1,active_changed:1,connectors_changed:1 [ 4482.057041] [drm:update_stream_scaling_settings [amdgpu]] Destination Rectangle x:0 y:0 width:3840 height:2160 [ 4482.057201] [drm:dm_update_crtcs_state [amdgpu]] amdgpu_crtc id:0 crtc_state_flags: enable:1, active:1, planes_changed:0, mode_changed:1,active_changed:1,connectors_changed:1 [ 4482.057357] [drm:dm_update_crtcs_state [amdgpu]] Enabling DRM crtc: 43 [ 4482.057539] [drm:dm_update_planes_state [amdgpu]] Enabling DRM plane: 41 on DRM crtc 43 [ 4482.057687] [drm:amdgpu_dm_atomic_check [amdgpu]] Atomic check failed with err: -22 xrandr: Configure crtc 0 failed [ 4482.092223] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] amdgpu_crtc id:0 crtc_state_flags: enable:0, active:0, planes_changed:0, mode_changed:0,active_changed:0,connectors_changed:0 xrandr: Configure crtc 0 failed [ 4482.094553] [drm:drm_mode_setcrtc [drm]] [CRTC:43:crtc-0] [ 4482.094567] [drm:drm_mode_setcrtc [drm]] [CONNECTOR:57:DP-2] [ 4482.094622] [drm:best_encoder [amdgpu]] Finding the best encoder [ 4482.094668] [drm:best_encoder [amdgpu]] Finding the best encoder [ 4482.094713] [drm:best_encoder [amdgpu]] Finding the best encoder [ 4482.094761] [drm:dm_update_crtcs_state [amdgpu]] amdgpu_crtc id:0 crtc_state_flags: enable:1, active:1, planes_changed:0, mode_changed:1,active_changed:1,connectors_changed:1 [ 4482.094809] [drm:update_stream_scaling_settings [amdgpu]] Destination Rectangle x:0 y:0 width:3840 height:2160 [ 4482.094849] [drm:dm_update_crtcs_state [amdgpu]] amdgpu_crtc id:0 crtc_state_flags: enable:1, active:1, planes_changed:0, mode_changed:1,active_changed:1,connectors_changed:1 [ 4482.094887] [drm:dm_update_crtcs_state [amdgpu]] Enabling DRM crtc: 43 [ 4482.094938] [drm:dm_update_planes_state [amdgpu]] Enabling DRM plane: 41 on DRM crtc 43 [ 4482.094979] [drm:amdgpu_dm_atomic_check [amdgpu]] Atomic check failed with err: -22 We also tried various modelines, reported by dmesg, by xorg and by edid-decode. So i think we tried modelines with clock less than ¿ 300000khz ? aprox. Bug seems similar to https://bugs.freedesktop.org/show_bug.cgi?id=102985 Which mentions something about the driver not taking some part of the EDID modes upper to 64. Dont know however which commit introduced that change to test it on Ubuntu 16.04 / Linux 4.15. The commit mentioned on that bug report seems invalid / obsolete. xrandr commands are like: xrandr --newmode "3840" 297.00 3840 4016 4104 4400 2160 2168 2178 2250 +hsync +vsync xrandr --addmode DisplayPort-0 "3840" xrandr --output DisplayPort-0 --mode "3840" -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 108890] VLC Segmentation fault (core dumped)
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=108890 Bug ID: 108890 Summary: VLC Segmentation fault (core dumped) Product: DRI Version: unspecified Hardware: Other OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu-pro Assignee: dri-devel(a)lists.freedesktop.org Reporter: snurfle(a)gmail.com Created attachment 142649 --> https://bugs.freedesktop.org/attachment.cgi?id=142649&action=edit Pertinent system logs Upgraded Ubuntu 16.04 to 18.04.1. VLC worked correctly prior to the upgrade; no hardware changes were made. VLC plays music files correctly. Any video files cause "Segmentation fault (core dumped)" Happens if 2x-clicking a video file, or if dropping a video file onto a running VLC window, or if selecting a video from Media -> Open File. Specific file format does not matter - I have confirmed with mp4, mkv, webm, avi, mov Turning hardware acceleration off does not correct the issue. Full output: VLC media player 3.0.4 Vetinari (revision 3.0.4-0-gf615db6332) [0000557badb0d570] main libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface. [0000557badb114e0] main playlist: playlist is empty Gtk-Message: 10:02:40.800: GtkDialog mapped without a transient parent. This is discouraged. Segmentation fault (core dumped) Videos play correctly with xine. Possibly related symptoms: Videos viewed on Chrome exhibit tearing (with hw accel on or off) but not in Firefox. After the initial upgrade, the system would freeze at every boot - screen would flicker and attempt to launch the GUI, but would drop back to the terminal. Safe Mode from the recovery console would flicker the screen and return to the recovery console. ***This behavior was the same when booting to a live Ubuntu 18.04.1 disc.*** Ultimately required amdgpu-uninstall from recovery console CLI to get to a login/desktop. Currently running the latest AMDGPU driver, and have removed and re-installed it multiple times. ("amdgpu-pro-18.40-676022-ubuntu-18.04.tar.xz") No other graphics issues are apparent with the system; Geeks3d GPUtest runs very smoothly and gives very impressive results. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 108882] Many different installation problems with amdgpu-pro-18.40-676022-rhel-6 driver in CentOS 6.10
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=108882 Bug ID: 108882 Summary: Many different installation problems with amdgpu-pro-18.40-676022-rhel-6 driver in CentOS 6.10 Product: DRI Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu-pro Assignee: dri-devel(a)lists.freedesktop.org Reporter: elmar(a)yasara.org Created attachment 142636 --> https://bugs.freedesktop.org/attachment.cgi?id=142636&action=edit The various logs Dear AMD Team, unfortunately installation of your amdgpu-pro-18.40-676022-rhel-6 driver in CentOS 6.10 goes wrong at many spots. So far I had been using fglrx happily, but now I needed Vulkan support, so I decided to upgrade. Since I got a AMD Radeon R9 290X I followed instructions at https://amdgpu-install.readthedocs.io/en/latest/ and used amdgpu-pro-install --opencl=legacy the script ran through, I rebooted, and got a black screen. Logging in remotely and looking at /var/log/Xorg.0.log I saw lots of entries about fglrx. Since your instructions don't mention uninstalling old drivers, and your amdgpu-pro-install doesn't complain, I don't think that's my fault. Next, I uninstalled fglrx, to be sure also amdgpu-pro-uninstall, rebooted, and went for another amdgpu-pro-install --opencl=legacy After another reboot, a 'startx' finally gave me a running X-server, but no OpenGL/GLX (running glxinfo yielded 'no GLX visual found'). Next I checked what amdgpu-pro-install did to my /etc/X11/xorg.conf and found this: Section "ServerLayout" Identifier "Main" Option "AIGLX" "false" EndSection Section "Device" Identifier "Videocard0" Driver "radeon" EndSection This doesn't look like it's a proper xorg.conf for amdgpu-pro. After some googling, I replaced xorg.conf with this file: /usr/share/X11/xorg.conf.d/00-amdgpu-pro.conf After an X-server restart, 'glxinfo' in a terminal gave a different error: libGL error: failed to open drm device: Permission denied libGL error: failed to load driver: radeonsi libGL error: failed to open drm device: Permission denied libGL error: failed to load driver: radeonsi libGL error: failed to open drm device: Permission denied libGL error: failed to load driver: radeonsi Whenever there is a permission problem, I try again as 'root', and indeed, things worked. After some googling, I did cd /dev/dri ls -l crw-rw----+ 1 root video 226, 0 Nov 27 23:06 card0 crw-rw----. 1 root video 226, 64 Nov 27 23:06 controlD64 crw-rw----+ 1 root video 226, 128 Nov 27 23:06 renderD128 Then I did chmod a+rw * and got crw-rw-rw-+ 1 root video 226, 0 Nov 27 23:06 card0 crw-rw-rw-. 1 root video 226, 64 Nov 27 23:06 controlD64 crw-rw-rw-+ 1 root video 226, 128 Nov 27 23:06 renderD128 And magically, after many hours of fiddling, OpenGL and OpenCL worked for a normal user. Yupppie! So I figured it's time to file a bug report, ended up at https://amdgpu-install.readthedocs.io/en/latest/install-bugrep.html#generat… This page shows countless commands to run to save my system config. And amazingly, each command is shown with a '$' in front. This means that I cannot just copy the entire script into a terminal, but instead have to do it line-by-line manually, or copy it to a text editor and cut the $s out. Seriously? Hope this report helped to improve things... Regards, Elmar -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 108034] Error installing vega 64 drivers in Ubuntu bionic kernel 4.18.8
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=108034 Bug ID: 108034 Summary: Error installing vega 64 drivers in Ubuntu bionic kernel 4.18.8 Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu-pro Assignee: dri-devel(a)lists.freedesktop.org Reporter: diego.alonso.gonzalez+bugs(a)gmail.com Created attachment 141700 --> https://bugs.freedesktop.org/attachment.cgi?id=141700&action=edit logs as stated by https://amdgpu-install.readthedocs.io/en/amd-18.30/install-bugrep.html It seems drivers are not getting properly installed This is what i saw during installation: [...] Building initial module for 4.18.8-041808-generic ERROR (dkms apport): kernel package linux-headers-4.18.8-041808-generic is not supported Error! Bad return status for module build on kernel: 4.18.8-041808-generic (x86_64) Consult /var/lib/dkms/amdgpu/18.30-641594/build/make.log for more information. [...] [...] WARNING: amdgpu dkms failed for running kernel [...] -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 107266] Radeon Pro Duo (Polaris) - ring sdma0 timeout
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=107266 Bug ID: 107266 Summary: Radeon Pro Duo (Polaris) - ring sdma0 timeout Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu-pro Assignee: dri-devel(a)lists.freedesktop.org Reporter: rhlug(a)hotmail.com Running a polaris Pro Duo on Ubuntu 18.04, Kernel from ROCm branch 4.17.0-rc2-180424-fkxamd and everything works great. In testing latest drm-next-4.19-wip kernel, I get the following errors on boot, and have no working opencl (ie clinfo hangs indefinitely) [ 58.913281] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=573, emitted seq=574 [ 58.913284] [drm] GPU recovery disabled. [ 58.914276] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma1 timeout, signaled seq=331, emitted seq=333 [ 58.914280] [drm] GPU recovery disabled. [ 58.914312] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma1 timeout, signaled seq=331, emitted seq=333 [ 58.914313] [drm] GPU recovery disabled. Please let me know if you need any specifics. -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 106527] OpenCL corrupted memory on AMD R9 280X
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=106527 Bug ID: 106527 Summary: OpenCL corrupted memory on AMD R9 280X Product: DRI Version: XOrg git Hardware: Other OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu-pro Assignee: dri-devel(a)lists.freedesktop.org Reporter: riccardodemaria(a)gmail.com I am trying to use the AMD R9 280X (Tahiti) with the latest Ubuntu 18.04 and AMDGPU-PRO driver. OpenCL appears to work with export GPU_FORCE_64BIT_PTR=1 see https://bugs.freedesktop.org/show_bug.cgi?id=102491 however the memory appears corrupted on the device resulting in random data populating partially or entirely the buffers. A simple OpenCL program is sufficient to show the problem: https://github.com/rdemaria/opencl_simpletest in my case. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 103887] OpenCL segfault on RX550 (Lexa)
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=103887 Bug ID: 103887 Summary: OpenCL segfault on RX550 (Lexa) Product: DRI Version: XOrg git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: DRM/AMDgpu-pro Assignee: dri-devel(a)lists.freedesktop.org Reporter: luka.karinja(a)gmail.com Hello. Support for RX550 (Lexa) seem to be missing for the amdgpu-pro driver i did try amdgpu-pro from 17.10 - 17.40. clinfo shows no devices aviabile and if i force an app to use the opencl lib from amdgpupro the app segfaults... Release notes from the drivers clearly states Lexa supports OpenCL with pro drivers -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 102491] OpenCL app gets CL_OUT_OF_HOST_MEMORY on Cape Verde 7770
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=102491 Bug ID: 102491 Summary: OpenCL app gets CL_OUT_OF_HOST_MEMORY on Cape Verde 7770 Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu-pro Assignee: dri-devel(a)lists.freedesktop.org Reporter: ka.nick(a)mail.ru Created attachment 133896 --> https://bugs.freedesktop.org/attachment.cgi?id=133896&action=edit 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 -- You are receiving this mail because: You are the assignee for the bug.

1 7

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel September 2019