Summary: | r600g doesn't seem to flush when it should → visual stuck | ||
---|---|---|---|
Product: | Mesa | Reporter: | Kai <kai> |
Component: | Drivers/Gallium/r600 | Assignee: | Default DRI bug account <dri-devel> |
Status: | RESOLVED MOVED | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | sa, spacey500 |
Version: | git | ||
Hardware: | Other | ||
OS: | All | ||
URL: | http://bugs.winehq.org/show_bug.cgi?id=29802 | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Kai
2012-02-06 10:10:33 UTC
Please attach your xorg log and dmesg output. (In reply to comment #1) > Please attach your xorg log and dmesg output. Here you go: Xorg.log: <http://dev.carbon-project.org/debian/wine.bugs/29802/fdo%2345709.Xorg.0.log.xz> dmesg: <http://dev.carbon-project.org/debian/wine.bugs/29802/fdo%2345709.dmesg.xz> Does the game work with softpipe or llvmpipe (it might be unplayably slow but will tell if you if it's r600g specific or a common problem in G3D). Does it work with stable Mesa, 7.11.2? If it is a regression it might be similar to bug 44647, that one is caused by a removed flush. (In reply to comment #3) > Does it work with stable Mesa, 7.11.2? > > If it is a regression it might be similar to bug 44647, that one is caused by a > removed flush. No, 7.11.2 shows the same behaviour. Just FYI: I can't test this anylonger since I no longer have a r600g-driven ASIC around. I experience the same behavior, trying to run Dungeon Keeper 2 under wine. Used stack: libdrm: 2.4.50 Mesa: 10.0.0 (r600g) Linux: 3.12.0 DDX: 7.2.0 X.org: 14.3-r2 Hardware: 1002:9710 (RS880 [Radeon HD 4200]) Wine: 1.7.4 -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/403. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.