Bug 94630 - Intel Gpu hang in Debian Testing with Kde
Summary: Intel Gpu hang in Debian Testing with Kde
Status: CLOSED DUPLICATE of bug 93262
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) All
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-19 20:57 UTC by Juanjo Benages
Modified: 2017-07-24 22:42 UTC (History)
1 user (show)

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


Attachments
GPU crash dump (2.04 MB, text/plain)
2016-03-19 20:57 UTC, Juanjo Benages
no flags Details

Description Juanjo Benages 2016-03-19 20:57:58 UTC
Created attachment 122432 [details]
GPU crash dump

The machine is a Acer Aspire 5749 with intel i3-2330M processor

The versions of xorg and the intel server are
xserver-xorg-video-intel/testing,now 2:2.99.917+git20160307-2
xserver-xorg-core/testing,now 2:1.18.2-1

Output of dmesg
[  876.697649] [drm] stuck on render ring
[  876.698298] [drm] GPU HANG: ecode 6:0:0x87e8fffd, in Xorg [848], reason: Ring hung, action: reset
[  876.698300] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[  876.698301] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[  876.698302] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[  876.698303] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[  876.698304] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[  876.700382] drm/i915: Resetting chip after gpu hang
[  888.746549] [drm] stuck on render ring
[  888.747153] [drm] GPU HANG: ecode 6:0:0x87e8fffd, in Xorg [848], reason: Ring hung, action: reset
[  888.747235] [drm:i915_set_reset_status [i915]] *ERROR* gpu hanging too fast, banning!
[  888.749266] drm/i915: Resetting chip after gpu hang
Comment 1 Chris Wilson 2016-03-30 09:08:34 UTC

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


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.