[Bug 41668] New: Screen locks up at random points when using a 3D compositing wm (gnome-shell) on an rv515 (radeon mobility x1300)

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Oct 10 22:08:22 PDT 2011


           Summary: Screen locks up at random points when using a 3D
                    compositing wm (gnome-shell) on an rv515 (radeon
                    mobility x1300)
           Product: Mesa
           Version: 7.11
          Platform: x86-64 (AMD64)
        OS/Version: Linux (All)
            Status: NEW
          Severity: critical
          Priority: medium
         Component: Drivers/Gallium/r300
        AssignedTo: dri-devel at lists.freedesktop.org
        ReportedBy: inaudible at simplesuperlativ.es

Created an attachment (id=52202)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=52202)
dmesg output using drm.debug=14

i have an intermittent issue with "ATI Mobility Radeon X1300" on an up-to-date
archlinux laptop running gnome-shell.. all's well until rendering breaks,
sometimes after many hours/days use.. there's no real sign of a repeatable
action and nothing reported in logs.. X continues to run and the mouse cursor
is active, and even changes to represent the screen content.. 

the closest i can get to a repeatable action is an almost certain freeze using
gimp with strenuous brush activity using the clone tool on an average size

if i restart gdm i still have no mouse/keyboard interaction with onscreen
although gdm dress is displayed.. if i killall -HUP gnome-shell in the running
session the window content (without decorations) briefly displays but when it
settles only the background appears

if i switch to the VT and back to X then window content with border decorations
is displayed instead of background image, but still no interaction

i can't launch any X applications from VT or ssh, or use another WM to replace.

`DISPLAY=:0 openbox --replace` results in:

"Invalid MIT-MAGIC-COOKIE-1 keyOpenbox-Message: Failed to open the display from
the DISPLAY environment variable."

however, if i kill gdm, and create an xinitrc for openbox i can start an
Xsession with keybd/mouse interaction, so i guess there's definitely something
up with 3d (offscreen?) rendering

from within the openbox session:
running glxgears just shows an empty black box.. all other glx demos are the
same empty boxes.. 
when i'm logged in to this openbox xsession i can launch xapps via `DISPLAY=:0
foobar` variable.. so this bug i'm encountering must do something to interrupt
the ability to draw new windows?

i can only get a working 3D X session by unloading/reloading kernel drivers.. 

here's the very basic script i'm using to unload drivers so i can start X with

# unbind kms fb before unloading modules.. 
echo 0 > /sys/class/vtconsole/vtcon1/bind 
sleep 1

# unload kernel modules
rmmod drm_kms_helper ttm radeon drm
sleep 1

# reload kernel modules
modprobe radeon

some basic information:
GL_VERSION:  2.1 Mesa 7.11
GL_VENDOR:   X.Org R300 Project
GL_RENDERER: Gallium 0.4 on ATI RV515
uname -a: Linux neondada 3.0-ARCH #1 SMP PREEMPT Tue Aug 30 08:53:25 CEST 2011
x86_64 Intel(R) Core(TM)2 CPU T5600 @ 1.83GHz GenuineIntel GNU/Linux

i have included output from startx, dmesg (with drm.debug=14), Xorg.0.log &

Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the dri-devel mailing list