From owner-freebsd-current@FreeBSD.ORG  Sat Sep  3 04:59:51 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 4ED7B106566C;
	Sat,  3 Sep 2011 04:59:51 +0000 (UTC)
	(envelope-from lists@eitanadler.com)
Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com
	[209.85.212.54])
	by mx1.freebsd.org (Postfix) with ESMTP id CB8538FC13;
	Sat,  3 Sep 2011 04:59:50 +0000 (UTC)
Received: by vws18 with SMTP id 18so3651591vws.13
	for <multiple recipients>; Fri, 02 Sep 2011 21:59:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=eitanadler.com; s=0xdeadbeef;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc:content-type;
	bh=4hpvD6ny2l9Cwzeo/VKrbsrVZq/QS9ooo/GpHQ9z150=;
	b=PumvMB8tSWXIIWSHfEgdswSBYkPP8w6tGzyPHhdKYqVLKhoHUi8422YiDHPUrtPTwn
	xV+QB5hF0S88kg1AzZOVdfGw/5y3+VRaG/jJUFH1cqS1LwFYj2bca+FhIMQ8HOrse05o
	GQxYR5Gf6FLLOaUApyHWPNo3H9FqVoXXV0wrc=
Received: by 10.52.187.40 with SMTP id fp8mr731373vdc.42.1315024571182; Fri,
	02 Sep 2011 21:36:11 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.189.131 with HTTP; Fri, 2 Sep 2011 21:35:41 -0700 (PDT)
In-Reply-To: <CAJ-Vmo=k14BTrrUJ4L4=83mjwPPgM7m=ik+hSzNEU4A8Dn+QFQ@mail.gmail.com>
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>
From: Eitan Adler <lists@eitanadler.com>
Date: Sat, 3 Sep 2011 00:35:41 -0400
Message-ID: <CAF6rxgmwk+JXkSN+_TnduogPfD0P-W0MGunWiYSkYAyHVE26Xg@mail.gmail.com>
To: Adrian Chadd <adrian@freebsd.org>
Content-Type: text/plain; charset=UTF-8
Cc: Daniel Eischen <deischen@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 04:59:51 -0000

On Sat, Sep 3, 2011 at 12:24 AM, Adrian Chadd <adrian@freebsd.org> wrote:
> Hi,
>
> The most direct way to fix this is to find the exact commit which
> introduced the break.

>>> Anything else you'd like me to try?

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.

-- 
Eitan Adler