Bug 100852 - GPU Hang
Summary: GPU Hang
Status: CLOSED DUPLICATE of bug 98999
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: x86-64 (AMD64) 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-27 13:29 UTC by vasileios.revelas
Modified: 2017-07-27 16:40 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
Output of /sys/class/drm/card0/error (22.56 KB, application/x-bzip)
2017-04-27 13:29 UTC, vasileios.revelas
no flags Details

Description vasileios.revelas 2017-04-27 13:29:20 UTC
Created attachment 131097 [details]
Output of /sys/class/drm/card0/error

I'm running Ubuntu 16.04.2 (Linux 4.4.0-72-generic)
Received the following in my dmesg:

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

I've attached the contents of /sys/class/drm/card0/error. I'd be happy to supply any additional information.
Comment 1 Chris Wilson 2017-04-27 13:38:36 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.