Re: ath0 bug in current?

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

On Thu, Mar 27, 2008 at 10:10:00PM +0100, Vincent wrote:
> Hi there,
> 
> since I compiled the latest -current this morning, my ath0 cardbus 
> Wificard stopped working. It detects no AP anymore. Here is a dump after 
> a sysctl -w hw.ath0.debug=1
> 
> 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.
> 
> At launch, the card seems to associate itself with the AP, but the WPA 
> authentication exchange times out and then no further try happens since 
> the card is unable to relocate the AP.

When you say that the authentication exchange times out, do you mean
that you get an 802.11 Disassociate message with a 'Reason Code'
indicating such?  I ask because that is what I often get.  I am using
WPA on an rtw(4), however.  The interval between my client receiving and
responding to some messages was about one quarter of a second!  The AP,
a Linksys WRT54GC, does not wait that long.

Dave

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