Bug 90921 - [BDW] GPU HANG: ecode 8:0:0xfffffffe, in Xorg [325], reason: Ring hung, action: reset
Summary: [BDW] GPU HANG: ecode 8:0:0xfffffffe, in Xorg [325], reason: Ring hung, actio...
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:
: 95205 (view as bug list)
Depends on:
Blocks:
 
Reported: 2015-06-10 05:30 UTC by kgsmith@gmail.com
Modified: 2016-11-18 12:56 UTC (History)
3 users (show)

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


Attachments
cat /sys/class/drm/card0/error (396.84 KB, text/plain)
2015-06-10 05:30 UTC, kgsmith@gmail.com
no flags Details
kernel log stacktrace (7.66 KB, text/plain)
2015-10-07 13:12 UTC, lleonini
no flags Details

Description kgsmith@gmail.com 2015-06-10 05:30:51 UTC
Created attachment 116414 [details]
cat /sys/class/drm/card0/error

Jun 09 22:12:20 yozhik wpa_actiond[332]: Interface 'wlp3s0' reestablished connection to network 'lighthouse'
Jun 09 22:12:21 yozhik kernel: [drm] stuck on render ring
Jun 09 22:12:21 yozhik kernel: [drm] GPU HANG: ecode 8:0:0xfffffffe, in Xorg [325], reason: Ring hung, action: reset
Jun 09 22:12:21 yozhik kernel: [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
Jun 09 22:12:21 yozhik kernel: [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
Jun 09 22:12:21 yozhik kernel: [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
Jun 09 22:12:21 yozhik kernel: [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
Jun 09 22:12:21 yozhik kernel: [drm] GPU crash dump saved to /sys/class/drm/card0/error
Jun 09 22:12:21 yozhik kernel: drm/i915: Resetting chip after gpu hang
Jun 09 22:12:27 yozhik kernel: [drm] stuck on render ring
Jun 09 22:12:27 yozhik kernel: [drm] GPU HANG: ecode 8:0:0x405fffff, in Xorg [325], reason: Ring hung, action: reset
Jun 09 22:12:27 yozhik kernel: drm/i915: Resetting chip after gpu hang

OS: Arch

% uname -a
Linux yozhik 4.0.4-2-ARCH #1 SMP PREEMPT Fri May 22 03:05:23 UTC 2015 x86_64 GNU/Linux

vendor_id       : GenuineIntel
cpu family      : 6
model           : 61
model name      : Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz
stepping        : 4
microcode       : 0x16
cpu MHz         : 1369.570
cache size      : 4096 KB
physical id     : 0
siblings        : 4
core id         : 0
cpu cores       : 2
apicid          : 0
initial apicid  : 0
fpu             : yes
fpu_exception   : yes
cpuid level     : 20
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch ida arat epb pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm rdseed adx smap xsaveopt
bugs            :
bogomips        : 5190.53
clflush size    : 64
cache_alignment : 64
address sizes   : 39 bits physical, 48 bits virtual
power management:


Notes:
The xf86-video-intel driver was so buggy when I installed the machine two weeks ago that I ended up having to use fbdev which I'm still using.
Comment 1 Ander Conselvan de Oliveira 2015-06-17 08:03:41 UTC
What version of xf86-video-intel are you using?
Comment 2 kgsmith@gmail.com 2015-06-17 12:53:13 UTC
I'm not. I'm using fbdev as mentioned in my previous comment. The version is xf86-video-fbdev 0.4.4-4.
Comment 3 lleonini 2015-10-07 13:12:05 UTC
Created attachment 118733 [details]
kernel log stacktrace
Comment 4 lleonini 2015-10-07 13:19:36 UTC
Hi,

I have a, maybe, similar problem since some weeks. I have tried the Intel driver with UXA or SNA but the crashes happen with both.
I'm using the mate desktop without compositing and without compiz. These freeze happen any time, even when I'm not using any applications except vim in terminal...

They *seems* to happen only when I'm on battery. From the kernel log, I'm wondering if there is a relation between intel wifi card and the crash or if it's only due to graphic card...


ii  intel-microcode  3.20150121.1 amd64
ii  libdrm-intel1:amd64 2.4.64-1 amd64
ii  libdrm-intel1:i386 2.4.64-1 i386
ii  xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu3 amd64


DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=15.10
DISTRIB_CODENAME=wily
DISTRIB_DESCRIPTION="Ubuntu Wily Werewolf (development branch)"

Linux t450s 4.2.0-14-generic #16-Ubuntu SMP Fri Oct 2 05:14:57 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
Comment 5 yann 2016-06-07 15:31:11 UTC
*** Bug 95205 has been marked as a duplicate of this bug. ***
Comment 6 David d'E 2016-06-07 15:53:49 UTC
OK. You tagged my bug 95205 as a duplicate of this one... but what is the solution to the problem ?

thanks
Comment 7 yann 2016-06-07 16:41:36 UTC
David, I noticed that you have a quite old kernel 3.10.0-327.13.1.el7.x86_64
Can you try to update it ? You may consider to latest drm-intel-nightly or Linux stable, 4.6.1
Comment 8 Tom Chance 2016-06-17 15:17:54 UTC
I think I may be having a related problem since I upgraded (on debian stretch) to kernel 4.6.0 from 4.5.0.

I get the following in syslog:

Jun 17 11:18:10 piglet /usr/lib/gdm3/gdm-x-session[1160]: (EE) [mi] EQ overflowing.  Additional events will be discarded until existing events are processed.
Jun 17 11:18:10 piglet /usr/lib/gdm3/gdm-x-session[1160]: (EE)
Jun 17 11:18:10 piglet /usr/lib/gdm3/gdm-x-session[1160]: (EE) Backtrace:
Jun 17 11:18:10 piglet /usr/lib/gdm3/gdm-x-session[1160]: (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x55fd88968f6e]
Jun 17 11:18:10 piglet /usr/lib/gdm3/gdm-x-session[1160]: (EE) 1: /usr/lib/xorg/Xorg (mieqEnqueue+0x253) [0x55fd8894aa33]
Jun 17 11:18:10 piglet /usr/lib/gdm3/gdm-x-session[1160]: (EE) 2: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x55fd88823632]
Jun 17 11:18:10 piglet /usr/lib/gdm3/gdm-x-session[1160]: (EE) 3: /usr/lib/xorg/Xorg (xf86PostMotionEvent+0xd6) [0x55fd8885a956]
Jun 17 11:18:10 piglet /usr/lib/gdm3/gdm-x-session[1160]: (EE) 4: /usr/lib/xorg/modules/input/synaptics_drv.so (0x7f0fbb634000+0x5f89) [0x7f0fbb639f$
Jun 17 11:18:10 piglet /usr/lib/gdm3/gdm-x-session[1160]: (EE) 5: /usr/lib/xorg/modules/input/synaptics_drv.so (0x7f0fbb634000+0x7532) [0x7f0fbb63b5$
Jun 17 11:18:10 piglet /usr/lib/gdm3/gdm-x-session[1160]: (EE) 6: /usr/lib/xorg/Xorg (0x55fd887b7000+0x940f8) [0x55fd8884b0f8]
Jun 17 11:18:10 piglet /usr/lib/gdm3/gdm-x-session[1160]: (EE) 7: /usr/lib/xorg/Xorg (0x55fd887b7000+0xb9392) [0x55fd88870392]
Jun 17 11:18:10 piglet /usr/lib/gdm3/gdm-x-session[1160]: (EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (0x7f0fc3a6d000+0x334e0) [0x7f0fc3aa04e0]
Jun 17 11:18:10 piglet /usr/lib/gdm3/gdm-x-session[1160]: (EE) 9: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x5) [0x7f0fc3b4e4f5]
Jun 17 11:18:10 piglet /usr/lib/gdm3/gdm-x-session[1160]: (EE) 10: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f0fbf3ef000+0x24f5d) [0x7f0fbf413f$
Jun 17 11:18:10 piglet /usr/lib/gdm3/gdm-x-session[1160]: (EE) 11: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f0fbf3ef000+0x28904) [0x7f0fbf4179$
Jun 17 11:18:10 piglet /usr/lib/gdm3/gdm-x-session[1160]: (EE) 12: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f0fbf3ef000+0x5c3ee) [0x7f0fbf44b3$
Jun 17 11:18:10 piglet /usr/lib/gdm3/gdm-x-session[1160]: (EE) 13: /usr/lib/xorg/Xorg (BlockHandler+0x4a) [0x55fd8880f5ba]
Jun 17 11:18:10 piglet /usr/lib/gdm3/gdm-x-session[1160]: (EE) 14: /usr/lib/xorg/Xorg (WaitForSomething+0x163) [0x55fd88965c33]
Jun 17 11:18:10 piglet /usr/lib/gdm3/gdm-x-session[1160]: (EE) 15: /usr/lib/xorg/Xorg (0x55fd887b7000+0x53a1e) [0x55fd8880aa1e]
Jun 17 11:18:10 piglet /usr/lib/gdm3/gdm-x-session[1160]: (EE) 16: /usr/lib/xorg/Xorg (0x55fd887b7000+0x57c03) [0x55fd8880ec03]
Jun 17 11:18:10 piglet /usr/lib/gdm3/gdm-x-session[1160]: (EE) 17: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x7f0fc3a8d5f0]
Jun 17 11:18:10 piglet /usr/lib/gdm3/gdm-x-session[1160]: (EE) 18: /usr/lib/xorg/Xorg (_start+0x29) [0x55fd887f8f99]
Jun 17 11:18:10 piglet /usr/lib/gdm3/gdm-x-session[1160]: (EE)
Jun 17 11:18:10 piglet /usr/lib/gdm3/gdm-x-session[1160]: (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up the stack.
Jun 17 11:18:10 piglet /usr/lib/gdm3/gdm-x-session[1160]: (EE) [mi] mieq is *NOT* the cause.  It is a victim.
Jun 17 11:18:10 piglet kernel: [ 1087.627729] [drm] stuck on render ring
Jun 17 11:18:10 piglet kernel: [ 1087.634979] [drm] GPU HANG: ecode 8:0:0xfffffffe, in Xorg [1162], reason: Ring hung, action: reset
Jun 17 11:18:10 piglet kernel: [ 1087.634995] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
Jun 17 11:18:10 piglet kernel: [ 1087.635004] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
Jun 17 11:18:10 piglet kernel: [ 1087.635012] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
Jun 17 11:18:10 piglet kernel: [ 1087.635019] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
Jun 17 11:18:10 piglet kernel: [ 1087.635029] [drm] GPU crash dump saved to /sys/class/drm/card0/error
Jun 17 11:18:10 piglet kernel: [ 1087.641887] drm/i915: Resetting chip after gpu hang
Jun 17 11:18:10 piglet /usr/lib/gdm3/gdm-x-session[1160]: [mi] Increasing EQ size to 1024 to prevent dropped events.
Jun 17 11:18:10 piglet /usr/lib/gdm3/gdm-x-session[1160]: [mi] EQ processing has resumed after 37 dropped events.
Jun 17 11:18:10 piglet /usr/lib/gdm3/gdm-x-session[1160]: [mi] This may be caused by a misbehaving driver monopolizing the server's resources.
Jun 17 11:18:13 piglet pulseaudio[916]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended.
Jun 17 11:18:18 piglet kernel: [ 1095.635999] [drm] stuck on render ring
Jun 17 11:18:18 piglet kernel: [ 1095.642984] [drm] GPU HANG: ecode 8:0:0xfffffffe, in Xorg [1162], reason: Ring hung, action: reset
Jun 17 11:18:18 piglet kernel: [ 1095.643414] [drm:i915_set_reset_status [i915]] *ERROR* gpu hanging too fast, banning!
Jun 17 11:18:18 piglet kernel: [ 1095.646268] drm/i915: Resetting chip after gpu hang
Jun 17 11:18:18 piglet /usr/lib/gdm3/gdm-x-session[1160]: (EE) intel(0): Failed to submit rendering commands (Input/output error), disabling acceleration.

The computer hangs. This problem doesn't occur when I boot up with kernel 4.5.0.
Comment 9 yann 2016-09-28 13:12:42 UTC
We seem to have neglected the bug a bit, apologies.

There were improvements pushed in kernel and Mesa that will benefit to your system, so please re-test with latest kernel & Mesa to see if this issue is still occurring.
Comment 10 yann 2016-11-18 12:56:53 UTC
(In reply to yann from comment #9)
> We seem to have neglected the bug a bit, apologies.
> 
> There were improvements pushed in kernel and Mesa that will benefit to your
> system, so please re-test with latest kernel & Mesa to see if this issue is
> still occurring.

Timeout. Assuming that it is fixed by now. If this is not the case, please re-test with latest kernel & Mesa (12-13) to see if this issue is still occurring since there were improvements pushed in kernel and Mesa that will benefit to your system, and fill a new bug.


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.