Bug 92244 - GPU HANG: ecode 8:0:0xef9ffffd, in chromium [1721], reason: Ring hung, action: reset
Summary: GPU HANG: ecode 8:0:0xef9ffffd, in chromium [1721], reason: Ring hung, action...
Status: CLOSED WONTFIX
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
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: 2015-10-02 13:59 UTC by Nils Schneider
Modified: 2017-07-04 01:55 UTC (History)
2 users (show)

See Also:
i915 platform: BDW
i915 features: GEM/execlists


Attachments
GPU crash dump from /sys/class/drm/card0/error (385.69 KB, text/plain)
2015-10-02 13:59 UTC, Nils Schneider
no flags Details

Description Nils Schneider 2015-10-02 13:59:37 UTC
Created attachment 118607 [details]
GPU crash dump from /sys/class/drm/card0/error

My system hung when using chromium and I got this in dmesg. I hope this helps!

[15203.320448] [drm] stuck on render ring
[15203.322114] [drm] GPU HANG: ecode 8:0:0xef9ffffd, in chromium [1721], reason: Ring hung, action: reset
[15203.322118] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[15203.322120] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[15203.322122] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[15203.322124] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[15203.322127] [drm] GPU crash dump saved to /sys/class/drm/card0/error
Comment 1 Chris Wilson 2015-10-02 14:12:13 UTC
execlists failed to advance onto the next context.
Comment 2 yann 2017-02-24 08:17:56 UTC
We seem to have neglected the bug a bit, apologies.

Nils Schneider, since There were improvements pushed in kernel, xf86-video-intel & mesa that will benefit to your system, so please re-test with latest kernel, xf86-video-intel & mesa and mark as REOPENED if you can reproduce (and attach fresh gpu error dump & kernel log) and RESOLVED/* if you cannot reproduce.
Comment 3 nils 2017-02-24 08:43:17 UTC
Thanks for getting back at this. Unfortunately, I'm not using the hardware I was using in 2015 anymore so I can't check this.
Comment 4 yann 2017-02-24 08:55:08 UTC
(In reply to nils from comment #3)
> Thanks for getting back at this. Unfortunately, I'm not using the hardware I
> was using in 2015 anymore so I can't check this.

Understood. Thanks Nils for your feedback. Therefore I am closing it.
If it occurs on your new hardware, please open a new ticket with proper logs (kernel & gpu error dump)


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.