Lines Matching refs:bug
12 If you've found a bug on a kernel version isn't listed on kernel.org,
15 kernels, and see if you can reproduce the bug on that. It's preferable
16 to reproduce the bug on the latest -rc kernel.
27 increases your chances of getting your bug fixed. Simply posting to the
28 generic linux-kernel mailing list (LKML) may cause your bug report to be
41 bug report. Some maintainers prefer bugs to be reported via bugzilla
45 To find out where to send an emailed bug report, find your subsystem or
47 entries, and send your bug report to the person(s) listed in the "M:"
56 If it is a security bug, please copy the Security Contact listed in the
61 a bug in kernel.org bugzilla and send email to
70 If you haven't reported a bug before, please read:
84 The most important information in a bug report is how to reproduce the
85 bug. This includes system information, and (most importantly)
86 step-by-step instructions for how a user can trigger the bug.
89 a netconsole trace, or type the message from your screen into the bug
91 bug report. This explains what you should do with the "Oops" information
94 This is a suggested format for a bug report sent via email or bugzilla.
95 Having a standardized bug report form makes it easier for you not to
98 relevant to your bug, feel free to exclude it.
104 Use that information to fill in all fields of the bug report form, and
114 [5.] Most recent kernel version which did not have the bug:
135 Expectations for bug reporters
138 Linux kernel maintainers expect bug reporters to be able to follow up on
139 bug reports. That may include running new tests, applying patches,
140 recompiling your kernel, and/or re-triggering your bug. The most
141 frustrating thing for maintainers is for someone to report a bug, and then
144 That said, it's still useful for a kernel maintainer to know a bug exists
147 kernel and I can't reproduce my bug anymore" are also helpful, because
154 they may not be able to address your bug in a day, a week, or two weeks.
163 have a high priority bug, please wait at least a week after the first bug
170 merge window), escalate the bug to LKML and Linus Torvalds.