From owner-freebsd-current@FreeBSD.ORG  Sat Sep  3 14:45:21 2011
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 36AAE106564A;
	Sat,  3 Sep 2011 14:45:21 +0000 (UTC)
	(envelope-from eischen@vigrid.com)
Received: from mail.netplex.net (mail.netplex.net [204.213.176.10])
	by mx1.freebsd.org (Postfix) with ESMTP id E5AB98FC14;
	Sat,  3 Sep 2011 14:45:20 +0000 (UTC)
Received: from [10.0.0.19] (ip-414b102e.ct.fixed.ntplx.com [65.75.16.46])
	(authenticated bits=0)
	by mail.netplex.net (8.14.4/8.14.4/NETPLEX) with ESMTP id
	p83EW7pv001250
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Sat, 3 Sep 2011 10:32:08 -0400
X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6
	(mail.netplex.net [204.213.176.10]);
	Sat, 03 Sep 2011 10:32:10 -0400 (EDT)
References: <Pine.GSO.4.64.1108242007100.23746@sea.ntplx.net>
	<201108250940.44847.jhb@freebsd.org>
	<Pine.GSO.4.64.1108251313130.28322@sea.ntplx.net>
	<Pine.GSO.4.64.1109021226010.9560@sea.ntplx.net>
	<CAJ-Vmo=k14BTrrUJ4L4=83mjwPPgM7m=ik+hSzNEU4A8Dn+QFQ@mail.gmail.com>
	<CAF6rxgmwk+JXkSN+_TnduogPfD0P-W0MGunWiYSkYAyHVE26Xg@mail.gmail.com>
	<CAJ-Vmo=Y1V0fo+5_MWcnTk_DmoSPRbO8=B6eWLi28T2=yjmzUw@mail.gmail.com>
In-Reply-To: <CAJ-Vmo=Y1V0fo+5_MWcnTk_DmoSPRbO8=B6eWLi28T2=yjmzUw@mail.gmail.com>
Mime-Version: 1.0 (iPhone Mail 8L1)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii
Message-Id: <3C2243F3-8DBA-40A2-A7FF-B668A9809FEE@vigrid.com>
X-Mailer: iPhone Mail (8L1)
From: Daniel Eischen <eischen@vigrid.com>
Date: Sat, 3 Sep 2011 10:32:05 -0400
To: Adrian Chadd <adrian@freebsd.org>
Cc: Daniel Eischen <deischen@freebsd.org>, Eitan Adler <lists@eitanadler.com>,
	"freebsd-current@freebsd.org" <freebsd-current@freebsd.org>
Subject: Re: ath0 no longer attaches, cardbus problems?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Sep 2011 14:45:21 -0000

On Sep 3, 2011, at 2:02 AM, Adrian Chadd <adrian@freebsd.org> wrote:

> On 3 September 2011 12:35, Eitan Adler <lists@eitanadler.com> wrote:
>=20
>> The best way to do this is to find a known working version of the
>> kernel and then "bisect" the version from the known bad and known good
>> versions until you arrive at the breaking commit. It is easier if you
>> look at the svn log to see which commits might matter.  Yes this takes
>> a while, but is the surest way to find the regression.
>=20
> You shouldn't have to try many kernels. 130,000 revisions, only a max
> of 18 attempts needed. :)
>=20
> No, you don't need a whole buildworld. Just try booting the kernel and
> see when it attaches.

There's a reason I haven't upgraded this system in over a year.  It takes a l=
ong time to update the src tree and a long time to build a kernel.  I miss t=
he 2.x/3.x days where you could build world on system like this in about an h=
our or so.

--
DE=