€•™xŒsphinx.addnodes”Œdocument”“”)”}”(Œ rawsource”Œ”Œchildren”]”(Œ translations”Œ LanguagesNode”“”)”}”(hhh]”(hŒ pending_xref”“”)”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…””}”Œparent”hsbaŒ attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ refdomain”Œstd”Œreftype”Œdoc”Œ reftarget”Œ*/translations/zh_CN/admin-guide/bug-bisect”Œmodname”NŒ classname”NŒ refexplicit”ˆuŒtagname”hhh ubh)”}”(hhh]”hŒChinese (Traditional)”…””}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ*/translations/zh_TW/admin-guide/bug-bisect”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒItalian”…””}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ*/translations/it_IT/admin-guide/bug-bisect”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒJapanese”…””}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ*/translations/ja_JP/admin-guide/bug-bisect”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒKorean”…””}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ*/translations/ko_KR/admin-guide/bug-bisect”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒPortuguese (Brazilian)”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ*/translations/pt_BR/admin-guide/bug-bisect”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒSpanish”…””}”hh–sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ*/translations/sp_SP/admin-guide/bug-bisect”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h hhŒ _document”hŒsource”NŒline”NubhŒcomment”“”)”}”(hŒ0SPDX-License-Identifier: (GPL-2.0+ OR CC-BY-4.0)”h]”hŒ0SPDX-License-Identifier: (GPL-2.0+ OR CC-BY-4.0)”…””}”hh·sbah}”(h]”h ]”h"]”h$]”h&]”Œ xml:space”Œpreserve”uh1hµhhh²hh³ŒD/var/lib/git/docbuild/linux/Documentation/admin-guide/bug-bisect.rst”h´Kubh¶)”}”(hŒ<[see the bottom of this file for redistribution information]”h]”hŒ<[see the bottom of this file for redistribution information]”…””}”hhÈsbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1hµhhh²hh³hÇh´KubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒBisecting a regression”h]”hŒBisecting a regression”…””}”(hhÝh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÛhhØh²hh³hÇh´KubhŒ paragraph”“”)”}”(hŒÅThis document describes how to use a ``git bisect`` to find the source code change that broke something -- for example when some functionality stopped working after upgrading from Linux 6.0 to 6.1.”h]”(hŒ%This document describes how to use a ”…””}”(hhíh²hh³Nh´NubhŒliteral”“”)”}”(hŒ``git bisect``”h]”hŒ git bisect”…””}”(hh÷h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hõhhíubhŒ’ to find the source code change that broke something -- for example when some functionality stopped working after upgrading from Linux 6.0 to 6.1.”…””}”(hhíh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÇh´KhhØh²hubhì)”}”(hXtThe text focuses on the gist of the process. If you are new to bisecting the kernel, better follow Documentation/admin-guide/verify-bugs-and-bisect-regressions.rst instead: it depicts everything from start to finish while covering multiple aspects even kernel developers occasionally forget. This includes detecting situations early where a bisection would be a waste of time, as nobody would care about the result -- for example, because the problem happens after the kernel marked itself as 'tainted', occurs in an abandoned version, was already fixed, or is caused by a .config change you or your Linux distributor performed.”h]”hXxThe text focuses on the gist of the process. If you are new to bisecting the kernel, better follow Documentation/admin-guide/verify-bugs-and-bisect-regressions.rst instead: it depicts everything from start to finish while covering multiple aspects even kernel developers occasionally forget. This includes detecting situations early where a bisection would be a waste of time, as nobody would care about the result -- for example, because the problem happens after the kernel marked itself as ‘tainted’, occurs in an abandoned version, was already fixed, or is caused by a .config change you or your Linux distributor performed.”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÇh´K hhØh²hubh×)”}”(hhh]”(hÜ)”}”(hŒ;Finding the change causing a kernel issue using a bisection”h]”hŒ;Finding the change causing a kernel issue using a bisection”…””}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÛhjh²hh³hÇh´Kubhì)”}”(hX×*Note: the following process assumes you prepared everything for a bisection. This includes having a Git clone with the appropriate sources, installing the software required to build and install kernels, as well as a .config file stored in a safe place (the following example assumes '~/prepared_kernel_.config') to use as pristine base at each bisection step; ideally, you have also worked out a fully reliable and straight-forward way to reproduce the regression, too.*”h]”hŒemphasis”“”)”}”(hj0h]”hXÙNote: the following process assumes you prepared everything for a bisection. This includes having a Git clone with the appropriate sources, installing the software required to build and install kernels, as well as a .config file stored in a safe place (the following example assumes ‘~/prepared_kernel_.config’) to use as pristine base at each bisection step; ideally, you have also worked out a fully reliable and straight-forward way to reproduce the regression, too.”…””}”(hj4h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j2hj.ubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÇh´Khjh²hubhŒ bullet_list”“”)”}”(hhh]”hŒ list_item”“”)”}”(hX)Preparation: start the bisection and tell Git about the points in the history you consider to be working and broken, which Git calls 'good' and 'bad':: git bisect start git bisect good v6.0 git bisect bad v6.1 Instead of Git tags like 'v6.0' and 'v6.1' you can specify commit-ids, too. ”h]”(hì)”}”(hŒ—Preparation: start the bisection and tell Git about the points in the history you consider to be working and broken, which Git calls 'good' and 'bad'::”h]”hŒžPreparation: start the bisection and tell Git about the points in the history you consider to be working and broken, which Git calls ‘good’ and ‘bad’:”…””}”(hjRh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÇh´KhjNubhŒ literal_block”“”)”}”(hŒ9git bisect start git bisect good v6.0 git bisect bad v6.1”h]”hŒ9git bisect start git bisect good v6.0 git bisect bad v6.1”…””}”hjbsbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j`h³hÇh´K"hjNubhì)”}”(hŒKInstead of Git tags like 'v6.0' and 'v6.1' you can specify commit-ids, too.”h]”hŒSInstead of Git tags like ‘v6.0’ and ‘v6.1’ you can specify commit-ids, too.”…””}”(hjph²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÇh´K&hjNubeh}”(h]”h ]”h"]”h$]”h&]”uh1jLhjIh²hh³hÇh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œbullet”Œ*”uh1jGh³hÇh´Khjh²hubhŒenumerated_list”“”)”}”(hhh]”(jM)”}”(hŒ¹Copy your prepared .config into the build directory and adjust it to the needs of the codebase Git checked out for testing:: cp ~/prepared_kernel_.config .config make olddefconfig ”h]”(hì)”}”(hŒ|Copy your prepared .config into the build directory and adjust it to the needs of the codebase Git checked out for testing::”h]”hŒ{Copy your prepared .config into the build directory and adjust it to the needs of the codebase Git checked out for testing:”…””}”(hj•h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÇh´K(hj‘ubja)”}”(hŒ6cp ~/prepared_kernel_.config .config make olddefconfig”h]”hŒ6cp ~/prepared_kernel_.config .config make olddefconfig”…””}”hj£sbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j`h³hÇh´K+hj‘ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jLhjŽh²hh³hÇh´NubjM)”}”(hŒôNow build, install, and boot a kernel. This might fail for unrelated reasons, for example, when a compile error happens at the current stage of the bisection a later change resolves. In such cases run ``git bisect skip`` and go back to step 1. ”h]”hì)”}”(hŒóNow build, install, and boot a kernel. This might fail for unrelated reasons, for example, when a compile error happens at the current stage of the bisection a later change resolves. In such cases run ``git bisect skip`` and go back to step 1.”h]”(hŒÉNow build, install, and boot a kernel. This might fail for unrelated reasons, for example, when a compile error happens at the current stage of the bisection a later change resolves. In such cases run ”…””}”(hj»h²hh³Nh´Nubhö)”}”(hŒ``git bisect skip``”h]”hŒgit bisect skip”…””}”(hjÃh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hõhj»ubhŒ and go back to step 1.”…””}”(hj»h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÇh´K.hj·ubah}”(h]”h ]”h"]”h$]”h&]”uh1jLhjŽh²hh³hÇh´NubjM)”}”(hXíCheck if the functionality that regressed works in the kernel you just built. If it works, execute:: git bisect good If it is broken, run:: git bisect bad Note, getting this wrong just once will send the rest of the bisection totally off course. To prevent having to start anew later you thus want to ensure what you tell Git is correct; it is thus often wise to spend a few minutes more on testing in case your reproducer is unreliable. After issuing one of these two commands, Git will usually check out another bisection point and print something like 'Bisecting: 675 revisions left to test after this (roughly 10 steps)'. In that case go back to step 1. If Git instead prints something like 'cafecaca0c0dacafecaca0c0dacafecaca0c0da is the first bad commit', then you have finished the bisection. In that case move to the next point below. Note, right after displaying that line Git will show some details about the culprit including its patch description; this can easily fill your terminal, so you might need to scroll up to see the message mentioning the culprit's commit-id. In case you missed Git's output, you can always run ``git bisect log`` to print the status: it will show how many steps remain or mention the result of the bisection. ”h]”(hì)”}”(hŒMCheck if the functionality that regressed works in the kernel you just built.”h]”hŒMCheck if the functionality that regressed works in the kernel you just built.”…””}”(hjåh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÇh´K3hjáubhì)”}”(hŒIf it works, execute::”h]”hŒIf it works, execute:”…””}”(hjóh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÇh´K5hjáubja)”}”(hŒgit bisect good”h]”hŒgit bisect good”…””}”hjsbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j`h³hÇh´K7hjáubhì)”}”(hŒIf it is broken, run::”h]”hŒIf it is broken, run:”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÇh´K9hjáubja)”}”(hŒgit bisect bad”h]”hŒgit bisect bad”…””}”hjsbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j`h³hÇh´K;hjáubhì)”}”(hXNote, getting this wrong just once will send the rest of the bisection totally off course. To prevent having to start anew later you thus want to ensure what you tell Git is correct; it is thus often wise to spend a few minutes more on testing in case your reproducer is unreliable.”h]”hXNote, getting this wrong just once will send the rest of the bisection totally off course. To prevent having to start anew later you thus want to ensure what you tell Git is correct; it is thus often wise to spend a few minutes more on testing in case your reproducer is unreliable.”…””}”(hj+h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÇh´K=hjáubhì)”}”(hŒÛAfter issuing one of these two commands, Git will usually check out another bisection point and print something like 'Bisecting: 675 revisions left to test after this (roughly 10 steps)'. In that case go back to step 1.”h]”hŒßAfter issuing one of these two commands, Git will usually check out another bisection point and print something like ‘Bisecting: 675 revisions left to test after this (roughly 10 steps)’. In that case go back to step 1.”…””}”(hj9h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÇh´KBhjáubhì)”}”(hX§If Git instead prints something like 'cafecaca0c0dacafecaca0c0dacafecaca0c0da is the first bad commit', then you have finished the bisection. In that case move to the next point below. Note, right after displaying that line Git will show some details about the culprit including its patch description; this can easily fill your terminal, so you might need to scroll up to see the message mentioning the culprit's commit-id.”h]”hX­If Git instead prints something like ‘cafecaca0c0dacafecaca0c0dacafecaca0c0da is the first bad commit’, then you have finished the bisection. In that case move to the next point below. Note, right after displaying that line Git will show some details about the culprit including its patch description; this can easily fill your terminal, so you might need to scroll up to see the message mentioning the culprit’s commit-id.”…””}”(hjGh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÇh´KFhjáubhì)”}”(hŒ¦In case you missed Git's output, you can always run ``git bisect log`` to print the status: it will show how many steps remain or mention the result of the bisection.”h]”(hŒ6In case you missed Git’s output, you can always run ”…””}”(hjUh²hh³Nh´Nubhö)”}”(hŒ``git bisect log``”h]”hŒgit bisect log”…””}”(hj]h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hõhjUubhŒ` to print the status: it will show how many steps remain or mention the result of the bisection.”…””}”(hjUh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÇh´KMhjáubeh}”(h]”h ]”h"]”h$]”h&]”uh1jLhjŽh²hh³hÇh´Nubeh}”(h]”h ]”h"]”h$]”h&]”Œenumtype”Œarabic”Œprefix”hŒsuffix”Œ.”uh1jŒhjh²hh³hÇh´K(ubjH)”}”(hhh]”(jM)”}”(hXRecommended complementary task: put the bisection log and the current .config file aside for the bug report; furthermore tell Git to reset the sources to the state before the bisection:: git bisect log > ~/bisection-log cp .config ~/bisection-config-culprit git bisect reset ”h]”(hì)”}”(hŒºRecommended complementary task: put the bisection log and the current .config file aside for the bug report; furthermore tell Git to reset the sources to the state before the bisection::”h]”hŒ¹Recommended complementary task: put the bisection log and the current .config file aside for the bug report; furthermore tell Git to reset the sources to the state before the bisection:”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÇh´KQhj‰ubja)”}”(hŒWgit bisect log > ~/bisection-log cp .config ~/bisection-config-culprit git bisect reset”h]”hŒWgit bisect log > ~/bisection-log cp .config ~/bisection-config-culprit git bisect reset”…””}”hj›sbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j`h³hÇh´KUhj‰ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jLhj†h²hh³hÇh´NubjM)”}”(hXZRecommended optional task: try reverting the culprit on top of the latest codebase and check if that fixes your bug; if that is the case, it validates the bisection and enables developers to resolve the regression through a revert. To try this, update your clone and check out latest mainline. Then tell Git to revert the change by specifying its commit-id:: git revert --no-edit cafec0cacaca0 Git might reject this, for example when the bisection landed on a merge commit. In that case, abandon the attempt. Do the same, if Git fails to revert the culprit on its own because later changes depend on it -- at least unless you bisected a stable or longterm kernel series, in which case you want to check out its latest codebase and try a revert there. If a revert succeeds, build and test another kernel to check if reverting resolved your regression. ”h]”(hì)”}”(hŒçRecommended optional task: try reverting the culprit on top of the latest codebase and check if that fixes your bug; if that is the case, it validates the bisection and enables developers to resolve the regression through a revert.”h]”hŒçRecommended optional task: try reverting the culprit on top of the latest codebase and check if that fixes your bug; if that is the case, it validates the bisection and enables developers to resolve the regression through a revert.”…””}”(hj³h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÇh´KYhj¯ubhì)”}”(hŒ~To try this, update your clone and check out latest mainline. Then tell Git to revert the change by specifying its commit-id::”h]”hŒ}To try this, update your clone and check out latest mainline. Then tell Git to revert the change by specifying its commit-id:”…””}”(hjÁh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÇh´K^hj¯ubja)”}”(hŒ"git revert --no-edit cafec0cacaca0”h]”hŒ"git revert --no-edit cafec0cacaca0”…””}”hjÏsbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j`h³hÇh´Kahj¯ubhì)”}”(hXdGit might reject this, for example when the bisection landed on a merge commit. In that case, abandon the attempt. Do the same, if Git fails to revert the culprit on its own because later changes depend on it -- at least unless you bisected a stable or longterm kernel series, in which case you want to check out its latest codebase and try a revert there.”h]”hXdGit might reject this, for example when the bisection landed on a merge commit. In that case, abandon the attempt. Do the same, if Git fails to revert the culprit on its own because later changes depend on it -- at least unless you bisected a stable or longterm kernel series, in which case you want to check out its latest codebase and try a revert there.”…””}”(hjÝh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÇh´Kchj¯ubhì)”}”(hŒcIf a revert succeeds, build and test another kernel to check if reverting resolved your regression.”h]”hŒcIf a revert succeeds, build and test another kernel to check if reverting resolved your regression.”…””}”(hjëh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÇh´Kihj¯ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jLhj†h²hh³hÇh´Nubeh}”(h]”h ]”h"]”h$]”h&]”jŠj‹uh1jGh³hÇh´KQhjh²hubhì)”}”(hŒ|With that the process is complete. Now report the regression as described by Documentation/admin-guide/reporting-issues.rst.”h]”hŒ|With that the process is complete. Now report the regression as described by Documentation/admin-guide/reporting-issues.rst.”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÇh´Klhjh²hubh×)”}”(hhh]”(hÜ)”}”(hŒBisecting linux-next”h]”hŒBisecting linux-next”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÛhjh²hh³hÇh´Kpubhì)”}”(hŒÛIf you face a problem only happening in linux-next, bisect between the linux-next branches 'stable' and 'master'. The following commands will start the process for a linux-next tree you added as a remote called 'next'::”h]”hŒæIf you face a problem only happening in linux-next, bisect between the linux-next branches ‘stable’ and ‘master’. The following commands will start the process for a linux-next tree you added as a remote called ‘next’:”…””}”(hj$h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÇh´Krhjh²hubja)”}”(hŒGgit bisect start git bisect good next/stable git bisect bad next/master”h]”hŒGgit bisect start git bisect good next/stable git bisect bad next/master”…””}”hj2sbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j`h³hÇh´Kvhjh²hubhì)”}”(hŒéThe 'stable' branch refers to the state of linux-mainline that the current linux-next release (found in the 'master' branch) is based on -- the former thus should be free of any problems that show up in -next, but not in Linus' tree.”h]”hŒóThe ‘stable’ branch refers to the state of linux-mainline that the current linux-next release (found in the ‘master’ branch) is based on -- the former thus should be free of any problems that show up in -next, but not in Linus’ tree.”…””}”(hj@h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÇh´Kzhjh²hubhì)”}”(hXOThis will bisect across a wide range of changes, some of which you might have used in earlier linux-next releases without problems. Sadly there is no simple way to avoid checking them: bisecting from one linux-next release to a later one (say between 'next-20241020' and 'next-20241021') is impossible, as they share no common history.”h]”hXWThis will bisect across a wide range of changes, some of which you might have used in earlier linux-next releases without problems. Sadly there is no simple way to avoid checking them: bisecting from one linux-next release to a later one (say between ‘next-20241020’ and ‘next-20241021’) is impossible, as they share no common history.”…””}”(hjNh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÇh´Khjh²hubeh}”(h]”Œbisecting-linux-next”ah ]”h"]”Œbisecting linux-next”ah$]”h&]”uh1hÖhjh²hh³hÇh´Kpubh×)”}”(hhh]”(hÜ)”}”(hŒAdditional reading material”h]”hŒAdditional reading material”…””}”(hjgh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÛhjdh²hh³hÇh´K†ubjH)”}”(hhh]”(jM)”}”(hŒÀThe `man page for 'git bisect' `_ and `fighting regressions with 'git bisect' `_ in the Git documentation.”h]”hì)”}”(hŒÀThe `man page for 'git bisect' `_ and `fighting regressions with 'git bisect' `_ in the Git documentation.”h]”(hŒThe ”…””}”(hj|h²hh³Nh´NubhŒ reference”“”)”}”(hŒB`man page for 'git bisect' `_”h]”hŒman page for ‘git bisect’”…””}”(hj†h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”Œman page for 'git bisect'”Œrefuri”Œ#https://git-scm.com/docs/git-bisect”uh1j„hj|ubhŒtarget”“”)”}”(hŒ& ”h]”h}”(h]”Œman-page-for-git-bisect”ah ]”h"]”Œman page for 'git bisect'”ah$]”h&]”Œrefuri”j—uh1j˜Œ referenced”Khj|ubhŒ and ”…””}”(hj|h²hh³Nh´Nubj…)”}”(hŒ[`fighting regressions with 'git bisect' `_”h]”hŒ*fighting regressions with ‘git bisect’”…””}”(hj¬h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”Œ&fighting regressions with 'git bisect'”j–Œ/https://git-scm.com/docs/git-bisect-lk2009.html”uh1j„hj|ubj™)”}”(hŒ2 ”h]”h}”(h]”Œ$fighting-regressions-with-git-bisect”ah ]”h"]”Œ&fighting regressions with 'git bisect'”ah$]”h&]”Œrefuri”j¼uh1j˜j§Khj|ubhŒ in the Git documentation.”…””}”(hj|h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÇh´Kˆhjxubah}”(h]”h ]”h"]”h$]”h&]”uh1jLhjuh²hh³hÇh´NubjM)”}”(hŒ}`Working with git bisect `_ from kernel developer Nathan Chancellor.”h]”hì)”}”(hŒ}`Working with git bisect `_ from kernel developer Nathan Chancellor.”h]”(j…)”}”(hŒT`Working with git bisect `_”h]”hŒWorking with git bisect”…””}”(hjâh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”ŒWorking with git bisect”j–Œ7https://nathanchance.dev/posts/working-with-git-bisect/”uh1j„hjÞubj™)”}”(hŒ: ”h]”h}”(h]”Œworking-with-git-bisect”ah ]”h"]”Œworking with git bisect”ah$]”h&]”Œrefuri”jòuh1j˜j§KhjÞubhŒ) from kernel developer Nathan Chancellor.”…””}”(hjÞh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÇh´K‹hjÚubah}”(h]”h ]”h"]”h$]”h&]”uh1jLhjuh²hh³hÇh´NubjM)”}”(hŒ_`Using Git bisect to figure out when brokenness was introduced `_.”h]”hì)”}”(hjh]”(j…)”}”(hŒ^`Using Git bisect to figure out when brokenness was introduced `_”h]”hŒ=Using Git bisect to figure out when brokenness was introduced”…””}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”Œ=Using Git bisect to figure out when brokenness was introduced”j–Œhttp://webchick.net/node/99”uh1j„hjubj™)”}”(hŒ ”h]”h}”(h]”Œ=using-git-bisect-to-figure-out-when-brokenness-was-introduced”ah ]”h"]”Œ=using git bisect to figure out when brokenness was introduced”ah$]”h&]”Œrefuri”j'uh1j˜j§KhjubhŒ.”…””}”(hjh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÇh´Khjubah}”(h]”h ]”h"]”h$]”h&]”uh1jLhjuh²hh³hÇh´NubjM)”}”(hŒV`Fully automated bisecting with 'git bisect run' `_. ”h]”hì)”}”(hŒU`Fully automated bisecting with 'git bisect run' `_.”h]”(j…)”}”(hŒT`Fully automated bisecting with 'git bisect run' `_”h]”hŒ3Fully automated bisecting with ‘git bisect run’”…””}”(hjMh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”Œ/Fully automated bisecting with 'git bisect run'”j–Œhttps://lwn.net/Articles/317154”uh1j„hjIubj™)”}”(hŒ" ”h]”h}”(h]”Œ-fully-automated-bisecting-with-git-bisect-run”ah ]”h"]”Œ/fully automated bisecting with 'git bisect run'”ah$]”h&]”Œrefuri”j]uh1j˜j§KhjIubhŒ.”…””}”(hjIh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÇh´KŽhjEubah}”(h]”h ]”h"]”h$]”h&]”uh1jLhjuh²hh³hÇh´Nubeh}”(h]”h ]”h"]”h$]”h&]”jŠj‹uh1jGh³hÇh´Kˆhjdh²hubh¶)”}”(hŒend-of-content”h]”hŒend-of-content”…””}”hjsbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1hµhjdh²hh³hÇh´K‘ubh¶)”}”(hXèThis document is maintained by Thorsten Leemhuis . If you spot a typo or small mistake, feel free to let him know directly and he'll fix it. You are free to do the same in a mostly informal way if you want to contribute changes to the text -- but for copyright reasons please CC linux-doc@vger.kernel.org and 'sign-off' your contribution as Documentation/process/submitting-patches.rst explains in the section 'Sign your work - the Developer's Certificate of Origin'.”h]”hXèThis document is maintained by Thorsten Leemhuis . If you spot a typo or small mistake, feel free to let him know directly and he'll fix it. You are free to do the same in a mostly informal way if you want to contribute changes to the text -- but for copyright reasons please CC linux-doc@vger.kernel.org and 'sign-off' your contribution as Documentation/process/submitting-patches.rst explains in the section 'Sign your work - the Developer's Certificate of Origin'.”…””}”hjsbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1hµhjdh²hh³hÇh´K™ubh¶)”}”(hXeThis text is available under GPL-2.0+ or CC-BY-4.0, as stated at the top of the file. If you want to distribute this text under CC-BY-4.0 only, please use 'The Linux kernel development community' for author attribution and link this as source: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/plain/Documentation/admin-guide/bug-bisect.rst”h]”hXeThis text is available under GPL-2.0+ or CC-BY-4.0, as stated at the top of the file. If you want to distribute this text under CC-BY-4.0 only, please use 'The Linux kernel development community' for author attribution and link this as source: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/plain/Documentation/admin-guide/bug-bisect.rst”…””}”hjsbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1hµhjdh²hh³hÇh´K ubh¶)”}”(hXNote: Only the content of this RST file as found in the Linux kernel sources is available under CC-BY-4.0, as versions of this text that were processed (for example by the kernel's build system) might contain content taken from files which use a more restrictive license.”h]”hXNote: Only the content of this RST file as found in the Linux kernel sources is available under CC-BY-4.0, as versions of this text that were processed (for example by the kernel's build system) might contain content taken from files which use a more restrictive license.”…””}”hj«sbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1hµhjdh²hh³hÇh´K¥ubeh}”(h]”Œadditional-reading-material”ah ]”h"]”Œadditional reading material”ah$]”h&]”uh1hÖhjh²hh³hÇh´K†ubeh}”(h]”Œ;finding-the-change-causing-a-kernel-issue-using-a-bisection”ah ]”h"]”Œ;finding the change causing a kernel issue using a bisection”ah$]”h&]”uh1hÖhhØh²hh³hÇh´Kubeh}”(h]”Œbisecting-a-regression”ah ]”h"]”Œbisecting a regression”ah$]”h&]”uh1hÖhhh²hh³hÇh´Kubeh}”(h]”h ]”h"]”h$]”h&]”Œsource”hÇuh1hŒcurrent_source”NŒ current_line”NŒsettings”Œdocutils.frontend”ŒValues”“”)”}”(hÛNŒ generator”NŒ datestamp”NŒ source_link”NŒ source_url”NŒ toc_backlinks”Œentry”Œfootnote_backlinks”KŒ sectnum_xform”KŒstrip_comments”NŒstrip_elements_with_classes”NŒ strip_classes”NŒ report_level”KŒ halt_level”KŒexit_status_level”KŒdebug”NŒwarning_stream”NŒ traceback”ˆŒinput_encoding”Œ utf-8-sig”Œinput_encoding_error_handler”Œstrict”Œoutput_encoding”Œutf-8”Œoutput_encoding_error_handler”jôŒerror_encoding”Œutf-8”Œerror_encoding_error_handler”Œbackslashreplace”Œ language_code”Œen”Œrecord_dependencies”NŒconfig”NŒ id_prefix”hŒauto_id_prefix”Œid”Œ dump_settings”NŒdump_internals”NŒdump_transforms”NŒdump_pseudo_xml”NŒexpose_internals”NŒstrict_visitor”NŒ_disable_config”NŒ_source”hÇŒ _destination”NŒ _config_files”]”Œ7/var/lib/git/docbuild/linux/Documentation/docutils.conf”aŒfile_insertion_enabled”ˆŒ raw_enabled”KŒline_length_limit”M'Œpep_references”NŒ pep_base_url”Œhttps://peps.python.org/”Œpep_file_url_template”Œpep-%04d”Œrfc_references”NŒ rfc_base_url”Œ&https://datatracker.ietf.org/doc/html/”Œ tab_width”KŒtrim_footnote_reference_space”‰Œsyntax_highlight”Œlong”Œ smart_quotes”ˆŒsmartquotes_locales”]”Œcharacter_level_inline_markup”‰Œdoctitle_xform”‰Œ docinfo_xform”KŒsectsubtitle_xform”‰Œ image_loading”Œlink”Œembed_stylesheet”‰Œcloak_email_addresses”ˆŒsection_self_link”‰Œenv”NubŒreporter”NŒindirect_targets”]”Œsubstitution_defs”}”Œsubstitution_names”}”Œrefnames”}”Œrefids”}”Œnameids”}”(jÎjËjÆjÃjaj^j¾j»j£j jÆjÃjüjùj1j.jgjduŒ nametypes”}”(jΉjƉja‰j¾‰j£ˆjƈjüˆj1ˆjgˆuh}”(jËhØjÃjj^jj»jdj jšjÃj½jùjój.j(jdj^uŒ footnote_refs”}”Œ citation_refs”}”Œ autofootnotes”]”Œautofootnote_refs”]”Œsymbol_footnotes”]”Œsymbol_footnote_refs”]”Œ footnotes”]”Œ citations”]”Œautofootnote_start”KŒsymbol_footnote_start”KŒ id_counter”Œ collections”ŒCounter”“”}”…”R”Œparse_messages”]”Œtransform_messages”]”Œ transformer”NŒ include_log”]”Œ decoration”Nh²hub.