Version:  2.0.40 2.2.26 2.4.37 3.13 3.14 3.15 3.16 3.17 3.18 3.19 4.0 4.1 4.2 4.3 4.4 4.5 4.6 4.7 4.8 4.9 4.10

Linux/REPORTING-BUGS

  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 
 12       Send the output to the maintainer of the kernel area that seems to
 13 be involved with the problem. Don't worry too much about getting the
 14 wrong person. If you are unsure send it to the person responsible for the
 15 code relevant to what you were doing. If it occurs repeatably try and
 16 describe how to recreate it. That is worth even more than the oops itself.
 17 The list of maintainers is in the MAINTAINERS file in this directory.
 18 
 19       If you are totally stumped as to whom to send the report, send it to
 20 linux-kernel@vger.kernel.org. (For more information on the linux-kernel
 21 mailing list see http://www.tux.org/lkml/).
 22 
 23 This is a suggested format for a bug report sent to the Linux kernel mailing 
 24 list. Having a standardized bug report form makes it easier  for you not to 
 25 overlook things, and easier for the developers to find the pieces of 
 26 information they're really interested in. Don't feel you have to follow it.
 27 
 28       First run the ver_linux script included as scripts/ver_linux, which
 29 reports the version of some important subsystems.  Run this script with
 30 the command "sh scripts/ver_linux".
 31 
 32 Use that information to fill in all fields of the bug report form, and
 33 post it to the mailing list with a subject of "PROBLEM: <one line
 34 summary from [1.]>" for easy identification by the developers    
 35 
 36 [1.] One line summary of the problem:    
 37 [2.] Full description of the problem/report:
 38 [3.] Keywords (i.e., modules, networking, kernel):
 39 [4.] Kernel version (from /proc/version):
 40 [5.] Output of Oops.. message (if applicable) with symbolic information 
 41      resolved (see Documentation/oops-tracing.txt)
 42 [6.] A small shell script or example program which triggers the
 43      problem (if possible)
 44 [7.] Environment
 45 [7.1.] Software (add the output of the ver_linux script here)
 46 [7.2.] Processor information (from /proc/cpuinfo):
 47 [7.3.] Module information (from /proc/modules):
 48 [7.4.] Loaded driver and hardware information (/proc/ioports, /proc/iomem)
 49 [7.5.] PCI information ('lspci -vvv' as root)
 50 [7.6.] SCSI information (from /proc/scsi/scsi)
 51 [7.7.] Other information that might be relevant to the problem
 52        (please look in /proc and include all information that you
 53        think to be relevant):
 54 [X.] Other notes, patches, fixes, workarounds:
 55 
 56 
 57 Thank you

This page was automatically generated by LXR 0.3.1 (source).  •  Linux is a registered trademark of Linus Torvalds  •  Contact us