Summary: | Screen corruption in xterms with i810 and XAA | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | David Krause <freedesktop> | ||||||||||||
Component: | Driver/intel | Assignee: | Alan Hourihane <alanh> | ||||||||||||
Status: | RESOLVED DUPLICATE | QA Contact: | |||||||||||||
Severity: | normal | ||||||||||||||
Priority: | high | CC: | matthieu.herrb | ||||||||||||
Version: | 6.9.0 | ||||||||||||||
Hardware: | x86 (IA32) | ||||||||||||||
OS: | OpenBSD | ||||||||||||||
Whiteboard: | |||||||||||||||
i915 platform: | i915 features: | ||||||||||||||
Attachments: |
|
Description
David Krause
2006-02-05 01:17:04 UTC
Created attachment 4551 [details]
dmesg
Created attachment 4552 [details]
Xorg.0.log
Created attachment 4553 [details]
xorg.conf
Created attachment 4554 [details]
xterm screenshot showing the problem
I wonder if there's some kind of compiler optimization bug here as the XAA code hasn't changed much and the i810's XAA driver code hasn't changed at all between the two releases. What compiler did you use to compile 6.8.2 and 6.9.0 ?? As another test, could you take the XAA module from 6.8.2 and see if it corrects the problem in 6.9.0 ? Actually, looking at your log. I think this is pretty close to bug #5443. Can you try the patches in this bug noted in comment #49 ? I tried those patches and I don't see the corruption with them. I will attach a new log file also. Created attachment 4570 [details] Xorg.0.log with the patches from bug 5443 *** This bug has been marked as a duplicate of 5443 *** (In reply to comment #7) > I tried those patches and I don't see the corruption with them. I will attach a > new log file also. David, can you send me a cvs diff against the OpenBSD XF4 tree with the patches you applied ? If this includes commenting out xf86ValidatePci(), I'm a bit worried, because this is a fairly intrusive change. I don't think it can be applied as is. |
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.