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?
Date: Fri, 20 Jun 2008 12:17:22 +0200 [thread overview]
Message-ID: <20080620101722.GD17692@elte.hu> (raw)
In-Reply-To: <485AFC9B.7090502@gmail.com>
* 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
next prev parent reply other threads:[~2008-06-20 10:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-20 0:40 Bisecting tip/auto-x86-next? Kevin Winchester
2008-06-20 7:15 ` Sitsofe Wheeler
2008-06-20 10:04 ` Ingo Molnar
2008-06-20 22:23 ` Kevin Winchester
2008-06-20 10:07 ` Ingo Molnar
2008-06-20 10:17 ` Ingo Molnar [this message]
2008-06-20 10:49 ` Pavel Machek
2008-06-20 11:40 ` Kevin Winchester
2008-06-20 10:51 ` Rafael J. Wysocki
2008-06-20 11:37 ` Kevin Winchester
2008-06-20 15:36 ` Ingo Molnar
2008-06-21 0:00 ` Kevin Winchester
2008-06-21 0:14 ` Yinghai Lu
2008-06-21 10:00 ` Kevin Winchester
2008-06-21 10:18 ` Yinghai Lu
2008-06-21 10:23 ` Kevin Winchester
2008-06-21 10:30 ` Yinghai Lu
2008-06-21 10:39 ` Kevin Winchester
2008-06-21 10:50 ` Yinghai Lu
2008-06-21 11:49 ` Kevin Winchester
2008-06-23 11:12 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080620101722.GD17692@elte.hu \
--to=mingo@elte.hu \
--cc=hpa@zytor.com \
--cc=kjwinchester@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--cc=tglx@linutronix.de \
--cc=yhlu.kernel@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox