[Bug 97545] [HSW] DRM/i915 GPU hang after resume
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Sat May 6 21:23:23 UTC 2017
https://bugs.freedesktop.org/show_bug.cgi?id=97545
Burak Sezer <bburaksezer at gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|INVALID |---
Status|RESOLVED |REOPENED
--- Comment #9 from Burak Sezer <bburaksezer at gmail.com> ---
Hello,
I have the same problem. Here are some info about my environment:
Kernel: Linux turing 4.4.0-75-generic #96-Ubuntu SMP on Ubuntu 16.04.2 LTS
Mesa: client glx vendor string: Mesa Project and SGI
Device: Mesa DRI Intel(R) Haswell Desktop (0x412)
OpenGL renderer string: Mesa DRI Intel(R) Haswell Desktop
OpenGL core profile version string: 3.3 (Core Profile) Mesa 12.0.6
OpenGL version string: 3.0 Mesa 12.0.6
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 12.0.6
I was surfing on the Internet at the time of the hang with Google Chrome
58.0.3029.96 (64-bit)
How I can provide valuable information to resolve that problem?
Error messages from the driver:
[45609.749114] [drm] stuck on render ring
[45609.749785] [drm] GPU HANG: ecode 7:0:0x84dfbffe, in chrome [24099], reason:
Ring hung, action: reset
[45609.749785] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[45609.749786] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[45609.749786] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[45609.749787] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[45609.749787] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[45609.751891] drm/i915: Resetting chip after gpu hang
--
You are receiving this mail because:
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-3d-bugs/attachments/20170506/65c5a94c/attachment.html>
More information about the intel-3d-bugs
mailing list