From owner-freebsd-current@FreeBSD.ORG Mon Sep 12 12:21:38 2011 Return-Path: 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 B7BDA1065673; Mon, 12 Sep 2011 12:21:38 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 63D938FC1E; Mon, 12 Sep 2011 12:21:38 +0000 (UTC) Received: by vxi39 with SMTP id 39so3807332vxi.13 for ; Mon, 12 Sep 2011 05:21:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; bh=ai9fpkBiwP8aAVrtQYiGaIt9sdbK8uIinWvZynl1gmQ=; b=tcv/ePS/j8TtJN0/VithHNzUVLgOX+5pXYG5DXZw2Gih4dHIaT9BQdIHdHQu075s91 Fx7PFvZ/5sfqPty/JcXHGgu2DTc+XP5tMtzROu1vSirGjR+KQr+RIYnGQIFSnWHuwoCU ecBdX6tMl8c1OIIp/0Nm7Ouh81cHDaO2Xr6FE= MIME-Version: 1.0 Received: by 10.52.93.143 with SMTP id cu15mr2975472vdb.60.1315830097712; Mon, 12 Sep 2011 05:21:37 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.52.161.138 with HTTP; Mon, 12 Sep 2011 05:21:37 -0700 (PDT) Date: Mon, 12 Sep 2011 20:21:37 +0800 X-Google-Sender-Auth: wi-kXPKEQyNw_20HrrlEgAB7D9w Message-ID: From: Adrian Chadd To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-mobile@freebsd.org Subject: Has ath(4) ever worked one release and not worked another, please poke me.. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Mon, 12 Sep 2011 12:21:38 -0000 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.) Thanks, Adrian