From owner-freebsd-wireless@FreeBSD.ORG Tue Aug 7 00:58:05 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 D53D7106564A for ; Tue, 7 Aug 2012 00:58:05 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id AC33E8FC08 for ; Tue, 7 Aug 2012 00:58:05 +0000 (UTC) Received: by pbbrp2 with SMTP id rp2so2196063pbb.13 for ; Mon, 06 Aug 2012 17:58:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=Hoc3+w8WCDtcjs17Osst0ITjQZmB0MEmqTPwOCXlz7Y=; b=V+kixo75Isy7DgE3txQ5Ds9Tc6rUNfBq6+0Ff8+Mzt8Mm4EoXxLHjluZq3Q9Zj5Mo9 pdlxOwe/U3L8UlD/0jHqznYKezOw6pWVaSoH5++iSc/4W2axRGs4X8eooFl7543HLZ85 WbBjtQ0HvJKnzLPNkPpdBquaNqp6rkZjLhTOGE4RZAPN+gjF/4HWbZHrdYl1EDBsdrw6 t26tiSUp6a+2o2kwpXc5XaV43qh7mjim5fpRZhLMH74DnqPfjiy6LuxuEp0NYOywXj2G SwOsyJVfzv+IocqZtpE48yc+unPED1w51sMTNhYvlPekyX/8jT0DXFoDzjmxzA6XL4Nf ndYQ== MIME-Version: 1.0 Received: by 10.68.223.164 with SMTP id qv4mr23202635pbc.20.1344301085306; Mon, 06 Aug 2012 17:58:05 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.68.115.232 with HTTP; Mon, 6 Aug 2012 17:58:05 -0700 (PDT) Date: Mon, 6 Aug 2012 17:58:05 -0700 X-Google-Sender-Auth: kwpF40jkXpYDeqv70orlLCUada8 Message-ID: From: Adrian Chadd To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: (ANother) stall fixed, please update to HEAD 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, 07 Aug 2012 00:58:05 -0000 Hi all, I've fixed another stupid Adrian-induced issue in the TX path (to do with restarting DMA after a stuck beacon). I'd appreciate it if users would sync up to -HEAD and try it out. It doesn't fix BAR TX and buffer exhaustion related issues but it should fix the stall issues seen in 2.4GHz when the NIC gets unhappy (and thus "stuck beacon"). Thanks, Adrian