Bug 196775 - OpenCL returns CL_OUT_OF_HOST_MEMORY on Cape Verde 7770
Summary: OpenCL returns CL_OUT_OF_HOST_MEMORY on Cape Verde 7770
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - non Intel) (show other bugs)
Hardware: x86-64 Linux
: P1 normal
Assignee: drivers_video-dri
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-08-26 07:38 UTC by Nick
Modified: 2017-08-26 07:54 UTC (History)
0 users

See Also:
Kernel Version: 4.12.0-pf7
Subsystem:
Regression: No
Bisected commit-id:

Attachments
Clinfo output (8.03 KB, text/plain)
2017-08-26 07:38 UTC, Nick 		Details
Kernel config (103.90 KB, text/x-mpsub)
2017-08-26 07:39 UTC, Nick 		Details
Dmesg output (60.32 KB, text/plain)
2017-08-26 07:40 UTC, Nick 		Details
darktable-cltest output (1.43 KB, text/plain)
2017-08-26 07:41 UTC, Nick 		Details
lspci -k output (4.10 KB, text/plain)
2017-08-26 07:43 UTC, Nick 		Details
Add an attachment (proposed patch, testcase, etc.)

Description Nick 2017-08-26 07:38:34 UTC 
Created attachment 258115 [details]
Clinfo output

Trying to couple mainline amdgpu driver with opencl from amdgpu-pro (installed via Gentoo dev-libs/amdgpu-pro-opencl package). Clinfo and apps see the opencl but when trying to create a command queue driver returns CL_OUT_OF_HOST_MEMORY. (My previous attempts end up with clinfo crash, so it is an obvious progress). The same behavior is reported on Ubuntu 16.04.3 as you may see here https://redmine.darktable.org/issues/11702

kernel 4.12.0-pf7 (4.11 ->)
xorg-server-1.19.3
libdrm-2.4.82
x11-drivers/xf86-video-amdgpu-1.3.0
dev-libs/amdgpu-pro-opencl-17.30.465504
Comment 1 Nick 2017-08-26 07:39:44 UTC 
Created attachment 258119 [details]
Kernel config
Comment 2 Nick 2017-08-26 07:40:28 UTC 
Created attachment 258121 [details]
Dmesg output
Comment 3 Nick 2017-08-26 07:41:22 UTC 
Created attachment 258123 [details]
darktable-cltest output
Comment 4 Nick 2017-08-26 07:43:08 UTC 
Created attachment 258125 [details]
lspci -k output
Note You need to log in before you can comment on or make changes to this bug.