GoogleGit

blob: 55a6074ccbb715d99b642fa510d3c993121f453d [file] [log] [blame]
  1. [Some of this is taken from Frohwalt Egerer's original linux-kernel FAQ]
  2. What follows is a suggested procedure for reporting Linux bugs. You
  3. aren't obliged to use the bug reporting format, it is provided as a guide
  4. to the kind of information that can be useful to developers - no more.
  5. If the failure includes an "OOPS:" type message in your log or on
  6. screen please read "Documentation/oops-tracing.txt" before posting your
  7. bug report. This explains what you should do with the "Oops" information
  8. to make it useful to the recipient.
  9. Send the output to the maintainer of the kernel area that seems to
  10. be involved with the problem, and cc the relevant mailing list. Don't
  11. worry too much about getting the wrong person. If you are unsure send it
  12. to the person responsible for the code relevant to what you were doing.
  13. If it occurs repeatably try and describe how to recreate it. That is
  14. worth even more than the oops itself. The list of maintainers and
  15. mailing lists is in the MAINTAINERS file in this directory. If you
  16. know the file name that causes the problem you can use the following
  17. command in this directory to find some of the maintainers of that file:
  18. perl scripts/get_maintainer.pl -f <filename>
  19. If it is a security bug, please copy the Security Contact listed
  20. in the MAINTAINERS file. They can help coordinate bugfix and disclosure.
  21. See Documentation/SecurityBugs for more information.
  22. If you are totally stumped as to whom to send the report, send it to
  23. linux-kernel@vger.kernel.org. (For more information on the linux-kernel
  24. mailing list see http://www.tux.org/lkml/).
  25. This is a suggested format for a bug report sent to the Linux kernel mailing
  26. list. Having a standardized bug report form makes it easier for you not to
  27. overlook things, and easier for the developers to find the pieces of
  28. information they're really interested in. Don't feel you have to follow it.
  29. First run the ver_linux script included as scripts/ver_linux, which
  30. reports the version of some important subsystems. Run this script with
  31. the command "sh scripts/ver_linux".
  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. [1.] One line summary of the problem:
  36. [2.] Full description of the problem/report:
  37. [3.] Keywords (i.e., modules, networking, kernel):
  38. [4.] Kernel information
  39. [4.1.] Kernel version (from /proc/version):
  40. [4.2.] Kernel .config file:
  41. [5.] Most recent kernel version which did not have the bug:
  42. [6.] Output of Oops.. message (if applicable) with symbolic information
  43. resolved (see Documentation/oops-tracing.txt)
  44. [7.] A small shell script or example program which triggers the
  45. problem (if possible)
  46. [8.] Environment
  47. [8.1.] Software (add the output of the ver_linux script here)
  48. [8.2.] Processor information (from /proc/cpuinfo):
  49. [8.3.] Module information (from /proc/modules):
  50. [8.4.] Loaded driver and hardware information (/proc/ioports, /proc/iomem)
  51. [8.5.] PCI information ('lspci -vvv' as root)
  52. [8.6.] SCSI information (from /proc/scsi/scsi)
  53. [8.7.] Other information that might be relevant to the problem
  54. (please look in /proc and include all information that you
  55. think to be relevant):
  56. [X.] Other notes, patches, fixes, workarounds:
  57. Thank you