diff options
authorLinus Torvalds2005-04-16 17:20:36 -0500
committerLinus Torvalds2005-04-16 17:20:36 -0500
commit1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 (patch)
tree0bba044c4ce775e45a88a51686b5d9f90697ea9d /REPORTING-BUGS
Initial git repository build. I'm not bothering with the full history, even though we have it. We can create a separate "historical" git archive of that later if we want to, and in the meantime it's about 3.2GB when imported into git - space that would just make the early git days unnecessarily complicated, when we don't have a lot of good infrastructure for it. Let it rip!
Diffstat (limited to 'REPORTING-BUGS')
1 files changed, 61 insertions, 0 deletions
new file mode 100644
index 000000000000..2045eaea2d9e
--- /dev/null
@@ -0,0 +1,61 @@
1[Some of this is taken from Frohwalt Egerer's original linux-kernel FAQ]
3 What follows is a suggested procedure for reporting Linux bugs. You
4aren't obliged to use the bug reporting format, it is provided as a guide
5to the kind of information that can be useful to developers - no more.
7 If the failure includes an "OOPS:" type message in your log or on
8screen please read "Documentation/oops-tracing.txt" before posting your
9bug report. This explains what you should do with the "Oops" information
10to make it useful to the recipient.
12 Send the output the maintainer of the kernel area that seems to
13be involved with the problem. Don't worry too much about getting the
14wrong person. If you are unsure send it to the person responsible for the
15code relevant to what you were doing. If it occurs repeatably try and
16describe how to recreate it. That is worth even more than the oops itself.
17The list of maintainers is in the MAINTAINERS file in this directory.
19 If it is a security bug, please copy the Security Contact listed
20in the MAINTAINERS file. They can help coordinate bugfix and disclosure.
21See Documentation/SecurityBugs for more infomation.
23 If you are totally stumped as to whom to send the report, send it to
24linux-kernel@vger.kernel.org. (For more information on the linux-kernel
25mailing list see http://www.tux.org/lkml/).
27This is a suggested format for a bug report sent to the Linux kernel mailing
28list. Having a standardized bug report form makes it easier for you not to
29overlook things, and easier for the developers to find the pieces of
30information they're really interested in. Don't feel you have to follow it.
32 First run the ver_linux script included as scripts/ver_linux, which
33reports the version of some important subsystems. Run this script with
34the command "sh scripts/ver_linux".
36Use that information to fill in all fields of the bug report form, and
37post it to the mailing list with a subject of "PROBLEM: <one line
38summary from [1.]>" for easy identification by the developers
40[1.] One line summary of the problem:
41[2.] Full description of the problem/report:
42[3.] Keywords (i.e., modules, networking, kernel):
43[4.] Kernel version (from /proc/version):
44[5.] Output of Oops.. message (if applicable) with symbolic information
45 resolved (see Documentation/oops-tracing.txt)
46[6.] A small shell script or example program which triggers the
47 problem (if possible)
48[7.] Environment
49[7.1.] Software (add the output of the ver_linux script here)
50[7.2.] Processor information (from /proc/cpuinfo):
51[7.3.] Module information (from /proc/modules):
52[7.4.] Loaded driver and hardware information (/proc/ioports, /proc/iomem)
53[7.5.] PCI information ('lspci -vvv' as root)
54[7.6.] SCSI information (from /proc/scsi/scsi)
55[7.7.] Other information that might be relevant to the problem
56 (please look in /proc and include all information that you
57 think to be relevant):
58[X.] Other notes, patches, fixes, workarounds:
61Thank you