Bug 97373

Summary: [drm:i915_hangcheck_elapsed [i915]] *ERROR* Hangcheck timer elapsed... render ring idle
Product: DRI Reporter: mikhail.v.gavrilov
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: CLOSED FIXED QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: normal    
Priority: medium CC: intel-gfx-bugs
Version: XOrg git   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: HSW i915 features: GPU hang
Attachments:
Description Flags
dmesg
none
GPU crash dump
none
dmesg
none
GPU crash dump none

Description mikhail.v.gavrilov 2016-08-17 06:17:49 UTC
Created attachment 125834 [details]
dmesg

[ 1255.413579] [drm:i915_hangcheck_elapsed [i915]] *ERROR* Hangcheck timer elapsed... render ring idle
[ 1315.411666] [drm] no progress on render ring
[ 1315.412144] [drm] GPU HANG: ecode 7:-1:0x00000000, reason: Ring hung, action: reset
[ 1315.412247] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 1315.412248] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 1315.412249] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 1315.412250] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 1315.412251] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 1315.417835] [drm:i915_switch_context [i915]] *ERROR* ring init context: -11
[ 1315.420875] drm/i915: Resetting chip after gpu hang
[ 1323.403422] [drm] stuck on render ring
[ 1323.404058] [drm] GPU HANG: ecode 7:0:0xf3cffffe, in chrome [2337], reason: Ring hung, action: reset
[ 1323.406989] drm/i915: Resetting chip after gpu hang
Comment 1 mikhail.v.gavrilov 2016-08-17 06:18:31 UTC
Created attachment 125835 [details]
GPU crash dump
Comment 2 mikhail.v.gavrilov 2016-08-25 19:12:25 UTC
Created attachment 126034 [details]
dmesg
Comment 3 mikhail.v.gavrilov 2016-08-25 19:22:08 UTC
Created attachment 126036 [details]
GPU crash dump
Comment 4 Jari Tahvanainen 2017-03-29 07:22:30 UTC
We seem to have neglected the bug quite a bit, apologies.

Mikhail, since there has been quite a lot improvements pushed in kernel that will benefit to your system, please re-test with latest kernel and mark as REOPENED if you can reproduce (and attach kernel log and card0/error info, like you did earlier) and RESOLVED/* if you cannot reproduce.
Comment 5 Chris Wilson 2017-04-08 19:19:17 UTC
Context restore failed, and the erroneous context is not included. So presuming this is one the request reordering bugs that leads to invalid contexts...

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.