All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 41592] New: [Radeon] The display often freezes with gnome-shell 3.2
Date: Sat,  8 Oct 2011 11:28:04 -0700 (PDT)	[thread overview]
Message-ID: <bug-41592-502@http.bugs.freedesktop.org/> (raw)

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

           Summary: [Radeon] The display often freezes with gnome-shell
                    3.2
           Product: Mesa
           Version: 7.11
          Platform: x86-64 (AMD64)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/r600
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: mirandir@orange.fr


Since the Gnome 3.2 update, there are many many lines like this in my Xorg.log
:

[ 4192.459] (II) RADEON(0): radeon_dri2_flip_event_handler:981
fevent[0x17e2360] width 1366 pitch 5632 (/4 1408)
[ 4193.043] (II) RADEON(0): radeon_dri2_schedule_flip:619 fevent[0x184a890]

And gnome-shell freezes very often, when i exit fullscreen games or just after
that I unlocked gnome-screensaver.
I have to switch to a VT and kill the gnome-shell process, then it restart and
I can continue to work.

I attach my dmesg and Xorg.log.


Additional info:
* Archlinux 64 bits, kernel-3.0.6, mesa-7.11, xorg-server-1.10.4 and
gnome-shell-3.2.0
* ATI Mobility Radeon HD5470 with the radeon driver.

(I can't reproduce this bug with my laptop with Intel graphics)

-- 
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-08 18:28 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-08 18:28 bugzilla-daemon [this message]
2011-10-08 18:28 ` [Bug 41592] [Radeon] The display often freezes with gnome-shell 3.2 bugzilla-daemon
2011-10-08 18:29 ` bugzilla-daemon
2011-10-10 13:07 ` bugzilla-daemon
2011-10-10 13:08 ` bugzilla-daemon
2011-10-10 13:16 ` bugzilla-daemon
2011-10-10 20:57 ` bugzilla-daemon
2011-10-10 21:19 ` bugzilla-daemon
2011-10-11 11:23 ` bugzilla-daemon
2011-10-11 16:49 ` bugzilla-daemon
2011-10-13 16:17 ` bugzilla-daemon
2011-10-30 11:35 ` bugzilla-daemon
2011-10-30 11:35 ` bugzilla-daemon
2011-10-30 20:58 ` bugzilla-daemon
2011-10-31 10:42 ` bugzilla-daemon
2011-10-31 11:50 ` bugzilla-daemon
2011-10-31 12:14 ` bugzilla-daemon
2011-10-31 12:19 ` bugzilla-daemon
2011-10-31 13:14 ` bugzilla-daemon
2011-10-31 14:43 ` bugzilla-daemon
2011-11-01 17:44 ` bugzilla-daemon
2011-11-02 17:53 ` 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-41592-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.