Kernel bug hunt - 'Commit bisect start' yields 'A merge base must be tested'

John Hupp lubuntu at
Thu Dec 12 22:36:54 UTC 2013

I'm trying to track down a kernel bug, and I'm just starting to commit 
bisect the Ubuntu kernels as detailed at

However, when I run the 'git bisect start <BAD> <GOOD>' command, it 
responds with 'Bisecting: a merge base must be tested'

This message is explained lightly in the same article's FAQ at

But it doesn't actually say how to test the identified commit. Since 
this is the first result, there is no debian.master/changelog yet (as 
far as I know) to edit as instructed at 
And has git also reset the tree so that the identified merge base commit 
is now the top commit?

Can someone point the way here?

More information about the Lubuntu-users mailing list