Bug 93817 - Skylake Intel HD Graphics 520 GPU HANG: ecode 9:0:0x87cafff2, in chrome [3189], reason: Ring hung, action: reset
Summary: Skylake Intel HD Graphics 520 GPU HANG: ecode 9:0:0x87cafff2, in chrome [318...
Status: RESOLVED INVALID
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: Intel 3D Bugs Mailing List
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-21 23:15 UTC by Sam Pfeiffer
Modified: 2017-02-10 22:38 UTC (History)
2 users (show)

See Also:
i915 platform: SKL
i915 features: GPU hang


Attachments
GPU crash dump saved to /sys/class/drm/card0/error (2.81 MB, text/plain)
2016-01-21 23:15 UTC, Sam Pfeiffer
Details

Description Sam Pfeiffer 2016-01-21 23:15:06 UTC
Created attachment 121198 [details]
GPU crash dump saved to /sys/class/drm/card0/error

GPU hangs when using chrome, usually when opening new tab.

Dmesg said:

[ 2056.404562] [drm] stuck on render ring
[ 2056.407972] [drm] GPU HANG: ecode 9:0:0x87cafff2, in chrome [3189], reason: Ring hung, action: reset
[ 2056.407974] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 2056.407976] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 2056.407977] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 2056.407978] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 2056.407979] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 2056.410627] drm/i915: Resetting chip after gpu hang
[ 2058.392267] [drm] RC6 on


So here I'm attaching the crash dump.

Full dmesg since boot can be found here: http://pastebin.com/Km6MMYEG
Comment 1 yann 2016-09-14 16:28:19 UTC
Sam, there were workaround for SKL and improvements pushed in kernel and Mesa that will benefit to your system, so please re-test with latest kernel & Mesa to see if this issue is still occurring.

In the meantime, assigning to Mesa product.

From this error dump, hung is happening in render ring batch with active head at 0x2b85163c, with 0x78150009 (3D UNKNOWN: 3d_965 opcode = 0x7815) as IPEHR.

Batch extract (around 0x2b85163c):

0x2b851618:      0x00000000: MI_NOOP
Bad length 7 in (null), expected 6-6
0x2b85161c:      0x7b000005: 3DPRIMITIVE: fail sequential
0x2b851620:      0x00000104:    vertex count
0x2b851624:      0x00000006:    start vertex
0x2b851628:      0x00000000:    instance count
0x2b85162c:      0x00000001:    start instance
0x2b851630:      0x00000000:    index bias
0x2b851634:      0x00000000: MI_NOOP
0x2b851638:      0x78150009: 3D UNKNOWN: 3d_965 opcode = 0x7815
0x2b85163c:      0x00000003: MI_NOOP
Comment 2 Matt Turner 2016-11-04 00:17:23 UTC
We don't have enough information.

- What kernel version are you using? (uname -a)
- What Mesa version are you using? (glxinfo | grep Mesa)

Please test a new version of Mesa (12 or 13) and mark as REOPENED
if you can reproduce and RESOLVED/* if you cannot reproduce.
Comment 3 Annie 2017-02-10 22:38:27 UTC
Dear Reporter,

This Mesa bug has been in the "NEEDINFO" status for over 60 days. I am closing this bug based on lack of response but feel free to reopen if resolution is still needed. Please ensure you're supplying the correct information as requested.

Thank you.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.