From owner-freebsd-wireless@FreeBSD.ORG Tue Jan 10 18:30:25 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A892E106566C; Tue, 10 Jan 2012 18:30:25 +0000 (UTC) (envelope-from adrian.chadd@gmail.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 55C368FC0A; Tue, 10 Jan 2012 18:30:24 +0000 (UTC) Received: by vbbfr13 with SMTP id fr13so5842069vbb.13 for ; Tue, 10 Jan 2012 10:30:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=ooy5nHkZAj2csH3xbozdr6piijWDhMHRPqjkNlj3Tnw=; b=EBNLIZEijUQg1k5W0IrikKIGPG5/PMzD4OuHXidieBhmzNrsnSU2K2baanA/L4aY6b u/HdKQq3Hx8kFhXiyNx3DkROgCYd4cClqsTiaP2jiENY1AoKDCi2DYe6DorzCBu/V+6t PiVNX2UqUT1azrbck9NJ7A1hg55FE1QXa7R+g= MIME-Version: 1.0 Received: by 10.52.173.80 with SMTP id bi16mr9896294vdc.115.1326220224522; Tue, 10 Jan 2012 10:30:24 -0800 (PST) Received: by 10.52.36.5 with HTTP; Tue, 10 Jan 2012 10:30:24 -0800 (PST) In-Reply-To: <201201101800.q0AI0Oxx088371@freefall.freebsd.org> References: <201201101800.q0AI0Oxx088371@freefall.freebsd.org> Date: Tue, 10 Jan 2012 10:30:24 -0800 Message-ID: From: Adrian Chadd To: Joel Dahl Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org Subject: Re: kern/163318: [ath] ath(4) stops working X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jan 2012 18:30:25 -0000 Hi, On 10 January 2012 10:00, Joel Dahl wrote: > =A0For the record: I put in another PCI ath(4) card and I'm seeing the sa= me > =A0thing with this card. After a while, wireless stops working. It seems = to > =A0go in to some power save mode, and then gets stuck. ifconfig wlan0 sca= n > =A0fixes it, as usual. > > =A0One thing I've noticed though is that it seems to take much longer for= this > =A0card to stop working. Usually around 9-10 hours. Could be a coincidenc= e of > =A0course. Hm. Right, I didn't think it was chipset specific. I think it's very likely another subtle race condition inside net80211 which we just haven't properly fixed. The scan stuff _should_ be running in the net80211 taskqueue (which one exists per interface, iirc.) So it shouldn't be racing with itself, but it may be racing with other bits. I'm trying to reproduce it here, but I won't have a dual-core machine w/ an AR9220 ready for another week or two. Adrian