[Bug 81040] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Fri Aug 29 07:26:06 PDT 2014
https://bugs.freedesktop.org/show_bug.cgi?id=81040
Oliver <oliver at leibrock.eu> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |oliver at leibrock.eu
--- Comment #11 from Oliver <oliver at leibrock.eu> ---
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
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20140829/1805938d/attachment.html>
More information about the intel-gfx-bugs
mailing list