Re: [Intel-gfx] drm stuck on render ring starting xlock on a x201 using SNA

[Chris Wilson]

On Sun, Jan 11, 2015 at 07:06:19PM -0500, Charles Devereaux wrote:
Hello
 
Aftertrying to leave an xlock started with  xlock -nolock +use3d -mode
gears, I get a drm stuck on render ring error.
The funny thing is this problem did not happen on the exact same thinkpad
x201 laptop using an identical xorg.conf but with a debian jessie i386  (I
did a clean reinstall of debian jessie amd64)
 
xorg.conf contains:
Section Device
    Identifier  i950
    Driver  intel
    BusID   PCI:0:2:0
    Screen 0
    Option    AccelMethod    SNA
    Option  FallbackDebug true
EndSection
 
I'm using kernel  3.14.25, and I saved /sys/class/drm/card0/error and
gpucrash in case it's not a know bug.
Any suggestion?

It's impossible to tell without the complete information
(/sys/class/drm/card0/error, dmesg and Xorg.0.log) but it sounds like
the kernel bug: https://bugs.freedesktop.org/show_bug.cgi?id=87780
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

[Intel-gfx] drm stuck on render ring starting xlock on a x201 using SNA

[Charles Devereaux]

Hello

Aftertrying to leave an xlock started with  xlock -nolock +use3d -mode
gears, I get a drm stuck on render ring error.

The funny thing is this problem did not happen on the exact same thinkpad
x201 laptop using an identical xorg.conf but with a debian jessie i386  (I
did a clean reinstall of debian jessie amd64)

xorg.conf contains:
Section Device
Identifier  i950
Driver  intel
BusID   PCI:0:2:0
Screen 0
OptionAccelMethodSNA
Option  FallbackDebug true
EndSection

I'm using kernel  3.14.25, and I saved /sys/class/drm/card0/error and
gpucrash in case it's not a know bug.

Any suggestion?

[0.396228] [drm] Initialized drm 1.1.0 20060810
[0.396870] [drm] Memory usable by graphics device = 2048M
[0.405464] i915 :00:02.0: irq 43 for MSI/MSI-X
[0.405480] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[0.405483] [drm] Driver supports precise vblank timestamp query.
[0.405586] vgaarb: device changed decodes:
PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[0.408539] ACPI: Battery Slot [BAT0] (battery present)
[0.460085] [drm] Enabling RC6 states: RC6 off, RC6p off, RC6pp off
[0.471385] fbcon: inteldrmfb (fb0) is primary device
(...)
[1.077765] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on
minor 0
(...)
[  207.574130] [drm] stuck on render ring
[  207.574149] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[  207.574152] [drm] GPU hangs can indicate a bug anywhere in the entire
gfx stack, including userspace.
[  207.574154] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI - DRM/Intel
[  207.574155] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[  207.574157] [drm] The gpu crash dump is required to analyze gpu hangs,
so please always attach it.
[  207.581041] [drm:init_ring_common] *ERROR* failed to set render ring
head to zero ctl  head 008014dc tail  start 3000
[  207.632121] [drm:init_ring_common] *ERROR* render ring initialization
failed ctl 0001f001 head 008014dc tail  start 3000
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx