001 [Some of this is taken from Frohwalt Egerer's original linux-kernel FAQ]
002
003 What follows is a suggested procedure for reporting Linux bugs. You
004 aren't obliged to use the bug reporting format, it is provided as a guide
005 to the kind of information that can be useful to developers - no more.
006
007 If the failure includes an "OOPS:" type message in your log or on
008 screen please read "Documentation/oops-tracing.txt" before posting your
009 bug report. This explains what you should do with the "Oops" information
010 to make it useful to the recipient.
011
012 Send the output to the maintainer of the kernel area that seems to
013 be involved with the problem, and cc the relevant mailing list. Don't
014 worry too much about getting the wrong person. If you are unsure send it
015 to the person responsible for the code relevant to what you were doing.
016 If it occurs repeatably try and describe how to recreate it. That is
017 worth even more than the oops itself. The list of maintainers and
018 mailing lists is in the MAINTAINERS file in this directory.
019
020 If it is a security bug, please copy the Security Contact listed
021 in the MAINTAINERS file. They can help coordinate bugfix and disclosure.
022 See Documentation/SecurityBugs for more information.
023
024 If you are totally stumped as to whom to send the report, send it to
025 linux-kernel@vger.kernel.org. (For more information on the linux-kernel
026 mailing list see http://www.tux.org/lkml/).
027
028 This is a suggested format for a bug report sent to the Linux kernel mailing
029 list. Having a standardized bug report form makes it easier for you not to
030 overlook things, and easier for the developers to find the pieces of
031 information they're really interested in. Don't feel you have to follow it.
032
033 First run the ver_linux script included as scripts/ver_linux, which
034 reports the version of some important subsystems. Run this script with
035 the command "sh scripts/ver_linux".
036
037 Use that information to fill in all fields of the bug report form, and
038 post it to the mailing list with a subject of "PROBLEM: <one line
039 summary from [1.]>" for easy identification by the developers.
040
041 [1.] One line summary of the problem:
042 [2.] Full description of the problem/report:
043 [3.] Keywords (i.e., modules, networking, kernel):
044 [4.] Kernel information
045 [4.1.] Kernel version (from /proc/version):
046 [4.2.] Kernel .config file:
047 [5.] Most recent kernel version which did not have the bug:
048 [6.] Output of Oops.. message (if applicable) with symbolic information
049 resolved (see Documentation/oops-tracing.txt)
050 [7.] A small shell script or example program which triggers the
051 problem (if possible)
052 [8.] Environment
053 [8.1.] Software (add the output of the ver_linux script here)
054 [8.2.] Processor information (from /proc/cpuinfo):
055 [8.3.] Module information (from /proc/modules):
056 [8.4.] Loaded driver and hardware information (/proc/ioports, /proc/iomem)
057 [8.5.] PCI information ('lspci -vvv' as root)
058 [8.6.] SCSI information (from /proc/scsi/scsi)
059 [8.7.] Other information that might be relevant to the problem
060 (please look in /proc and include all information that you
061 think to be relevant):
062 [X.] Other notes, patches, fixes, workarounds:
063
064
065 Thank you
