From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Christian Kujau <lists@nerdbynature.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux ppc dev <linuxppc-dev@lists.ozlabs.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: 3.0-rc1: powerpc hangs at Kernel virtual memory layout
Date: Wed, 01 Jun 2011 13:49:03 +1000 [thread overview]
Message-ID: <1306900143.29297.13.camel@pasglop> (raw)
In-Reply-To: <alpine.DEB.2.01.1105311959000.21697@trent.utfs.org>
On Tue, 2011-05-31 at 20:02 -0700, Christian Kujau wrote:
> (Cc'in Linus)
>
> On Tue, 31 May 2011 at 17:48, Christian Kujau wrote:
> > In the meantime, "git bisect" behaves kinda weird, I don't know what went
> > wrong here:
> >
> > $ git bisect start
> > $ git bisect good # Linux 2.6.39
> > $ git bisect bad v3.0-rc1 # Linux 3.0-rc1
> > $ git bisect bad # c44dead70a...
> > $ git bisect bad # d93515611b..
> >
> > ...yet the ./Makefile shows[0] that I'm already way behind: 2.6.39-rc2.
> > Maybe "git bisect" got confused with that whole 2.6.x -> 3.0 renaming?
>
> Hm, I tried again, from a clean v3.0-rc1 (git reset --hard), but after the
> 2nd "git bad" I'm at 2.6.39-rc2 again - while I /should/ be somwhere
> inbetween v2.6.39..v3.0-rc1, right?
Kernel version is totally irrelevant when bisecting. You are not walking
through a linear series of patches but a complex tree of merges which
might have forked off different versions in the first place.
Cheers,
Ben.
next prev parent reply other threads:[~2011-06-01 3:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-31 23:50 3.0-rc1: powerpc hangs at Kernel virtual memory layout Christian Kujau
2011-06-01 0:25 ` Benjamin Herrenschmidt
2011-06-01 0:48 ` Christian Kujau
2011-06-01 1:08 ` Christian Kujau
2011-06-01 3:02 ` Christian Kujau
2011-06-01 3:49 ` Benjamin Herrenschmidt [this message]
2011-06-02 0:16 ` Christian Kujau
2011-06-02 0:47 ` Benjamin Herrenschmidt
2011-06-02 2:57 ` Benjamin Herrenschmidt
2011-06-02 3:06 ` Christian Kujau
2011-06-02 4:27 ` Christian Kujau
2011-06-02 7:33 ` Benjamin Herrenschmidt
2011-06-06 2:11 ` Christian Kujau
2011-06-06 3:46 ` Benjamin Herrenschmidt
2011-06-10 22:54 ` Christian Kujau
2011-06-10 22:59 ` Rafał Miłecki
2011-06-02 6:00 ` Rafał Miłecki
2011-06-02 6:07 ` Rafał Miłecki
2011-06-02 6:16 ` Christian Kujau
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=1306900143.29297.13.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lists@nerdbynature.de \
--cc=torvalds@linux-foundation.org \
/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;
as well as URLs for NNTP newsgroup(s).