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 you are totally stumped as to whom to send the report, send it to (For more information on the linux-kernel
  21mailing list see
  23This is a suggested format for a bug report sent to the Linux kernel mailing 
  24list. Having a standardized bug report form makes it easier  for you not to 
  25overlook things, and easier for the developers to find the pieces of 
  26information they're really interested in. Don't feel you have to follow it.
  28      First run the ver_linux script included as scripts/ver_linux, which
  29reports the version of some important subsystems.  Run this script with
  30the command "sh scripts/ver_linux".
  32Use that information to fill in all fields of the bug report form, and
  33post it to the mailing list with a subject of "PROBLEM: <one line
  34summary from [1.]>" for easy identification by the developers    
  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:
  57Thank you
  58 kindly hosted by Redpill Linpro AS, provider of Linux consulting and operations services since 1995.