Bug 98807 - [drm:i915_hangcheck_elapsed [i915]] *ERROR* Hangcheck timer elapsed... blitter ring idle
Summary: [drm:i915_hangcheck_elapsed [i915]] *ERROR* Hangcheck timer elapsed... blitte...
Status: CLOSED DUPLICATE of bug 54226
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: Other All
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
Depends on:
Reported: 2016-11-21 11:17 UTC by Matwey V. Kornilov
Modified: 2017-07-24 22:39 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

/sys/class/drm/card0/error (2.19 MB, text/plain)
2016-11-21 11:17 UTC, Matwey V. Kornilov
no flags Details
hwinfo output (554.19 KB, text/plain)
2016-11-21 11:19 UTC, Matwey V. Kornilov
no flags Details

Description Matwey V. Kornilov 2016-11-21 11:17:40 UTC
Created attachment 128101 [details]


I am running openSUSE 42.1 with 4.1.27-24-default kernel and Xorg 7.6_1.17.2.

In dmesg I see the following:

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

Attached here is output from /sys/class/drm/card0/error
Comment 1 Matwey V. Kornilov 2016-11-21 11:19:00 UTC
Created attachment 128102 [details]
hwinfo output
Comment 2 Chris Wilson 2016-11-21 12:22:53 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.