[Bug 103228] New: GPU hang in compute shader
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Wed Oct 11 17:34:05 UTC 2017
https://bugs.freedesktop.org/show_bug.cgi?id=103228
Bug ID: 103228
Summary: GPU hang in compute shader
Product: DRI
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Intel
Assignee: intel-gfx-bugs at lists.freedesktop.org
Reporter: sgunderson at bigfoot.com
QA Contact: intel-gfx-bugs at lists.freedesktop.org
CC: intel-gfx-bugs at lists.freedesktop.org
Created attachment 134798
--> https://bugs.freedesktop.org/attachment.cgi?id=134798&action=edit
GPU hang log
Hi,
I'm developing a compression system through compute shaders. The first shader
now works fine, but after adding a second shader (even if it's got an empty
main()), I've started getting GPU hangs:
[2557115.719316] [drm] GPU HANG: ecode 7:0:0x8fd8ffff, in narabu-encoder
[11429], reason: Hang on rcs0, action: reset
[2557115.719318] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[2557115.719319] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[2557115.719320] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[2557115.719321] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[2557115.719321] [drm] GPU crash dump saved to /sys/class/drm/card0/error
This is a Haswell laptop (Lenovo X240), Mesa 17.2.2, kernel 4.13.0. Attached is
a gzipped crash dump (error.gz). My current code is available at
https://storage.sesse.net/haswell-gpu-hang.tar.xz
Make narabu-encoder and run it; it hangs the GPU nearly every time for me,
adding 125 ms or so to the measured runtime.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20171011/1b1e1a77/attachment-0001.html>
More information about the intel-gfx-bugs
mailing list