Lines Matching refs:issues
4 Reporting issues
40 If you are facing multiple issues with the Linux kernel at once, report each
51 Step-by-step guide how to report issues to the kernel maintainers
54 The above TL;DR outlines roughly how to report issues to the Linux kernel
56 reporting issues to Free/Libre & Open Source Software (FLOSS) projects. For
72 will often be needed anyway to hunt down and fix issues.
80 issue, or a really severe problem: those are 'issues of high priority' that
96 issues at once, create separate notes for each of them and make sure they
107 time this won't be bugzilla.kernel.org, as issues typically need to be sent
129 up there, scroll down to the instructions for issues only happening with
156 you are dealing with one of those 'issues of high priority': they need
158 issues' below.
203 Reporting issues only occurring in older kernel version lines
234 Reference section: Reporting issues to the kernel maintainers
272 issues to the Linux kernel developers.
282 will often be needed anyway to hunt down and fix issues.*
285 with reports for issues that don't even happen with their current code. It's
294 Most of these vendor kernels are quite unsuitable for reporting issues to the
299 issues with these kernels to the vendor. Its developers should look into the
308 developers in fact are willing to handle reports about issues occurring with
313 Sid or Fedora Rawhide. Some developers will also accept reports about issues
381 issue, or a really severe problem: those are 'issues of high priority' that
384 Linus Torvalds and the leading Linux kernel developers want to see some issues
385 fixed as soon as possible, hence there are 'issues of high priority' that get
387 qualify: regressions, security issues, and really severe problems.
399 provides additional details how to best handle security issues.
429 main memory for example can result in a multitude of issues that will
430 manifest itself in problems looking like kernel issues.
551 issues at once, create separate notes for each of them and make sure they
556 If you deal with multiple issues at once, you'll have to report each of them
558 various issues in one report also makes it quite difficult for others to tear
559 it apart. Hence, only combine issues in one report if they are very strongly
566 Note: it's often fruitless to report issues that only happened once, as they
582 Linux developers want to fix badly, as such issues are even more unwanted than
584 people. The developers thus want to learn about such issues as quickly as
595 time this won't be bugzilla.kernel.org, as issues typically need to be sent
607 That's why you have to find the right place and way to report issues yourself.
784 reports for issues that don't even happen with the current code. It's just a
920 eliminate the reason for it before you reporting issues that occur with it. See
928 up there, scroll down to the instructions for issues only happening with
937 head over to the section "Details about reporting issues only occurring in
1083 you are dealing with one of those 'issues of high priority': they need
1085 issues' below.*
1187 insights how the components were configured. For some issues it might be
1221 you, unless it's one of those 'issues of high priority' outlined earlier: in
1225 Special handling for high priority issues
1228 Reports for high priority issues need special handling.
1230 **Severe issues**: make sure the subject or ticket title as well as the first
1252 **Security issues**: for these issues your will have to evaluate if a
1255 For issues that bear such a risk you will need to adjust the reporting process
1342 The 'issues of high priority' (see above for an explanation) are an exception
1368 to help to get issues resolved once they were reported.
1377 issues are normally reported in public it could be anyone that's replying —
1441 'issues of high priority' outlined earlier. So don't be too devastating if you
1443 issues to deal with currently and won't have time to look into this for the
1450 getting help are explained in 'Why some issues won't get any reaction or remain
1566 Reference for "Reporting issues only occurring in older kernel version lines"
1596 *Perform the first three steps in the section "Reporting issues only
1677 Why some issues won't get any reaction or remain unfixed after being reported
1680 When reporting a problem to the Linux developers, be aware only 'issues of high
1681 priority' (regressions, security issues, severe problems) are definitely going
1684 other issues as well. But be aware that sometimes they can't or won't help; and
1722 Priorities are another reason why some issues are not fixed, as maintainers
1731 maintainers who are quite interested in fixing as many issues as possible.
1738 issues to the Linux kernel developers: the length and complexity of this
1759 …rg/pub/scm/linux/kernel/git/torvalds/linux.git/plain/Documentation/admin-guide/reporting-issues.rst