Bug 96901 - GPU HANG: ecode 6:-1:0x00000000, reason: Kicking stuck semaphore on render ring, action: continue
Summary: GPU HANG: ecode 6:-1:0x00000000, reason: Kicking stuck semaphore on render ri...
Status: CLOSED DUPLICATE of bug 52226
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-07-12 15:40 UTC by Tomasz Melcer
Modified: 2017-07-24 22:41 UTC (History)
1 user (show)

See Also:
i915 platform: SNB
i915 features: GPU hang

Attachments
sudo cat /sys/class/drm/card0/error | xz (49.81 KB, application/x-xz)
2016-07-12 15:40 UTC, Tomasz Melcer 		no flags Details
View All

Description Tomasz Melcer 2016-07-12 15:40:54 UTC 
Created attachment 125030 [details]
sudo cat /sys/class/drm/card0/error | xz

[47139.652943] [drm] GPU HANG: ecode 6:-1:0x00000000, reason: Kicking stuck semaphore on render ring, action: continue
[47139.652946] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[47139.652946] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[47139.652947] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[47139.652948] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[47139.652948] [drm] GPU crash dump saved to /sys/class/drm/card0/error

liori@liori-pc:~$ uname -a
Linux liori-pc 4.6.0-0.bpo.1-amd64 #1 SMP Debian 4.6.1-1~bpo8+1 (2016-06-14) x86_64 GNU/Linux

Distribution: Debian Jessie with enabled official backports.

Motherboard: Gigabyte Z68X-UD3H-B3

Screens: one 1920x1080 screen on HDMI.
Comment 1 Chris Wilson 2016-07-15 20:06:57 UTC 

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

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.