From owner-freebsd-mobile@FreeBSD.ORG Mon Sep 12 15:21:33 2011 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2E93C1065670; Mon, 12 Sep 2011 15:21:33 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id DF27E8FC12; Mon, 12 Sep 2011 15:21:32 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.4/8.14.3) with ESMTP id p8CFFGq6029356; Mon, 12 Sep 2011 09:15:16 -0600 (MDT) (envelope-from imp@bsdimp.com) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: Date: Mon, 12 Sep 2011 10:15:04 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: <802BD398-6F6B-4584-B1AD-36FDFB23D0D2@bsdimp.com> References: To: Daniel Eischen X-Mailer: Apple Mail (2.1084) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0.1 (harmony.bsdimp.com [127.0.0.1]); Mon, 12 Sep 2011 09:15:17 -0600 (MDT) Cc: Adrian Chadd , freebsd-current@freebsd.org, freebsd-mobile@freebsd.org Subject: Re: Has ath(4) ever worked one release and not worked another, please poke me.. X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Sep 2011 15:21:33 -0000 On Sep 12, 2011, at 8:01 AM, Daniel Eischen wrote: > On Mon, 12 Sep 2011, Adrian Chadd wrote: >=20 >> Hi all, >>=20 >> I've had reports here and there from users who have said ath(4) = worked >> for them in a previous release, and then suddenly stopped working. >> Either it stopped probing at all during boot, or it would probe but >> then spit out errors when trying to get allocated resources. >>=20 >> There's been some recent commits to -HEAD which hopefully have >> resolved a class of problems that cardbus users have seen. But I'd >> like to know if this has popped up for anyone else. >>=20 >> So, if you're "anyone else", and you've got an example piece of >> equipment and an ath(4) NIC which used to work and now doesn't, = please >> step forward. Please only do so if you're willing to help diagnose = the >> problem by downloading/compiling/running older kernel images and >> wrangling verbose boot messages from it all. It's likely going to be >> time consuming and quite tedious. >>=20 >> I'd like to try and nail whatever lingering issues can be tracked = down >> before 9.0-RELEASE if possible. Yes, this even means for older NICs >> (ie, the non-11n ones.) >=20 > As described in previous email to -current, part of r222753 > needs to be backed out in order for my cardbus ath to work. That's not an ath(4) issue, but a cardbus(4) issue. I'll take care of = it after the funeral when I return home, likely next week. Of course, = John can take care of it sooner if he wants. Warner