[Bug 414560] Re: ath9k disassociates/reassociates a lot

Tyrael marco.crociani at gmail.com
Wed Feb 17 18:27:02 UTC 2010


With 2.6.32-02063208-generic #02063208 SMP Wed Feb 10 10:10:27 UTC 2010 x86_64 GNU/Linux (http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.32.8/)
I still have problems. The connection works only for some time (10 minutes? 15?) than also if ping to router works html navigation doesn't work.

dmesg
[   80.170140] cfg80211: Calling CRDA to update world regulatory domain
[   80.248137] cfg80211: World regulatory domain updated:
[   80.248145]     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[   80.248153]     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[   80.248160]     (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[   80.248167]     (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[   80.248174]     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[   80.248180]     (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[   80.284909] ACPI: PCI Interrupt Link [LN3A] enabled at IRQ 19
[   80.284923]   alloc irq_desc for 19 on node -1
[   80.284930]   alloc kstat_irqs on node -1
[   80.284947] ath9k 0000:04:00.0: PCI INT A -> Link[LN3A] -> GSI 19 (level, low) -> IRQ 19
[   80.284964] ath9k 0000:04:00.0: setting latency timer to 64
[   80.712120] ath: EEPROM regdomain: 0x60
[   80.712128] ath: EEPROM indicates we should expect a direct regpair map
[   80.712137] ath: Country alpha2 being used: 00
[   80.712141] ath: Regpair used: 0x60
[   80.768021] phy0: Selected rate control algorithm 'ath9k_rate_control'
[   80.770603] Registered led device: ath9k-phy0::radio
[   80.770816] Registered led device: ath9k-phy0::assoc
[   80.771612] Registered led device: ath9k-phy0::tx
[   80.771871] Registered led device: ath9k-phy0::rx
[   80.771933] phy0: Atheros AR9280 MAC/BB Rev:2 AR5133 RF Rev:d0: mem=0xffffc90003200000, irq=19
[   80.831098] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   88.219743] wlan0: deauthenticating from 00:22:6b:62:72:0a by local choice (reason=3)
[   88.228706] wlan0: direct probe to AP 00:22:6b:62:72:0a (try 1)
[   88.423788] wlan0: direct probe to AP 00:22:6b:62:72:0a (try 2)
[   88.623779] wlan0: direct probe to AP 00:22:6b:62:72:0a (try 3)
[   88.823782] wlan0: direct probe to AP 00:22:6b:62:72:0a timed out
[   89.788421] ath9k: Failed to stop TX DMA in 100 msec after killing last frame
[   89.788443] ath9k: Unable to stop TxDMA. Reset HAL!
[   99.408412] wlan0: direct probe to AP 00:22:6b:62:72:0a (try 1)
[   99.415011] wlan0: direct probe responded
[   99.415022] wlan0: authenticate with AP 00:22:6b:62:72:0a (try 1)
[   99.417212] wlan0: authenticated
[   99.417252] wlan0: associate with AP 00:22:6b:62:72:0a (try 1)
[   99.421767] wlan0: RX AssocResp from 00:22:6b:62:72:0a (capab=0x411 status=0 aid=1)
[   99.421775] wlan0: associated
[   99.433445] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

-- 
ath9k disassociates/reassociates a lot
https://bugs.launchpad.net/bugs/414560
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.




More information about the kernel-bugs mailing list