threads / discuss / 3739

Problem with git bisect between 2.6.15 and 2.6.16

Subject: Problem with git bisect between 2.6.15 and 2.6.16

## tl;dr

5 messages between Mar 28, 2006 and Mar 29, 2006.

replies: 4people: 3as markdown or json

Greg Lee· Mar 28, 2006, 00:00 UTC · lore

I get the following when I try to git bisect between 2.6.15 and 2.6.16:
 
[root@Fedora-test tmp]# git clone
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git linux-git
[root@Fedora-test linux-git]# git bisect start
[root@Fedora-test linux-git]# cd linux-git
[root@Fedora-test linux-git]# git bisect good v2.6.16
[root@Fedora-test linux-git]# git bisect bad v2.6.15
dab47a31f42a23d2b374e1cd7d0b797e8e08b23d was both good and bad

What is the proper method to do a bisect between 2.6.15 and 2.6.16?

Greg

sean· Mar 28, 2006, 00:06 UTC · re: Greg Lee · lore

Re: Problem with git bisect between 2.6.15 and 2.6.16

On Mon, 27 Mar 2006 19:00:25 -0500 "Greg Lee" <glee@casabyte.com> wrote:

Show 12 quoted lines

> I get the following when I try to git bisect between 2.6.15 and 2.6.16:
>  
> [root@Fedora-test tmp]# git clone
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git linux-git
> [root@Fedora-test linux-git]# git bisect start
> [root@Fedora-test linux-git]# cd linux-git
> [root@Fedora-test linux-git]# git bisect good v2.6.16
> [root@Fedora-test linux-git]# git bisect bad v2.6.15
> dab47a31f42a23d2b374e1cd7d0b797e8e08b23d was both good and bad
> 
> What is the proper method to do a bisect between 2.6.15 and 2.6.16?
>

You need to do the bisect start after you cd into the linux-git directory. Also, it appears you have the good and bad reversed, presumably the newer (v2.6.16) is bad, and the older (v.2.6.15) is good.

Sean

Greg Lee· Mar 28, 2006, 00:16 UTC · re: sean · lore

RE: Problem with git bisect between 2.6.15 and 2.6.16

> You need to do the bisect start after you cd into the linux-git 
> directory.

Sorry, cut and paste error, I did the cd before the bisect:

[root@Fedora-test git]# git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git linux-git-fresh [root@Fedora-test git]# cd linux-git-fresh/ [root@Fedora-test linux-git-fresh]# git bisect start [root@Fedora-test linux-git-fresh]# git bisect bad v2.6.15 [root@Fedora-test linux-git-fresh]# git bisect good v2.6.16 dab47a31f42a23d2b374e1cd7d0b797e8e08b23d was both good and bad

> Also, it appears you have the good and bad reversed,
> presumably the newer (v2.6.16) is bad, and the older (v.2.6.15)
> is good.

No, the problem was fixed in 2.6.16 and I'm trying to figure out what fixed it so that I can back-port the fix into a previous kernel version, so 2.6.16 is good and 2.6.15 is bad.

Greg

Tony Luck· Mar 28, 2006, 00:22 UTC · re: Greg Lee · lore

Re: Problem with git bisect between 2.6.15 and 2.6.16

> No, the problem was fixed in 2.6.16 and I'm trying to figure out what fixed it so that I
> can back-port the fix into a previous kernel version, so 2.6.16 is good and 2.6.15 is bad.

You'll need to invert "good" and bad" for this. I.e. mark 2.6.15 as good, 2.6.16 as bad, and then as you test mark kernels with the bug as good, and ones without as bad. Try not to go insane while working in this inverted parallel universe :-)

-Tony

Greg Lee· Mar 29, 2006, 19:28 UTC · re: Tony Luck · lore

RE: Problem with git bisect between 2.6.15 and 2.6.16

> You'll need to invert "good" and bad" for this.  I.e. mark 2.6.15 as good, 2.6.16 as

bad, and

> then as you test mark kernels with the bug as good, and ones without as bad.  Try not to

go

> insane while working in this inverted parallel universe :-)
> 
> -Tony

This was progressing fine until I ran into an issue that makes the kernel unstable causing it to crash at semi-random times. I'm down to about 350 commits left in the bisect. I've tried:

git reset --hard HEAD~3

no luck, same problem, unstable

then I tried --hard HEAD~50

no luck, same problem, unstable

I'm concerned about moving too much further in the "~" direction, will this cause me other problems?

Greg