Bug 82601

Summary: GPU HANG: ecode 0:0xf5fffffe, in mpv [4446], reason: Ring hung, action: reset
Product: DRI Reporter: Cyril Hrubis <metan>
Component: DRM/IntelAssignee: Jesse Barnes <jbarnes>
Status: CLOSED DUPLICATE QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: normal    
Priority: medium CC: intel-gfx-bugs
Version: XOrg git   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
GPU crash dump
none
/sys/class/drm/card0/error none

Description Cyril Hrubis 2014-08-14 07:53:00 UTC
Created attachment 104606 [details]
GPU crash dump

While I was playing video in mpv and simultaneously browsing web in chromium my desktop stuck for a few seconds. The content of dmesg told me to report this bug. 

[15961.655448] [drm] stuck on render ring
[15961.656284] [drm] GPU HANG: ecode 0:0xf5fffffe, in mpv [4446], reason: Ring hung, action: reset
[15961.656286] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[15961.656288] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[15961.656289] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[15961.656290] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[15961.656292] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[15963.655165] [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off


I'm using Gentoo with 3.15.3 vanilla kernel, xorg-server 1.15.0, xf86-video-intel 2.21.15 and mpv 0.3.10.
Comment 1 Dmitry Osipenko 2014-09-04 09:27:50 UTC
Created attachment 105729 [details]
/sys/class/drm/card0/error

Seems I have same issue. Gentoo x64 3.16, xorg-server 1.16, xf86-video-intel 2.99.914, mesa 10.2.4. This happens from time to time, mostly while watching youtube (flash with firefox).
Comment 2 Chris Wilson 2014-09-04 09:32:26 UTC

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

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.