Bug 100448 - [drm] GPU HANG: ecode 6:0:0x00fff8df, in Xwayland [1636], reason: Hang on render ring, action: reset
Summary: [drm] GPU HANG: ecode 6:0:0x00fff8df, in Xwayland [1636], reason: Hang on ren...
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: Other All
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-29 13:53 UTC by mikhail.v.gavrilov
Modified: 2017-04-11 13:17 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments
dmesg (62.32 KB, text/plain)
2017-03-29 13:53 UTC, mikhail.v.gavrilov 		no flags Details
/sys/class/drm/card0/error (19.28 KB, text/plain)
2017-03-29 13:53 UTC, mikhail.v.gavrilov 		no flags Details
View All

Description mikhail.v.gavrilov 2017-03-29 13:53:19 UTC 
Created attachment 130532 [details]
dmesg

Kernel 4.11.0-0.rc2

[  101.841803] [drm] GPU HANG: ecode 6:0:0x00fff8df, in Xwayland [1636], reason: Hang on render ring, action: reset
[  101.841805] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[  101.841805] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[  101.841806] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[  101.841806] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[  101.841807] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[  101.856990] drm/i915: Resetting chip after gpu hang
[  109.838383] drm/i915: Resetting chip after gpu hang
[  117.838499] drm/i915: Resetting chip after gpu hang
[  198.863210] drm/i915: Resetting chip after gpu hang
[  206.863314] drm/i915: Resetting chip after gpu hang
[  206.863359] [drm:i915_reset [i915]] *ERROR* GPU recovery failed
Comment 1 mikhail.v.gavrilov 2017-03-29 13:53:47 UTC 
Created attachment 130533 [details]
/sys/class/drm/card0/error
Comment 2 Chris Wilson 2017-03-29 14:06:52 UTC 
The GPU stopped behaving correctly in that batch. The context looks invalid though, so it should be

commit 5d4bac5503fcc67dd7999571e243cee49371aef7
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Wed Mar 22 20:59:30 2017 +0000

    drm/i915: Restore marking context objects as dirty on pinnin

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.