Bug 759931 - ath9k: wireless keeps disconnecting and reconnecting
Summary: ath9k: wireless keeps disconnecting and reconnecting
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 17
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: John W. Linville
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-04 22:26 UTC by Sam Irlapati
Modified: 2012-09-28 17:23 UTC (History)
16 users (show)

Fixed In Version: kernel-3.4.4-3.fc17.x86_64
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-13 14:54:16 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
log files of info asked for. (22.95 KB, text/plain)
2011-12-08 18:48 UTC, Sam Irlapati
no flags Details
wpa-spplicant log file (104.49 KB, text/x-log)
2011-12-08 18:51 UTC, Sam Irlapati
no flags Details
output of "modinfo ath9k" and "iwevent -t" (24.70 KB, text/plain)
2011-12-14 02:49 UTC, Sam Irlapati
no flags Details

Description Sam Irlapati 2011-12-04 22:26:25 UTC
Description of problem:


Version-Release number of selected component (if applicable):
NetworkManager-0.9.1.90-5.git20110927.fc16.x86_64


How reproducible:
Boot computer up.


Steps to Reproduce:
1. boot computer up
2.
3.
  
Actual results:
I keep seeing the following the /var/log/messages
Dec  4 16:17:12 Salem kernel: [ 1980.248125] cfg80211: Calling CRDA to update world regulatory domain
Dec  4 16:17:12 Salem NetworkManager[1044]: <info> (wlan0): supplicant interface state: completed -> disconnected
Dec  4 16:17:12 Salem NetworkManager[1044]: NetworkManager[1044]: <info> (wlan0): supplicant interface state: completed -> disconnected
Dec  4 16:17:12 Salem kernel: [ 1980.271081] cfg80211: World regulatory domain updated:
Dec  4 16:17:12 Salem kernel: [ 1980.271094] cfg80211:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Dec  4 16:17:12 Salem kernel: [ 1980.271103] cfg80211:     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Dec  4 16:17:12 Salem kernel: [ 1980.271111] cfg80211:     (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Dec  4 16:17:12 Salem kernel: [ 1980.271118] cfg80211:     (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Dec  4 16:17:12 Salem kernel: [ 1980.271126] cfg80211:     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Dec  4 16:17:12 Salem kernel: [ 1980.271133] cfg80211:     (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Dec  4 16:17:12 Salem kernel: [ 1980.271171] cfg80211: Calling CRDA for country: US
Dec  4 16:17:12 Salem NetworkManager[1044]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Dec  4 16:17:12 Salem NetworkManager[1044]: NetworkManager[1044]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Dec  4 16:17:13 Salem NetworkManager[1044]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Dec  4 16:17:13 Salem NetworkManager[1044]: NetworkManager[1044]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Dec  4 16:17:13 Salem NetworkManager[1044]: <info> (wlan0): supplicant interface state: authenticating -> associating
Dec  4 16:17:13 Salem NetworkManager[1044]: NetworkManager[1044]: <info> (wlan0): supplicant interface state: authenticating -> associating
Dec  4 16:17:13 Salem NetworkManager[1044]: <info> (wlan0): supplicant interface state: associating -> completed
Dec  4 16:17:13 Salem NetworkManager[1044]: NetworkManager[1044]: <info> (wlan0): supplicant interface state: associating -> completed
Dec  4 16:21:24 Salem kernel: [ 2232.280257] cfg80211: Calling CRDA to update world regulatory domain
Dec  4 16:21:24 Salem NetworkManager[1044]: <info> (wlan0): supplicant interface state: completed -> disconnected
Dec  4 16:21:24 Salem NetworkManager[1044]: NetworkManager[1044]: <info> (wlan0): supplicant interface state: completed -> disconnected
Dec  4 16:21:24 Salem kernel: [ 2232.295245] cfg80211: World regulatory domain updated:
Dec  4 16:21:24 Salem kernel: [ 2232.295257] cfg80211:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Dec  4 16:21:24 Salem kernel: [ 2232.295266] cfg80211:     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Dec  4 16:21:24 Salem kernel: [ 2232.295274] cfg80211:     (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Dec  4 16:21:24 Salem kernel: [ 2232.295281] cfg80211:     (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Dec  4 16:21:24 Salem kernel: [ 2232.295288] cfg80211:     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Dec  4 16:21:24 Salem kernel: [ 2232.295296] cfg80211:     (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Dec  4 16:21:24 Salem kernel: [ 2232.295343] cfg80211: Calling CRDA for country: US
Dec  4 16:21:24 Salem NetworkManager[1044]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Dec  4 16:21:24 Salem NetworkManager[1044]: NetworkManager[1044]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Dec  4 16:21:25 Salem NetworkManager[1044]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Dec  4 16:21:25 Salem NetworkManager[1044]: NetworkManager[1044]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Dec  4 16:21:25 Salem NetworkManager[1044]: <info> (wlan0): supplicant interface state: authenticating -> associating
Dec  4 16:21:25 Salem NetworkManager[1044]: NetworkManager[1044]: <info> (wlan0): supplicant interface state: authenticating -> associating
Dec  4 16:21:25 Salem NetworkManager[1044]: <info> (wlan0): supplicant interface state: associating -> completed
Dec  4 16:21:25 Salem NetworkManager[1044]: NetworkManager[1044]: <info> (wlan0): supplicant interface state: associating -> completed
Dec  4 16:22:39 Salem kernel: [ 2307.288143] cfg80211: Calling CRDA to update world regulatory domain
Dec  4 16:22:39 Salem NetworkManager[1044]: <info> (wlan0): supplicant interface state: completed -> disconnected
Dec  4 16:22:39 Salem NetworkManager[1044]: NetworkManager[1044]: <info> (wlan0): supplicant interface state: completed -> disconnected
Dec  4 16:22:39 Salem kernel: [ 2307.301521] cfg80211: World regulatory domain updated:
Dec  4 16:22:39 Salem kernel: [ 2307.301533] cfg80211:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Dec  4 16:22:39 Salem kernel: [ 2307.301542] cfg80211:     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Dec  4 16:22:39 Salem kernel: [ 2307.301550] cfg80211:     (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Dec  4 16:22:39 Salem kernel: [ 2307.301558] cfg80211:     (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Dec  4 16:22:39 Salem kernel: [ 2307.301565] cfg80211:     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Dec  4 16:22:39 Salem kernel: [ 2307.301572] cfg80211:     (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Dec  4 16:22:39 Salem kernel: [ 2307.301616] cfg80211: Calling CRDA for country: US
Dec  4 16:22:39 Salem NetworkManager[1044]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Dec  4 16:22:39 Salem NetworkManager[1044]: NetworkManager[1044]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Dec  4 16:22:40 Salem NetworkManager[1044]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Dec  4 16:22:40 Salem NetworkManager[1044]: NetworkManager[1044]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Dec  4 16:22:40 Salem NetworkManager[1044]: <info> (wlan0): supplicant interface state: authenticating -> associating
Dec  4 16:22:40 Salem NetworkManager[1044]: NetworkManager[1044]: <info> (wlan0): supplicant interface state: authenticating -> associating
Dec  4 16:22:40 Salem NetworkManager[1044]: <info> (wlan0): supplicant interface state: associating -> completed
Dec  4 16:22:40 Salem NetworkManager[1044]: NetworkManager[1044]: <info> (wlan0): supplicant interface state: associating -> completed


Expected results:
NetworkManager should not always be reconnecting.


Additional info:
I am setting this to a high priority because it slows down wireless bandwidth. When using SSH, the command lines and it's output shows up in spurts. Multimedia streaming is slow too, it often is buffering.

Comment 1 Jirka Klimes 2011-12-08 10:23:16 UTC
What WiFi card and driver do you use? What is your signal strength?
Do you see any errors regarding wlan0 in 'dmesg' output?

Please post the following details:
$ lspci -nnvv | grep Network
$ dmesg | grep wlan0
$ nmcli dev wifi
$ /var/log/wpa_supplicant.log
  (it would be better to get debugging logs ('-dddt' option),
   see http://live.gnome.org/NetworkManager/Debugging#wpa_supplicant07)

Comment 2 Sam Irlapati 2011-12-08 18:48:55 UTC
Created attachment 542692 [details]
log files of info asked for.

This attachment has the output of the first 3 commands you asked for.

Comment 3 Sam Irlapati 2011-12-08 18:51:53 UTC
Created attachment 542693 [details]
wpa-spplicant log file

wpa supplicant log file. Just so you know i do not use any encryption on my network.

Comment 4 Jirka Klimes 2011-12-12 12:16:10 UTC
CTRL-EVENT-DISCONNECTED bssid=00:19:5b:56:72:2f reason=4

The "reason=4" means "Deauthenticated due to inactivity" (http://lxr.linux.no/linux+v3.1.5/include/linux/ieee80211.h#L1117). That could be caused by the ath9k driver that may not handle power saving correctly and thus the AP thinks your client is gone and deauthenticates it.

Try disabling power management with:
# iwconfig wlan0 power off
(https://bugzilla.redhat.com/show_bug.cgi?id=701768#c1)

For the poor performance issue try 'nohwcrypt=1' option - http://fedoraproject.org/wiki/Common_F15_bugs#Poor_transfer_speeds_with_Atheros-based_wireless_chipsets

Would you provide the following info to debug further:
$ modinfo ath9k
# iw event -t  (leave it running, reproducing the issue, it prints wireless events)

Comment 5 Sam Irlapati 2011-12-14 02:49:46 UTC
Created attachment 546508 [details]
output of "modinfo ath9k" and "iwevent -t"

This the log file for the output before "iwconfig wlan0 power off" and "nohwcrypt=1".

When should turn off the powersaving in the ath9k? Should it be done at start time? Should i make sure the card is down when i do it? I have tried doing it when the it was connected to the network and the log files still had the messages of re-scaning.

Comment 6 Britton Dodd 2012-04-19 01:54:04 UTC
I believe I am having a similar problem. This occurs *every* time I wake from standby by either closing the lid or suspending via the menu. Here is the dmesg dump


[   53.595314] [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream !
[   55.789234] hda-intel: IRQ timing workaround is activated for card #1. Suggest a bigger bdl_pos_adj.
[   73.979119] fuse init (API version 7.18)
[   78.801544] lp: driver loaded but no devices found
[   78.924741] ppdev: user-space parallel port driver
[  946.724320] wlan0: moving STA 00:25:9c:48:c3:e0 to state 2
[  946.724329] wlan0: moving STA 00:25:9c:48:c3:e0 to state 1
[  946.724336] wlan0: moving STA 00:25:9c:48:c3:e0 to state 0
[  946.738541] cfg80211: Calling CRDA to update world regulatory domain
[  946.748967] cfg80211: World regulatory domain updated:
[  946.748974] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[  946.748982] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[  946.748988] cfg80211:   (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[  946.748995] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[  946.749001] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[  946.749032] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[  946.749065] cfg80211: Calling CRDA for country: US
[  946.757942] cfg80211: Regulatory domain changed to country: US
[  946.757949] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[  946.757957] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
[  946.757964] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
[  946.757970] cfg80211:   (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[  946.757976] cfg80211:   (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[  946.757982] cfg80211:   (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[  946.757989] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
[  966.083591] wlan0: authenticate with 00:25:9c:48:c3:e0 (try 1)
[  966.283262] wlan0: authenticate with 00:25:9c:48:c3:e0 (try 2)
[  966.483254] wlan0: authenticate with 00:25:9c:48:c3:e0 (try 3)
[  966.683257] wlan0: authentication with 00:25:9c:48:c3:e0 timed out
[  973.193298] wlan0: authenticate with 00:25:9c:48:c3:e0 (try 1)
[  973.393262] wlan0: authenticate with 00:25:9c:48:c3:e0 (try 2)
[  973.593278] wlan0: authenticate with 00:25:9c:48:c3:e0 (try 3)
[  973.793260] wlan0: authentication with 00:25:9c:48:c3:e0 timed out
[  980.300320] wlan0: authenticate with 00:25:9c:48:c3:e0 (try 1)
[  980.500307] wlan0: authenticate with 00:25:9c:48:c3:e0 (try 2)
[  980.700277] wlan0: authenticate with 00:25:9c:48:c3:e0 (try 3)
[  980.900277] wlan0: authentication with 00:25:9c:48:c3:e0 timed out
[  996.088257] wlan0: authenticate with 02:25:9c:48:c3:e1 (try 1)
[  996.288254] wlan0: authenticate with 02:25:9c:48:c3:e1 (try 2)
[  996.488170] wlan0: authenticate with 02:25:9c:48:c3:e1 (try 3)
[  996.688222] wlan0: authentication with 02:25:9c:48:c3:e1 timed out
[ 1003.181471] wlan0: authenticate with 02:25:9c:48:c3:e1 (try 1)
[ 1003.381231] wlan0: authenticate with 02:25:9c:48:c3:e1 (try 2)
[ 1003.581302] wlan0: authenticate with 02:25:9c:48:c3:e1 (try 3)
[ 1003.781294] wlan0: authentication with 02:25:9c:48:c3:e1 timed out
[ 1010.283181] wlan0: authenticate with 02:25:9c:48:c3:e1 (try 1)
[ 1010.483198] wlan0: authenticate with 02:25:9c:48:c3:e1 (try 2)
[ 1010.683279] wlan0: authenticate with 02:25:9c:48:c3:e1 (try 3)
[ 1010.883128] wlan0: authentication with 02:25:9c:48:c3:e1 timed out
[ 1017.396723] wlan0: authenticate with 00:25:9c:48:c3:e0 (try 1)
[ 1017.596259] wlan0: authenticate with 00:25:9c:48:c3:e0 (try 2)
[ 1017.796287] wlan0: authenticate with 00:25:9c:48:c3:e0 (try 3)
[ 1017.996193] wlan0: authentication with 00:25:9c:48:c3:e0 timed out
[ 1018.408349] libfcoe_device_notification: NETDEV_UNREGISTER lo
[ 1024.494381] wlan0: authenticate with 00:25:9c:48:c3:e0 (try 1)
[ 1024.694240] wlan0: authenticate with 00:25:9c:48:c3:e0 (try 2)
[ 1024.894099] wlan0: authenticate with 00:25:9c:48:c3:e0 (try 3)
[ 1025.094294] wlan0: authentication with 00:25:9c:48:c3:e0 timed out
[ 1031.601853] wlan0: authenticate with 00:25:9c:48:c3:e0 (try 1)
[ 1031.801260] wlan0: authenticate with 00:25:9c:48:c3:e0 (try 2)
[ 1032.001055] wlan0: authenticate with 00:25:9c:48:c3:e0 (try 3)
[ 1032.201034] wlan0: authentication with 00:25:9c:48:c3:e0 timed out
[ 1035.098387] libfcoe_device_notification: NETDEV_UNREGISTER lo
[ 1040.184153] wlan0: authenticate with 00:25:9c:48:c3:e0 (try 1)
[ 1040.384180] wlan0: authenticate with 00:25:9c:48:c3:e0 (try 2)
[ 1040.584175] wlan0: authenticate with 00:25:9c:48:c3:e0 (try 3)
[ 1040.784297] wlan0: authentication with 00:25:9c:48:c3:e0 timed out
[ 1047.302445] wlan0: authenticate with 00:25:9c:48:c3:e0 (try 1)
[ 1047.502236] wlan0: authenticate with 00:25:9c:48:c3:e0 (try 2)
[ 1047.702208] wlan0: authenticate with 00:25:9c:48:c3:e0 (try 3)
[ 1047.902230] wlan0: authentication with 00:25:9c:48:c3:e0 timed out
[ 1053.027646] libfcoe_device_notification: NETDEV_UNREGISTER wlan0
[ 1053.039750] ath9k: Driver unloaded
[ 1113.111941] ath9k: version magic '3.3.0-8.fc16.x86_64 SMP mod_unload ' should be '3.3.1-5.fc16.x86_64 SMP mod_unload '
[ 1131.309732] ath: EEPROM regdomain: 0x60
[ 1131.309739] ath: EEPROM indicates we should expect a direct regpair map
[ 1131.309747] ath: Country alpha2 being used: 00
[ 1131.309752] ath: Regpair used: 0x60
[ 1131.313060] ieee80211 phy1: Selected rate control algorithm 'ath9k_rate_control'
[ 1131.313811] Registered led device: ath9k-phy1
[ 1131.313824] ieee80211 phy1: Atheros AR9285 Rev:2 mem=0xffffc90002b20000, irq=17
[ 1131.359094] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1134.250122] wlan0: authenticate with 00:25:9c:48:c3:e0 (try 1)
[ 1134.252229] wlan0: authenticated
[ 1134.274870] wlan0: associate with 00:25:9c:48:c3:e0 (try 1)
[ 1134.282557] wlan0: RX AssocResp from 00:25:9c:48:c3:e0 (capab=0x411 status=0 aid=4)
[ 1134.282561] wlan0: associated
[ 1134.282565] wlan0: moving STA 00:25:9c:48:c3:e0 to state 1
[ 1134.282567] wlan0: moving STA 00:25:9c:48:c3:e0 to state 2
[ 1134.291264] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 1134.323940] wlan0: moving STA 00:25:9c:48:c3:e0 to state 3
[ 1144.850013] wlan0: no IPv6 routers present


During each three sets of authentication timeouts, I get prompted to re-enter the key. What I don't understand is that the station moving states.... I didn't physically move out of range, and the connection is stable for the Win7 machine two feet from me (my wife on her computer). I was able to rmmod and modprobe ath9k to get it working again. This particular event happened pretty out-of-the-blue, however usually I get this error when waking from standby. This is why the timestamps arent more than 4 integer digits.

Comment 7 Britton Dodd 2012-04-19 01:58:55 UTC
This isnt the same issue...my apologies.

Comment 8 Dan Williams 2012-04-19 22:37:25 UTC
(In reply to comment #7)
> This isnt the same issue...my apologies.

No problem; for reference Britton has filed bug 814011 for this issue.

Comment 9 Dan Williams 2012-04-19 22:40:23 UTC
Looks a lot like the driver is misbehaving WRT powersave, like Jirka says.  Moving to kernel...

Comment 10 Sam Irlapati 2012-07-13 16:12:44 UTC
this still exists in fedora 17. Has any progress been made?

Comment 11 Justin M. Forbes 2012-07-16 16:41:45 UTC
With which kernel in Fedora 17. There were a number of updates in 3.4.4 that fixed ath9k for many users.

Comment 12 Sam Irlapati 2012-07-16 16:55:09 UTC
3.4.4-3.fc17.x86_64

Comment 13 Sam Irlapati 2012-07-18 14:03:13 UTC
I take back what i said. this is not a problem any more. I am sorry for the trouble.

Comment 14 John W. Linville 2012-07-18 14:26:50 UTC
Closing on the basis of comment 12...

Comment 15 Mohammed Shafi 2012-07-18 14:32:25 UTC
(In reply to comment #13)
> I take back what i said. this is not a problem any more. I am sorry for the
> trouble.

Could also be fixed by one of the patches in ath9k :)

Comment 16 Sam Irlapati 2012-07-20 02:37:40 UTC
I hate to say this bit it is happening again. It looks like an intermittent problem. I can look for patterns to see when it happens and when it does not. Is there anything i can do to get you more info?

Comment 17 Stanislaw Gruszka 2012-07-20 08:05:22 UTC
Hmm, perhaps you can try to update AP firmware, maybe problems lies there.

Comment 18 Adhidarma Hadiwinoto 2012-08-01 03:39:12 UTC
I confirm this problem. Still exists on current Fedora 17, kernel 3.4.6-2.fc17.x86_64.

$ lspci -v
02:00.0 Network controller: Atheros Communications Inc. Device 0034 (rev 01)
	Subsystem: Lite-On Communications Inc Device 6621
	Flags: bus master, fast devsel, latency 0, IRQ 19
	Memory at c0400000 (64-bit, non-prefetchable) [size=512K]
	Expansion ROM at aff00000 [disabled] [size=64K]
	Capabilities: [40] Power Management version 2
	Capabilities: [50] MSI: Enable- Count=1/4 Maskable+ 64bit+
	Capabilities: [70] Express Endpoint, MSI 00
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [140] Virtual Channel
	Capabilities: [160] Device Serial Number 00-00-00-00-00-00-00-00
	Kernel driver in use: ath9k

Connection is intermittent and replicated on multiple type of access point, so I think it should not AP firmware problem.

Comment 19 Peter Hinse 2012-08-02 17:48:09 UTC
Same here with Intel iwlwifi:


02:00.0 Network controller: Intel Corporation Centrino Wireless-N 1000
	Subsystem: Intel Corporation Centrino Wireless-N 1000 BGN
	Flags: bus master, fast devsel, latency 0, IRQ 45
	Memory at d2500000 (64-bit, non-prefetchable) [size=8K]
	Capabilities: <access denied>
	Kernel driver in use: iwlwifi

With high traffic on the interface (Dropbox sync), there is a pattern in disconnects:


Aug  2 19:25:15 smallboy NetworkManager[743]: <info> (wlan0): supplicant interface state: completed -> disconnected
Aug  2 19:27:15 smallboy NetworkManager[743]: <info> (wlan0): supplicant interface state: completed -> disconnected
Aug  2 19:29:15 smallboy NetworkManager[743]: <info> (wlan0): supplicant interface state: completed -> disconnected
Aug  2 19:31:15 smallboy NetworkManager[743]: <info> (wlan0): supplicant interface state: completed -> disconnected

Without traffic, there are no disconnects at all. Will try to log some debug messages...

System info: Fedora 17, Kernel 3.4.6-2.fc17.x86_64 (same with all other F17 kernels before)

Comment 20 Peter Hinse 2012-08-02 19:54:22 UTC
I did some more tests: seems to mostly happen only when running on battery, now after a reboot when idle (and not while transferring data):

wpa_supplicant.log:

wlan0: CTRL-EVENT-DISCONNECTED bssid=00:26:f2:cb:20:40 reason=4
wlan0: Failed to initiate AP scan
wlan0: SME: Trying to authenticate with 00:26:f2:cb:20:40 (SSID='Pommesbude' freq=2437 MHz)
wlan0: Trying to associate with 00:26:f2:cb:20:40 (SSID='Pommesbude' freq=2437 MHz)
wlan0: Associated with 00:26:f2:cb:20:40
wlan0: WPA: Key negotiation completed with 00:26:f2:cb:20:40 [PTK=CCMP GTK=TKIP]
wlan0: CTRL-EVENT-CONNECTED - Connection to 00:26:f2:cb:20:40 completed (reauth) [id=0 id_str=]
wlan0: CTRL-EVENT-DISCONNECTED bssid=00:26:f2:cb:20:40 reason=4
wlan0: Failed to initiate AP scan
wlan0: SME: Trying to authenticate with 00:26:f2:cb:20:40 (SSID='Pommesbude' freq=2437 MHz)
wlan0: Trying to associate with 00:26:f2:cb:20:40 (SSID='Pommesbude' freq=2437 MHz)
wlan0: Associated with 00:26:f2:cb:20:40
wlan0: WPA: Key negotiation completed with 00:26:f2:cb:20:40 [PTK=CCMP GTK=TKIP]
wlan0: CTRL-EVENT-CONNECTED - Connection to 00:26:f2:cb:20:40 completed (reauth) [id=0 id_str=]

In /var/log/messages I see this every two minutes:


Aug  2 21:42:22 smallboy kernel: [12739.465269] cfg80211: Calling CRDA to update world regulatory domain
Aug  2 21:42:22 smallboy NetworkManager[743]: <info> (wlan0): supplicant interface state: completed -> disconnected
Aug  2 21:42:22 smallboy kernel: [12739.499428] cfg80211: World regulatory domain updated:
Aug  2 21:42:22 smallboy kernel: [12739.499433] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Aug  2 21:42:22 smallboy kernel: [12739.499438] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Aug  2 21:42:22 smallboy kernel: [12739.499442] cfg80211:   (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Aug  2 21:42:22 smallboy kernel: [12739.499447] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Aug  2 21:42:22 smallboy kernel: [12739.499451] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Aug  2 21:42:22 smallboy kernel: [12739.499455] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Aug  2 21:42:22 smallboy kernel: [12739.499480] cfg80211: Calling CRDA for country: DE
Aug  2 21:42:22 smallboy kernel: [12739.502453] cfg80211: Regulatory domain changed to country: DE
Aug  2 21:42:22 smallboy kernel: [12739.502458] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Aug  2 21:42:22 smallboy kernel: [12739.502462] cfg80211:   (2400000 KHz - 2483500 KHz @ 40000 KHz), (N/A, 2000 mBm)
Aug  2 21:42:22 smallboy kernel: [12739.502467] cfg80211:   (5150000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm)
Aug  2 21:42:22 smallboy kernel: [12739.502471] cfg80211:   (5250000 KHz - 5350000 KHz @ 40000 KHz), (N/A, 2000 mBm)
Aug  2 21:42:22 smallboy kernel: [12739.502474] cfg80211:   (5470000 KHz - 5725000 KHz @ 40000 KHz), (N/A, 2698 mBm)
Aug  2 21:42:23 smallboy NetworkManager[743]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Aug  2 21:42:30 smallboy NetworkManager[743]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Aug  2 21:42:30 smallboy NetworkManager[743]: <info> (wlan0): supplicant interface state: authenticating -> associating
Aug  2 21:42:30 smallboy NetworkManager[743]: <info> (wlan0): supplicant interface state: associating -> 4-way handshake
Aug  2 21:42:30 smallboy NetworkManager[743]: <info> (wlan0): supplicant interface state: 4-way handshake -> completed

Comment 21 Adhidarma Hadiwinoto 2012-08-11 14:00:01 UTC
Looks like the problem has vanished since kernel 3.5.0-2.fc17.x86_64.

Comment 22 John W. Linville 2012-08-13 14:54:16 UTC
Closing on the basis of comment 21...

Comment 23 Gustavo 2012-09-28 17:23:14 UTC
Hello,
I know this issue is closed, but I have the same problem with my laptop.
It's running F17:
root@raptor ~]# uname -a
Linux raptor 3.5.4-1.fc17.x86_64 #1 SMP Mon Sep 17 15:03:59 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux


Note You need to log in before you can comment on or make changes to this bug.