Re: Finding a rogue src/sys commit with bisection?

On 11/15/14, 10:52 AM, Steve Kargl wrote:
> On Sat, Nov 15, 2014 at 07:46:09PM +0100, Mateusz Guzik wrote:
>> On Sat, Nov 15, 2014 at 10:43:32AM -0800, Steve Kargl wrote:
>>> Before I totally hose by /usr/src directory, does anyone
>>> have some guidelines on doing a binary search for a rogue
>>> commit in /usr/src/sys?.  Either cam or usb (or acpi?) has
>>> broken the ability to remove a external USB device once it
>>> is plugged into a usb port on my Dell Latitude D530 laptop.
>>> I know that a good kernel can be built with r271273 and
>>> a bad kernel comes from (nearly) top of tree at r274456.
>>>
>>> I assume I need to do somthing along the lines
>>>
>>> % cd /usr/src/sys
>>> % svn merge -r 274456:272864    (half way point between good and bad)
>>> (build kernel and test)
>>> % cd /usr/src/sys
>>> % svn revert -R .
>>> (assume 272864 builds working kernel)
>>> % svn merge -r 274456:273660   (1/2 point between 272864 and 274456).
>>>
>> http://search.cpan.org/dist/App-SVN-Bisect/bin/svn-bisect
>>
> There's no instructions on how to install it.
>
>> In absolutely worst case yu can check out git tree and bisect that :->
>>
> Nope.  Learning how to use git and github is well beyond any interest
> I have.

I just sent you a workflow that will take you about 10 minutes to sort 
out for git.

If you want reply in private and I can send you my phone number to show 
how if you get stuck.

-Alfred