Bug 81040 - [drm:i915_set_reset_status] GPU Hang: *ERROR* render ring hung inside bo
Summary: [drm:i915_set_reset_status] GPU Hang: *ERROR* render ring hung inside bo
Status: CLOSED WONTFIX
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
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: 2014-07-08 10:35 UTC by Alex Kirienko
Modified: 2017-07-24 22:53 UTC (History)
4 users (show)

See Also:
i915 platform:
i915 features:


Attachments
/sys/class/drm/card0/error dump (210.18 KB, text/plain)
2014-07-08 10:35 UTC, Alex Kirienko
no flags Details
/sys/class/drm/card0/error second dump (206.24 KB, text/plain)
2014-07-09 07:02 UTC, Alex Kirienko
no flags Details
Xorg.log for second error dump (14.05 KB, text/plain)
2014-07-09 07:03 UTC, Alex Kirienko
no flags Details

Description Alex Kirienko 2014-07-08 10:35:00 UTC
Created attachment 102429 [details]
/sys/class/drm/card0/error dump

Hello. 

I'm using xubuntu 14.04 x64 with Compton compositor. 
After last update I have regular gui freezes. I happens when I try to open IDEA - java-based IDE.  

I have attached GPU crash dump from /sys/class/drm/card0/error
Comment 1 Alex Kirienko 2014-07-08 10:42:38 UTC
Error message from syslog

8 17:17:34 sirius-delta kernel: [  608.597940] [drm] stuck on render ring
Jul  8 17:17:34 sirius-delta kernel: [  608.597948] [drm] GPU crash dump saved to /sys/class/drm/card0/error
Jul  8 17:17:34 sirius-delta kernel: [  608.597951] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
Jul  8 17:17:34 sirius-delta kernel: [  608.597953] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
Jul  8 17:17:34 sirius-delta kernel: [  608.597955] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
Jul  8 17:17:34 sirius-delta kernel: [  608.597957] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
Jul  8 17:17:34 sirius-delta kernel: [  608.602291] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0x37aa000 ctx 0) at 0x37aa6cc
Jul  8 17:17:40 sirius-delta kernel: [  614.577641] [drm] stuck on render ring
Jul  8 17:17:46 sirius-delta kernel: [  620.569301] [drm] stuck on render ring
Jul  8 17:17:52 sirius-delta kernel: [  626.609036] [drm] stuck on render ring
Jul  8 17:17:59 sirius-delta kernel: [  633.589305] [drm] stuck on render ring
Jul  8 17:18:05 sirius-delta kernel: [  639.617077] [drm] stuck on render ring
Jul  8 17:18:11 sirius-delta kernel: [  645.608725] [drm] stuck on render ring
Jul  8 17:18:17 sirius-delta kernel: [  651.588409] [drm] stuck on render ring
Jul  8 17:18:23 sirius-delta kernel: [  657.628118] [drm] stuck on render ring
Jul  8 17:18:29 sirius-delta kernel: [  663.595769] [drm] stuck on render ring



I have removed compton and have no freezes so far. 

I have insalled Updated and Optimized Open Graphics Drivers cos I have random freezes with native ubuntu intel drivers. WebGL in google maps make freeze for sure. UOOG drivers solved this issues and I was very happy. 
Right now I don't have freezes on google maps.
Comment 2 Chris Wilson 2014-07-08 11:23:41 UTC
The issue is that something scribbles over a batch submitted to the GPU. By the time the error occurred the culprit has already vanished. Please do try to update your xf86-video-intel and attach your Xorg.0.log.
Comment 3 Alex Kirienko 2014-07-09 07:02:51 UTC
Created attachment 102462 [details]
/sys/class/drm/card0/error second dump
Comment 4 Alex Kirienko 2014-07-09 07:03:26 UTC
Created attachment 102463 [details]
Xorg.log for second error dump
Comment 5 Alex Kirienko 2014-07-09 07:10:09 UTC
Hello.

Thank you for your quick feedback. 
I'm using intel driver from this ppa https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers 
Yesterday I got new updates, but looks like problem is still here. I got freezes even on native xfce compositor.

I have added drm error log and x.org log. I have done it right after latest freeze.
Comment 6 Alex Kirienko 2014-07-09 08:52:09 UTC
I forget to specify my hardware. 

I'm using ThinkPad T510 with HD screen. And I also use FullHD second screen connected via DisplayPort.
Comment 7 Alex Kirienko 2014-07-09 09:02:14 UTC
I got freezes again and again. It's impossible to work on this machine. 
Looks like freezes appear only when second FullHD screen is attached. 

I will use only notebook screen for a while for test.
Comment 8 Alex Kirienko 2014-07-10 04:23:46 UTC
I have used notebook without external screen for a while. And no freezes so far. Problem appears only with external screen attached to displayPort with DP->DVI cable.
Comment 9 Alex Kirienko 2014-07-10 04:41:21 UTC
I also don't have freezes with external screen if I use mirroring. 

I have tried old kernels, but still have freezes.
Comment 10 Andy Tanner-Smith 2014-08-28 11:50:50 UTC
I have this issue also. 
OS = Ubuntu 14.04
HW LENOVO 765912G/765912G, BIOS 7LETD0WW (2.30 )

---
This is from my syslog:

Aug 28 11:54:11 Cuthbert kernel: [10218.804051] [drm] stuck on render ring
Aug 28 11:54:11 Cuthbert kernel: [10218.804059] [drm] GPU crash dump saved to /sys/class/drm/card0/error
Aug 28 11:54:11 Cuthbert kernel: [10218.804062] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
Aug 28 11:54:11 Cuthbert kernel: [10218.804064] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
Aug 28 11:54:11 Cuthbert kernel: [10218.804067] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
Aug 28 11:54:11 Cuthbert kernel: [10218.804069] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
Aug 28 11:54:11 Cuthbert kernel: [10218.805049] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0x58db000 ctx 0) at 0x58db698
Aug 28 11:54:12 Cuthbert kernel: [10219.024047] [drm] GMBUS [i915 gmbus vga] timed out, falling back to bit banging on pin 2
Aug 28 11:54:12 Cuthbert kernel: [10219.312070] [drm:i915_reset] *ERROR* Failed to reset chip.
Aug 28 11:54:14 Cuthbert gnome-session[2238]: WARNING: Child process 2334 was already dead.
Aug 28 11:54:14 Cuthbert gnome-session[2238]: WARNING: App 'compiz.desktop' exited with code 1
Aug 28 11:54:14 Cuthbert gnome-session[2238]: WARNING: App 'compiz.desktop' respawning too quickly
Aug 28 11:54:14 Cuthbert gnome-session[2238]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Aug 28 11:54:18 Cuthbert kernel: [10225.603549] ------------[ cut here ]------------
Aug 28 11:54:18 Cuthbert kernel: [10225.603597] WARNING: CPU: 1 PID: 1212 at /build/buildd/linux-3.13.0/drivers/gpu/drm/i915/intel_display.c:922 assert_pll+0x68/0x70 [i915]()
Aug 28 11:54:18 Cuthbert kernel: [10225.603600] PLL state assertion failure (expected on, current off)
Aug 28 11:54:18 Cuthbert kernel: [10225.603602] Modules linked in: md4 ctr ccm rfcomm bnep binfmt_misc snd_hda_codec_analog nls_utf8 cifs fscache arc4 coretemp kvm pcmcia joydev serio_raw iwl4965 iwlegacy thinkpad_acpi nvram snd_hda_intel snd_hda_codec snd_hwdep snd_seq_midi lpc_ich snd_seq_midi_event mac80211 yenta_socket pcmcia_rsrc snd_pcm snd_rawmidi pcmcia_core btusb cfg80211 i915 bluetooth snd_page_alloc drm_kms_helper snd_seq drm snd_seq_device snd_timer i2c_algo_bit wmi snd soundcore parport_pc ppdev lp parport video mac_hid hid_generic usbhid hid psmouse firewire_ohci ahci firewire_core libahci crc_itu_t e1000e ptp pps_core
Aug 28 11:54:18 Cuthbert kernel: [10225.603652] CPU: 1 PID: 1212 Comm: Xorg Not tainted 3.13.0-35-generic #62-Ubuntu
Aug 28 11:54:18 Cuthbert kernel: [10225.603654] Hardware name: LENOVO 765912G/765912G, BIOS 7LETD0WW (2.30 ) 02/27/2012

Let me know if you will need the whole file and I will send a dropbox link.
Comment 11 Oliver 2014-08-29 14:26:06 UTC
Hello,

I do have same issues wiht my Ubuntu 14.04 on my Lenove T410 ThinkPad with 
external 20" LCD Monitor.

During freeze, occurs after 5 minutes or 2 days, the laptop does not respond
to any input on the current Screen, but the programs are still running in 
background, e.g. sound and movie are still playing.

CRTL+ALT+F2 is still possible and it is possible to do a sudo services lightdm 
restart (<- without any help).

# uname -a
Linux 3.13.0-35-lowlatency #62-Ubuntu SMP PREEMPT Fri Aug 15 02:26:48 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

# dmesg | grep drm
[   16.164993] [drm] Initialized drm 1.1.0 20060810
[   16.632588] [drm] Memory usable by graphics device = 2048M
[   16.632595] fb: conflicting fb hw usage inteldrmfb vs VESA VGA - removing generic driver
[   16.675847] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[   16.675850] [drm] Driver supports precise vblank timestamp query.
[   16.781756] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit banging on pin 5
[   16.830977] fbcon: inteldrmfb (fb0) is primary device
[   17.131313] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[   17.138523] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
[  838.809713] [drm] stuck on render ring
[  838.809721] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[  838.809723] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[  838.809724] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[  838.809726] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[  838.809728] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[  838.815554] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0x62de000 ctx 0) at 0x62e008c
[  844.808341] [drm] stuck on render ring
[  850.823095] [drm] stuck on render ring
[  856.833821] [drm] stuck on render ring
[  862.836487] [drm] stuck on render ring
[  868.847232] [drm] stuck on render ring
[  874.849866] [drm] stuck on render ring
[  880.856604] [drm] stuck on render ring
[  886.855267] [drm] stuck on render ring
[  892.870001] [drm] stuck on render ring
[  892.870074] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0x62de000 ctx 0) at 0x62e008c
[  898.880735] [drm] stuck on render ring
[  898.880840] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0x62de000 ctx 0) at 0x62e008c
[  898.880903] [drm:i915_context_is_banned] *ERROR* context hanging too fast, declaring banned!
#
# Xorg -version

X.Org X Server 1.15.1
Release Date: 2014-04-13
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.2.0-37-generic x86_64 Ubuntu
Current Operating System: Linux DragonT 3.13.0-35-lowlatency #62-Ubuntu SMP PREEMPT Fri Aug 15 02:26:48 UTC 2014 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-lowlatency root=/dev/sda1 ro quiet splash acpi_osi=Linux acpi_backlight=vendor vt.handoff=7
Build Date: 16 April 2014  01:36:29PM
xorg-server 2:1.15.1-0ubuntu2 (For technical support please see http://www.ubuntu.com/support) 
Current version of pixman: 0.30.2
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
#

I have not attached the GPU dump as the error file is 0 size.

Let me know if you need more or specific files and I will upload them here.

Cheers

 Oliver
Comment 12 Rodrigo Vivi 2014-10-15 20:16:26 UTC
Is it possible to try latest drm-intel-nightly branch from cgit.freedesktop.org/drm-intel? Please collect new logs and error state from it.
Comment 13 Andy Tanner-Smith 2014-10-15 20:38:27 UTC
I might be cross posting. The bug I have reported here, may or may not be related to https://bugs.freedesktop.org/show_bug.cgi?id=83423

This latter bug is affecting more often now and is predictably reproducible.  Before I reported I had downloaded and installed the latest Intel Drivers for my Mobile GM965/GL960 Graphics Controller, and have installed Linux Kernel 3.17.

I will try with the latest RC as you suggest and let you know.
Comment 14 Alex Kirienko 2014-10-15 20:56:03 UTC
(In reply to Rodrigo Vivi from comment #12)
> Is it possible to try latest drm-intel-nightly branch from
> cgit.freedesktop.org/drm-intel? Please collect new logs and error state from
> it.

Hello. I'm sorry, but I have moved to ubuntu 14.04 and don't have any problems so far. So I can't check it with latest drivers.
Comment 15 Andy Tanner-Smith 2014-10-16 21:44:30 UTC
I have tried the latest DRM-Nightly as requested by Rodrigo, but my problem persists

[ 86.804054] [drm] stuck on render ring
[ 86.804857] [drm] GPU HANG: ecode 0:0x9f47f9fd. in chrome [2284].
reason: Ring hung, action: reset
[ 86.804860] [drm] 8P0 hangs can indicate a bug anywhere in the entire
gfx stack. including userspace.
[ 86.804861] [drm] Please file a _new_ bug report on
bugs.freedesktop.org against DRI -> DRM/Intel
[ 86.804862] [drnfl drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[ 86.804864] [drip] The gpu crash dum is required to analyze gpu
hangs. so please always attach it.
[ 86.804865] [drmu GPU crash dump saved to /sys/class/drm/cardO/error
[ 86.805067] [drm:1815_reset] *ERROR* Failed to reset chip: -19

/sys/class/drm/cardO/error file size is "0" so I think the dump does
not get written to the disk.

Again I think this is the same issue as https://bugs.freedesktop.org/show_bug.cgi?id=83423
Comment 16 Andy Tanner-Smith 2014-10-16 21:45:44 UTC
Sorry typos in the post before this is correct

[ 86.804054] [drm] stuck on render ring
[ 86.804857] [drm] GPU HANG: ecode 0:0x9f47f9fd. in chrome [2284].
reason: Ring hung, action: reset
[ 86.804860] [drm] 8P0 hangs can indicate a bug anywhere in the entire
gfx stack. including userspace.
[ 86.804861] [drm] Please file a _new_ bug report on
bugs.freedesktop.org against DRI -> DRM/Intel
[ 86.804862] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[ 86.804864] [drm] The gpu crash dum is required to analyze gpu
hangs. so please always attach it.
[ 86.804865] [drm] GPU crash dump saved to /sys/class/drm/cardO/error
[ 86.805067] [drm: i915_reset] *ERROR* Failed to reset chip: -19
Comment 17 Rodrigo Vivi 2014-10-16 22:13:00 UTC
Andy, your one is definitely 83423.

But I'm not convinced yet the original reported here is the same.
So I'll leve the needinfo here trying to get original case to get newer kernel and newer xf86-video-intel.
Comment 18 Rodrigo Vivi 2015-01-15 18:43:05 UTC
timeout. Feel free to reopen providing new/refreshed logs with latest kernel or preferably latest drm-intel-nightly from cgit.freedesktop.org.


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.