From owner-freebsd-wireless@FreeBSD.ORG Fri Dec 2 02:50:53 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 D8FA1106564A for ; Fri, 2 Dec 2011 02:50:53 +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 900578FC0A for ; Fri, 2 Dec 2011 02:50:53 +0000 (UTC) Received: by vcbfk1 with SMTP id fk1so3161927vcb.13 for ; Thu, 01 Dec 2011 18:50:52 -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=Id73D8AuG9gzeQUsClK/B7Y8vW6ECJDX7SkhsPX3B2w=; b=wCnWjunTpQwkvfBmLgLy6xQVfjR4IlVUtIHVyy1Yf59n+y/65GF9+RttTsZYwDGV73 4K88rfqPDpj35v2LaqNX0/zD8Py3NXhdrPjVWnm0B4NcuKvlcX3ciPmV5ip6zZwA48b9 N2bOuG950/KtZfGh1GT3PpEg33gIrBY4e2btg= MIME-Version: 1.0 Received: by 10.52.94.227 with SMTP id df3mr8710013vdb.51.1322794252696; Thu, 01 Dec 2011 18:50:52 -0800 (PST) Received: by 10.52.109.10 with HTTP; Thu, 1 Dec 2011 18:50:52 -0800 (PST) In-Reply-To: <4ED3B4D1.3020701@entel.upc.edu> References: <3d4d2d249836fafc6acd885693c02198@webmail.entel.upc.edu> <4ECFCDAB.1080407@entel.upc.edu> <4ED3B4D1.3020701@entel.upc.edu> Date: Fri, 2 Dec 2011 10:50:52 +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: Fri, 02 Dec 2011 02:50:53 -0000 Hi, I've taken a quick peek. There's nothing obviously wrong with that trace. Can you please redo this with: * 5 runs? * 100 pings a second - ie, ping -i 0.01 * capture the output of athstats -i ath0 before and after each run, as well as during a run * let it run for say, 60 seconds at a time. Also, once that's done, try it again with this: wlandebug -i wlan0 +power +input +output +state +assoc +mlme see if anything interesting pops up at the same time as your latency increases. (then wlandebug -i wlan0 0 to disable it all.) Thanks, Adrian