Bug 97304 - repeated [drm:ring_stuck] *ERROR* Kicking stuck semaphore on render ring
Summary: repeated [drm:ring_stuck] *ERROR* Kicking stuck semaphore on render ring
Status: CLOSED DUPLICATE of bug 54226
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-08-11 17:40 UTC by SA
Modified: 2017-07-24 22:40 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
GPU crash dump from /sys/class/drm/card0/error (2.19 MB, text/plain)
2016-08-11 17:40 UTC, SA
no flags Details

Description SA 2016-08-11 17:40:09 UTC
Created attachment 125712 [details]
GPU crash dump from /sys/class/drm/card0/error

During using the Google Chrome on Ubuntu 14.04/64 I often experience this error:

Aug 12 03:28:56 * kernel: [105286.318002] [drm:ring_stuck] *ERROR* Kicking stuck semaphore on render ring
Aug 12 03:28:56 * kernel: [105286.318007] [drm] GPU crash dump saved to /sys/class/drm/card0/error
Aug 12 03:28:56 * kernel: [105286.318008] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
Aug 12 03:28:56 * kernel: [105286.318009] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
Aug 12 03:28:56 * kernel: [105286.318010] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
Aug 12 03:28:56 * kernel: [105286.318010] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.

Doing as suggested: filing new bug.

Mostly this appears after heavy Adobe/Pepper flash usage, but not always.
Comment 1 Chris Wilson 2016-08-11 17:51:22 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.