Lines Matching full:sometimes

247 should be enough for most people. But sometimes there are situations where even
316 Note, the previous paragraph is starting with the word 'most', as sometimes
333 better than not reporting the issue at all: sometimes such reports directly or
408 developers sometimes can not avoid incompatibilities when implementing new
431 Problems that look a lot like a kernel issue are sometimes caused by build or
465 Reminder, you are dealing with computers, which sometimes do unexpected things,
535     the issue afterwards. Sometimes simply restarting will be enough, sometimes
544     they are Open Source): they sometimes cause errors in unrelated kernel
667 name is too specific. Sometimes you will need to search on the net for help;
686 that was replaced by a newer solution you need to switch to. Sometimes the code
743 areas rarely changed (like old or unmaintained drivers): sometimes such code is
809    most of the time is better avoided. Longterm kernels (sometimes called 'LTS
859 These aspects are also why longterm kernels (sometimes called "LTS kernels")
885 sometimes needed for debugging or testing fixes, as described later in this
1024 of several ways to decode kernel stack traces. Sometimes different steps will
1068 will be able to help without knowing the culprit. Sometimes they might
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
1594 Even small and seemingly obvious code-changes sometimes introduce new and
1654    weeks, but sometimes it takes a bit longer.
1698 other issues as well. But be aware that sometimes they can't or won't help; and
1699 sometimes there isn't even anyone to send a report to.
1710 but can't: sometimes they lack hardware programming documentation to do so.
1717 anymore. Sometimes developer stops caring for their code and Linux at all, as
1739 spend on maintenance work on the upstream kernel. Sometimes maintainers also