dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 41668] New: Screen locks up at random points when using a 3D compositing wm (gnome-shell) on an rv515 (radeon mobility x1300)
Date: Mon, 10 Oct 2011 22:08:22 -0700 (PDT)	[thread overview]
Message-ID: <bug-41668-502@http.bugs.freedesktop.org/> (raw)

https://bugs.freedesktop.org/show_bug.cgi?id=41668

           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@lists.freedesktop.org
        ReportedBy: inaudible@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
image.

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.. 
radeon/drm/ttm/drm_kms_helper.. 

here's the very basic script i'm using to unload drivers so i can start X with
3D..
---
#!/bin/bash

# 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 &
glxinfo.

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

             reply	other threads:[~2011-10-11  5:08 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-11  5:08 bugzilla-daemon [this message]
2011-10-11  5:09 ` [Bug 41668] Screen locks up at random points when using a 3D compositing wm (gnome-shell) on an rv515 (radeon mobility x1300) bugzilla-daemon
2011-10-11  5:09 ` bugzilla-daemon
2011-10-11  5:10 ` bugzilla-daemon
2011-10-11  5:12 ` bugzilla-daemon
2011-10-11  5:12 ` bugzilla-daemon
2011-10-11  5:13 ` bugzilla-daemon
2011-10-11  9:34 ` bugzilla-daemon
2011-10-11 16:28 ` bugzilla-daemon
2011-10-11 16:30 ` bugzilla-daemon
2011-10-12  2:25 ` bugzilla-daemon
2011-10-12  2:27 ` bugzilla-daemon
2011-10-12  2:28 ` bugzilla-daemon
2011-10-12  2:42 ` bugzilla-daemon
2011-10-12 10:07 ` bugzilla-daemon
2011-10-12 10:24 ` bugzilla-daemon
2011-10-13  6:27 ` bugzilla-daemon
2011-10-13 13:01 ` bugzilla-daemon
2011-10-24 23:46 ` bugzilla-daemon
2011-10-24 23:47 ` bugzilla-daemon
2011-12-15  1:38 ` bugzilla-daemon
2011-12-15  1:39 ` bugzilla-daemon
2011-12-15  7:21 ` bugzilla-daemon
2011-12-15 14:20 ` bugzilla-daemon
2011-12-15 15:19 ` bugzilla-daemon
2012-02-12  8:59 ` bugzilla-daemon
2012-02-13 13:40 ` bugzilla-daemon
2012-02-13 14:20 ` bugzilla-daemon
2012-02-19 11:19 ` bugzilla-daemon
2012-02-19 12:25 ` bugzilla-daemon
2012-04-24  8:37 ` bugzilla-daemon
2012-04-26  2:44 ` bugzilla-daemon
2013-01-11 21:11 ` bugzilla-daemon
2013-01-14 13:10 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-41668-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).