From mboxrd@z Thu Jan  1 00:00:00 1970
From: =?ISO-8859-1?Q?Torquil_Macdonald_S=F8rensen?= <torquil@gmail.com>
Date: Mon, 23 Aug 2010 17:20:03 +0200
Subject: [ath9k-devel] AR9285: Possible intermittent connection drop-outs
In-Reply-To: <AANLkTimEVJwVsGrsDkhCp6vA6auqYqP6913_RQse=zRR@mail.gmail.com>
References: <4C6AB479.2010603@gmail.com>	<AANLkTik=6gKT7+eXc8H9fGfWJ6egD5bm8CMzTJivbP7Z@mail.gmail.com>	<4C6FC95C.4090703@gmail.com>
	<AANLkTimEVJwVsGrsDkhCp6vA6auqYqP6913_RQse=zRR@mail.gmail.com>
Message-ID: <4C7291A3.3090803@gmail.com>
List-Id: <ath9k-devel.lists.ath9k.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: ath9k-devel@lists.ath9k.org

On 23/08/10 14:05, Mohammed Shafi wrote:
> Hi Torquil,
>
>                  Thanks for your ath9k debug messages .I tested the
> ath9k driver in 2.6.35.2
>
> with D-LINK DIR655  router  in ubunt 10.04 , but could not    reproduce
> the issue .I got  all
>
> of  your   similar debugging  messages(invalid cmd 2  several times
> ,cycle count
>
> ,ofdm,cck etc   under healthy connection( which you had  suspected for
> the connection loss ).
>
>                I think those were mainly  (modulation schemes ofdm ,cck ).
>
> while cmd is related to ANI information (enum ath9k_ani_cmd in ani.h).
>
>
> I had got these things under healthy connection ,
>
>   6464.669170] ath: Writing ofdmbase=12582412   cckbase=12582712
> [ 6464.728750] ath: invalid cmd 2
>
>   Aug 23 16:35:51 atheros-laptop kernel: [ 6345.264144] ath: ANI parameters:
> 1994 Aug 23 16:35:51 atheros-laptop kernel: [ 6345.264149] ath:
> noiseImmunityLevel=0, spurImmunityLevel=7, ofdmWeakSigDetectOff=0
> 1995 Aug 23 16:35:51 atheros-laptop kernel: [ 6345.264156] ath:
> cckWeakSigThreshold=0, firstepLevel=2, listenTime=78
> 1996 Aug 23 16:35:51 atheros-laptop kernel: [ 6345.264163] ath:
> cycleCount=1452171193, ofdmPhyErrCount=436, cckPhyErrCount=14
> 1997 Aug 23 16:35:51 atheros-laptop kernel: [ 6345.264169]
> 1998 Aug 23 16:35:51 atheros-laptop kernel: [ 6345.264176] ath: ANI
> parameters:
> 1999 Aug 23 16:35:51 atheros-laptop kernel: [ 6345.264181] ath:
> noiseImmunityLevel=0, spurImmunityLevel=7, ofdmWeakSigDetectOff=0
> 2000 Aug 23 16:35:51 atheros-laptop kernel: [ 6345.264188] ath:
> cckWeakSigThreshold=0, firstepLevel=2, listenTime=78
> 2001 Aug 23 16:35:51 atheros-laptop kernel: [ 6345.264195] ath:
> cycleCount=1452171193, ofdmPhyErrCount=436, cckPhyErrCount=14
>
>
>
>                         I hope that enabling ATH_DBG_FATAL will give us
> some some clear idea.
>
> If you obtain the ath9k debug messages with ATH_DBG_FATAL please do send
> as soon
>
> as you get it.
>
>
> with thanks and regards,
>
> shafi

Thanks for your effort! Your results are interesting. I will check the FATAL DBG 
option too see if it gives me some more interesting info.

I will also determine for sure if the error messages I mentioned earlier only 
appear when I have connection problems. I'll probably make a simple script that 
will parse the ath9k log and pick out only those messages so I can see exactly 
when they occur.

I will get back to you when I have more info.

Thanks again for your help,
Torquil S?rensen