Lines Matching full:sometimes

238 should be enough for most people. But sometimes there are situations where even
307 Note, the previous paragraph is starting with the word 'most', as sometimes
324 better than not reporting the issue at all: sometimes such reports directly or
416 Problems that look a lot like a kernel issue are sometimes caused by build or
450 Reminder, you are dealing with computers, which sometimes do unexpected things,
520     the issue afterwards. Sometimes simply restarting will be enough, sometimes
529     they are Open Source): they sometimes cause errors in unrelated kernel
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
728 areas rarely changed (like old or unmaintained drivers): sometimes such code is
794    most of the time is better avoided. Longterm kernels (sometimes called 'LTS
844 These aspects are also why longterm kernels (sometimes called "LTS kernels")
870 sometimes needed for debugging or testing fixes, as described later in this
1009 of several ways to decode kernel stack traces. Sometimes different steps will
1053 will be able to help without knowing the culprit. Sometimes they might
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
1580 Even small and seemingly obvious code-changes sometimes introduce new and
1640    weeks, but sometimes it takes a bit longer.
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.
1703 anymore. Sometimes developer stops caring for their code and Linux at all, as
1725 spend on maintenance work on the upstream kernel. Sometimes maintainers also