REPORTING-BUGS 3.3 KB
Newer Older
L
Linus Torvalds 已提交
1 2
[Some of this is taken from Frohwalt Egerer's original linux-kernel FAQ]

3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
What follows is a suggested procedure for reporting Linux bugs. You aren't
obliged to use the bug reporting format, it is provided as a guide to the
kind of information that can be useful to developers - no more.

If the failure includes an "OOPS:" type message in your log or on screen
please read "Documentation/oops-tracing.txt" before posting your bug
report. This explains what you should do with the "Oops" information to
make it useful to the recipient.

Send the output to the maintainer of the kernel area that seems to be
involved with the problem, and cc the relevant mailing list. Don't worry
too much about getting the wrong person. If you are unsure send it to the
person responsible for the code relevant to what you were doing.  If it
occurs repeatably try and describe how to recreate it. That is worth even
more than the oops itself.  The list of maintainers and mailing lists is
in the MAINTAINERS file in this directory.  If you know the file name that
causes the problem you can use the following command in this directory to
find some of the maintainers of that file:

22
     perl scripts/get_maintainer.pl -f <filename>
L
Linus Torvalds 已提交
23

24 25 26
If it is a security bug, please copy the Security Contact listed in the
MAINTAINERS file.  They can help coordinate bugfix and disclosure.  See
Documentation/SecurityBugs for more information.
L
Linus Torvalds 已提交
27

28
If you are totally stumped as to whom to send the report, send it to
L
Linus Torvalds 已提交
29 30 31
linux-kernel@vger.kernel.org. (For more information on the linux-kernel
mailing list see http://www.tux.org/lkml/).

32 33 34
This is a suggested format for a bug report sent to the Linux kernel mailing
list. Having a standardized bug report form makes it easier for you not to
overlook things, and easier for the developers to find the pieces of
L
Linus Torvalds 已提交
35 36
information they're really interested in. Don't feel you have to follow it.

37
First run the ver_linux script included as scripts/ver_linux, which
L
Linus Torvalds 已提交
38 39 40 41 42
reports the version of some important subsystems.  Run this script with
the command "sh scripts/ver_linux".

Use that information to fill in all fields of the bug report form, and
post it to the mailing list with a subject of "PROBLEM: <one line
43
summary from [1.]>" for easy identification by the developers.
L
Linus Torvalds 已提交
44

45
[1.] One line summary of the problem:
L
Linus Torvalds 已提交
46 47
[2.] Full description of the problem/report:
[3.] Keywords (i.e., modules, networking, kernel):
48 49 50
[4.] Kernel information
[4.1.] Kernel version (from /proc/version):
[4.2.] Kernel .config file:
51 52
[5.] Most recent kernel version which did not have the bug:
[6.] Output of Oops.. message (if applicable) with symbolic information
L
Linus Torvalds 已提交
53
     resolved (see Documentation/oops-tracing.txt)
54
[7.] A small shell script or example program which triggers the
L
Linus Torvalds 已提交
55
     problem (if possible)
56 57 58 59 60 61 62 63
[8.] Environment
[8.1.] Software (add the output of the ver_linux script here)
[8.2.] Processor information (from /proc/cpuinfo):
[8.3.] Module information (from /proc/modules):
[8.4.] Loaded driver and hardware information (/proc/ioports, /proc/iomem)
[8.5.] PCI information ('lspci -vvv' as root)
[8.6.] SCSI information (from /proc/scsi/scsi)
[8.7.] Other information that might be relevant to the problem
L
Linus Torvalds 已提交
64 65 66 67 68 69
       (please look in /proc and include all information that you
       think to be relevant):
[X.] Other notes, patches, fixes, workarounds:


Thank you