What information should go in a bug report?
• (ADB) Does it affect system security? Is it related to a specific driver/hardware configuration? Did you manage to identify the piece(s) of kernel code concerned? It really depends on the kind of bug you found. • (TYT) Please follow general good bug reporting guidelines: remember, the developers don’t have access to your system, and they’re not mind readers. Tell us which kernel version, and what your hardware is (if you’re not sure, more detail is better than less). At the very least, tell us what processor and motherboard you have, how much memory, how many and what kind of disks (IDE, SCSI, etc.), what kind of disk controllers you have, what other expansion boards (specify whether they’re PCI or ISA or some other bus). Also useful: what version of gcc and binutils were used to compile the kernel. Try to find a simple, reliable way to trigger the problem.
• (ADB) Does it affect system security? Is it related to a specific driver/hardware configuration? Did you manage to identify the piece(s) of kernel code concerned? It really depends on the kind of bug you found. • (TYT) Please follow general good bug reporting guidelines: remember, the developers don’t have access to your system, and they’re not mind readers. Tell us which kernel version, and what your hardware is (if you’re not sure, more detail is better than less). At the very least, tell us what processor and motherboard you have, how much memory, how many and what kind of disks (IDE, SCSI, etc.), what kind of disk controllers you have, what other expansion boards (specify whether they’re PCI or ISA or some other bus). Also useful: what version of gcc and binutils were used to compile the kernel. Try to find a simple, reliable way to trigger the problem. Telling the developer that they have to set up some complicated application environment (especially if it involves some ghastly
