Re: ath0 bug in current?

[David Young <dyoung%pobox.com@localhost>]

On Thu, Mar 27, 2008 at 10:32:50PM +0100, Vincent wrote:
> Just a correction:
> 
> >ath_init: if_flags 0xffff8803
> >ath_stop_locked: invalid 0 if_flags 0xffff8803
> >ath_tx_start: m 0xc1276300 len 46
> >NODS 00:0f:b5:64:19:a8->ff:ff:ff:ff:ff:ff(ff:ff:ff:ff:ff:ff) probe_req 1M
> > 4000 0000 ffff ffff ffff 000f b564 19a8 ffff ffff ffff 0000 0000 0108 
> >8284 8b96
> > 0c12 1824 3204 3048 606c
> >ath_tx_start: 0: 00000000 2f4b83b0 2134002e 0100002a 00040000 0000001b
> >ath_tx_start: TXDP[1] = 1dbc320 (0xcb8f4320) depth 1
> >ath_start: discard data packet, state SCAN
> >ath_start: discard data packet, state SCAN
> >ath_start: discard data packet, state SCAN
> >and this is repeated ad libidum with only TXDP address changing.
> 
> Not quite true. More precisely, after 11 such cycles, I get an infinite 
> series of:
> 
> ath_start: discard data packet, state SCAN

I believe that wpa_supplicant believes it has driven the kernel state
machine to a different state than SCAN, but it has not, and it never
resynchronizes.

Dave

-- 
David Young             OJC Technologies
dyoung%ojctech.com@localhost      Urbana, IL * (217) 278-3933 ext 24