Summary: | [XAA] garbled screen with compiz but no KMS on ATI Radeon Mobility 7500 | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | Bryce Harrington <bryce> | ||||||||||||
Component: | Driver/Radeon | Assignee: | xf86-video-ati maintainers <xorg-driver-ati> | ||||||||||||
Status: | RESOLVED FIXED | QA Contact: | Xorg Project Team <xorg-team> | ||||||||||||
Severity: | major | ||||||||||||||
Priority: | high | CC: | jamie | ||||||||||||
Version: | 7.4 (2008.09) | Keywords: | regression | ||||||||||||
Hardware: | x86 (IA32) | ||||||||||||||
OS: | Linux (All) | ||||||||||||||
Whiteboard: | |||||||||||||||
i915 platform: | i915 features: | ||||||||||||||
Attachments: |
|
Description
Bryce Harrington
2010-03-17 19:07:05 UTC
Created attachment 34181 [details]
compiz_and_no_kms_garbled_screen.png
Created attachment 34182 [details]
XorgLog.txt
Created attachment 34183 [details]
XorgLogOld.txt
Created attachment 34184 [details]
BootDmesg.txt
Created attachment 34185 [details]
CurrentDmesg.txt
isn't KMS + EXA + metacity stable? I've gone ahead and disabled XAA render accel, it's been broken in the xserver for a while now. 5c256808cb5fea955eea96ffe9196473715156aa > isn't KMS + EXA + metacity stable?
Jamie was saying that this particular configuration led to gpu lockups after a few hours of use. However I do not know if this configuration got re-tested with the 2.6.33 drm backport.
Jamie, you indicated the lockup issue still exists with KMS/XAA/compiz, and the compiz crash still occurs for KMS/EXA/compiz. Can you confirm that the KMS/EXA/metacity combo works, or does it still freeze after a few hours?
XAA/metacity/RenderAccel off/no KMS has been the only stable configuration for my system. KMS/EXA/metacity locks up, though not as often as with compiz. When I retested everything with the recent .33 backported DRM, I did not specifically test KMS/EXA/metacity since KMS/EXA/compiz was still broken. I lent my laptop to a member of Canonical's kernel team for testing fixes/reproducing. I can follow up with him to test this configuration if required. (In reply to comment #9) > XAA/metacity/RenderAccel off/no KMS has been the only stable configuration for > my system. KMS/EXA/metacity locks up, though not as often as with compiz. When > I retested everything with the recent .33 backported DRM, I did not > specifically test KMS/EXA/metacity since KMS/EXA/compiz was still broken. Do the patches in bug 26302 help with kms? Alex, The patches from 26302 *do* help. Quoting me from that bug: "These patches resolve this issue completely. After a lot of automated testing and many hours of real world use with up to date packages that include these fixes, it no longer crashes. Thanks to everyone who helped fix this. :) From our kernel changelog: [ Upstream Kernel Changes ] ... * drm/radeon/bo: add some fallback placements for VRAM only objects. - LP: #507148 * drm/radeon/kms: don't print error on -ERESTARTSYS. - LP: #507148 ... " I've not specifically testing KMS with XAA, but KMS with EXA/compiz works well now. (In reply to comment #11) > > I've not specifically testing KMS with XAA, but KMS with EXA/compiz works well > now. XAA doesn't work with kms, so there's nothing to test :) |
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.