Bug 93876

Summary: [drm] GPU HANG: ecode 6:-1:0x00000000, reason: Kicking stuck semaphore on render ring, action: continue
Product: DRI Reporter: samuel.rakitnican
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: XOrg git   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
/sys/class/drm/card0/error none

Description samuel.rakitnican 2016-01-26 17:09:01 UTC
Created attachment 121306 [details]
/sys/class/drm/card0/error

[Sij26 01:40] [drm] GPU HANG: ecode 6:-1:0x00000000, reason: Kicking stuck semap
hore on render ring, action: continue
[  +0,000004] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stac
k, including userspace.
[  +0,000001] [drm] Please file a _new_ bug report on bugs.freedesktop.org again
st DRI -> DRM/Intel
[  +0,000000] [drm] drm/i915 developers can then reassign to the right component
 if it's not a kernel issue.
[  +0,000001] [drm] The gpu crash dump is required to analyze gpu hangs, so plea
se always attach it.
[  +0,000001] [drm] GPU crash dump saved to /sys/class/drm/card0/error


$ uname -r
4.3.3-301.fc23.x86_64


Seems to get better with every kernel update and got to the point that dmesg is not filled with messages for couple of days by running with a new kernel.
Comment 1 Chris Wilson 2016-01-26 20:45:40 UTC
The biggest recent change would be read-read not requiring the semaphore. Other than that there still haven't been any major breakthroughs on how to make snb behave.

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

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.