Bug 90245 - [ 8752.762791] [drm] GPU HANG: ecode 8:0:0xfffffffe, in systemd-logind [322], reason: Ring hung, action: reset
Summary: [ 8752.762791] [drm] GPU HANG: ecode 8:0:0xfffffffe, in systemd-logind [322],...
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
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: 2015-04-29 23:05 UTC by sadieperkins
Modified: 2017-07-24 22:47 UTC (History)
2 users (show)

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


Attachments
/sys/class/drm/card0/error (2.73 MB, text/plain)
2015-04-29 23:05 UTC, sadieperkins
no flags Details

Description sadieperkins 2015-04-29 23:05:58 UTC
Created attachment 115458 [details]
/sys/class/drm/card0/error

upon resume from suspend:

[ 8752.760464] [drm] stuck on render ring
[ 8752.762791] [drm] GPU HANG: ecode 8:0:0xfffffffe, in systemd-logind [322], reason: Ring hung, action: reset
[ 8752.762793] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 8752.762794] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 8752.762795] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 8752.762795] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 8752.762796] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 8752.767176] drm/i915: Resetting chip after gpu hang
[ 8758.753135] [drm] stuck on render ring
[ 8758.755711] [drm] GPU HANG: ecode 8:0:0xb39ef7f4, in systemd-logind [322], reason: Ring hung, action: reset
[ 8758.755803] [drm:i915_set_reset_status [i915]] *ERROR* gpu hanging too fast, banning!
[ 8758.759871] drm/i915: Resetting chip after gpu hang


uname -a:
Linux mirai 4.0.1-1-ARCH #1 SMP PREEMPT Wed Apr 29 12:00:26 CEST 2015 x86_64 GNU/Linux

X version:
[    30.847] 
X.Org X Server 1.17.1
Release Date: 2015-02-10
[    30.847] X Protocol Version 11, Revision 0
[    30.847] Build Operating System: Linux 3.19.2-1-ARCH x86_64 
[    30.847] Current Operating System: Linux mirai 4.0.1-1-ARCH #1 SMP PREEMPT Wed Apr 29 12:00:26 CEST 2015 x86_64
[    30.847] Kernel command line: root=UUID=708c7685-283d-4745-bc13-f263f51b125a rw cryptdevice=/dev/disk/by-uuid/92ceacb6-5049-4820-ab04-c1aeecc6ecbb:cryptoroot initrd=initramfs-linux.img psmouse.proto=imps
[    30.847] Build Date: 14 April 2015  10:34:18AM
[    30.847]  
[    30.847] Current version of pixman: 0.32.6
[    30.847]    Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.

lspci:
00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09)
00:02.0 VGA compatible controller: Intel Corporation Broadwell-U Integrated Graphics (rev 09)
00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller (rev 09)
00:14.0 USB controller: Intel Corporation Wildcat Point-LP USB xHCI Controller (rev 03)
00:16.0 Communication controller: Intel Corporation Wildcat Point-LP MEI Controller #1 (rev 03)
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection (3) I218-V (rev 03)
00:1b.0 Audio device: Intel Corporation Wildcat Point-LP High Definition Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #6 (rev e3)
00:1c.1 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #3 (rev e3)
00:1f.0 ISA bridge: Intel Corporation Wildcat Point-LP LPC Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation Wildcat Point-LP SATA Controller [AHCI Mode] (rev 03)
00:1f.3 SMBus: Intel Corporation Wildcat Point-LP SMBus Controller (rev 03)
00:1f.6 Signal processing controller: Intel Corporation Wildcat Point-LP Thermal Management Controller (rev 03)
03:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
Comment 1 Jeff Zheng 2015-04-30 00:53:04 UTC
Is it similar to bug 89600?
Comment 2 Mika Kuoppala 2015-05-05 14:51:06 UTC
Could you please test with: https://patchwork.freedesktop.org/patch/48028/
Comment 3 Jani Nikula 2016-04-21 12:33:56 UTC
(In reply to Mika Kuoppala from comment #2)
> Could you please test with: https://patchwork.freedesktop.org/patch/48028/

Timeout, presumed fixed by the commit, closing. Please reopen if the problem persists with latest kernels.


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.