Lines Matching full:might
21 In all other cases try your best guess which kernel part might be causing the
55 developers. It might be all that's needed for people already familiar with
89 kernel modules on-the-fly, which solutions like DKMS might be doing locally
93 that made the kernel set this flag might be causing the issue you face.
111 thoroughly for reports that might match your issue. If you find anything,
119 situations; during the merge window that actually might be even the best
149 link to it. Include or upload all other information that might be relevant,
188 the issue might have already been fixed there. If you first noticed the
212 might not get the issue solved in older releases: the fix might be too big
219 the issue in mainline, as its commit message might tell you if the fix is
239 experienced users might wonder how to actually do one of those steps. That's
260 so, you might want to mention you'd like to see the issue fixed in the
295 Linux kernel developers: an issue you face with one of them might have been
297 the modifications and enhancements by the vendor might be causing the issue you
302 or might not what you want. You thus might want to consider circumventing the
361 you might be able to provide valuable additional information. That can be
363 developers might look for people that can provide additional information or
367 Note, searching `bugzilla.kernel.org <https://bugzilla.kernel.org/>`_ might also
368 be a good idea, as that might provide valuable insights or turn up matching
372 thus might not even be aware of the bugzilla ticket. Hence, check the ticket if
394 might want to be aware of; it for example explains how to add your issue to the
432 * If you're dealing with a filesystem issue, you might want to check the file
433 system in question with ``fsck``, as it might be damaged in a way that leads
437 changed in parallel to updating the kernel. The problem for example might be
462 kernel modules on-the-fly, which solutions like DKMS might be doing locally
469 the first time. Also remove any modules they might have installed. Then reboot
472 Note, you might not be aware that your system is using one of these solutions:
475 module not part of the Linux kernel. That why your might need to uninstall the
483 that made the kernel set this flag might be causing the issue you face.*
485 The kernel marks itself with a 'taint' flag when something happens that might
486 lead to follow-up errors that look totally unrelated. The issue you face might
510 itself, as the kernel knows it might misbehave in strange ways after that
517 Every Oops and any other problem that happens after that point might be a
523 the cause for the Oops might already be fixed in the newer Linux kernel
530 areas and thus might be causing the issue you face. You therefore have to
533 temporarily uninstall such software including any modules they might have
557 separately, as they might be handled by different developers. Describing
567 might be caused by a bit flip due to cosmic radiation. That's why you should
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
639 interface, which might be something like 'wlp58s0'. This name can be used like
654 MAINTAINERS file, as then you might find something like this::
691 and might leave some work for other developers on the subsystem specific list;
723 Note: in case you cloned the Linux sources with git you might want to call
726 question, as they might be able to help. But use these results with care, as it
737 thoroughly for reports that might match your issue. If you find anything,
760 to check the mailing list archives for the subsystem as well, as someone might
776 situations; during the merge window that actually might be even the best
788 earlier: doing so dramatically increases the risk that your issue report might
815 In about two out of every nine to ten weeks, mainline might point you to a
822 quite busy then and might have no spare time to deal with issue reports. It's
828 That's why it might make sense to wait till the merge window is over. But don't
840 take a few days or weeks. Another reason: the fix you hope for might be too
857 unsuitable for testing and issue reporting: the changes might cause the issue
869 Please note that you might need to build your own kernel manually later: that's
871 document. Also be aware that pre-compiled kernels might lack debug symbols that
873 BUG occurs; if you plan to decode those, you might be better off compiling a
934 users might still be plagued by it, as long as it's not fixed in either stable
982 might need to get from the Linux sources if your distro does not package it)
1007 reason for it in the report. If you're lucky, it might not be needed. And if it
1008 is, someone might help you to get things going. Also be aware this is just one
1050 interpret, which might render your testing useless. Once you found the major
1053 will be able to help without knowing the culprit. Sometimes they might
1064 provides a good deal of other information about regressions you might want to be
1076 link to it. Include or upload all other information that might be relevant,
1109 Also include all the relevant information others might need to understand the
1154 Things that might be wise to provide
1157 Depending on the issue you might need to add more background data. Here are a
1164 * If the issue might be related to your computer hardware, mention what kind
1168 for example is not, because it might be the one from 2012; that one looks
1183 * Gather additional information from the kernel that might be of interest. The
1185 hardware you use. If you have a problem with hardware you even might want to
1187 insights how the components were configured. For some issues it might be
1194 Those examples should give your some ideas of what data might be wise to
1286 might immediately spot what's causing the issue; they then might write a patch
1305 you receive. That includes mails with any additional data you might want to add
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
1332 **Be patient**: If you are really lucky you might get a reply to your report
1334 are scattered around the globe and thus might be in a different time zone – one
1338 reports. Sometimes it will take longer, as they might be busy with the merge
1347 Sometimes the maintainer might not be responding in a timely manner; other
1348 times there might be disagreements, for example if an issue qualifies as
1351 might be appropriate to get a higher authority involved. In case of a WiFi
1353 maintainers or all else fails, it might be one of those rare situations where
1378 including people that want to help, but in the end might guide you totally off
1382 the right people, as a reminder to the maintainer (see below) might be in order
1388 the attention of someone that might help and risk losing it the longer you
1424 to move forward. That might mean: prepare a better report and make those people
1460 easier. And with a bit of luck there might be someone in the team that knows a
1461 bit about programming and might be able to write a fix.
1507 the issue might have already been fixed there. If you first noticed the
1518 vendor applied might be interfering. You need to rule that out by performing
1556 Once your report is out your might get asked to do a proper one, as it allows to
1577 might not get the issue solved in older releases: the fix might be too big
1588 fix you are hoping for might be one of those that won't be backported to the
1614 the issue in mainline, as its commit message might tell you if the fix is
1648 list archive might have the answer you are looking for.
1651 outlined above, as the commit might tell you if a backport can be expected.
1653 * Check the discussions for any indicators the fix might be too risky to get
1727 not get completely stuck, the programmer thus might have no other choice than
1763 (for example by the kernel's build system) might contain content taken from