I'm trying to track down a kernel bug -- as detailed in my thread 'Clients fail to boot: 'Error: socket failed: connection refused' (like bug 951526)' -- and I'm just starting to commit bisect the Ubuntu kernels as detailed at https://wiki.ubuntu.com/Kernel/KernelBisection#Commit_bisecting_Ubuntu_kernel_versions
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 https://wiki.ubuntu.com/Kernel/KernelBisection#Bisecting:_a_merge_base_must_be_tested 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 https://wiki.ubuntu.com/Kernel/KernelBisection#Give_this_test_a_version_number. 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? ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
