Bug 90329

Summary: kernel: [drm] GPU HANG: ecode 8:0:0xfffffffe, in chromium [26167], reason: Ring hung, action: reset
Product: DRI Reporter: sadieperkins
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: CLOSED FIXED QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: normal    
Priority: medium CC: intel-gfx-bugs
Version: XOrg git   
Hardware: x86-64 (AMD64)   
OS: All   
Whiteboard:
i915 platform: BDW i915 features: GPU hang, power/suspend-resume
Attachments:
Description Flags
/sys/class/drm/card0/error none

Description sadieperkins 2015-05-05 22:29:28 UTC
Created attachment 115568 [details]
/sys/class/drm/card0/error

3 seconds after resume from suspend, chromium's "/usr/lib/chromium/chromium --type=gpu-process" process was using 100% cpu and had to be killed:



kernel: [drm] stuck on render ring
kernel: [drm] GPU HANG: ecode 8:0:0xfffffffe, in chromium [26167], reason: Ring hung, action: reset
kernel: [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
kernel: [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
kernel: [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
kernel: [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
kernel: [drm] GPU crash dump saved to /sys/class/drm/card0/error
kernel: drm/i915: Resetting chip after gpu hang
Comment 1 Mika Kuoppala 2015-05-11 07:37:18 UTC
Is it possible to try with this patch?
http://article.gmane.org/gmane.comp.freedesktop.xorg.drivers.intel/59225
Comment 2 Ileana 2016-04-19 11:08:34 UTC
Any updates? Is Mika's patch fixing the issue?
Comment 3 yann 2016-09-28 13:25:00 UTC
 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.