From owner-freebsd-current@FreeBSD.ORG Sat Nov 15 18:56:35 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D427056C; Sat, 15 Nov 2014 18:56:35 +0000 (UTC) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask.apl.washington.edu", Issuer "troutmask.apl.washington.edu" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B2A5AA4F; Sat, 15 Nov 2014 18:56:35 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.9/8.14.9) with ESMTP id sAFIuZu4030500 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 15 Nov 2014 10:56:35 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.9/8.14.9/Submit) id sAFIuZYI030499; Sat, 15 Nov 2014 10:56:35 -0800 (PST) (envelope-from sgk) Date: Sat, 15 Nov 2014 10:56:35 -0800 From: Steve Kargl To: Ian Lepore Subject: Re: Finding a rogue src/sys commit with bisection? Message-ID: <20141115185635.GB30440@troutmask.apl.washington.edu> References: <20141115184332.GA30344@troutmask.apl.washington.edu> <1416077544.4781.148.camel@revolution.hippie.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1416077544.4781.148.camel@revolution.hippie.lan> User-Agent: Mutt/1.5.23 (2014-03-12) 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 18:56:35 -0000 On Sat, Nov 15, 2014 at 11:52:24AM -0700, Ian Lepore wrote: > On Sat, 2014-11-15 at 10:43 -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). > > > > Rinse and repeat. > > > > I've always used 'svn up -rnnnnnn' to bisect. No need to revert, just > repeatedly update to the next halfway point, and when you're all done, > -rHEAD to get back to normal. I've also had very good results with > using -DNO_CLEAN on kernel bisects, it lets you zoom in quickly then > when you think you have a candidate you can do a more complete > clean-and-rebuild to be sure. Sometimes build glitches will require a > clean rebuild at some bisect points. > Ian, Thanks! I, obviously, had not considered 'svn update' as a method to achieve what I wanti/need to do. -- Steve