On 10/11/2016 23:45, Moby wrote:
The general prescription is as follows:
git bisect reset git bisect start git bisect bad git bisect good v4.5
Build and test the resulting kernel, then
git bisect good or git bisect bad, whichever is appropriate. Repeat the previous step.
When yo do the above, what happens? If it fails, please post the console output.
Larry
The bisect is done - I think. In addition to the bug with the Makefile,
I also kept running into a kernel bug that kept causing segfaults in
wpa_supplicant.
I started with kernel 4.8.1, which had the packet loss, and I did a
bisect bad on it. Then I checked out v4.5, which did not have packet
loss in it, and I did bisect good on it. From then on, almost every
bisect resulted in a kernel where wpa_supplicant kept segfaulting.
Ikept doing a bisect good on these, since I wanted the bisection to
"proceed towards 4.8.1" - I am not sure if this was the right thing to
do. However, at the end of all this, I am sitting at version
4.6.0-rc7-1-default+, and git bisect good replies with:
2dcd0af568b0cf583645c8a317dd12e344b1c72a is the first bad commit
commit 2dcd0af568b0cf583645c8a317dd12e344b1c72a
Author: Linus Torvalds