After enabling "exa" acceleration on my "IBM ThinkPad T23", screen corruption occurs [see attached screenshot]. The system is running "Xorg 7.2" as part of the current "Fedora Core" development tree. After commenting out the "exa" entry, the screen is rendered correctly again.
Created attachment 8782 [details] "Xorg 7.2" configuration file for "SuperSavage/IXC 64"
Created attachment 8783 [details] "Xorg 7.2" log file for "SuperSavage/IXC 64"
Created attachment 8784 [details] "Xorg 7.2" screenshot for "SuperSavage/IXC 64" showing screen corruption
Does the corruption go away if you return false from the copy() or UTS() functions?
(In reply to comment #4) > Does the corruption go away if you return false from the copy() or UTS() > functions? > Argh... not copy, solid. doe sit still give you problem if you return false is in SavagePrepareSolid() or SavageUploadToScreen(). you might as well check copy too...
(In reply to comment #4) > Does the corruption go away if you return false from the copy() or UTS() Huh? You mean in the driver source code?
(In reply to comment #6) > (In reply to comment #4) > > Does the corruption go away if you return false from the copy() or UTS() > > Huh? You mean in the driver source code? > yes in the savage source. see my post above.
Sorry about the phenomenal bug spam, guys. Adding xorg-team@ to the QA contact so bugs don't get lost in future.
(In reply to comment #5) > Argh... not copy, solid. Does it still give you problem if you return false > in SavagePrepareSolid() or SavageUploadToScreen()? You might as well check > copy too... No luck here. I've tried various combinations in "savage_exa.c" but the only result is a badly unresponsive system.
This should be fixed in savage git head.
Closing as per Alex's comments. Reopen if not fixed.
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.