From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 196775] New: OpenCL returns CL_OUT_OF_HOST_MEMORY on Cape Verde 7770
Date: Sat, 26 Aug 2017 07:38:34 +0000 [thread overview]
Message-ID: <bug-196775-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=196775
Bug ID: 196775
Summary: OpenCL returns CL_OUT_OF_HOST_MEMORY on Cape Verde
7770
Product: Drivers
Version: 2.5
Kernel Version: 4.12.0-pf7
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: ka.nick@mail.ru
Regression: No
Created attachment 258115
--> https://bugzilla.kernel.org/attachment.cgi?id=258115&action=edit
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
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2017-08-26 7:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-26 7:38 bugzilla-daemon [this message]
2017-08-26 7:39 ` [Bug 196775] OpenCL returns CL_OUT_OF_HOST_MEMORY on Cape Verde 7770 bugzilla-daemon
2017-08-26 7:40 ` bugzilla-daemon
2017-08-26 7:41 ` bugzilla-daemon
2017-08-26 7:43 ` bugzilla-daemon
2017-08-26 7:54 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-196775-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.