Bug 100888 - GPU HANG: ecode 9:0:0x84dffff8, in Xorg [1134], reason: Engine(s) hung, action: reset
Summary: GPU HANG: ecode 9:0:0x84dffff8, in Xorg [1134], reason: Engine(s) hung, actio...
Status: CLOSED DUPLICATE of bug 98999
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other Linux (All)
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-04-30 09:39 UTC by Konrad W.
Modified: 2017-07-27 16:41 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
GPU hang ecode 9:0:0x84dffff8 (442.37 KB, text/plain)
2017-04-30 09:39 UTC, Konrad W.
no flags Details

Description Konrad W. 2017-04-30 09:39:30 UTC
Created attachment 131159 [details]
GPU hang ecode 9:0:0x84dffff8

dmesg:

[10576.039149] [drm] stuck on render ring
[10576.039457] [drm] GPU HANG: ecode 9:0:0x84dffff8, in Xorg [1134], reason: Engine(s) hung, action: reset
[10576.039460] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[10576.039463] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[10576.039466] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[10576.039468] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[10576.039470] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[10576.041273] drm/i915: Resetting chip after gpu hang
[10578.039620] [drm] RC6 on

The /sys/class/drm/card0/error is in attachment.
Comment 1 Chris Wilson 2017-05-02 09:48:37 UTC
commit 4acd4a7d3d2f41227022fa7581cfb85a0b124eae
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Mon Dec 5 15:13:24 2016 +0000

    sna/gen9: Emit a dummy primitive between VertexElements

*** This bug has been marked as a duplicate of bug 98999 ***


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.