> Hi Bob,
quoted text
> 
> I attached a dmesg output that covers initial association, the timed out
> transfer deassociation, and the following reassociation.
> 
> I cleared dmesg before these occurrences to get a clean trace.  Let me know
> if you need anything else.
> 
> Thanks,
> Phil

Great, thanks.

[ 3606.561930] ath0: switched to short barker preamble (BSSID=00:0f:24:c2:59:70)
[ 3629.398993] ath0: RX deauthentication from 00:0f:24:c2:59:70 (reason=2)
[ 3629.398996] ath0: deauthenticated

Hmm, reason = 2 means AP disconnected you because authorization was no longer 
valid.  That's not ringing bells for me.

5006s are known to still be a little iffy.  That's what I have so I'll try 
replicating your test case at home.  In the meantime can you verify you have
the patch below in the compat driver?  (Just make sure the "rxs.flag = 0;" 
part is in base.c.):

   http://permalink.gmane.org/gmane.linux.kernel.wireless.general/14684

-- 
Bob Copeland %% www.bobcopeland.com

_______________________________________________
ath5k-devel mailing list
ath5k-devel@lists.ath5k.org
https://lists.ath5k.org/mailman/listinfo/ath5k-devel