From owner-freebsd-mobile@FreeBSD.ORG Mon Sep 12 13:15:21 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 F2281106566B for ; Mon, 12 Sep 2011 13:15:21 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.netplex.net (mail.netplex.net [204.213.176.10]) by mx1.freebsd.org (Postfix) with ESMTP id B3BEB8FC1B for ; Mon, 12 Sep 2011 13:15:21 +0000 (UTC) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.14.4/8.14.4/NETPLEX) with ESMTP id p8CD1sal015392; Mon, 12 Sep 2011 09:01:54 -0400 X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-4.2.6 (mail.netplex.net [204.213.176.10]); Mon, 12 Sep 2011 09:01:54 -0400 (EDT) Date: Mon, 12 Sep 2011 09:01:54 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Adrian Chadd In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: 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 Reply-To: Daniel Eischen List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Sep 2011 13:15:22 -0000 On Mon, 12 Sep 2011, Adrian Chadd wrote: > Hi all, > > 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. > > 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. > > 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. > > 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.) As described in previous email to -current, part of r222753 needs to be backed out in order for my cardbus ath to work. -- DE