Bug 85333 - Occasional GPU HANG
Summary: Occasional GPU HANG
Status: CLOSED DUPLICATE of bug 54226
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: 2014-10-22 15:40 UTC by Michał Mirosław
Modified: 2017-07-24 22:50 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
Contents of /sys/class/drm/card0/error (2.19 MB, text/plain)
2014-10-22 15:40 UTC, Michał Mirosław
no flags Details

Description Michał Mirosław 2014-10-22 15:40:07 UTC
Created attachment 108238 [details]
Contents of /sys/class/drm/card0/error

Kernel occasionally reports GPU HANG. I noticed no user-visible effects correlated to this message. This is GPU integrated on Sandy Bridge Core i7-2600K.

Kernel log:

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

xdpyinfo excerpt:

vendor string:    The X.Org Foundation
vendor release number:    11601000
X.Org version: 1.16.1

OS: Debian jessie.

I can provide more info when you need it.
Comment 1 Michał Mirosław 2014-10-22 15:42:09 UTC
This is on vanilla kernel 3.17.1.
Comment 2 Chris Wilson 2014-10-22 16:57:55 UTC

*** 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.