ath9k disassociates when scanning

Bug #853950 reported by Steve Magoun
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

My wireless network connection disassociates and reassociates every 120sec. It happens pretty reliably - upt to 95% of the time when I'm actively using the connection (e.g. participating in a discussion in Mumble or cloning a git tree from a remote server). The disassociate/reassociate cycle causes network transfers to temporarily stall, and applications using UDP (such as Mumble) drop out.

Based on feedback from other people in my group, the problem may be limited to the ath9k driver.

The 120sec number is suspicious; I believe NetworkManager runs a background scanning thread at a 120sec interval. I can also reproduce the problem by manually initiating a scan via 'iwlist wlan0 scanning'.

The problem started when I upgraded from 11.04 to 11.10 beta 1.

The reason code given in syslog is almost always '10', though I have seen a very occasional '2'. Here is an example of what I get in syslog each time this happens:

Sep 19 11:28:11 steve-laptop kernel: [ 8383.513754] wlan0: deauthenticated from 00:27:0d:71:8f:80 (Reason: 10)
Sep 19 11:28:11 steve-laptop wpa_supplicant[805]: CTRL-EVENT-DISCONNECTED bssid=00:27:0d:71:8f:80 reason=10
Sep 19 11:28:11 steve-laptop NetworkManager[673]: <info> (wlan0): supplicant interface state: completed -> disconnected
Sep 19 11:28:11 steve-laptop kernel: [ 8383.560356] cfg80211: All devices are disconnected, going to restore regulatory settings
Sep 19 11:28:11 steve-laptop kernel: [ 8383.560368] cfg80211: Restoring regulatory settings
Sep 19 11:28:11 steve-laptop kernel: [ 8383.560402] cfg80211: Calling CRDA to update world regulatory domain
Sep 19 11:28:11 steve-laptop kernel: [ 8383.569424] cfg80211: Ignoring regulatory request Set by core since the driver uses its own custom regulatory domain
Sep 19 11:28:11 steve-laptop kernel: [ 8383.569435] cfg80211: World regulatory domain updated:
Sep 19 11:28:11 steve-laptop kernel: [ 8383.569440] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Sep 19 11:28:11 steve-laptop kernel: [ 8383.569449] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Sep 19 11:28:11 steve-laptop kernel: [ 8383.569457] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Sep 19 11:28:11 steve-laptop kernel: [ 8383.569464] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Sep 19 11:28:11 steve-laptop kernel: [ 8383.569472] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Sep 19 11:28:11 steve-laptop kernel: [ 8383.569479] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Sep 19 11:28:11 steve-laptop NetworkManager[673]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Sep 19 11:28:13 steve-laptop wpa_supplicant[805]: Trying to authenticate with 00:27:0d:71:8f:80 (SSID='<redacted>' freq=2412 MHz)
Sep 19 11:28:13 steve-laptop NetworkManager[673]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Sep 19 11:28:13 steve-laptop wpa_supplicant[805]: Trying to associate with 00:27:0d:71:8f:80 (SSID='<redacted>' freq=2412 MHz)
Sep 19 11:28:13 steve-laptop kernel: [ 8385.826720] wlan0: authenticate with 00:27:0d:71:8f:80 (try 1)
Sep 19 11:28:13 steve-laptop kernel: [ 8385.828715] wlan0: authenticated
Sep 19 11:28:13 steve-laptop wpa_supplicant[805]: Associated with 00:27:0d:71:8f:80
Sep 19 11:28:13 steve-laptop kernel: [ 8385.832945] wlan0: associate with 00:27:0d:71:8f:80 (try 1)
Sep 19 11:28:13 steve-laptop kernel: [ 8385.836196] wlan0: RX ReassocResp from 00:27:0d:71:8f:80 (capab=0x431 status=0 aid=5)
Sep 19 11:28:13 steve-laptop kernel: [ 8385.836205] wlan0: associated
Sep 19 11:28:13 steve-laptop NetworkManager[673]: <info> (wlan0): supplicant interface state: authenticating -> associating
Sep 19 11:28:13 steve-laptop NetworkManager[673]: <info> (wlan0): supplicant interface state: associating -> 4-way handshake
Sep 19 11:28:13 steve-laptop wpa_supplicant[805]: WPA: Key negotiation completed with 00:27:0d:71:8f:80 [PTK=TKIP GTK=TKIP]
Sep 19 11:28:13 steve-laptop wpa_supplicant[805]: CTRL-EVENT-CONNECTED - Connection to 00:27:0d:71:8f:80 completed (reauth) [id=0 id_str=]
Sep 19 11:28:13 steve-laptop NetworkManager[673]: <info> (wlan0): supplicant interface state: 4-way handshake -> completed

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: linux-image-3.0.0-11-generic 3.0.0-11.18
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: steve 1782 F.... pulseaudio
 /dev/snd/pcmC0D0p: steve 1782 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xdb500000 irq 46'
   Mixer name : 'Realtek ALC889A'
   Components : 'HDA:10ec0885,106b2c00,00100103'
   Controls : 33
   Simple ctrls : 19
Date: Mon Sep 19 10:56:51 2011
HibernationDevice: RESUME=UUID=efdcd1bc-2e1a-4a77-8ff8-e46a71b2a78c
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1)
MachineType: Apple Inc. MacBookPro3,1
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-11-generic root=UUID=4b3d81ed-fb5d-4946-97c0-ec537e1bfa3f ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.0.0-11-generic N/A
 linux-backports-modules-3.0.0-11-generic N/A
 linux-firmware 1.60
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to oneiric on 2011-09-02 (17 days ago)
dmi.bios.date: 03/05/08
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP31.88Z.0070.B07.0803051658
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Mac-F4238BC8
dmi.board.vendor: Apple Inc.
dmi.board.version: PVT
dmi.chassis.asset.tag: Asset Tag#
dmi.chassis.type: 2
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-F4238BC8
dmi.modalias: dmi:bvnAppleInc.:bvrMBP31.88Z.0070.B07.0803051658:bd03/05/08:svnAppleInc.:pnMacBookPro3,1:pvr1.0:rvnAppleInc.:rnMac-F4238BC8:rvrPVT:cvnAppleInc.:ct2:cvrMac-F4238BC8:
dmi.product.name: MacBookPro3,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

Revision history for this message
Steve Magoun (smagoun) wrote :
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Brad Figg (brad-figg) wrote : Test with newer development kernel (3.0.0-12.19)

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.0.0-12.19
Revision history for this message
Steve Magoun (smagoun) wrote :

Still buggy in 3.0.0-12.19:
Linux steve-laptop 3.0.0-12-generic #19-Ubuntu SMP Fri Sep 23 21:23:39 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Brad Figg (brad-figg) wrote : Test with newer development kernel (3.0.0-12.20)

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.0.0-12.20
Revision history for this message
Steve Magoun (smagoun) wrote :

Still buggy with 3.0.0-12.20.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the release candidate kernel versus the daily build. Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

tags: added: needs-upstream-testing
Revision history for this message
Dean McLennan (dgmclennan) wrote :
Download full text (6.8 KiB)

Using latest 12.04 daily with kernel 3.3 rc1 mainline on UX31E zenbook
kern.log

Jan 27 11:50:46 blade kernel: [ 4512.596320] wlan0: moving STA 00:12:17:b8:79:3e to state 2
Jan 27 11:50:46 blade kernel: [ 4512.596329] wlan0: moving STA 00:12:17:b8:79:3e to state 1
Jan 27 11:50:46 blade kernel: [ 4512.596335] wlan0: moving STA 00:12:17:b8:79:3e to state 0
Jan 27 11:50:46 blade kernel: [ 4512.600400] cfg80211: All devices are disconnected, going to restore regulatory settings
Jan 27 11:50:46 blade kernel: [ 4512.600415] cfg80211: Restoring regulatory settings
Jan 27 11:50:46 blade kernel: [ 4512.600427] cfg80211: Calling CRDA to update world regulatory domain
Jan 27 11:50:46 blade NetworkManager[809]: <info> (wlan0): supplicant interface state: completed -> disconnected
Jan 27 11:50:46 blade kernel: [ 4512.608115] cfg80211: Ignoring regulatory request Set by core since the driver uses its own custom regulatory domain
Jan 27 11:50:46 blade kernel: [ 4512.608172] cfg80211: World regulatory domain updated:
Jan 27 11:50:46 blade kernel: [ 4512.608179] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Jan 27 11:50:46 blade kernel: [ 4512.608193] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Jan 27 11:50:46 blade kernel: [ 4512.608205] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Jan 27 11:50:46 blade kernel: [ 4512.608217] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Jan 27 11:50:46 blade kernel: [ 4512.608227] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Jan 27 11:50:46 blade kernel: [ 4512.608234] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Jan 27 11:50:46 blade NetworkManager[809]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Jan 27 11:50:47 blade wpa_supplicant[816]: Trying to authenticate with 00:12:17:b8:79:3e (SSID='nexxus' freq=2442 MHz)
Jan 27 11:50:47 blade NetworkManager[809]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Jan 27 11:50:47 blade kernel: [ 4513.691611] wlan0: authenticate with 00:12:17:b8:79:3e (try 1)
Jan 27 11:50:47 blade kernel: [ 4513.694318] wlan0: authenticated
Jan 27 11:50:47 blade wpa_supplicant[816]: Trying to associate with 00:12:17:b8:79:3e (SSID='nexxus' freq=2442 MHz)
Jan 27 11:50:47 blade kernel: [ 4513.696033] wlan0: associate with 00:12:17:b8:79:3e (try 1)
Jan 27 11:50:47 blade NetworkManager[809]: <info> (wlan0): supplicant interface state: authenticating -> associating
Jan 27 11:50:47 blade wpa_supplicant[816]: Associated with 00:12:17:b8:79:3e
Jan 27 11:50:47 blade kernel: [ 4513.700767] wlan0: RX ReassocResp from 00:12:17:b8:79:3e (capab=0x411 status=0 aid=1)
Jan 27 11:50:47 blade kernel: [ 4513.700778] wlan0: associated
Jan 27 11:50:47 blade kernel: [ 4513.700790] wlan0: moving STA 00:12:17:b8:79:3e to state 1
Jan 27 11:50:47 blade kernel: [ 4513.700797] wlan0: moving STA 00:12:17:b8:79:3e to state 2
Jan 27 11:50:47 blade NetworkManager[809]: <info> (wlan0): supplicant interface state: associating -> group handshake
Jan 27 11:50:47 blade wpa_supplicant[816]: WPA: Key negotiation completed wi...

Read more...

Revision history for this message
Steve Magoun (smagoun) wrote :

I can't currently reproduce this in 12.04 on the Macbook Pro 3,1 with the 3.2.0-12.21 kernel.

Test case:
1) In one terminal, `tail -f /var/log/syslog`
2) In another terminal, clone the Ubuntu kernel git tree: `git clone git://kernel.ubuntu.com/ubuntu/ubuntu-precise.git`
2a) Optional, download an ISO in a browser to ensure that the network card is loaded up
3) In a third terminal, `iwlist wlan0 scanning`

While the iwlist command is running, I see no interruption in the git transfer or browser download, and nothing in syslog.

Revision history for this message
penalvch (penalvch) wrote :

Steve Magoun, this bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

tags: added: regression-release
Changed in linux (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.