From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 93374] [radeonsi] Tonga (Radeon R9 380) hangs on running hello world OpenCL program
Date: Sun, 03 Jan 2016 00:10:30 +0000 [thread overview]
Message-ID: <bug-93374-502-aLzfLQ706x@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-93374-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 980 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=93374
EoD <EoD@xmw.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |EoD@xmw.de
--- Comment #3 from EoD <EoD@xmw.de> ---
Is it possible to work around the lock?
I ran into the same issue, when I tried running clpeak (
https://github.com/krrishnarraj/clpeak ) on kernel 4.4.0-rc7 with current
mesa-git and an R9 380X.
kernel: amdgpu 0000:01:00.0: IH ring buffer overflow (0x000C01D0, 0x00000B40,
0x000001E0)
kernel: amdgpu 0000:01:00.0: GPU fault detected: 147 0x05f88802
kernel: amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x0004009C
kernel: amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0A088002
kernel: VM fault (0x02, vmid 5) at page 262300, read from 'TC9' (0x54433900)
(136)
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2376 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 prev parent reply other threads:[~2016-01-03 0:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-14 18:36 [Bug 93374] [radeonsi] Tonga (Radeon R9 380) hangs on running hello world OpenCL program bugzilla-daemon
2015-12-15 7:21 ` bugzilla-daemon
2015-12-15 7:46 ` bugzilla-daemon
2016-01-03 0:10 ` bugzilla-daemon [this message]
2016-01-04 10:41 ` bugzilla-daemon
2016-01-06 0:43 ` 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-93374-502-aLzfLQ706x@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