Switch branches/tags
wl18xx-r5-20120103 wl18xx-internal-2012-05-21 wl18xx-20120203 wl18xx-20120202 wl18xx-2012-07-08 wl18xx-2012-07-08-2 wl18xx-2012-04-04 wl18xx-2012-03-23 wl18xx-2012-03-22 wl18xx-2012-03-21 wl18xx-2012-03-20 wl18xx-2012-03-02 wl18xx-2012-02-28 wl18xx-2012-02-27 wl18xx-2012-02-22 wl18xx-2012-02-21 wl18xx-2012-02-15 wl18xx-2012-02-14 wl18xx-2012-02-09 wl18xx-2012-02-08 wl18xx-2012-02-07 wl18xx-2011-12-16 wl18xx-2011-12-15 wl18xx-2011-12-15-2 wl18xx-2011-12-14 wl18xx-2011-12-13 wl18xx-2011-12-08-pre-rebase wl18xx-2011-12-02 wl18xx-2011-12-02-3 wl18xx-2011-12-02-2 wl18xx-2011-12-01 wl18xx-2011-11-30 wl18xx-2011-11-29 wl18xx-2011-11-29-2 wl18xx-2011-11-22 wl18xx-2011-11-21 wl18xx-2011-11-19-blaze wl18xx-2011-11-17-blaze wl18xx-2011-11-14-blaze wl18xx-2011-11-14-2-blaze wl18xx-2011-11-04-blaze wl18xx-2011-10-11 wl18xx-02-20 upstreaming-2013-03-25 upstreaming-2013-03-07 upstreaming-2013-03-05 upstream-3.4 testing-2011-12-12 r8.a6.06_38 r8.a3.09-build_51 r8.a3.09-build_50 r8.a3.09-build_49 r8.a3.09-build_48 r8.a3.09-build_47 r8.a3.09-build_45 r8.a3.09-build_44 r8.a3.09-build_43 r8.a3.09-build_42 r8.a3.09-build_41 r8.a3.09-build_39 r8.a3.09-build_38 r8.a3.09-build_37 r8.a3.09-build_36 r8.a3.09-build_35 r8.a3.09-build_30 r8.a3.09-build_29 r8.a3.09-build_28 r8.a3.09-build_27 r8.a3.09-build_25 r8.a3.09-build_24 r8.a3.09-build_23 r8.a3.09-build_22 r8.a3.09-build_21 r8.a3.09-build_20 r8.a3.09-build_19 r8.a3.08-build_18 r8.a3.08-build_16 r8.a3.08-build_14 r8.a3.08-build_13 r8.a3.08-build_12 r8.a3.08-build_11 r8.a3.08-build_10 r8.a3.05-build_7 r8.a3.05-build_6 r8.a3.05-build_5 r8.a3.05-build_4 r8.a3.05-build_3 r8.a3.05-build_1 r8.a2.09 r8.a2.08 r8.a2.08-candidate r8.a2.07 r8.a2.07-build_146 r8.a2.07-build_141 r8.a2.07-build_140 r8.a2.07-build_139 r8.a2.07-build_136 r8.a2.06 r8.a2.05 r8.a2.04
Nothing to show
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
69 lines (57 sloc) 3.29 KB
[Some of this is taken from Frohwalt Egerer's original linux-kernel FAQ]
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:
perl scripts/ -f <filename>
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.
If you are totally stumped as to whom to send the report, send it to (For more information on the linux-kernel
mailing list see
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
information they're really interested in. Don't feel you have to follow it.
First run the ver_linux script included as scripts/ver_linux, which
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
summary from [1.]>" for easy identification by the developers.
[1.] One line summary of the problem:
[2.] Full description of the problem/report:
[3.] Keywords (i.e., modules, networking, kernel):
[4.] Kernel information
[4.1.] Kernel version (from /proc/version):
[4.2.] Kernel .config file:
[5.] Most recent kernel version which did not have the bug:
[6.] Output of Oops.. message (if applicable) with symbolic information
resolved (see Documentation/oops-tracing.txt)
[7.] A small shell script or example program which triggers the
problem (if possible)
[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
(please look in /proc and include all information that you
think to be relevant):
[X.] Other notes, patches, fixes, workarounds:
Thank you