Lines Matching full:guide

26    https://docs.kernel.org/admin-guide/verify-bugs-and-bisect-regressions.html
32 over to the* ':ref:`step-by-step guide <introguide_bissbs>`' *below. It utilizes
73     # * Note, when short on storage space, check the guide for an alternative:
101        #   job. See the step-by-step guide for further details.
222 Step-by-step guide on how to verify bugs and bisect regressions
225 This guide describes how to set up your own Linux kernels for investigating bugs
247  :ref:`Complementary tasks: cleanup during and after following this guide <introclosure_bissbs>`.
258 out Documentation/admin-guide/reporting-issues.rst, which works in conjunction
267 as a regression check out Documentation/admin-guide/reporting-regressions.rst.
269 If you run into any problems while following this guide or have ideas how to
312   guide:
314   * Do you follow this guide to verify if a bug is present in the code the
340   throughout this guide will refer to the last kernel that has been working
374   them, as all further commands in this guide are meant to be executed from
451   since you started that guide, ensure that you tried using the feature causing
467   during this guide, this is most likely the reason. You can reduce or nearly
588   much your kernels actually require will be determined later during this guide.
614 * In case you plan to follow this guide further, check how much storage space
694   stable team. See Documentation/admin-guide/reporting-issues.rst for details.
698 Do you follow this guide to verify if a problem is present in the code
701 :ref:`Complementary tasks: cleanup during and after following this guide <introclosure_bissbs>`.
793   In case you skipped the 'test latest codebase' step in the guide, check its
923 During and after following this guide you might want or need to remove some of
930   identifier. This guide stores them in '~/kernels-built', but the following
936   actual bisection (e.g. segment 3 of this guide). The two ones you created
1063 You have reached the end of the step-by-step guide.
1067 improve the guide?
1077 Reference section for the step-by-step guide
1081 step-by-step guide.
1089 The steps in all later sections of this guide depend on those described here.
1091 [:ref:`back to step-by-step guide <introprep_bissbs>`].
1106 [:ref:`back to step-by-step guide <backup_bissbs>`]
1118 But there is a more important reason why this guide contains this step: most
1121 considered 'vanilla' anymore, as Documentation/admin-guide/reporting-issues.rst
1124 [:ref:`back to step-by-step guide <vanilla_bissbs>`]
1141 its purpose; 'Documentation/admin-guide/module-signing.rst' and various web
1161 [:ref:`back to step-by-step guide <secureboot_bissbs>`]
1174 [:ref:`back to step-by-step guide <bootworking_bissbs>`]
1192 [:ref:`back to step-by-step guide <diskspace_bissbs>`]
1200   guide.* [:ref:`...<rangecheck_bissbs>`]
1214 will be built and tested in the segment '2' of this guide; Git would force you
1217 [:ref:`back to step-by-step guide <rangecheck_bissbs>`]
1265 for tasks not covered in this guide -- for example when building utilities from
1268 [:ref:`back to step-by-step guide <buildrequires_bissbs>`]
1278 The step-by-step guide outlines how to download the Linux sources using a full
1312 [:ref:`back to step-by-step guide <sources_bissbs>`]
1336 branches as explained in the step-by-step guide.
1358 [:ref:`back to step-by-step guide <sources_bissbs>`]
1369 *Note, this is the first of multiple steps in this guide that create or modify
1370 build artifacts. The commands used in this guide store them right in the source
1373 ``O=~/linux-builddir/`` to all make calls used throughout this guide. You will
1383   delete it. This for example is important in case you followed this guide
1388   kernel and will use defaults, as briefly outlined in the guide. In that case
1409 (say 5.15). That's one of the reasons why the previous step in the guide told
1419 [:ref:`back to step-by-step guide <oldconfig_bissbs>`]
1429 As explained briefly in the step-by-step guide already: with localmodconfig it
1464 step-by-step guide mentions::
1468 [:ref:`back to step-by-step guide <localmodconfig_bissbs>`]
1484 [:ref:`back to step-by-step guide <tagging_bissbs>`]
1510 'Decode failure messages' in Documentation/admin-guide/reporting-issues.rst
1513 [:ref:`back to step-by-step guide <debugsymbols_bissbs>`]
1534 when following this guide on a few commodity distributions.
1547   Documentation/admin-guide/module-signing.rst.
1549 [:ref:`back to step-by-step guide <configmods_bissbs>`]
1566 [:ref:`back to step-by-step guide <configmods_bissbs>`]
1577 directory every time during this guide before you start building another
1583 [:ref:`back to step-by-step guide <saveconfig_bissbs>`]
1611   Documentation/admin-guide/reporting-regressions.rst explains in more detail.
1637 [:ref:`back to step-by-step guide <introlatestcheck_bissbs>`]
1651 [:ref:`back to step-by-step guide <checkoutmaster_bissbs>`]
1703 The step-by-step guide uses the default make targets (e.g. 'bzImage' and
1705 steps of the guide then install. You instead can also directly build everything
1719 step-by-step guide's instructions on installing and removing your kernel;
1727 [:ref:`back to step-by-step guide <build_bissbs>`]
1736 What you need to do after executing the command in the step-by-step guide
1770 [:ref:`back to step-by-step guide <install_bissbs>`]
1787 the guide will match all files needed to boot your kernel -- but neither the
1791 [:ref:`back to step-by-step guide <storagespace_bissbs>`]
1807 Documentation/admin-guide/tainted-kernels.rst; doing so is also in your own
1810 [:ref:`back to step-by-step guide <tainted_bissbs>`]
1833   be a problem that is specific to that series; the next step in this guide will
1836 [:ref:`back to step-by-step guide <recheckbroken_bissbs>`]
1851 [:ref:`back to step-by-step guide <recheckstablebroken_bissbs>`]
1871 Many readers of this guide normally run kernels that are patched, use add-on
1881 [:ref:`back to step-by-step guide <introworkingcheck_bissbs>`]
1915 [:ref:`back to step-by-step guide <recheckworking_bissbs>`]
1925 [:ref:`back to step-by-step guide <introbisect_bissbs>`].
1939 [:ref:`back to step-by-step guide <bisectstart_bissbs>`]
1967 [:ref:`back to step-by-step guide <bisectbuild_bissbs>`]
1981 [:ref:`back to step-by-step guide <bisecttest_bissbs>`]
2001 [:ref:`back to step-by-step guide <bisectlog_bissbs>`]
2016 The step-by-step guide covers everything relevant already except one slightly
2022 [:ref:`back to step-by-step guide <revert_bissbs>`]
2024 Cleanup steps during and after following this guide
2027   *During and after following this guide you might want or need to remove some
2032 [:ref:`back to step-by-step guide <introclosure_bissbs>`].
2058 step-by-step guide will delete all of these files for you while also removing
2075 [:ref:`back to step-by-step guide <makeroom_bissbs>`]
2087 the step-by-step guide might not free as much space as you would like. In that
2102 [:ref:`back to step-by-step guide <finishingtouch_bissbs>`]
2118 [:ref:`back to step-by-step guide <introoptional_bissbs>`].
2129 To compile kernels on another system, slightly alter the step-by-step guide's
2132 * Start following the guide on the machine where you want to install and test
2143 * Continue the guide on the build host (e.g. with ':ref:`Ensure to have enough
2158 * Continue the guide, but ignore the instructions outlining how to compile,
2216 …org/pub/scm/linux/kernel/git/torvalds/linux.git/plain/Documentation/admin-guide/verify-bugs-and-bi…