From owner-freebsd-wireless@FreeBSD.ORG Sun Dec 4 10:22:05 2011 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 D705E106566B for ; Sun, 4 Dec 2011 10:22:05 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 88B438FC0C for ; Sun, 4 Dec 2011 10:22:05 +0000 (UTC) Received: by vcbfk1 with SMTP id fk1so5256864vcb.13 for ; Sun, 04 Dec 2011 02:22:05 -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; bh=M0DgjXK+XsR7Ei/8f/S80FF0w4LQ0QmGHOqWVmYMSxw=; b=Lsn2UEmf3C3GjTYrx2G7fOWQfXPF6/+Xa39KRVU+hx2t6WOhfkTGydXZZ5XFbPqY5q zZWCp2n1sKZCnHX5MFGK2HxsYt+Cjv3TMkAVVHd18SU/zrdDAaCNI1gihn1wwS59LOze C75fvy/AD3g6N5R8FcHy2itEYnIq8n8BqYeIo= MIME-Version: 1.0 Received: by 10.52.20.35 with SMTP id k3mr2861303vde.34.1322994125051; Sun, 04 Dec 2011 02:22:05 -0800 (PST) Received: by 10.52.109.10 with HTTP; Sun, 4 Dec 2011 02:22:05 -0800 (PST) In-Reply-To: References: <3d4d2d249836fafc6acd885693c02198@webmail.entel.upc.edu> <4ECFCDAB.1080407@entel.upc.edu> <4ED3B4D1.3020701@entel.upc.edu> <4EDA4BBA.6010203@entel.upc.edu> <4EDA609F.2080401@entel.upc.edu> <4EDB3A2B.4050503@entel.upc.edu> Date: Sun, 4 Dec 2011 18:22:05 +0800 Message-ID: From: Adrian Chadd To: =?ISO-8859-1?Q?Gustau_P=E9rez?= Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: Big delays between an AR5416 AP and its clients 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: Sun, 04 Dec 2011 10:22:05 -0000 Ok, to enable logging: Firstly, let's just debug the non-beacon TX : sysctl dev.ath.0.debug=0x3c000000 wlandebug -i wlan0 +rate Then send some pings. You'll get a _lot_ of debugging. Please capture some debugging. :) Point out which log entries correspond to increased latency. (This is assuming it's a TX issue; it's possibly an RX issue too..) Thanks, Adrian