Bug 99046

Summary: [BDW] GPU HANG: ecode 8:2:0xc9835ff6, in Xorg [697], reason: Ring hung, action: reset
Product: DRI Reporter: j1102681
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: CLOSED DUPLICATE QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: normal    
Priority: medium CC: intel-gfx-bugs
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: BDW i915 features: GPU hang
Attachments:
Description Flags
Dump of the GPU hang none

Description j1102681 2016-12-10 12:23:29 UTC
Created attachment 128404 [details]
Dump of the GPU hang

When I woke up my laptop from suspension rarely I get a gpu hang.
Just to give an approximative idea about the frequency, maybe this happen once every fifty suspensions.

The dmesg says:
[28377.998735] [drm] stuck on blitter ring
[28377.999292] [drm] GPU HANG: ecode 8:2:0xc9835ff6, in Xorg [697], reason: Ring hung, action: reset
[28377.999294] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[28377.999295] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[28377.999296] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[28377.999297] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[28377.999298] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[28378.707379] [drm:gen8_do_reset [i915]] *ERROR* blitter ring: reset request timeout
[28378.707389] drm/i915: Resetting chip after gpu hang
[28378.707405] [drm:i915_reset [i915]] *ERROR* Failed to reset chip: -5
[28383.775909] [drm:intel_lr_context_deferred_alloc [i915]] *ERROR* ring create req: -5
[28384.275334] [drm:intel_lr_context_deferred_alloc [i915]] *ERROR* ring create req: -5
[28384.772331] [drm:intel_lr_context_deferred_alloc [i915]] *ERROR* ring create req: -5
[28385.267864] [drm:intel_lr_context_deferred_alloc [i915]] *ERROR* ring create req: -5
[28385.785094] [drm:intel_lr_context_deferred_alloc [i915]] *ERROR* ring create req: -5
[28609.499571] [drm:intel_lr_context_deferred_alloc [i915]] *ERROR* ring create req: -5
[28610.057585] [drm:intel_lr_context_deferred_alloc [i915]] *ERROR* ring create req: -5
[28610.608001] [drm:intel_lr_context_deferred_alloc [i915]] *ERROR* ring create req: -5
[28611.143264] [drm:intel_lr_context_deferred_alloc [i915]] *ERROR* ring create req: -5
[28611.703511] [drm:intel_lr_context_deferred_alloc [i915]] *ERROR* ring create req: -5
[28612.242389] [drm:intel_lr_context_deferred_alloc [i915]] *ERROR* ring create req: -5

I have a laptop with an Intel HD Graphics 5500 and the kernel 4.4.19-1
Comment 1 yann 2016-12-12 10:22:12 UTC
Please test with latest version of kernel and Mesa (12 or 13) and mark as REOPENED if you can reproduce and RESOLVED/* if you cannot reproduce.

Moreover, can you attach xorg log and confirm your content from /etc/X11/xorg.conf.d/20-modesetting.conf ?

You may try either:
- update your version of xf86-video-intel (https://cgit.freedesktop.org/xorg/driver/xf86-video-intel/)
- use glamor to see if this resolve your issue: in /etc/X11/xorg.conf.d/20-modesetting.conf, set the following

Section "Device"
    Identifier  "Intel Graphics"
    Driver      "modesetting"
    Option      "AccelMethod"    "glamor"
    Option      "DRI"            "3"
    Option      "Backlight"      "intel_backlight"
EndSection
Comment 2 Chris Wilson 2016-12-12 10:33:18 UTC
(Note this error state is a kernel bug.)
Comment 3 j1102681 2016-12-15 17:38:05 UTC
I can't update my kernel due to another bug (not related to the graphic drivers) and I can't reporduce the problem because it happens rarely. I'll try your suggestions, thank you.
Comment 4 Chris Wilson 2017-02-05 17:36:36 UTC
Note that this is not a strict dup of bug 99632, but it happens to be an early bug in the long line of hibernate bugs.

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

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.