From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 94012] Tonga OpenCL clpeak vm faults
Date: Fri, 05 Feb 2016 18:29:44 +0000 [thread overview]
Message-ID: <bug-94012-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1329 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=94012
Bug ID: 94012
Summary: Tonga OpenCL clpeak vm faults
Product: DRI
Version: DRI git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: adf.lists@gmail.com
Created attachment 121540
--> https://bugs.freedesktop.org/attachment.cgi?id=121540&action=edit
vm debug
R9285 llvm,mesa,libclc yesterdays gits.
No ideea if this is a regression as I've only just noticed tonga got added to
libclc so this is first time testing OpenCL.
clpeak - https://github.com/krrishnarraj/clpeak.git
produces vmfaults. It will run to completion.
R600_DEBUG=check_vm ./clpeak
Platform: Clover
Device: AMD TONGA (DRM 3.1.0, LLVM 3.9.0)
Driver version : 11.2.0-devel (Linux x64)
Compute units : 28
Clock frequency : 0 MHz
Global memory bandwidth (GBPS)
float : 1.45
float2 : 1.44
float4 : 1.45
float8 : 1.45
float16 : Detected a VM fault, exiting...
Attaching output and vm debug file from
R600_DEBUG=check_vm,cs ./clpeak &>~/clpeak-cs
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2711 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2016-02-05 18:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-05 18:29 bugzilla-daemon [this message]
2016-02-05 18:30 ` [Bug 94012] Tonga OpenCL clpeak vm faults bugzilla-daemon
2016-03-31 15:14 ` 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-94012-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).