| Summary: | X displays various artifacts, white lines all over the screen | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | xorg | Reporter: | Bryce Harrington <bryce> | ||||||||||||
| Component: | Driver/Radeon | Assignee: | xf86-video-ati maintainers <xorg-driver-ati> | ||||||||||||
| Status: | RESOLVED NOTABUG | QA Contact: | Xorg Project Team <xorg-team> | ||||||||||||
| Severity: | major | ||||||||||||||
| Priority: | high | CC: | 93fy5qj02 | ||||||||||||
| Version: | 7.4 (2008.09) | ||||||||||||||
| Hardware: | x86-64 (AMD64) | ||||||||||||||
| OS: | Linux (All) | ||||||||||||||
| Whiteboard: | |||||||||||||||
| i915 platform: | i915 features: | ||||||||||||||
| Attachments: |
|
||||||||||||||
|
Description
Bryce Harrington
2009-09-02 17:41:15 UTC
Created attachment 29134 [details]
Screenshot.png
Created attachment 29135 [details]
Screenshot.png (against jaunty)
Created attachment 29136 [details] [review] Xorg.0.log Created attachment 29137 [details] [review] dmesg please try with the latest git from master. make sure you have: 794ae743c305331741e7cf45dd71c755fe325ed5 A Ubuntu package of 794ae743 can be found in this PPA for testing: https://edge.launchpad.net/~xorg-edgers/+archive/ppa + xserver-xorg-video-ati - 1:6.12.99+git20090902.794ae743-0ubuntu0tormod Tested the package above; I still get the same screen corruption. Some additional info: I see two qualitatively different types of corruption: (A) dots, lines and patches in random places; and (B) flickering lines across the screen. I don't know if they have the same root cause or not. The screenshot from Jaunty has both, and I still see both with 794ae743. That said, "B" manifests less frequently (typically within a day or two, whereas "A" starts happening right away), and when "B" does happen, a logout attempt causes X to freeze with 100% CPU (logout works fine before then). Today when the B-type corruption manifested, I captured a syslog with DRM debugging before and after a logout attempt. The X freeze in response to logout seems to be the same problem as bug 23661. Attaching that syslog. Created attachment 29244 [details]
syslog with DRM debugging
"Corrupted" X freezes in response to logout attempt
Does: Option "DisplayPriority" "HIGH" in the device section of your config help? No; at least, I still see type "A" corruption right away. I can wait and see if type "B" still manifests eventually. By the way, I've already tried AGPMode -- that didn't help either (blank screen with AGPMode=2, same problems as before with 1,4,8). AGPmode won't do anything in your case as your card is not AGP. Please try the following options and see if any of them help: Option "DRI" "FALSE" Option "EXANoComposite" Option "EXANoUploadToScreen" Option "EXANoDownloadFromScreen" I've tried turning DRI off and that decreases, but does not eliminate corruption. In Jaunty, I saw corruption after about a month with DRI off, but with the latest snapshot I start seeing it after several minutes. Just to clarify, the corruption happens with both EXA and XAA. I normally use XAA because with EXA, X freezes very soon (bug 23661). I can try and see if the EXA options make a difference in EXA mode if that's what you want. With AccelMethod=exa, EXANoComposite, EXANoUploadToScreen and EXANoDownloadFromScreen, screen corruption remains the same. But I haven't seen X freeze so far. Did it ever work properly with older versions of X? Can you rule out a hardware problem, e.g. does it work in another operating system? There wasn't any corruption in Intrepid and before. It started when I upgraded to Jaunty. I'll see if I can confirm that with a live CD. It appears to be a hardware problem that developed over time. I rebooted into an old Fedora Core 9 installation with fglrx driver and now it also showed corruption, although less and different. A new graphics card (of a different model) works fine. I don't know for sure if bug 23661 was also caused by hardware (Fedora never froze), but it might as well be, and I won't be able to debug it anyway, so feel free to close it, too. Thanks for your patience with this. |
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.