Heya folks,

I'm having some problems with ath9k in the 2.6.27-rc6 kernel. First of
all, it incorrectly reports the connection bitrate as 1 megabit per
second:

wlan0     IEEE 802.11abgn  ESSID:"Introversion"
          Mode:Managed  Frequency:2.437 GHz  Access Point: 00:1E:52:79:4D:01
          Bit Rate=1 Mb/s   Tx-Power=23 dBm
          Retry min limit:7   RTS thr:off   Fragment thr=2352 B
          Encryption key: [snip]   Security mode:open
          Power Management:off
          Link Quality=67/100  Signal level:-52 dBm  Noise level=-95 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

Second, it will randomly drop the connection (could it possibly be
related to the message ' wlan0 (WE) : Wireless Event too big (320)'?).
One time, the connection dropped and I couldn't get it to reassociate,
and the dmesg showed the following:

[53963.201797] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[53964.809889] wlan0: authenticate with AP 00:1e:52:79:4d:01
[53964.811598] wlan0: authenticated
[53964.811742] wlan0: associate with AP 00:1e:52:79:4d:01
[53965.011340] wlan0: associate with AP 00:1e:52:79:4d:01
[53965.211343] wlan0: associate with AP 00:1e:52:79:4d:01
[53965.411345] wlan0: association with AP 00:1e:52:79:4d:01 timed out
[53976.532464] wlan0: authenticate with AP 00:1e:52:79:4d:01
[53976.542516] wlan0: authenticate with AP 00:1e:52:79:4d:01
[53976.751331] wlan0: authenticate with AP 00:1e:52:79:4d:01
[53976.752757] wlan0: authenticated
[53976.752762] wlan0: associate with AP 00:1e:52:79:4d:01
[53976.760374] wlan0: RX AssocResp from 00:1e:52:79:4d:01 (capab=0x431
status=0 aid=1)
[53976.760380] wlan0: associated
[53976.760721] wlan0 (WE) : Wireless Event too big (320)
[53976.772243] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

So I figured I'd try unloading and reloading the ath9k module. This
was the result:

[53997.493777] ath9k: driver unloaded
[54001.098532] ath9k: ...
[ message continues ]

I just had another incident where it disassociated and refused to
reassociate. I got about 100 of these in my dmesg (fixed by unloading
and reloading ath9k):

[...]
[ 1279.031033] ath_set_channel: unable to reset channel 149 (5745Mhz)
flags 0x30142 hal status 4294967277
[ 1279.031203] ath9k_config: Unable to set channel
[ 1279.323427] ath_set_channel: unable to reset channel 153 (5765Mhz)
flags 0x50142 hal status 4294967277
[ 1279.323577] ath9k_config: Unable to set channel
[ 1279.624562] ath_set_channel: unable to reset channel 157 (5785Mhz)
flags 0x30142 hal status 4294967277
[ 1279.624687] ath9k_config: Unable to set channel
[ 1279.916441] ath_set_channel: unable to reset channel 161 (5805Mhz)
flags 0x50142 hal status 4294967277
[ 1279.916586] ath9k_config: Unable to set channel
[ 1280.207274] ath_set_channel: unable to reset channel 165 (5825Mhz)
flags 0x10142 hal status 4294967277
[ 1280.207387] ath9k_config: Unable to set channel
[...]

- Steven
--

[ message continues ]

Is this a regression from 2.6.26?

Rafael
--

[ message continues ]

ath9k has been recently introduced (i.e. it's new to 2.6.27). So I'm not 
certain how to answer. Correct me if I'm wrong but a regression is a new  
bug for a specific component that did not surface in the previous release, 
correct? But if the component didn't exist in the previous version, is it 
still a regression?

- Steven
--

[ message continues ]

No, it isn't considered as a regression.

Thanks,
Rafael
--

[ message continues ]