Bug 93858 - [SKL] GPU HANG: ecode 9:0:0x85dfffff, reason: Ring hung, action: reset
Summary: [SKL] GPU HANG: ecode 9:0:0x85dfffff, reason: Ring hung, action: reset
Status: CLOSED FIXED
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: 2016-01-25 16:57 UTC by prochazka.nicolas
Modified: 2016-10-21 14:00 UTC (History)
3 users (show)

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


Attachments
error dump (78.02 KB, text/plain)
2016-01-25 16:57 UTC, prochazka.nicolas
no flags Details

Description prochazka.nicolas 2016-01-25 16:57:20 UTC
Created attachment 121272 [details]
error dump

[   55.022612] [drm] stuck on render ring
[   55.022790] [drm] GPU HANG: ecode 9:0:0x85dfffff, in qemu-system-x86 [7355], reason: Ring hung, action: reset
[   55.022792] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[   55.022793] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[   55.022794] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[   55.022795] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[   55.022796] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[   55.024452] drm/i915: Resetting chip after gpu hang
[   57.022762] [drm] RC6 on
[   79.023125] [drm] stuck on render ring
[   79.023307] [drm] GPU HANG: ecode 9:0:0x85dfffff, in qemu-system-x86 [7355], reason: Ring hung, action: reset
[   79.025076] drm/i915: Resetting chip after gpu hang
[   81.023324] [drm] RC6 on
[  349.027874] [drm] stuck on render ring
[  349.028051] [drm] GPU HANG: ecode 9:0:0x85dffffb, in qemu-system-x86 [7355], reason: Ring hung, action: reset
[  349.030364] drm/i915: Resetting chip after gpu hang
[  351.028182] [drm] RC6 on
Comment 1 raumkundschafter 2016-01-27 12:51:58 UTC
dmesg output:
[10053.445195] [drm] stuck on blitter ring
[10053.445870] [drm] GPU HANG: ecode 8:2:0xd8c75ff6, in Xorg [1016], reason: Ring hung, action: reset
[10053.445872] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[10053.445874] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[10053.445875] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[10053.445877] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[10053.445879] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[10054.147350] [drm:gen8_do_reset [i915]] *ERROR* blitter ring: reset request timeout
[10054.147355] drm/i915: Resetting chip after gpu hang
[10054.147365] [drm:i915_reset [i915]] *ERROR* Failed to reset chip: -5
[10058.949972] [drm:intel_lr_context_deferred_alloc [i915]] *ERROR* ring create req: -5
Comment 2 raumkundschafter 2016-01-27 12:55:30 UTC
missed to attach /sys/class/drm/card0/error as it's been renewed already after resume
Comment 3 raumkundschafter 2016-01-27 13:00:20 UTC
furthermore found this line in dmesg: 
[drm:i915_drm_resume [i915]] *ERROR* failed to re-initialize GPU, declaring wedged!
Comment 4 prochazka.nicolas 2016-01-27 13:08:51 UTC
eroor.dump is a gzip archive, sorry.
Comment 5 raumkundschafter 2016-01-27 13:14:52 UTC
there's no error dump in /sys/class/drm/card0 I'm afraid, only:
-rw------- 1 root root    0 Jan 27 12:48 error
Comment 6 yann 2016-09-13 15:29:13 UTC
There were workarounds for SKL available on latest kernel that may fix your issue. Please update your system and confirm if that issue is still occurring or not.
Comment 7 yann 2016-09-13 15:30:07 UTC
(In reply to yann from comment #6)
> There were workarounds for SKL available on latest kernel that may fix your
> issue. Please update your system and confirm if that issue is still
> occurring or not.

You may also update your version of Mesa as well
Comment 8 yann 2016-10-21 13:59:56 UTC
(In reply to yann from comment #7)
> (In reply to yann from comment #6)
> > There were workarounds for SKL available on latest kernel that may fix your
> > issue. Please update your system and confirm if that issue is still
> > occurring or not.
> 
> You may also update your version of Mesa as well

Timeout. Assuming that it is fixed by now. If this is not the case, please re-test with latest kernel & Mesa to see if this issue is still occurring since there were improvements pushed in kernel and Mesa that will benefit to your system.


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.