[Bug 45709] New: r600g doesn' t seem to flush when it should → visual stuck

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Feb 6 10:10:33 PST 2012


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

             Bug #: 45709
           Summary: r600g doesn't seem to flush when it should → visual
                    stuck
    Classification: Unclassified
           Product: Mesa
           Version: git
          Platform: Other
               URL: http://bugs.winehq.org/show_bug.cgi?id=29802
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/r600
        AssignedTo: dri-devel at lists.freedesktop.org
        ReportedBy: kai at dev.carbon-project.org


Yesterday I filed [0] in Wine's bug tracker. But now, after some replies there
(works with the proprietary nVidia driver) and an apitrace [1] (over 200 MB,
please download it only, if you can help) I concluded with the awesome help of
José Fonseca, that the bug is most likely in the driver (please note, that it
is also possible, that the issue is lurking e.g. in the common Gallium3D code).

In short, when I start Dungeon Keeper 2 with Wine I see everything until the
intro/logo videos end and then are stuck with the last video frame. I don't get
to see the main menu. Even though the menu is rendered as can be seen from the
trace.
Replaying the trace with and without -sb doesn't make a difference. In both
cases the replay shows the menu, while a live Wine "window" does not.

Please let me know, if you need something else.

Used stack:
libdrm: 2.4.30-1
Mesa: master/0fcc5189 (r600g)
Linux: 3.2.3
DDX: 6.14.3 + commits from Git up until and including master/ae45d7e6
X.org: 1.11.3.901 (1.11.4 RC 1)
Hardware: 1002:9553
Wine: 1.4 RC2

[0] <http://bugs.winehq.org/show_bug.cgi?id=29802>
[1] <http://dev.carbon-project.org/debian/wine.bugs/29802/DK2.trace>

-- 
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