Lines Matching full:might
9 (for example by the kernel's build system) might contain content taken from
30 In all other cases try your best guess which kernel part might be causing the
64 developers. It might be all that's needed for people already familiar with
98 kernel modules on-the-fly, which solutions like DKMS might be doing locally
102 that made the kernel set this flag might be causing the issue you face.
120 thoroughly for reports that might match your issue. If you find anything,
128 situations; during the merge window that actually might be even the best
158 link to it. Include or upload all other information that might be relevant,
197 the issue might have already been fixed there. If you first noticed the
221 might not get the issue solved in older releases: the fix might be too big
228 the issue in mainline, as its commit message might tell you if the fix is
248 experienced users might wonder how to actually do one of those steps. That's
269 so, you might want to mention you'd like to see the issue fixed in the
304 Linux kernel developers: an issue you face with one of them might have been
306 the modifications and enhancements by the vendor might be causing the issue you
311 or might not what you want. You thus might want to consider circumventing the
370 you might be able to provide valuable additional information. That can be
372 developers might look for people that can provide additional information or
376 Note, searching `bugzilla.kernel.org <https://bugzilla.kernel.org/>`_ might also
377 be a good idea, as that might provide valuable insights or turn up matching
381 thus might not even be aware of the bugzilla ticket. Hence, check the ticket if
402 an application shows erratic behavior with a newer kernel, which might happen
447 * If you're dealing with a filesystem issue, you might want to check the file
448 system in question with ``fsck``, as it might be damaged in a way that leads
452 changed in parallel to updating the kernel. The problem for example might be
477 kernel modules on-the-fly, which solutions like DKMS might be doing locally
484 the first time. Also remove any modules they might have installed. Then reboot
487 Note, you might not be aware that your system is using one of these solutions:
490 module not part of the Linux kernel. That why your might need to uninstall the
498 that made the kernel set this flag might be causing the issue you face.*
500 The kernel marks itself with a 'taint' flag when something happens that might
501 lead to follow-up errors that look totally unrelated. The issue you face might
525 itself, as the kernel knows it might misbehave in strange ways after that
532 Every Oops and any other problem that happens after that point might be a
538 the cause for the Oops might already be fixed in the newer Linux kernel
545 areas and thus might be causing the issue you face. You therefore have to
548 temporarily uninstall such software including any modules they might have
572 separately, as they might be handled by different developers. Describing
582 might be caused by a bit flip due to cosmic radiation. That's why you should
639 In case of a problem with the WiFi driver you for example might want to look at
652 other internal bus. In those cases you might want to check your WiFi manager or
654 interface, which might be something like 'wlp58s0'. This name can be used like
669 MAINTAINERS file, as then you might find something like this::
706 and might leave some work for other developers on the subsystem specific list;
738 Note: in case you cloned the Linux sources with git you might want to call
741 question, as they might be able to help. But use these results with care, as it
752 thoroughly for reports that might match your issue. If you find anything,
775 to check the mailing list archives for the subsystem as well, as someone might
791 situations; during the merge window that actually might be even the best
803 earlier: doing so dramatically increases the risk that your issue report might
830 In about two out of every nine to ten weeks, mainline might point you to a
837 quite busy then and might have no spare time to deal with issue reports. It's
843 That's why it might make sense to wait till the merge window is over. But don't
855 take a few days or weeks. Another reason: the fix you hope for might be too
872 unsuitable for testing and issue reporting: the changes might cause the issue
884 Please note that you might need to build your own kernel manually later: that's
886 document. Also be aware that pre-compiled kernels might lack debug symbols that
888 BUG occurs; if you plan to decode those, you might be better off compiling a
949 users might still be plagued by it, as long as it's not fixed in either stable
997 might need to get from the Linux sources if your distro does not package it)
1022 reason for it in the report. If you're lucky, it might not be needed. And if it
1023 is, someone might help you to get things going. Also be aware this is just one
1065 interpret, which might render your testing useless. Once you found the major
1068 will be able to help without knowing the culprit. Sometimes they might
1090 link to it. Include or upload all other information that might be relevant,
1123 Also include all the relevant information others might need to understand the
1168 Things that might be wise to provide
1171 Depending on the issue you might need to add more background data. Here are a
1178 * If the issue might be related to your computer hardware, mention what kind
1182 for example is not, because it might be the one from 2012; that one looks
1197 * Gather additional information from the kernel that might be of interest. The
1199 hardware you use. If you have a problem with hardware you even might want to
1201 insights how the components were configured. For some issues it might be
1208 Those examples should give your some ideas of what data might be wise to
1300 might immediately spot what's causing the issue; they then might write a patch
1319 you receive. That includes mails with any additional data you might want to add
1337 process someone might tell you to do something that requires a skill you might
1338 not have mastered yet. For example, you might be asked to use some test tools
1339 you never have heard of yet; or you might be asked to apply a patch to the
1346 **Be patient**: If you are really lucky you might get a reply to your report
1348 are scattered around the globe and thus might be in a different time zone – one
1352 reports. Sometimes it will take longer, as they might be busy with the merge
1361 Sometimes the maintainer might not be responding in a timely manner; other
1362 times there might be disagreements, for example if an issue qualifies as
1365 might be appropriate to get a higher authority involved. In case of a WiFi
1367 maintainers or all else fails, it might be one of those rare situations where
1392 including people that want to help, but in the end might guide you totally off
1396 the right people, as a reminder to the maintainer (see below) might be in order
1402 the attention of someone that might help and risk losing it the longer you
1438 to move forward. That might mean: prepare a better report and make those people
1474 easier. And with a bit of luck there might be someone in the team that knows a
1475 bit about programming and might be able to write a fix.
1521 the issue might have already been fixed there. If you first noticed the
1532 vendor applied might be interfering. You need to rule that out by performing
1570 Once your report is out your might get asked to do a proper one, as it allows to
1591 might not get the issue solved in older releases: the fix might be too big
1602 fix you are hoping for might be one of those that won't be backported to the
1628 the issue in mainline, as its commit message might tell you if the fix is
1662 list archive might have the answer you are looking for.
1665 outlined above, as the commit might tell you if a backport can be expected.
1667 * Check the discussions for any indicators the fix might be too risky to get
1741 not get completely stuck, the programmer thus might have no other choice than