From owner-freebsd-wireless@FreeBSD.ORG Fri Feb 17 07:26:46 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 1A0231065670 for ; Fri, 17 Feb 2012 07:26:46 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id A57498FC1B for ; Fri, 17 Feb 2012 07:26:45 +0000 (UTC) Received: by werm13 with SMTP id m13so2624375wer.13 for ; Thu, 16 Feb 2012 23:26:44 -0800 (PST) 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:content-type; bh=PPwA0ir0WzofFFm91RD6ia7sfPE3V/MldA4KqXQ4LBs=; b=CSN2noqzo+U2FpxAOOmImdTZ8ywQIyRFl/yzoe0IMQwO9p9dORBLDiNQlhJ3Icb97W YkGTiWgELw8wK2+s52RsnEU3LorOtxQujjaudQ9Tvb5x0bqcfrv1LvDmeCWdJS8RqZH9 c9cLx1dJVfQycZANEUWPx1JeAlVokTyn+yYyA= MIME-Version: 1.0 Received: by 10.180.96.8 with SMTP id do8mr1612618wib.21.1329463604538; Thu, 16 Feb 2012 23:26:44 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.154.199 with HTTP; Thu, 16 Feb 2012 23:26:44 -0800 (PST) Date: Thu, 16 Feb 2012 23:26:44 -0800 X-Google-Sender-Auth: R_J9Z-PYtsfsGJ3TdM0uH8bUxIw Message-ID: From: Adrian Chadd To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: ath fixes in -HEAD: squish (most) of the ath_rx_tasklet warnings 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: Fri, 17 Feb 2012 07:26:46 -0000 Hi, I've just rejiggled the reset/channel change path to (mostly) properly drain and pause the ath taskqueue when doing a reset/channel change. This has quietened most of the overlapping RX completions during reset - they seemed to have been occuring because an RX interrupt was coming in or had just come in before a reset. Please test the latest -HEAD and let me know if there are any issues. Thanks! Adrian