[Bug 31911] New: [r200] Severe flashing/flickering/blanking in Wings3D, possible regression

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu Nov 25 01:08:53 PST 2010


           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 at lists.freedesktop.org
        ReportedBy: skunk at 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

* 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

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