Messages in this thread | | | Date | Fri, 20 Jun 2008 12:17:22 +0200 | From | Ingo Molnar <> | Subject | Re: Bisecting tip/auto-x86-next? |
| |
* Kevin Winchester <kjwinchester@gmail.com> wrote:
> Hi, > > I am trying to track down a problem I reported here: > > http://lkml.org/lkml/2008/6/11/431
[ GART related bootup crash. ]
> None or you were cc'd on the original report because I had no idea of > the source of the issue. However, I have now narrowed down the > problem to the auto-x86-next tree. Thus I did something like: > > $ git bisect start > $ git bisect good linus/master > $ git bisect bad tip/auto-x86-next
ok, in that case you can use tip's topical structure and probably bisect purely x86/gart, which has all x86 gart changes.
I.e. do something like this:
git-checkout tip/x86/gart
build and boot that kernel, if it fails and mainline works then do:
git-bisect reset git-bisect start git-bisect good linus/master git-bisect bad tip/x86/gart
this should drastically reduce the number of bisection steps needed, to 3 or 4 iterations.
Ingo
| |