Re: ath: Unable to reset channel (2412 MHz), reset status -5

From: Justin P. Mattock
Date: Fri Jul 22 2011 - 01:07:54 EST


On 07/19/2011 08:49 AM, Mohammed Shafi wrote:
On Tue, Jul 19, 2011 at 8:55 PM, Justin P. Mattock
<justinmattock@xxxxxxxxx> wrote:
On 07/18/2011 11:46 PM, Mohammed Shafi wrote:

On Tue, Jul 19, 2011 at 12:05 PM, Justin P. Mattock
<justinmattock@xxxxxxxxx> wrote:

On 07/18/2011 11:25 PM, Mohammed Shafi wrote:

On Tue, Jul 19, 2011 at 11:43 AM, Justin P. Mattock
<justinmattock@xxxxxxxxx> wrote:

seems with the latest Mainline I am getting the ath9k carpping out
after
a
while of streaming(dmesg below)..:
http://fpaste.org/D7wM/

will try a bisect if I have the time..

I will try to recreate here with 3.0.0-rc7-wl, we can get more
information by ath9k debug=0xffffffff.
thanks.


cool!
seems to fire off randomly over here.

I have got AR5416, will try with that.


I can try the bisect, but might take a while, since external
activities(job). Seems this is just starting i.g. with
3.0.0-rc1 I never saw this, but with 3.0.0-rc7-00125-gf560f66
its making noise.

I am unable to get this problem in my AR5416 :( will also try
tomorrow. I am using the card for browsing etc.
recently there were patches for hardware code changes.
just a guess, please check does this patch helps(or is it already
there). i think this will be called via
ath_set_channel->ath9k_hw_reset->ath9k_hw_init_bb and may be
https://patchwork.kernel.org/patch/957902/


alright, I applied the patch above, and have ran this a few days in various hotspots etc.. unfortunantly this patch does not fix the issue.
dmesg is below:
http://fpaste.org/ozCA/

from what I remember, I had all my clients doing their thing, then all of a sudden everything slowly started to crap out.

as for bisecting, I think this might take a while due to the inconsistancy of this(seems to show up every 4/5 boots etc..)but if I get some free time, I will have a try.

Justin P. Mattock

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/