How to debug Xorg problems

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
m (Rendering problems (fonts, garbaged text...))
(clean up)
Line 9: Line 9:
 
The following would be useful to attach to your bug report:
 
The following would be useful to attach to your bug report:
  
* all of the X server log file(s) {{filename|/var/log/Xorg.*.log}}
+
* All of the X server log file(s) {{filename|/var/log/Xorg.*.log}}
* your [http://smolts.org/ smolt profile]. You can dump it to {{filename|/tmp/smoltprofile.txt}} with the following command:
+
* Your [http://smolts.org/ smolt profile]. You can dump it to {{filename|/tmp/smoltprofile.txt}} with the following command:
 
  smoltSendProfile -p > /tmp/smoltprofile.txt
 
  smoltSendProfile -p > /tmp/smoltprofile.txt
* if you use a xorg.conf, please include it in the bug report, otherwise, please specify in the bug report that it does not.
+
* If you use a xorg.conf, please include it in the bug report, otherwise, please specify in the bug report that it does not exist. (Usually {{filename|/etc/X11/xorg.conf}} but see "man xorg.conf" for other standard locations.)
 
* {{filename|/var/log/Xorg.0.log}} from a trial run where you move {{filename|/etc/X11/xorg.conf}} aside and let Xorg autodetect your hardware (if you have such a file).
 
* {{filename|/var/log/Xorg.0.log}} from a trial run where you move {{filename|/etc/X11/xorg.conf}} aside and let Xorg autodetect your hardware (if you have such a file).
  
Line 21: Line 21:
 
== KMS problems (most Intel and AMD/Radeon hardware) ==
 
== KMS problems (most Intel and AMD/Radeon hardware) ==
  
Please add drm.debug=1 to the kernel command line, reboot and attach {{filename|/var/log/messages}} to your bug report.
+
Try modifying the kernel command line as described below; instructions are on the [[Xorg/KMS]] page if you don't know how to do that.
  
Additionally, please add nomodeset to the kernel command line and try to reproduce the problem, and include the following information:
+
Please add <code>drm.debug=1</code> to the kernel command line, reboot and attach {{filename|/var/log/messages}} to your bug report.
* if you were able to reproduce the problem or not
+
 
 +
Additionally, please add <code>nomodeset</code>
 +
to the kernel command line and try to reproduce the problem, and include the following information:
 +
* Whether you were able to reproduce the problem or not
 
* X server log file(s) {{filename|/var/log/Xorg.*.log}} (these are different in KMS and non-KMS mode, we may need both)
 
* X server log file(s) {{filename|/var/log/Xorg.*.log}} (these are different in KMS and non-KMS mode, we may need both)
to your bug report as well.
 
 
You can follow the instructions listed on the [[Xorg/KMS]] page to edit the kernel command line.
 
  
 
== OpenGL / Mesa problems ==
 
== OpenGL / Mesa problems ==
  
* glxinfo output
+
Add the following to your bug report in addition to the general items:
* a screenshot
+
 
* whether other OpenGL applications are able to run without problems
+
* Output of the command <code>glxinfo</code>
 +
* A screenshot
 +
* Indicate whether or not other OpenGL applications are able to run without problems.
  
 
== Creating a xorg.conf ==
 
== Creating a xorg.conf ==
  
If you need to make manual changes to X configuration, you will need to [[How_to_create_xorg.conf|create a xorg.conf]] file.
+
If you need to make manual changes to X configuration, you will need to [[How_to_create_xorg.conf|create a xorg.conf]] file if it doesn't already exist.
  
 
== Stack traces ==
 
== Stack traces ==
 +
 +
You will need a stack trace if your X server crashes.
  
 
See the [http://wiki.x.org/wiki/Development/Documentation/ServerDebugging documentation] on the upstream wiki.
 
See the [http://wiki.x.org/wiki/Development/Documentation/ServerDebugging documentation] on the upstream wiki.

Revision as of 01:39, 26 June 2009

Foreword

If you are experiencing a problem with Xorg, please see the Fedora 11 common bugs document before filing a bug. Some easy configuration tweaks that fix a wide range of issues are listed there. If the problem you are seeing is not listed there or none of the workarounds seem to help, please consider filing a bug to help us make Fedora run better on your hardware.

Be prepared to include some information (logs) about your system as well. These should be complete (no snippets please), not in an archive, uncompressed, with MIME type set as text/plain.

Contents

General bug reports

The following would be useful to attach to your bug report:

  • All of the X server log file(s) /var/log/Xorg.*.log
  • Your smolt profile. You can dump it to /tmp/smoltprofile.txt with the following command:
smoltSendProfile -p > /tmp/smoltprofile.txt
  • If you use a xorg.conf, please include it in the bug report, otherwise, please specify in the bug report that it does not exist. (Usually /etc/X11/xorg.conf but see "man xorg.conf" for other standard locations.)
  • /var/log/Xorg.0.log from a trial run where you move /etc/X11/xorg.conf aside and let Xorg autodetect your hardware (if you have such a file).

Rendering problems (unreadable text, corrupted display...)

All of the above, with a screenshot showing the problem if at all possible.

KMS problems (most Intel and AMD/Radeon hardware)

Try modifying the kernel command line as described below; instructions are on the Xorg/KMS page if you don't know how to do that.

Please add drm.debug=1 to the kernel command line, reboot and attach /var/log/messages to your bug report.

Additionally, please add nomodeset to the kernel command line and try to reproduce the problem, and include the following information:

  • Whether you were able to reproduce the problem or not
  • X server log file(s) /var/log/Xorg.*.log (these are different in KMS and non-KMS mode, we may need both)

OpenGL / Mesa problems

Add the following to your bug report in addition to the general items:

  • Output of the command glxinfo
  • A screenshot
  • Indicate whether or not other OpenGL applications are able to run without problems.

Creating a xorg.conf

If you need to make manual changes to X configuration, you will need to create a xorg.conf file if it doesn't already exist.

Stack traces

You will need a stack trace if your X server crashes.

See the documentation on the upstream wiki.