Lines Matching +full:eye +full:- +full:term
1 .. SPDX-License-Identifier: (GPL-2.0+ OR CC-BY-4.0)
13 for kernel developers are left to Documentation/process/handling-regressions.rst.
24 #. Report your issue as outlined in Documentation/admin-guide/reporting-issues.rst,
34 #regzbot introduced: v5.13..v5.14-rc1
42 --------------------
69 provides to the userland. It thus does not apply to kernel-internal interfaces
77 Documentation/admin-guide/reporting-issues.rst, it already describes the
83 `regzbot's web-interface <https://linux-regtracking.leemhuis.info/regzbot/>`_.
105 culprit's commit message mentions in lines starting with "Signed-off-by:".
111 #regzbot introduced: v5.13..v5.14-rc1
115 v5.14-rc1 was the first version where you encountered the issue. If you
117 culprit's commit-id instead::
129 kernel regressions <https://linux-regtracking.leemhuis.info/regzbot/>`_ and the
147 reach -- for example, a specific hardware platform, firmware, Linux distro,
158 Documentation/admin-guide/reporting-issues.rst and described in more detail by
159 Documentation/admin-guide/bug-bisect.rst. It might sound like a lot of work, but
161 time-consuming to reliably reproduce the issue, consider teaming up with other
173 ------------------------------------
185 <http://www.kroah.com/log/blog/2018/08/24/what-stable-kernel-should-i-use/>`_.
187 users to test the latest pre-release or regular release. That's also in
196 Documentation/process/handling-regressions.rst.
206 supported by the tree maintainers -- e.g. Linus Torvalds for mainline and
207 Greg Kroah-Hartman et al. for various stable/longterm series.
238 Yes, but the difference has to be significant. A five percent slow-down in a
239 micro-benchmark thus is unlikely to qualify as regression, unless it also
248 externally developed kernel modules, as they run in kernel-space and hook into
275 regularly give mainline pre-releases (say v5.15-rc1 or -rc3) from each
277 integrated between Linux v5.14 and v5.15-rc1 which causes a regression, but at
279 5.15-rc1. All these changes often can simply be reverted and the regression thus
282 started to rely on aspects introduced by one of the follow-up changes: reverting
290 in the previous section. It hence needs to be dealt with on a case-by-case
292 mainline pre-releases.
300 Note, sometimes regressions can't be avoided to make progress -- and the latter
340 Start your machine with a known-good kernel and configure the newer Linux
347 Can I report a regression I found with pre-compiled vanilla kernels?
352 some known-to-be incompatible feature for the newer kernel. If in doubt, report
357 ---------------------------------------------
366 are fixed by keeping an eye on them until they are resolved. Neither of them are
375 the work, with the long term goal to automate regression tracking as much as
387 Check out `regzbot's web-interface <https://linux-regtracking.leemhuis.info/regzbot/>`_.
402 mailing list archive and reply to it using your mailer's "Reply-all" function.
403 In that mail, use one of the following commands in a stand-alone paragraph (IOW:
435 <https://gitlab.com/knurd42/regzbot/-/blob/main/docs/getting_started.md>`_ and
436 the `reference documentation <https://gitlab.com/knurd42/regzbot/-/blob/main/docs/reference.md>`_
440 end-of-content
442 This text is available under GPL-2.0+ or CC-BY-4.0, as stated at the top
443 of the file. If you want to distribute this text under CC-BY-4.0 only,
446 …ub/scm/linux/kernel/git/torvalds/linux.git/plain/Documentation/admin-guide/reporting-regressions.r…
449 is available under CC-BY-4.0, as versions of this text that were processed