Kernel bisecting - which commit is version 4.3.6?

graysky · 2016-03-14 20:19:16

I am following this wiki guide to bisect a kernel bug but find myself stuck at the starting line... how does one find out which commit corresponds to a 2 point release? For example, the good bisect is v4.3.6 but it the source isn't tagged as such. Thanks.

% pwd
/scratch/linux-git/src/linux

% git tag -l "v4.3*"
v4.3
v4.3-rc1
v4.3-rc2
v4.3-rc3
v4.3-rc4
v4.3-rc5
v4.3-rc6
v4.3-rc7

Last edited by graysky (2016-03-14 20:31:27)

ugjka · 2016-03-14 20:26:32

Are the numbers you posted right?

graysky · 2016-03-14 20:31:14

Fixed... I want to know which commit corresponds to the v4.3.6 release (last good) so I can compare it to v4.4 (first bad) and preform the bisect. Thanks!

Last edited by graysky (2016-03-14 20:48:17)

graysky · 2016-03-14 20:52:14

I think I got it by inspecting the changelog on kernel.org for v4.3.6 but I am curious why the 2-point releases aren't captured in the tags...

git bisect good 6a13feb9c82803e2b815eca72fa7a9f5561d7861
git bisect bad 73e7d63efb4d774883a338997943bfa59e127085

WorMzy · 2016-03-14 20:56:38

I'm not an expert in how the kernel developed, but I think you need to checkout the linux-stable git tree, rather than the Linus' mainline kernel git tree. The linux-stable git tree is the one with the refs you're after: https://git.kernel.org/cgit/linux/kerne … .git/refs/

graysky · 2016-03-14 21:17:05

@WorMzy - Thanks for the tip. I only got 4 builds into the bisect before you posted I believe the absolute commit IDs are identical between the two since one is a fork of the other, no?

The AUR PKGBUILD I am using has the following as it gitrepo:
git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git

Your suggestion is:
git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git

Last edited by graysky (2016-03-14 21:18:27)

mich41 · 2016-03-14 22:44:53

graysky wrote:

Your suggestion is:
git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git

Yes, this one. Linus' repo simply doesn't contain those maintenance-only branches, neither tags nor even commits.

loqs · 2016-03-14 22:48:02

Would be interested to know how you get on with this bisect as I understand it 4.3.X (stable) is branch with a different series of patches applied than the patches applied to mainline to become 4.4

mich41 · 2016-03-14 22:52:59

4.3.6 vs 4.4? Indeed, that won't fly. You need to check if 4.3 works and bisect against that.

graysky · 2016-03-14 22:57:31

mich41 wrote:

4.3.6 vs 4.4? Indeed, that won't fly. You need to check if 4.3 works and bisect against that.

graysky wrote:

I think I got it by inspecting the changelog on kernel.org for v4.3.6 but I am curious why the 2-point releases aren't captured in the tags...
git bisect good 6a13feb9c82803e2b815eca72fa7a9f5561d7861
git bisect bad 73e7d63efb4d774883a338997943bfa59e127085

I would think that what I did above would work, no?

mich41 · 2016-03-14 23:06:18

Your "good" is v4.3, not v4.3.6, so it will work on Linus' tree.

However, v4.4 is afd2ff9b7e1b367172f18ba7f693dfb62bdcb2dc and your "bad" is some random commit.

Last edited by mich41 (2016-03-14 23:07:02)

graysky · 2016-03-14 23:26:40

@mich41 -- Grrrr... well, I have completed the bisect and git gave me some good ones and bad ones along the way.

Arch Linux

#1 2016-03-14 20:19:16

Kernel bisecting - which commit is version 4.3.6?

#2 2016-03-14 20:26:32

Re: Kernel bisecting - which commit is version 4.3.6?

#3 2016-03-14 20:31:14

Re: Kernel bisecting - which commit is version 4.3.6?

#4 2016-03-14 20:52:14

Re: Kernel bisecting - which commit is version 4.3.6?

#5 2016-03-14 20:56:38

Re: Kernel bisecting - which commit is version 4.3.6?

#6 2016-03-14 21:17:05

Re: Kernel bisecting - which commit is version 4.3.6?

#7 2016-03-14 22:44:53

Re: Kernel bisecting - which commit is version 4.3.6?

#8 2016-03-14 22:48:02

Re: Kernel bisecting - which commit is version 4.3.6?

#9 2016-03-14 22:52:59

Re: Kernel bisecting - which commit is version 4.3.6?

#10 2016-03-14 22:57:31

Re: Kernel bisecting - which commit is version 4.3.6?

#11 2016-03-14 23:06:18

Re: Kernel bisecting - which commit is version 4.3.6?

#12 2016-03-14 23:26:40

Re: Kernel bisecting - which commit is version 4.3.6?

Board footer