Bug 88612 - many GPU hangs in kwin ecode 0:0x87d3bffa
Summary: many GPU hangs in kwin ecode 0:0x87d3bffa
Status: CLOSED DUPLICATE of bug 83677
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: 2015-01-20 06:21 UTC by Popescu Sorin
Modified: 2017-07-24 22:49 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments
cat of /sys/class/drm/card0/error (349.31 KB, text/plain)
2015-01-20 06:31 UTC, Popescu Sorin
no flags Details

Description Popescu Sorin 2015-01-20 06:21:47 UTC
[ 7360.047990] [drm] stuck on render ring
[ 7360.049784] [drm] GPU HANG: ecode 0:0x87d3bffa, in kwin [1859], reason: Ring hung, action: reset
[ 7360.049796] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 7360.049801] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 7360.049805] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 7360.049809] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 7360.049813] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[15132.231019] [drm] stuck on render ring
[15132.232856] [drm] GPU HANG: ecode 0:0x87d3bffa, in kwin [1859], reason: Ring hung, action: reset
[20444.312431] [drm] stuck on render ring
[20444.314223] [drm] GPU HANG: ecode 0:0x87d3bffa, in kwin [1859], reason: Ring hung, action: reset

Packages:

xf86-video-intel 2.99.917-1.1
kernel 3.18.2-2.1.g88366a3
libdrm_intel1 2.4.58-1.1
Comment 1 Popescu Sorin 2015-01-20 06:31:37 UTC
Created attachment 112517 [details]
cat of /sys/class/drm/card0/error
Comment 2 Chris Wilson 2015-01-20 09:20:14 UTC

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


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.