I was using the upstream linux-stable tree to perform the bisect. To clone that tree, you can run:
git clone git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-stable
Then cd into linux-stable
I used stable v3.2 as the first good and stable v3.3-rc1 as the first bad. Here are the actual commands:
git bisect start
git bisect good v3.2
git bisect bad v3.3-rc1
Or you could use the SHA1's for the kernel versions:
git bisect start
git bisect good 805a6af8dba5dfdd35ec35dc52ec0122400b2610
git bisect bad dcd6c92267155e70a94b3927bce681ce74b80d1f
git will then report the SHA1 for the first kernel build.
Hi Adam,
Here's some info to perform the kernel bisect.
I was using the upstream linux-stable tree to perform the bisect. To clone that tree, you can run: kernel. org/pub/ scm/linux/ kernel/ git/stable/ linux-stable. git linux-stable
git clone git://git.
Then cd into linux-stable
I used stable v3.2 as the first good and stable v3.3-rc1 as the first bad. Here are the actual commands:
git bisect start
git bisect good v3.2
git bisect bad v3.3-rc1
Or you could use the SHA1's for the kernel versions: d35ec35dc52ec01 22400b2610 0a94b3927bce681 ce74b80d1f
git bisect start
git bisect good 805a6af8dba5dfd
git bisect bad dcd6c92267155e7
git will then report the SHA1 for the first kernel build.