Bug 99259 - [SKL] GPU HANG: ecode 9:0:0x84dffff8, in X [941], reason: Hang on render ring, action: reset
Summary: [SKL] GPU HANG: ecode 9:0:0x84dffff8, in X [941], reason: Hang on render ring...
Status: CLOSED DUPLICATE of bug 99070
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
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-01-03 14:48 UTC by Vladimír Čunát
Modified: 2017-07-24 22:39 UTC (History)
1 user (show)

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


Attachments
/sys/class/drm/card0/error (8.86 KB, application/x-xz)
2017-01-03 14:48 UTC, Vladimír Čunát
no flags Details

Description Vladimír Čunát 2017-01-03 14:48:15 UTC
Created attachment 128727 [details]
/sys/class/drm/card0/error

It might be the same as #99070, but the message wanted a _new_ report.

Jan 03 15:35:25 nics kernel: [drm] GPU HANG: ecode 9:0:0x84dffff8, in X [941], reason: Hang on render ring, action: reset
Jan 03 15:35:25 nics kernel: [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
Jan 03 15:35:25 nics kernel: [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
Jan 03 15:35:25 nics kernel: [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
Jan 03 15:35:25 nics kernel: [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
Jan 03 15:35:25 nics kernel: [drm] GPU crash dump saved to /sys/class/drm/card0/error
Jan 03 15:35:25 nics kernel: drm/i915: Resetting chip after gpu hang
Jan 03 15:35:25 nics kernel: [drm] GuC firmware load skipped
Jan 03 15:35:27 nics kernel: [drm] RC6 on
Comment 1 yann 2017-01-04 15:07:05 UTC
Based on gpu error dump, I confirm this is a dup of bug 99070

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


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.