From owner-freebsd-wireless@FreeBSD.ORG Sat Aug 4 10:03:34 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8B249106564A for ; Sat, 4 Aug 2012 10:03:34 +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 5650B8FC0C for ; Sat, 4 Aug 2012 10:03:34 +0000 (UTC) Received: by pbbro2 with SMTP id ro2so2876399pbb.13 for ; Sat, 04 Aug 2012 03:03:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=F0flGn8gqe81Mr+SFu1XANikJHW7c6DEGJx/BUSH26M=; b=xD+PartAjo/ywNkOTKvsKncsE6miKTK8WaQQzTgtjVCgmEbBZwwCfT2UInMncZEPh6 hzF1YatgHLP6RRUnx9uU1XGeNQ4UG/hhImYR+kPk7iln7/G+7taLIjxggI5cmswDNiBc NR0/FFMDycFNJfIb1EsrStgwOjtkRdbzbHVjBuiXnVhoKYT2A+WyZMEVXQ7xivmToZV0 c7vyfTkDVqjpwYNP1UTL4wRye2S1hZLzwsixKFS2KHN+7LDSppRPiVkurbe9xz0ZCKB7 katRbtUuDy+uYwVd6PvM8kwcl2phNACCzapuWDEngVCz4iDIXkzfN/iv3GgNuHiRHJhW 9eTw== MIME-Version: 1.0 Received: by 10.68.228.2 with SMTP id se2mr3990081pbc.109.1344074614154; Sat, 04 Aug 2012 03:03:34 -0700 (PDT) Received: by 10.68.115.232 with HTTP; Sat, 4 Aug 2012 03:03:34 -0700 (PDT) In-Reply-To: References: Date: Sat, 4 Aug 2012 03:03:34 -0700 Message-ID: From: Adrian Chadd To: PseudoCylon Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org, Kim Culhan Subject: Re: ath lor 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: Sat, 04 Aug 2012 10:03:34 -0000 On 3 August 2012 22:11, PseudoCylon wrote: > I have added if_printf(), so we can track down the driver to blame. > https://gitorious.org/ieee80211/net80211/commit/4dbc79c5f832b4cdffe9966dbbeba9b1b8fd24da Cool. > I also added functions to revert changes when overflow (maybe too much). > https://gitorious.org/ieee80211/net80211/commit/dc1aa81ea1a9eeb7cf1a3a1c2b8a5a8cd85e687d > > >> Does it fix some/all of the LORs for you? >> > > So far, node/driver LOR in iv_key_delete() seems to be gone. This is a bit odd. I've not seen that, but you're testing with USB, right? I just saw a LOR between a node lock and a tcpinp lock. i was doing some iperf to an AR5416 802.11n AP running iperf locally. I've not seen this before as I've not run a NIC in AP mode with local traffic termination; I've only had APs do bridging. Thanks for chasing this down. Let me know if you see the node/power or node/scan LORs? Adrian