From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 45709] New: r600g doesn't seem to flush when it should → visual stuck
Date: Mon, 06 Feb 2012 18:10:33 +0000 [thread overview]
Message-ID: <bug-45709-502@http.bugs.freedesktop.org/> (raw)
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@lists.freedesktop.org
ReportedBy: kai@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.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2012-02-06 18:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-06 18:10 bugzilla-daemon [this message]
2012-02-06 20:41 ` [Bug 45709] r600g doesn't seem to flush when it should → visual stuck bugzilla-daemon
2012-02-06 20:55 ` bugzilla-daemon
2012-02-06 21:56 ` bugzilla-daemon
2012-02-07 17:22 ` bugzilla-daemon
2013-11-19 13:36 ` bugzilla-daemon
2013-12-09 11:40 ` bugzilla-daemon
2019-09-18 18:59 ` 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-45709-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.