[Bug 104211] New: GPU HANG
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Mon Dec 11 11:53:27 UTC 2017
https://bugs.freedesktop.org/show_bug.cgi?id=104211
Bug ID: 104211
Summary: GPU HANG
Product: DRI
Version: XOrg git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Intel
Assignee: intel-gfx-bugs at lists.freedesktop.org
Reporter: qq at kuku.eu.org
QA Contact: intel-gfx-bugs at lists.freedesktop.org
CC: intel-gfx-bugs at lists.freedesktop.org
Created attachment 136079
--> https://bugs.freedesktop.org/attachment.cgi?id=136079&action=edit
data from /sys/class/drm/card0/error
I was testing a qt-based app. The UI froze for several seconds, then resumed
without an issue. In dmesg, I've found the following:
[958940.926878] [drm] stuck on render ring
[958940.927417] [drm] GPU HANG: ecode 7:0:0x87dd7d10, in app [17354], reason:
Ring hung, action: reset
[958940.927418] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[958940.927419] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[958940.927419] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[958940.927420] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[958940.927420] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[958940.965440] drm/i915: Resetting chip after gpu hang
Distribution: Ubuntu 16.04.3 LTS
Kernel: 4.4.0-101-generic #124-Ubuntu SMP x86_64
X.Org X Server 1.18.4
Some version information from glxinfo:
Vendor: Intel Open Source Technology Center (0x8086)
Device: Mesa DRI Intel(R) Haswell Desktop (0x412)
Version: 17.0.7
GPU: Integrated into CPU, Intel(R) Core(TM) i3-4330 CPU
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20171211/16951e1e/attachment.html>
More information about the intel-gfx-bugs
mailing list