Date: Fri, 20 Jun 2008 12:17:22 +0200
From: Ingo Molnar <mingo@elte.hu>
To: Kevin Winchester <kjwinchester@gmail.com>
Cc: Ingo Molnar <mingo@redhat.com>, Thomas Gleixner <tglx@linutronix.de>,
       "H. Peter Anvin" <hpa@zytor.com>,
       Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
       Yinghai Lu <yhlu.kernel@gmail.com>, "Rafael J. Wysocki" <rjw@sisk.pl>,
       Pavel Machek <pavel@ucw.cz>
Subject: Re: Bisecting tip/auto-x86-next?
Message-ID: <20080620101722.GD17692@elte.hu>
References: <485AFC9B.7090502@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <485AFC9B.7090502@gmail.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1185
Lines: 42


* 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/