Documentation/admin-guide/reporting-issues.rst

15 you don't find any, install `the latest release from that series
26 don't find any to join, install `the latest mainline kernel
66 process won't feel wasted in the end:
107    time this won't be bugzilla.kernel.org, as issues typically need to be sent
128  * Reproduce the issue with the kernel you just installed. If it doesn't show
165    help yourself, if you don't get any help or if it's unsatisfying.
220    scheduled for backporting already. If you don't find anything that way,
226  * One of the former steps should lead to a solution. If that doesn't work
253  * A warranty or support contract with some vendor doesn't entitle you to
256    development community, and this document. That's why you can't demand
284 Like most programmers, Linux kernel developers don't like to spend time dealing
285 with reports for issues that don't even happen with their current code. It's
395 list of tracked regressions, to ensure it won't fall through the cracks.
458 Make sure your kernel doesn't get enhanced
522     But don't invest too much time into this at this point of the process, as
595     time this won't be bugzilla.kernel.org, as issues typically need to be sent
636 But this approach won't work if your WiFi chip is connected over USB or some
645 In case tricks like these don't bring you any further, try to search the
651 MAINTAINERS file. In the case of 'ath10k_pci' you won't find anything, as the
689 (LKML) <linux-kernel@vger.kernel.org> to CC. Don't omit either of the mailing
717 Don't sent your report to all of them. Send it to the maintainers, which the
783 programmers, Linux kernel developers don't like to spend time dealing with
784 reports for issues that don't even happen with the current code. It's just a
813 made a backup, as you were instructed above, didn't you?
828 That's why it might make sense to wait till the merge window is over. But don't
829 to that if you're dealing with something that shouldn't wait. In that case
847 further: if the issue doesn't occur with mainline it will guide you how to get
881 Those are likely a bit ahead of the latest mainline pre-release. Don't worry
927     *Reproduce the issue with the kernel you just installed. If it doesn't show
1006 Note, if you can't get this to work, simply skip this step and mention the
1010 be required to retrieve the relevant details. Don't worry about that, if that's
1023 promptly reverted if the issue they cause can't get solved quickly any other
1027 down the culprit, as maintainers often won't have the time or setup at hand to
1034 some time, but don't worry, it works a lot quicker than most people assume.
1043 highly recommended performing a bisection yourself. If you really can't or
1044 don't want to go down that route at least find out which mainline kernel
1161    include it. If you can't copy'n'paste it, try to capture a netconsole trace
1196 Don't worry too much about forgetting something, as developers will ask for
1283     help yourself, if you don't get any help or if it's unsatisfying.*
1396 proposed patch with a fix was applied, but in fact wasn't. Things like that
1418 After the reminder wait three more weeks for replies. If you still don't get a
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
1447 nothing happens anymore and reminders don't help to motivate anyone to work out
1450 getting help are explained in 'Why some issues won't get any reaction or remain
1453 Don't get devastated if you don't find any help or if the issue in the end does
1513 This kernel needs to be vanilla and shouldn't be tainted before the issue
1550 the distributor applied interfere. If the issue doesn't manifest itself there,
1588 fix you are hoping for might be one of those that won't be backported to the
1615     scheduled for backporting already. If you don't find anything that way,
1642  * If the commit doesn't tell you anything or if you can't find the fix, look
1658    * If the fix doesn't contain a stable tag and backporting was not discussed,
1666     *One of the former steps should lead to a solution. If that doesn't work
1671 If the previous three steps didn't get you closer to a solution there is only
1677 Why some issues won't get any reaction or remain unfixed after being reported
1684 other issues as well. But be aware that sometimes they can't or won't help; and
1685 sometimes there isn't even anyone to send a report to.
1696 but can't: sometimes they lack hardware programming documentation to do so.
1702 old that it's something you don't find much outside of computer museums
1730 But don't worry too much about all of this, a lot of drivers have active