threads / discuss / 7215

bisection oddity.

Subject: bisection oddity.

## tl;dr

2 messages between Mar 12, 2007 and Mar 12, 2007.

replies: 1people: 2as markdown or json

Dave Jones· Mar 12, 2007, 19:28 UTC · lore

I'm chasing a kernel bug that was introduced somewhere between v2.6.20 and 2.6.21rc1, and bisect has done this so far..

git-bisect start # bad: [c8f71b01a50597e298dc3214a2f2be7b8d31170c] Linux 2.6.21-rc1 git-bisect bad c8f71b01a50597e298dc3214a2f2be7b8d31170c # good: [fa285a3d7924a0e3782926e51f16865c5129a2f7] Linux 2.6.20 git-bisect good fa285a3d7924a0e3782926e51f16865c5129a2f7 # bad: [574009c1a895aeeb85eaab29c235d75852b09eb8] Merge branch 'upstream' of git://ftp.linux-mips.org/pub/scm/upstream-linus git-bisect bad 574009c1a895aeeb85eaab29c235d75852b09eb8 # bad: [43187902cbfafe73ede0144166b741fb0f7d04e1] Merge master.kernel.org:/pub/scm/linux/kernel/git/gregkh/driver-2.6 git-bisect bad 43187902cbfafe73ede0144166b741fb0f7d04e1 # good: [1545085a28f226b59c243f88b82ea25393b0d63f] drm: Allow for 44 bit user-tokens (or drm_file offsets) git-bisect good 1545085a28f226b59c243f88b82ea25393b0d63f # good: [c96e2c92072d3e78954c961f53d8c7352f7abbd7] Merge master.kernel.org:/pub/scm/linux/kernel/git/gregkh/usb-2.6 git-bisect good c96e2c92072d3e78954c961f53d8c7352f7abbd7

What I'm puzzled at is that this lands me at 2.6.20-rc5, which is *before* the range I'm interested in. What happened here?

	Dave
-- 
http://www.codemonkey.org.uk
Johannes Schindelin· Mar 12, 2007, 19:50 UTC · re: Dave Jones · lore

Re: bisection oddity.

Hi,
On Mon, 12 Mar 2007, Dave Jones wrote:
Show 19 quoted lines
> I'm chasing a kernel bug that was introduced somewhere between
> v2.6.20 and 2.6.21rc1, and bisect has done this so far..
> 
> git-bisect start
> # bad: [c8f71b01a50597e298dc3214a2f2be7b8d31170c] Linux 2.6.21-rc1
> git-bisect bad c8f71b01a50597e298dc3214a2f2be7b8d31170c
> # good: [fa285a3d7924a0e3782926e51f16865c5129a2f7] Linux 2.6.20
> git-bisect good fa285a3d7924a0e3782926e51f16865c5129a2f7
> # bad: [574009c1a895aeeb85eaab29c235d75852b09eb8] Merge branch 'upstream' of git://ftp.linux-mips.org/pub/scm/upstream-linus
> git-bisect bad 574009c1a895aeeb85eaab29c235d75852b09eb8
> # bad: [43187902cbfafe73ede0144166b741fb0f7d04e1] Merge master.kernel.org:/pub/scm/linux/kernel/git/gregkh/driver-2.6
> git-bisect bad 43187902cbfafe73ede0144166b741fb0f7d04e1
> # good: [1545085a28f226b59c243f88b82ea25393b0d63f] drm: Allow for 44 bit user-tokens (or drm_file offsets)
> git-bisect good 1545085a28f226b59c243f88b82ea25393b0d63f
> # good: [c96e2c92072d3e78954c961f53d8c7352f7abbd7] Merge master.kernel.org:/pub/scm/linux/kernel/git/gregkh/usb-2.6
> git-bisect good c96e2c92072d3e78954c961f53d8c7352f7abbd7
> 
> What I'm puzzled at is that this lands me at 2.6.20-rc5, which is *before*
> the range I'm interested in.  What happened here?
This lands me at
v2.6.20-rc5-301-g31c56d8

which is _not_ an ancestor of v2.6.20 (your first good commit), oddly enough. Start "gitk v2.6.20-rc5-301-g31c56d8...v2.6.20" to see how the commits are related.

So, it is intended behaviour.

Hth, Dscho

← back to recent threads