Commit 85163107 authored by Joe Rayhawk's avatar Joe Rayhawk
Browse files

moin2mdwn: convert page Bugs

parent 3fe7159d
First, go through the basic questions of [[TroubleShooting|TroubleShooting]].
If you are using packages from your distribution, send the bug reports to your distribution and not directly to us.
We use [[FreeDesktop Bugzilla|https://bugs.freedesktop.org]]. Bugs [[in the 2D driver|https://bugs.freedesktop.org/buglist.cgi?product=xorg&component=Driver%2Fnouveau]] and the Nouveau DRM (kernel) part are filed under product “xorg”, component “Driver/nouveau” ([[statistics|https://bugs.freedesktop.org/report.cgi?x_axis_field=resolution&y_axis_field=bug_status&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&component=Driver%2Fnouveau&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0=]]). Feel free to submit bugs about 2D implementation, but please search the bugzilla before submitting new bugs. If you are not sure your bug is a manifestation of an existing bug report, do open a new bug.
Bugs [[in the 3D driver|https://bugs.freedesktop.org/buglist.cgi?product=Mesa&component=Drivers%2FDRI%2Fnouveau]] are under product “Mesa”, component “Drivers/DRI/nouveau” ([[statistics|https://bugs.freedesktop.org/report.cgi?x_axis_field=resolution&y_axis_field=bug_status&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&component=Drivers%2FDRI%2Fnouveau&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0=]]). Please, check [[MesaDrivers|MesaDrivers]] page before submitting any reports.
<a name="HowToReport"></a> How to report?
* Attach **complete, unfiltered, untrimmed kernel log** from the boot up to and including the problem, and a complete X log if the problem manifests with X. Note, that `/var/log/messages` is not a kernel log. Running `dmesg` is the best way to get a kernel log, but assuming, that the log buffer has not wrapped around.
* Please, **do not compress files** you attach to bug reports, especially plain text files such as logs, unless the file is so huge bugzilla refuses to take it. Gzipping files makes taking a quick look impossible
* Make sure the **mime-type** of text files really is set to **`text/plain`**, and not e.g. `application/octet-stream` or `text/x-log`. This makes life a little easier for people reading bug reports. The point is to let people read text files directly in a web browser.
* Please include **version numbers or checkout dates** for all relevant components. This could be the kernel and DRM, x-server, xf86-video-nouveau, libdrm and possibly mesa.
* Do not use **links that go invalid** in time (e.g., pastebins, image bins, your web server at home), attach your files to the bug instead. Bug reports may be useful even after years.
* If the bug is related to modesetting, output configuration, etc, please attach [[VBIOS|DumpingVideoBios]] from your card.
We also have a [[mailing list|http://lists.freedesktop.org/mailman/listinfo/nouveau]] where you can ask questions, discuss patches or whatever is related to nouveau and its tools.
<a name="KernelLog"></a>
## Getting a kernel log
### Quick guide
1. add the following to the kernel command line: `log_buf_len=1M`
1. exercise your problem
1. run the command: `dmesg > kernel_log.txt`
1. use the file `kernel_log.txt` created above in your bug report, remember to set the MIME type to `text/plain` in bugzilla/email attachment
### Explanation
The best way is to use `dmesg` command and direct the output to a file. A problem with dmesg is, that it uses the kernel log buffer, which may wrap around. Therefore, use `log_buf_len=1M` on the kernel command line to increase the log buffer size to 1MB. The wraparound can be noticed by looking at the first lines in a dmesg output, it should be something like this (may vary according to kernel version):
[[!format txt """
[ 0.000000] Linux version 2.6.34-gentoo-r1 (root@localhost) (gcc version 4.3.4 (Gentoo 4.3.4 p1.1, pie-10.1.5) ) #1 PREEMPT Mon Aug 2 16:04:12 EEST 2010
[ 0.000000] Command line: root=/dev/sda5
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
[ 0.000000] BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
"""]]
The benefits of using `dmesg` command are:
* you get all kernel messages, also from debug level
* you get only kernel messages, without noise from user space like in system logger files
* you get messages from this boot only, no need to cut other boots out of the file
* it is what the developers expect to see
It is really the command `dmesg` to be used. A file like `/var/log/dmesg.log` or similar is **not** what we need.
First, go through the basic questions of TroubleShooting.
If you are using packages from your distribution, send the bug reports to your distribution and not directly to us.
We use [[https://bugs.freedesktop.org|FreeDesktop Bugzilla]]. Bugs [[https://bugs.freedesktop.org/buglist.cgi?product=xorg&component=Driver%2Fnouveau|in the 2D driver]] and the Nouveau DRM (kernel) part are filed under product “xorg”, component “Driver/nouveau” ([[https://bugs.freedesktop.org/report.cgi?x_axis_field=resolution&y_axis_field=bug_status&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&component=Driver%2Fnouveau&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0=|statistics]]).
Feel free to submit bugs about 2D implementation, but please search the bugzilla before submitting new bugs. If you are not sure your bug is a manifestation of an existing bug report, do open a new bug.
Bugs [[https://bugs.freedesktop.org/buglist.cgi?product=Mesa&component=Drivers%2FDRI%2Fnouveau|in the 3D driver]] are under product “Mesa”, component “Drivers/DRI/nouveau” ([[https://bugs.freedesktop.org/report.cgi?x_axis_field=resolution&y_axis_field=bug_status&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&component=Drivers%2FDRI%2Fnouveau&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0=|statistics]]). Please, check MesaDrivers page before submitting any reports.
<<Anchor(HowToReport)>>
How to report?
* Attach '''complete, unfiltered, untrimmed kernel log''' from the boot up to and including the problem, and a complete X log if the problem manifests with X. Note, that {{{/var/log/messages}}} is not a kernel log. Running {{{dmesg}}} is the best way to get a kernel log, but assuming, that the log buffer has not wrapped around.
* Please, '''do not compress files''' you attach to bug reports, especially plain text files such as logs, unless the file is so huge bugzilla refuses to take it. Gzipping files makes taking a quick look impossible
* Make sure the '''mime-type''' of text files really is set to '''{{{text/plain}}}''', and not e.g. {{{application/octet-stream}}} or {{{text/x-log}}}. This makes life a little easier for people reading bug reports. The point is to let people read text files directly in a web browser.
* Please include '''version numbers or checkout dates''' for all relevant components. This could be the kernel and DRM, x-server, xf86-video-nouveau, libdrm and possibly mesa.
* Do not use '''links that go invalid''' in time (e.g., pastebins, image bins, your web server at home), attach your files to the bug instead. Bug reports may be useful even after years.
* If the bug is related to modesetting, output configuration, etc, please attach [[DumpingVideoBios|VBIOS]] from your card.
We also have a [[http://lists.freedesktop.org/mailman/listinfo/nouveau|mailing list]] where you can ask questions, discuss patches or whatever is related to nouveau and its tools.
<<Anchor(KernelLog)>>
== Getting a kernel log ==
=== Quick guide ===
1. add the following to the kernel command line: {{{log_buf_len=1M}}}
1. exercise your problem
1. run the command: {{{dmesg > kernel_log.txt}}}
1. use the file {{{kernel_log.txt}}} created above in your bug report, remember to set the MIME type to {{{text/plain}}} in bugzilla/email attachment
=== Explanation ===
The best way is to use {{{dmesg}}} command and direct the output to a file. A problem with dmesg is, that it uses the kernel log buffer, which may wrap around. Therefore, use {{{log_buf_len=1M}}} on the kernel command line to increase the log buffer size to 1MB. The wraparound can be noticed by looking at the first lines in a dmesg output, it should be something like this (may vary according to kernel version):
{{{
[ 0.000000] Linux version 2.6.34-gentoo-r1 (root@localhost) (gcc version 4.3.4 (Gentoo 4.3.4 p1.1, pie-10.1.5) ) #1 PREEMPT Mon Aug 2 16:04:12 EEST 2010
[ 0.000000] Command line: root=/dev/sda5
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
[ 0.000000] BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
}}}
The benefits of using {{{dmesg}}} command are:
* you get all kernel messages, also from debug level
* you get only kernel messages, without noise from user space like in system logger files
* you get messages from this boot only, no need to cut other boots out of the file
* it is what the developers expect to see
It is really the command {{{dmesg}}} to be used. A file like {{{/var/log/dmesg.log}}} or similar is '''not''' what we need.
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment