Commit | Line | Data |
---|---|---|
1da177e4 LT |
1 | [Some of this is taken from Frohwalt Egerer's original linux-kernel FAQ] |
2 | ||
3 | What follows is a suggested procedure for reporting Linux bugs. You | |
4 | aren't obliged to use the bug reporting format, it is provided as a guide | |
5 | to the kind of information that can be useful to developers - no more. | |
6 | ||
7 | If the failure includes an "OOPS:" type message in your log or on | |
8 | screen please read "Documentation/oops-tracing.txt" before posting your | |
9 | bug report. This explains what you should do with the "Oops" information | |
10 | to make it useful to the recipient. | |
11 | ||
9dcbb32f | 12 | Send the output to the maintainer of the kernel area that seems to |
3ab32df7 BF |
13 | be involved with the problem, and cc the relevant mailing list. Don't |
14 | worry too much about getting the wrong person. If you are unsure send it | |
15 | to the person responsible for the code relevant to what you were doing. | |
16 | If it occurs repeatably try and describe how to recreate it. That is | |
17 | worth even more than the oops itself. The list of maintainers and | |
503f7944 JP |
18 | mailing lists is in the MAINTAINERS file in this directory. If you |
19 | know the file name that causes the problem you can use the following | |
20 | command in this directory to find some of the maintainers of that file: | |
21 | perl scripts/get_maintainer.pl -f <filename> | |
1da177e4 LT |
22 | |
23 | If it is a security bug, please copy the Security Contact listed | |
24 | in the MAINTAINERS file. They can help coordinate bugfix and disclosure. | |
9dcbb32f | 25 | See Documentation/SecurityBugs for more information. |
1da177e4 LT |
26 | |
27 | If you are totally stumped as to whom to send the report, send it to | |
28 | linux-kernel@vger.kernel.org. (For more information on the linux-kernel | |
29 | mailing list see http://www.tux.org/lkml/). | |
30 | ||
9dcbb32f TK |
31 | This is a suggested format for a bug report sent to the Linux kernel mailing |
32 | list. Having a standardized bug report form makes it easier for you not to | |
33 | overlook things, and easier for the developers to find the pieces of | |
1da177e4 LT |
34 | information they're really interested in. Don't feel you have to follow it. |
35 | ||
36 | First run the ver_linux script included as scripts/ver_linux, which | |
37 | reports the version of some important subsystems. Run this script with | |
38 | the command "sh scripts/ver_linux". | |
39 | ||
40 | Use that information to fill in all fields of the bug report form, and | |
41 | post it to the mailing list with a subject of "PROBLEM: <one line | |
9dcbb32f | 42 | summary from [1.]>" for easy identification by the developers. |
1da177e4 | 43 | |
9dcbb32f | 44 | [1.] One line summary of the problem: |
1da177e4 LT |
45 | [2.] Full description of the problem/report: |
46 | [3.] Keywords (i.e., modules, networking, kernel): | |
4e229bef RD |
47 | [4.] Kernel information |
48 | [4.1.] Kernel version (from /proc/version): | |
49 | [4.2.] Kernel .config file: | |
30e835e3 AM |
50 | [5.] Most recent kernel version which did not have the bug: |
51 | [6.] Output of Oops.. message (if applicable) with symbolic information | |
1da177e4 | 52 | resolved (see Documentation/oops-tracing.txt) |
30e835e3 | 53 | [7.] A small shell script or example program which triggers the |
1da177e4 | 54 | problem (if possible) |
30e835e3 AM |
55 | [8.] Environment |
56 | [8.1.] Software (add the output of the ver_linux script here) | |
57 | [8.2.] Processor information (from /proc/cpuinfo): | |
58 | [8.3.] Module information (from /proc/modules): | |
59 | [8.4.] Loaded driver and hardware information (/proc/ioports, /proc/iomem) | |
60 | [8.5.] PCI information ('lspci -vvv' as root) | |
61 | [8.6.] SCSI information (from /proc/scsi/scsi) | |
62 | [8.7.] Other information that might be relevant to the problem | |
1da177e4 LT |
63 | (please look in /proc and include all information that you |
64 | think to be relevant): | |
65 | [X.] Other notes, patches, fixes, workarounds: | |
66 | ||
67 | ||
68 | Thank you |