From owner-freebsd-current@FreeBSD.ORG Sat Nov 15 19:03:23 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9A244CD for ; Sat, 15 Nov 2014 19:03:23 +0000 (UTC) Received: from elvis.mu.org (elvis.mu.org [IPv6:2001:470:1f05:b76::196]) by mx1.freebsd.org (Postfix) with ESMTP id 86C01B33 for ; Sat, 15 Nov 2014 19:03:23 +0000 (UTC) Received: from AlfredMacbookAir.local (c-76-21-10-192.hsd1.ca.comcast.net [76.21.10.192]) by elvis.mu.org (Postfix) with ESMTPSA id 6169F341F83D; Sat, 15 Nov 2014 11:03:23 -0800 (PST) Message-ID: <5467A37B.8010506@mu.org> Date: Sat, 15 Nov 2014 11:03:23 -0800 From: Alfred Perlstein User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Steve Kargl Subject: Re: Finding a rogue src/sys commit with bisection? References: <20141115184332.GA30344@troutmask.apl.washington.edu> <5467A1F2.8000703@mu.org> <20141115190133.GA30576@troutmask.apl.washington.edu> In-Reply-To: <20141115190133.GA30576@troutmask.apl.washington.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Nov 2014 19:03:23 -0000 On 11/15/14, 11:01 AM, Steve Kargl wrote: > On Sat, Nov 15, 2014 at 10:56:50AM -0800, Alfred Perlstein wrote: >> On 11/15/14, 10:43 AM, 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). >>> >>> Rinse and repeat. >>> >> Use git, it has a built in bisector to shake this sort of thing out: >> > I won't be drawn into the git debate. > OK, so we don't want to use a tool purposefully built for the problem you are facing? Doesn't seem like a "git debate" more like hammering in screws... -Alfred