All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 31911] New: [r200] Severe flashing/flickering/blanking in Wings3D, possible regression
Date: Thu, 25 Nov 2010 01:08:53 -0800 (PST)	[thread overview]
Message-ID: <bug-31911-502@http.bugs.freedesktop.org/> (raw)

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

           Summary: [r200] Severe flashing/flickering/blanking in Wings3D,
                    possible regression
           Product: Mesa
           Version: git
          Platform: x86-64 (AMD64)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/DRI/r200
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: skunk@iskunk.org


I am running Ubuntu Maverick on amd64 with the 2.6.37-020637rc3-generic
mainline kernel, and Mesa packages with version string
7.10.0~git20101123+gallium.ed8b5fb2-0ubuntu0tormod from the xorg-edgers/radeon
PPA. My video card is an ATI FireGL 8800.

In running Wings3D, I no longer encounter GPU lockups as reported in bug 31417.
Instead, the application's 3D viewport area blanks out completely (all white)
for varying lengths of time, depending on what is going on:

* If I'm just moving the pointer around, the viewport might "flicker" briefly
from time to time;

* If I right-click to bring up a context menu, the viewport usually flickers on
cue;

* If I click to rotate the camera view, the viewport blanks and stays blank,
and only in brief, intermittent flashes do I see the view/object being
manipulated. The blanking appears to coincide with what would normally be a
smooth panning motion, and the un-blanking with any pause in that motion.


This is the first instance of this behavior that I've encountered, and it was
not observed in the 20101103 git pull (albeit with a different desktop
configuration), so this may well represent a regression.

(At the same time, I should point out that I am no longer able to reproduce the
GPU lockup described in bug 31417, so at least something's going right
somewhere.)

-- 
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:[~2010-11-25  9:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-25  9:08 bugzilla-daemon [this message]
2010-12-01  8:40 ` [Bug 31911] [r200] Severe flashing/flickering/blanking in Wings3D, possible regression bugzilla-daemon
2010-12-06  8:06 ` 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-31911-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.