From owner-freebsd-wireless@FreeBSD.ORG Sat Jul 21 17:57:09 2012 Return-Path: Delivered-To: wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 23D4A106566B; Sat, 21 Jul 2012 17:57:09 +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 DBFC68FC16; Sat, 21 Jul 2012 17:57:08 +0000 (UTC) Received: by pbbro2 with SMTP id ro2so8829695pbb.13 for ; Sat, 21 Jul 2012 10:57:08 -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=YCgDmhgwbCfMPu0EqxVZpiSZ74l6ZEu6zkEmFm9v7IA=; b=nUlDaHekAjjZHJggEVb4PhreMbWeNALyWL2IYYVHeJSQq04T7+VpKDmdbWpr9Qd6nL pWg0629wOhID97l6c7bMmDWcdKYKUY3xJhFcKoJCWBx0dXzsNwcvevmRo6dk4YbXHcQv GplMWbADROcae1Xtsffduzy1B3vwZ9I+FhKjrnt6F0GzTi7bdsKTYVuaYtf7mj7kPA9j 2r95GF+zejlPST9IJZVF+xxZkUUj+iTiqZCHQdNPgrmHLu+eWFAADIqbmY7z5AmsYCM+ Pdb7c+SEa+fVV/+Z9n/1hd0Jmbut5ot8djPo7aUxP9RGZx7Dg6vtccXy0VTmvsc3gWFY s7Qw== MIME-Version: 1.0 Received: by 10.66.84.7 with SMTP id u7mr7486912pay.83.1342893428620; Sat, 21 Jul 2012 10:57:08 -0700 (PDT) Received: by 10.68.191.138 with HTTP; Sat, 21 Jul 2012 10:57:08 -0700 (PDT) In-Reply-To: References: <298155894.20120709002844@serebryakov.spb.ru> <1491344515.20120709013411@serebryakov.spb.ru> <1252921508.20120709132351@serebryakov.spb.ru> <802688919.20120709140808@serebryakov.spb.ru> <1966637204.20120713194935@serebryakov.spb.ru> <5862675.20120713203432@serebryakov.spb.ru> <7750188.20120716011053@serebryakov.spb.ru> Date: Sat, 21 Jul 2012 10:57:08 -0700 Message-ID: From: Adrian Chadd To: lev@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: wireless@freebsd.org Subject: Re: ath0: device timeout with 802.11n client 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, 21 Jul 2012 17:57:09 -0000 Hey Lev, Have you had any luck reproducing this with the debugging enabled? I'd really like to get to the bottom of this issue. :) I thought I had fixed it late in June, but obviously there are some other race conditions I'm not currently handling. Thanks! Adrian