Bug 467755
Summary: | Speckled screen corruption while running firefox on an r530 based video card | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Bruno Wolff III <bruno> |
Component: | xorg-x11-drv-ati | Assignee: | X/OpenGL Maintenance List <xgl-maint> |
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | airlied, mads, xgl-maint |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-10-21 16:06:40 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Attachments: |
Description
Bruno Wolff III
2008-10-20 18:45:29 UTC
If X restarts can you get the /var/log/Xorg.0.log.old and dmesg if possible. Can you attach a normal Xorg log and dmesg now as well so I can see if I can reproduce. Created attachment 320931 [details]
Xorg.0.log probably from just after the restart
I think this is the Xorg.0.log from the unexpected restart. It has a timestamp from two minutes after the Xorg.0.old which seems close to the correct time. The timestamp on Xorg.0.old corresponds to the last reboot. (I'll be attaching that file next.)
Created attachment 320932 [details]
Xorg.0.log.old (probably from last reboot)
Created attachment 320934 [details]
dmesg from same time as previous xorg.log file
I am attaching the dmesg file which has a timestamp that matches (within a minute) that of the first Xorg.0.log file I attached (which is the latest one).
Created attachment 320937 [details]
Xorg.0.log after normal reboot
I did a reboot to get normal copies of Xorg.0.log and dmesg. I noticed Xorg.0.log.old had a timestamp from a couple of minutes before Xorg.0.log rather than that of the previous latest Xorg.0.log. I am not sure why that is. I didn't notice X start twice during the reboot and the difference seemed to large. Maybe the file was modified during shutdown.
Created attachment 320938 [details]
dmesg after normal reboot
I'll keep an eye on this, but I think it might be fixed now. Possibly the mesa update fixed it since I applied it last night and didn't see the problem while waiting to update the ati driver and the kernel. If it reoccurs I'll reopen the bug. Currently I am using: mesa-dri-drivers-7.2-0.12.fc10.x86_64 kernel-2.6.27.3-34.rc1.fc10.x86_64 xorg-x11-drv-ati-6.9.0-29.fc10.x86_64 Bruno, are you sure it is solved? It looks like a duplicate of Bug 466663, and there we agree that the situation has improved, but the problem hasn't been solved yet. I am not sure they were the same bug. Since I closed this bug I think I have seen odd glyphs for text two or three times that I didn't feel I knew enough about to open a bug for. The corruption I was seeing before seemed to cover rectangular shapes and was not just messed up glyphs. I haven't seen that reoccur. I'll add myself as a CC to 466663 and add comments if I see the problem again. There have already been two or three updates to xorg-x11-drv-ati (and some mesa updates) since I last saw the problem so I don't have anything to add right now. |