Date: Tue, 27 Dec 2011 17:03:32 +0100 From: =?ISO-8859-1?Q?Gustau_P=E9rez?= <gperez@entel.upc.edu> To: Adrian Chadd <adrian.chadd@gmail.com> Cc: freebsd-wireless@freebsd.org Subject: Re: Big delays between an AR5416 AP and its clients Message-ID: <4EF9EC54.1070005@entel.upc.edu> In-Reply-To: <CAJ-VmomUVGN0QreaC4CfLG-G0FbUJ7gOW2u56i069Lt9gBGyLQ@mail.gmail.com> References: <3d4d2d249836fafc6acd885693c02198@webmail.entel.upc.edu> <CAJ-Vmo=1k=oKP-vDUH=BLdyeVzGnQvNmJ6TwGcdQjwpgJWt52w@mail.gmail.com> <4ECFCDAB.1080407@entel.upc.edu> <CAJ-VmokQTpgxMo=gmj0LsYhD6t9mmoHXG_sbhZdFNW5_OSGbmg@mail.gmail.com> <a9d1d8f91deb80a89bed98c1ffdb23fd@webmail.entel.upc.edu> <CAJ-Vmo=P%2BWAArZ1Kidh947yHuftZTBwF=Vx5Kn36-LKtD4grPg@mail.gmail.com> <4ED3B4D1.3020701@entel.upc.edu> <CAJ-Vmo=1KimWWEkV4gqEyFiNQRZTkK8okPBSfnc494iJbtLzsw@mail.gmail.com> <4EDA4BBA.6010203@entel.upc.edu> <CAJ-Vmon7-PdC51nWjW-M-ojuShwG-iNrBpztNovsZpzgjm9BqA@mail.gmail.com> <4EDA609F.2080401@entel.upc.edu> <CAJ-VmomqbBpJ9whQ2EStP7i5fuaKvR=%2BA9gxQJm3hZnCi%2BJnOg@mail.gmail.com> <CAJ-Vmo=hEq9N=FhvdH8Ev7roG3TByJjri3q5rpLPDE__YZ=MZg@mail.gmail.com> <4EDB3A2B.4050503@entel.upc.edu> <CAJ-VmondwkhHor_BNHNm_k4aSaTQOZXi3a70KVCuN=HO8=5FZA@mail.gmail.com> <CAJ-VmomUVGN0QreaC4CfLG-G0FbUJ7gOW2u56i069Lt9gBGyLQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 04/12/2011 11:22, Adrian Chadd wrote:
> 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
Hi Adrian,
I managed to get a trace of the debug info. The file is HUGE and to
make things worse I can't tell exactly when it started to happen.
The trace beggins with no iphone associated while pinging the AR5416
box. Then, I started the iphone's supplicant, and at around 16:53:14 the
latency problem appeared. I hope it tells you anything useful, because I
don't know what I'm looking for.
The trace can be downloaded at:
http://www-entel.upc.edu/gus/ath_tx_logging.xz
Please let me know if you need any additional info.
Gus
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4EF9EC54.1070005>