Bug 692250

Summary: Screen corruption accompanied by kernel warning.
Product: [Fedora] Fedora Reporter: Ralph Loader <suckfish>
Component: xorg-x11-drv-atiAssignee: Jérôme Glisse <jglisse>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: bugzilla, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, mcepl, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-05-19 06:08:47 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Relevant part of /var/log/messages. none

Description Ralph Loader 2011-03-30 19:47:21 UTC 
Created attachment 488889 [details]
Relevant part of /var/log/messages.

Soon after booting into 2.6.38.2-8.fc15.x86_64 I experienced a sudden screen corruption (fonts and some colours messed up).

The attached file is a kernel WARNING that ended up in /var/log/messages at the same time.

This was a short while after interrupting xscreensaver while it was running a 3D screensaver.  I'm guessing that a 3D app terminated by a signal isn't being cleaned up correctly?

It is possible that this is related to bug 690977 (occurred on same machine).
Comment 1 Ralph Loader 2011-03-30 19:49:27 UTC 
System seemed to recover fine; after causing windows to repaint the visible symptoms disappeared.
Comment 2 Matěj Cepl 2011-04-13 17:07:04 UTC 
Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.

Please add drm.debug=0x04 to the kernel command line, restart computer, and attach

* your X server config file (/etc/X11/xorg.conf, if available),
* X server log file (/var/log/Xorg.*.log), and
* output of the dmesg command (if you are able to reproduce the issue, otherwise don't bother)

to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.
Comment 3 Jason Smith 2012-05-19 06:08:47 UTC 
    The information we've requested above is required in order to review this problem report further and diagnose or fix the issue if it is still present. Since it has been thirty days or more since we first requested additional information, we're assuming the problem is either no longer present in the current Fedora release, or that there is no longer any interest in tracking the problem. 

    Setting status to "CLOSED: INSUFFICIENT_DATA". If you still experience this problem after updating to our latest Fedora release and can provide the information previously requested, please feel free to reopen the bug report.

Thank you.

---
Jason
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers