From: W. Trevor King <wking@drexel.edu>
Date: Mon, 13 Feb 2012 15:19:23 +0000 (-0500)
Subject: Manual bisection of kernel bugs is possible using Git.
X-Git-Url: http://git.tremily.us/?a=commitdiff_plain;h=7bd15e015c780d7a6aebe7df935ec4adfc227cbc;p=blog.git

Manual bisection of kernel bugs is possible using Git.

A note to myself and others who hadn't read the man page ;).
---

diff --git a/posts/Git/notes.org b/posts/Git/notes.org
index 3bff515..e89f7d1 100644
--- a/posts/Git/notes.org
+++ b/posts/Git/notes.org
@@ -783,6 +783,19 @@ Then remove the files with
  | =-f=   | Force                                                       |
  |--------+-------------------------------------------------------------|
 
+** Bisecting a kernel bug (i.e. manual bisection)
+
+Although it is possible to automate this (if you have two boxes, one
+to build kernels and drive the bisection, and one to boot them and
+check the results), it is also possible to bisect kernel bugs "by
+hand" using =git bisect=.  The man page does a better job describing
+the process than I will.
+
+Note that Git will track the bisection state across reboots, which is
+convenient for tracking down kernel bugs.  You need to run =git bisect
+reset= to clear that state.  If you're nervous, you can save the state
+on your own with =git bisect log > your-file=.
+
 * Troubleshooting
 ** Git commit hangs with no output