Bug 84716

Summary: GPU HANG: ecode 0:0xf5f7fffe, in X [1053], reason: Ring hung, action: reset
Product: DRI Reporter: Dr. David Alan Gilbert <dgilbert>
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: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
copy of /sys/class/drm/card0/error none

Description Dr. David Alan Gilbert 2014-10-06 13:16:34 UTC
Created attachment 107425 [details]
copy of /sys/class/drm/card0/error

Lenovo T530 / Fedora 21 / KDE desktop / Firefox running; hung happened as switching virtual desktops

Linux dgilbert-t530 3.16.3-200.fc20.x86_64 #1 SMP Wed Sep 17 22:34:21 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

RPMs:
xorg-x11-drv-intel-2.21.15-7.fc20.x86_64
xorg-x11-drv-modesetting-0.8.0-2.fc20.x86_64
xorg-x11-server-common-1.14.4-11.fc20.x86_64
xorg-x11-drv-fbdev-0.4.3-10.fc20.x86_64
xorg-x11-glamor-0.5.1-3.20140115gitfb4d046c.fc20.x86_64
xorg-x11-server-Xorg-1.14.4-11.fc20.x86_64

[19244.184541] [drm] stuck on render ring
[19244.187843] [drm] GPU HANG: ecode 0:0xf5f7fffe, in X [1053], reason: Ring hung, action: reset
[19244.187848] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[19244.187849] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[19244.187851] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[19244.187853] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[19244.187854] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[19246.185097] [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off


See attached err file.
Comment 1 Chris Wilson 2014-10-06 13:24:27 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.