Lines Matching full:to
14 <https://lore.kernel.org/stable/>`_ archives for matching reports to join. If
16 <https://kernel.org/>`_. If it still shows the issue, report it to the stable
23 expect to be told about problems, which most of the time will be by email with a
26 don't find any to join, install `the latest mainline kernel
29 The issue was fixed there, but you would like to see it resolved in a still
41 separately. While writing your report, include all information relevant to the
43 regressions mailing list (regressions@lists.linux.dev) to your report. Also try
44 to pinpoint the culprit with a bisection; if you succeed, include its
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
58 step-by-step approach. It still tries to be brief for readability and leaves
63 a slightly different order. That's in your interest, to make sure you notice
65 something else. These steps thus help to ensure the time you invest in this
69 provided? Then in almost all cases you are better off to stop reading this
70 document and reporting the issue to your vendor instead, unless you are
71 willing to install the latest Linux version yourself. Be aware the latter
72 will often be needed anyway to hunt down and fix issues.
81 need special handling in some steps that are about to follow.
95 * Write down coarsely how to reproduce the issue. If you deal with multiple
98 needs to get reported to the kernel developers separately, unless they are
102 (say something broke when updating from 5.10.4 to 5.10.5), scroll down to
105 * Locate the driver or kernel subsystem that seems to be causing the issue.
107 time this won't be bugzilla.kernel.org, as issues typically need to be sent
108 by mail to a maintainer and a public mailing list.
120 approach, but in that development phase it can be an even better idea to
129 up there, scroll down to the instructions for issues only happening with
132 * Optimize your notes: try to find and write the most straightforward way to
134 details, and at the same time is easy to read and understand for others
139 decoding the kernel log to find the line of code that triggered the error.
141 * If your problem is a regression, try to narrow down when the issue was
144 * Start to compile the report by writing a detailed description about the
146 for reproducing, the Linux Distribution used, and your notes on how to
149 link to it. Include or upload all other information that might be relevant,
153 that briefly describes the problem and gets people to read on. Now give the
155 ready to send or file the report like the MAINTAINERS file told you, unless
162 to any inquiries. Test proposed fixes. Do proactive testing: retest with at
164 report your results. Send friendly reminders if things stall. And try to
173 face one of those if something breaks when updating from 5.10.4 to 5.10.5 (a
174 switch from 5.9.15 to 5.10.5 does not qualify). The developers want to fix such
175 regressions as quickly as possible, hence there is a streamlined process to
179 line you care about: go to the `front page of kernel.org
190 known to work performs fine as well.
192 * Send a short problem report to the Linux stable mailing list
196 issue and ideally explain how to reproduce it. Mention the first version
207 above, but failed to reproduce your issue there; at the same time you want to
213 or risky to get backported there.
226 * One of the former steps should lead to a solution. If that doesn't work
227 out, ask the maintainers for the subsystem that seems to be causing the
234 Reference section: Reporting issues to the kernel maintainers
239 experienced users might wonder how to actually do one of those steps. That's
241 above steps. Consider this as reference documentation: it's possible to read it
242 from top to bottom. But it's mainly meant to skim over and a place to look up
243 details how to actually perform those steps.
248 demands more than other FLOSS projects. We'd love to make it simpler. But
250 which would need constant maintenance; nobody has stepped up to do that
253 * A warranty or support contract with some vendor doesn't entitle you to
259 to claim your rights, use the vendor's support channel instead. When doing
260 so, you might want to mention you'd like to see the issue fixed in the
261 upstream Linux kernel; motivate them by saying it's the only way to ensure
264 * If you never reported an issue to a FLOSS project before you should consider
265 reading `How to Report Bugs Effectively
266 <https://www.chiark.greenend.org.uk/~sgtatham/bugs.html>`_, `How To Ask
268 <http://www.catb.org/esr/faqs/smart-questions.html>`_, and `How to ask good
271 With that off the table, find below the details on how to properly report
272 issues to the Linux kernel developers.
279 provided? Then in almost all cases you are better off to stop reading this
280 document and reporting the issue to your vendor instead, unless you are
281 willing to install the latest Linux version yourself. Be aware the latter
282 will often be needed anyway to hunt down and fix issues.*
284 Like most programmers, Linux kernel developers don't like to spend time dealing
287 easily happen when it comes to the kernel and often leads to frustration on both
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
300 report and, in case it turns out to be an upstream issue, fix it directly
302 or might not what you want. You thus might want to consider circumventing the
305 explain how to do that once it rules out other potential causes for your issue.
308 developers in fact are willing to handle reports about issues occurring with
311 small modifications to a kernel based on a recent Linux version; that for
317 want to use a mainline Linux and avoid using a stable kernel for this
321 Obviously you are free to ignore all this advice and report problems with an old
322 or heavily modified vendor kernel to the upstream Linux developers. But note,
325 indirectly will help to get the issue fixed over time.
338 interest to thoroughly check if somebody reported the issue already. At this
339 step of the process it's okay to just perform a rough search: a later step will
340 tell you to perform a more detailed search once you know where your issue needs
341 to be reported to. Nevertheless, do not hurry with this step of the reporting
348 If you get flooded with results consider telling your search engine to limit
349 search timeframe to the past month or year. And wherever you search, make sure
350 to use good search terms; vary them a few times, too. While doing so try to
351 look at the issue from the perspective of someone else: that will help you to
352 come up with other words to use as search terms. Also make sure not to use too
353 many search terms at once. Remember to search with and without information like
361 you might be able to provide valuable additional information. That can be
364 test a proposed fix. Jump to the section 'Duties after the report went out' for
365 details on how to get properly involved.
371 need to report your issue". The developers that should take care of the issue
382 need special handling in some steps that are about to follow.*
384 Linus Torvalds and the leading Linux kernel developers want to see some issues
394 might want to be aware of; it for example explains how to add your issue to the
395 list of tracked regressions, to ensure it won't fall through the cracks.
397 What qualifies as security issue is left to your judgment. Consider reading
399 provides additional details how to best handle security issues.
417 runtime environment. It's hard to rule out that problem completely, but you
421 binutils can cause the resulting kernel to misbehave.
428 * Try to make sure it's not faulty hardware that is causing your issue. Bad
432 * If you're dealing with a filesystem issue, you might want to check the file
434 to unexpected kernel behavior.
437 changed in parallel to updating the kernel. The problem for example might be
441 something in the BIOS Setup can also lead to problems that on look a lot
452 system. That's what you are about to do in this process. Thus, make sure to
453 create a fresh backup; also ensure you have all tools at hand to repair or
454 reinstall the operating system as well as everything you need to restore the
475 module not part of the Linux kernel. That why your might need to uninstall the
476 packages with such software to get rid of any 3rd party kernel module.
486 lead to follow-up errors that look totally unrelated. The issue you face might
487 be such an error if your kernel is tainted. That's why it's in your interest to
489 only reason why this step is here, as this process later will tell you to
490 install the latest mainline kernel; you will need to check the taint flag again
494 On a running system is easy to check if the kernel tainted itself: if ``cat
506 to find out why. Try to eliminate the reason. Often it's caused by one these
518 follow-up problem to that first Oops, even if both look totally unrelated.
521 a change to the configuration followed by a reboot can eliminate the Oops.
524 version you are going to install later in this process.
530 areas and thus might be causing the issue you face. You therefore have to
531 prevent those modules from loading when you want to report an issue to the
532 Linux kernel developers. Most of the time the easiest way to do that is:
547 Document how to reproduce issue
550 *Write down coarsely how to reproduce the issue. If you deal with multiple
553 needs to get reported to the kernel developers separately, unless they are
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
562 Additionally, during the reporting process you will have to test if the issue
564 you know exactly how to reproduce an issue quickly on a freshly booted system.
566 Note: it's often fruitless to report issues that only happened once, as they
567 might be caused by a bit flip due to cosmic radiation. That's why you should
568 try to rule that out by reproducing the issue before going further. Feel free
569 to ignore this advice if you are experienced enough to tell a one-time error
570 due to faulty hardware apart from a kernel issue that rarely happens and thus
571 is hard to reproduce.
578 (say something broke when updating from 5.10.4 to 5.10.5), scroll down to
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
585 possible, hence there is a streamlined process to report them. Note,
587 from 5.9.15 to 5.10.5) do not qualify.
590 Check where you need to report your issue
593 *Locate the driver or kernel subsystem that seems to be causing the issue.
595 time this won't be bugzilla.kernel.org, as issues typically need to be sent
596 by mail to a maintainer and a public mailing list.*
598 It's crucial to send your report to the right people, as the Linux kernel is a
606 file your issue and make it reach the developers that need to know about it.
607 That's why you have to find the right place and way to report issues yourself.
612 How to read the MAINTAINERS file
614 To illustrate how to use the :ref:`MAINTAINERS <maintainers>` file, lets assume
617 code it builds upon, but unless you suspect something like that stick to the
621 Sadly, there is no way to check which code is driving a particular hardware
624 In case of a problem with the WiFi driver you for example might want to look at
637 other internal bus. In those cases you might want to check your WiFi manager or
640 this to find the module driving it::
642 …[user@something ~]$ realpath --relative-to=/sys/module/ /sys/class/net/wlp58s0/device/driver/module
645 In case tricks like these don't bring you any further, try to search the
646 internet on how to narrow down the driver or subsystem in question. And if you
650 Once you know the driver or subsystem, you want to search for it in the
652 name is too specific. Sometimes you will need to search on the net for help;
671 that was replaced by a newer solution you need to switch to. Sometimes the code
674 That only leaves these options: arrange yourself to live with the issue, fix it
675 yourself, or find a programmer somewhere willing to fix it.
678 you where to find a subsystem specific bug tracker to file your issue. The
683 In this and many other cases you thus have to look for lines starting with
687 Your report later needs to go by mail to those addresses. Additionally, for all
688 issue reports sent by email, make sure to add the Linux Kernel Mailing List
689 (LKML) <linux-kernel@vger.kernel.org> to CC. Don't omit either of the mailing
692 and LKML is important to have one place where all issue reports can be found.
698 For people that have the Linux sources at hand there is a second option to find
699 the proper place to report: the script 'scripts/get_maintainer.pl' which tries
700 to find all people to contact. It queries the MAINTAINERS file and needs to be
701 called with a path to the source code in question. For drivers compiled as
707 Pass parts of this to the script::
717 Don't sent your report to all of them. Send it to the maintainers, which the
720 would need to send the report to 'Some Human <shuman@example.com>' with
723 Note: in case you cloned the Linux sources with git you might want to call
725 at the commit history to find which people recently worked on the code in
726 question, as they might be able to help. But use these results with care, as it
743 that you know where they need to be reported to. If it's mailing list, you will
749 ath10k@lists.infradead.org' for example will lead you to the `Info page for the
751 which at the top links to its
753 quite a few other lists miss a way to search the archives. In those cases use a
755 'site:lists.infradead.org/pipermail/ath10k/' to your search terms, which limits
756 the results to the archives at that URL.
758 It's also wise to check the internet, LKML and maybe bugzilla.kernel.org again
759 at this point. If your report needs to be filed in a bug tracker, you may want
760 to check the mailing list archives for the subsystem as well, as someone might
763 For details how to search and what to do if you find matching reports see
766 Do not hurry with this step of the reporting process: spending 30 to 60 minutes
777 approach, but in that development phase it can be an even better idea to
783 programmers, Linux kernel developers don't like to spend time dealing with
787 before reporting it. You are free to ignore this advice, but as outlined
798 * The over next subsection describes way to obtain and install such a kernel.
806 Head over to `kernel.org <https://kernel.org/>`_ to find out which version you
807 want to use for testing. Ignore the big yellow button that says 'Latest release'
809 mainline, which most of the time will point to a pre-release with a version
810 number like '5.8-rc2'. If that's the case, you'll want to use this mainline
811 kernel for testing, as that where all fixes have to be applied first. Do not let
815 In about two out of every nine to ten weeks, mainline might point you to a
821 more risky to use mainline during this period. Kernel developers are also often
822 quite busy then and might have no spare time to deal with issue reports. It's
824 window fixes the issue you face; that's why you soon would have to retest with
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
837 must be applied to mainline first. That's why checking the latest mainline
838 kernel is so important: any issue you want to see fixed in older version lines
839 needs to be fixed in mainline first before it can get backported, which can
841 hard or risky for backporting; reporting the issue again hence is unlikely to
845 are unsuitable for this part of the reporting process: they are to distant from
847 further: if the issue doesn't occur with mainline it will guide you how to get
850 How to obtain a fresh Linux kernel
862 latest mainline or stable Linux built as vanilla kernel. It's totally okay to
864 at least close to it. Additionally ensure the packages contain the latest
869 Please note that you might need to build your own kernel manually later: that's
872 are needed to decode messages the kernel prints when a panic, Oops, warning, or
873 BUG occurs; if you plan to decode those, you might be better off compiling a
889 How to actually build a kernel is not described here, as many websites explain
890 the necessary steps already. If you are new to it, consider following one of
891 those how-to's that suggest to use ``make localmodconfig``, as that tries to
892 pick up the configuration of your current kernel and then tries to adjust it
894 but quicker to compile.
897 please try to enable CONFIG_KALLSYMS when configuring your kernel.
900 the former. Be aware CONFIG_DEBUG_INFO increases the storage space required to
902 you later to pinpoint the exact line of code that triggers your issue. The
906 hard to reproduce. Sending an undecoded report is better than not reporting
917 something happens that can lead to follow-up errors that look totally
918 unrelated. That's why you need to check if the kernel you just installed does
919 not set this flag. And if it does, you in almost all the cases needs to
921 the section above for details how to do that.
928 up there, scroll down to the instructions for issues only happening with
933 line and abandoning your plan to report the issue. But keep in mind that other
936 those). If you prefer to use one of those or just want to help their users,
937 head over to the section "Details about reporting issues only occurring in
941 Optimize description to reproduce issue
944 *Optimize your notes: try to find and write the most straightforward way to
946 details, and at the same time is easy to read and understand for others
950 An unnecessarily complex report will make it hard for others to understand your
951 report. Thus try to find a reproducer that's straight forward to describe and
952 thus easy to understand in written form. Include all important details, but at
953 the same time try to keep it as short as possible.
964 decoding the kernel log to find the line of code that triggered the error.*
967 the executed code. This makes it possible to pinpoint the exact line in the
970 your kernel. If you did so, consider to decode the information from the
971 kernel's log. That will make it a lot easier to understand what lead to the
980 If you are running a packaged vanilla kernel, you will likely have to install
982 might need to get from the Linux sources if your distro does not package it)
1002 starting with 'Call trace', which show the path to the function where the
1006 Note, if you can't get this to work, simply skip this step and mention the
1008 is, someone might help you to get things going. Also be aware this is just one
1009 of several ways to decode kernel stack traces. Sometimes different steps will
1010 be required to retrieve the relevant details. Don't worry about that, if that's
1011 needed in your case, developers will tell you what to do.
1017 *If your problem is a regression, try to narrow down when the issue was
1021 worsens, that's why he deems regressions as unacceptable and wants to see them
1024 way. Reporting a regression is thus a bit like playing a kind of trump card to
1025 get something quickly fixed. But for that to happen the change that's causing
1026 the regression needs to be known. Normally it's up to the reporter to track
1027 down the culprit, as maintainers often won't have the time or setup at hand to
1030 To find the change there is a process called 'bisection' which the document
1032 will often require you to build about ten to twenty kernel images, trying to
1035 Thanks to a 'binary search' this will lead you to the one commit in the source
1038 (the first 12 characters of the commit id). This will lead you to existing
1042 bit of effort, which not everyone is willing to invest. Nevertheless, it's
1044 don't want to go down that route at least find out which mainline kernel
1046 5.5.15 to 5.8.4, then try at least all the mainline releases in that area (5.6,
1047 5.7 and 5.8) to check when it first showed up. Unless you're trying to find a
1049 has three sections (5.6.12, 5.7.8), as that makes the outcome hard to
1051 version which introduced the regression, feel free to move on in the reporting
1053 will be able to help without knowing the culprit. Sometimes they might
1055 be unable to help unless you perform a bisection.
1064 provides a good deal of other information about regressions you might want to be
1071 *Start to compile the report by writing a detailed description about the
1073 for reproducing, the Linux Distribution used, and your notes on how to
1076 link to it. Include or upload all other information that might be relevant,
1080 that briefly describes the problem and gets people to read on. Now give the
1082 ready to send or file the report like the MAINTAINERS file told you, unless
1087 Now that you have prepared everything it's time to write your report. How to do
1088 that is partly explained by the three documents linked to in the preface above.
1090 things specific to the Linux kernel.
1095 seconds to skim a mail before deciding to move on or look closer. Thus: the
1104 installed. Try to include the step-by-step instructions you wrote and optimized
1106 those rare cases where that's impossible try to describe what you did to
1109 Also include all the relevant information others might need to understand the
1124 In a lot of cases it's also wise to make two more things available to those
1129 * the kernel's messages that you get from ``dmesg`` written to a file. Make
1137 These two files are big, that's why it's a bad idea to put them directly into
1138 your report. If you are filing the issue in a bug tracker then attach them to
1144 <https://bugzilla.kernel.org/>`_, ...) and include a link to them in your
1146 they could be useful to someone many years from now; this for example can
1148 changed just to fix your issue.
1151 replies to your own mail. Just remember to actually do that once the report
1154 Things that might be wise to provide
1157 Depending on the issue you might need to add more background data. Here are a
1158 few suggestions what often is good to provide:
1161 include it. If you can't copy'n'paste it, try to capture a netconsole trace
1164 * If the issue might be related to your computer hardware, mention what kind
1167 laptop mention its name, but try to make sure it's meaningful. 'Dell XPS 13'
1174 to find the exact model name or specify the main components.
1177 modules, you want to mention the versions of kmod, systemd, and udev in use.
1178 If one of the DRM drivers misbehaves, you want to state the versions of
1184 output from ``lspci -nn`` will for example help others to identify what
1185 hardware you use. If you have a problem with hardware you even might want to
1188 good to include the contents of files like ``/proc/cpuinfo``,
1190 ``/proc/scsi/scsi``. Some subsystem also offer tools to collect relevant
1194 Those examples should give your some ideas of what data might be wise to
1195 attach, but you have to think yourself what will be helpful for others to know.
1204 Now that you have the detailed part of the report prepared let's get to the
1205 most important section: the first few sentences. Thus go to the top, add
1209 crucial parts readers need to know to understand what this is all about; if you
1210 think this bug affects a lot of users, mention this to get people interested.
1213 summary that explains quickly what the report is about. After that you have to
1216 Now that you have written this part take some time to optimize it, as it is the
1242 (regressions@lists.linux.dev). In case the report needs to be filed to some web
1243 tracker, proceed to do so. Once filed, forward the report by mail to the
1245 question. Make sure to inline the forwarded report, hence do not attach it.
1246 Also add a short note at the top where you mention the URL to the ticket.
1249 author of the culprit to the recipients; also CC everyone in the signed-off-by
1252 **Security issues**: for these issues your will have to evaluate if a
1253 short-term risk to other users would arise if details were publicly disclosed.
1255 For issues that bear such a risk you will need to adjust the reporting process
1258 * If the MAINTAINERS file instructed you to report the issue by mail, do not
1261 * If you were supposed to file the issue in a bug tracker make sure to mark
1263 offer a way to keep reports private, forget about it and send your report as
1264 a private mail to the maintainers instead.
1266 In both cases make sure to also mail your report to the addresses the
1269 the report's text to these addresses; but on top of it put a small note where
1270 you mention that you filed it with a link to the ticket.
1280 to any inquiries. Test proposed fixes. Do proactive testing: retest with at
1282 report your results. Send friendly reminders if things stall. And try to
1287 to fix it, test it, and send it straight for integration in mainline while
1288 tagging it for later backport to stable and longterm kernels that need it. Then
1289 all you need to do is reply with a 'Thank you very much' and switch to a version
1293 once you got the report out. What you'll have to do depends on the situations,
1295 details, here are a few important things you need to keep in mind for this part
1304 mailed reports always use the 'Reply-all' function when replying to any mails
1305 you receive. That includes mails with any additional data you might want to add
1306 to your report: go to your mail applications 'Sent' folder and use 'reply-all'
1310 mailing lists to group all related mails together.
1315 * Someone tells you to send something privately.
1317 * You were told to send something, but noticed it contains sensitive
1318 information that needs to be kept private. In that case it's okay to send it
1319 in private to the developer that asked for it. But note in the ticket or a
1323 process someone might tell you to do something that requires a skill you might
1324 not have mastered yet. For example, you might be asked to use some test tools
1325 you never have heard of yet; or you might be asked to apply a patch to the
1326 Linux kernel sources to test if it helps. In some cases it will be fine sending
1327 a reply asking for instructions how to do that. But before going that route try
1328 to find the answer own your own by searching the internet; alternatively
1330 about it to a chatroom or forum you normally hang out.
1332 **Be patient**: If you are really lucky you might get a reply to your report
1337 In general, kernel developers will take one to five business days to respond to
1350 ask others for public or private replies how to move on. If that fails, it
1351 might be appropriate to get a higher authority involved. In case of a WiFi
1354 it's okay to get Linus Torvalds involved.
1359 mail you sent as reply to your report (make sure it has all those in the CC
1360 that up to that point participated in the discussion). This will show your
1361 commitment and that you are willing to help. It also tells developers if the
1368 to help to get issues resolved once they were reported.
1373 Here are your duties in case you got replies to your report:
1376 developer of the particular code area that will respond to your report. But as
1378 including people that want to help, but in the end might guide you totally off
1380 many reasons why it's wise to quickly run an internet search to see who you're
1382 the right people, as a reminder to the maintainer (see below) might be in order
1383 later if discussion fades out without leading to a satisfying solution for the
1386 **Inquiries for data**: Often you will be asked to test something or provide
1387 additional details. Try to provide the requested information soon, as you have
1392 **Requests for testing**: When you are asked to test a diagnostic patch or a
1393 possible fix, try to test it in timely manner, too. But do it properly and make
1394 sure to not rush it: mixing things up can happen easily and can lead to a lot
1397 happen even to experienced testers occasionally, but they most of the time will
1400 What to do when nothing of substance happens
1409 your report arrived or had something more important to take care of. When
1410 writing the reminder, kindly ask if anything else from your side is needed to
1412 first lines of a mail that is a reply to your initial mail (see above) which
1420 to reach out to the wrong people? Was the report maybe offensive or so
1421 confusing that people decided to completely stay away from it? The best way to
1422 rule out such factors: show the report to one or two people familiar with FLOSS
1424 to move forward. That might mean: prepare a better report and make those people
1427 link to the first report.
1435 If the second reminder again results in no reaction within a week, try to
1439 Remember to prepare yourself for a disappointment: maintainers ideally should
1440 react somehow to every issue report, but they are only obliged to fix those
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
1449 comes to Linux kernel development. This and several other reasons for not
1455 You for example could try to find others that are affected and team up with
1456 them to get the issue resolved. Such a team could prepare a fresh report
1461 bit about programming and might be able to write a fix.
1467 This subsection provides details for the steps you need to perform if you face
1474 line you care about: go to the front page of kernel.org and make sure it
1481 need to check if the kernel developers still support the version line you care
1485 should consider switching to the newer one and forget about the older one:
1486 support for it is likely to be abandoned soon. Then it will get a "end-of-life"
1496 Maybe the issue you face is already known and was fixed or is about to. Hence,
1500 already finished and scheduled to get applied soon.
1509 known to work performs fine as well.*
1511 Before investing any more time in this process you want to check if the issue
1513 This kernel needs to be vanilla and shouldn't be tainted before the issue
1518 vendor applied might be interfering. You need to rule that out by performing
1519 a recheck. Say something broke when you updated from 5.10.4-vendor.42 to
1523 regression and you need switch back to the main step-by-step guide to report
1529 *Send a short problem report to the Linux stable mailing list
1533 issue and ideally explain how to reproduce it. Mention the first version
1538 line (say when updating from 5.10.4 to 5.10.5) a brief report is enough for
1539 the start to get the issue reported quickly. Hence a rough description to the
1546 try to find that version using vanilla kernels. Lets assume something broke when
1547 your distributor released a update from Linux kernel 5.10.5 to 5.10.8. Then as
1549 5.10.9. If it shows the problem, try a vanilla 5.10.5 to ensure that no patches
1551 try 5.10.7 and then (depending on the outcome) 5.10.8 or 5.10.6 to find the
1556 Once your report is out your might get asked to do a proper one, as it allows to
1558 reverted to fix the issue quickly). Hence consider to do a proper bisection
1560 the document Documentation/admin-guide/bug-bisect.rst for details how to
1561 perform one. In case of a successful bisection add the author of the culprit to
1569 This section provides details for the steps you need to take if you could not
1570 reproduce your issue with a mainline kernel, but want to see it fixed in older
1578 or risky to get backported there.*
1582 are very aware of that and thus only apply changes to these kernels that are
1586 to mainline. Other fixes are easy to get backported to the newest stable and
1587 longterm kernels, but too risky to integrate into older ones. So be aware the
1588 fix you are hoping for might be one of those that won't be backported to the
1589 version line your care about. In that case you'll have no other choice then to
1590 live with the issue or switch to a newer Linux version, unless you want to
1599 You need to carry out a few steps already described in another section of this
1622 got fixed there. The commit that fixed it would need to get backported as well
1623 to get the issue solved. That's why you want to search for it or any
1626 * First try to find the fix in the Git repository that holds the Linux kernel
1638 If that's case the developer marked the fix safe for backporting to version
1647 instructions to find the subsystem in question: its bug tracker or mailing
1653 * Check the discussions for any indicators the fix might be too risky to get
1654 backported to the version line you care about. If that's the case you have
1655 to live with the issue or switch to the kernel version line where the fix
1660 you would like to see it fixed, if suitable.
1666 *One of the former steps should lead to a solution. If that doesn't work
1667 out, ask the maintainers for the subsystem that seems to be causing the
1671 If the previous three steps didn't get you closer to a solution there is only
1672 one option left: ask for advice. Do that in a mail you sent to the maintainers
1673 for the subsystem where the issue seems to have its roots; CC the mailing list
1680 When reporting a problem to the Linux developers, be aware only 'issues of high
1682 to get resolved. The maintainers or if all else fails Linus Torvalds himself
1685 sometimes there isn't even anyone to send a report to.
1687 This is best explained with kernel developers that contribute to the Linux
1689 written by such programmers, often because they simply wanted to make their
1693 report. But nobody can force them to do, as they are contributing voluntarily.
1695 Then there are situations where such developers really want to fix an issue,
1696 but can't: sometimes they lack hardware programming documentation to do so.
1705 nobody is willing to take over the job as maintainer – and nobody can be forced
1706 to, as contributing to the Linux kernel is done on a voluntary basis. Abandoned
1718 hardware aside to limit the scope. Often spare time contributors take over once
1723 quite often are forced to set those, as time to work on Linux is limited.
1724 That's true for spare time or the time employers grant their developers to
1726 get overwhelmed with reports, even if a driver is working nearly perfectly. To
1728 to prioritize issue reports and reject some of them.
1737 Compared with other Free/Libre & Open Source Software it's hard to report
1738 issues to the Linux kernel developers: the length and complexity of this
1741 art will lay some groundwork to improve the situation over time.
1748 you spot a typo or small mistake, feel free to let him know directly and
1749 he'll fix it. You are free to do the same in a mostly informal way if you
1750 want to contribute changes to the text, but for copyright reasons please CC
1756 of the file. If you want to distribute this text under CC-BY-4.0 only,