[Some of this is taken from Frohwalt Egerer's original linux-kernel FAQ]     What follows is a suggested procedure for reporting Linux bugs. Youaren't obliged to use the bug reporting format, it is provided as a guideto the kind of information that can be useful to developers - no more.     If the failure includes an "OOPS:" type message in your log or onscreen please read "Documentation/oops-tracing.txt" before posting yourbug report. This explains what you should do with the "Oops" informationto make it useful to the recipient.      Send the output the maintainer of the kernel area that seems tobe involved with the problem. Don't worry too much about getting thewrong person. If you are unsure send it to the person responsible for thecode relevant to what you were doing. If it occurs repeatably try anddescribe how to recreate it. That is worth even more than the oops itself.The list of maintainers is in the MAINTAINERS file in this directory.      If you are totally stumped as to whom to send the report, send it tolinux-kernel@vger.kernel.org. (For more information on the linux-kernelmailing list see http://www.tux.org/lkml/).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, whichreports the version of some important subsystems.  Run this script withthe command "sh scripts/ver_linux".Use that information to fill in all fields of the bug report form, andpost it to the mailing list with a subject of "PROBLEM: <one linesummary 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 version (from /proc/version):[5.] Output of Oops.. message (if applicable) with symbolic information      resolved (see Documentation/oops-tracing.txt)[6.] A small shell script or example program which triggers the     problem (if possible)[7.] Environment[7.1.] Software (add the output of the ver_linux script here)[7.2.] Processor information (from /proc/cpuinfo):[7.3.] Module information (from /proc/modules):[7.4.] Loaded driver and hardware information (/proc/ioports, /proc/iomem)[7.5.] PCI information ('lspci -vvv' as root)[7.6.] SCSI information (from /proc/scsi/scsi)[7.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