ath9k: Sometimes cannot establish wireless connection on the first attempt after login

[Jaromir Obr]

I'm not able to reproduce it reliably.

Sometimes when I login to Gnome, WiFi connection cannot be established. Network manager shows a progress (wheel) on gnome panel, but it fails to connect during one minute - dialog with preselected credentials to WPA2 connection appears and I have to click on "Connect" again.

dmesg log shows:
-----------------------
[ 55.087224] wlan0: direct probe to AP 00:24:01:98:1c:f0 (try 1)
[ 55.087238] wlan0: deauthenticating from 00:24:01:98:1c:f0 by local choice (reason=3)
[ 55.087343] wlan0: direct probe to AP 00:24:01:98:1c:f0 (try 1)
[ 55.091935] wlan0: direct probe responded
[ 55.091942] wlan0: authenticate with AP 00:24:01:98:1c:f0 (try 1)
[ 55.098572] wlan0: authenticated
[ 55.098601] wlan0: associate with AP 00:24:01:98:1c:f0 (try 1)
[ 55.125392] wlan0: RX AssocResp from 00:24:01:98:1c:f0 (capab=0x431 status=0 aid=3)
[ 55.125397] wlan0: associated
[ 55.126211] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 65.180041] wlan0: deauthenticating from 00:24:01:98:1c:f0 by local choice (reason=3)
[ 65.370325] ath9k: Two wiphys trying to scan at the same time
[ 65.370357] wlan0: deauthenticating from 00:24:01:98:1c:f0 by local choice (reason=3)
[ 65.410022] wlan0: no IPv6 routers present
[ 65.568203] wlan0: direct probe to AP 00:24:01:98:1c:f0 (try 1)
[ 65.571406] wlan0: direct probe responded
[ 65.571413] wlan0: authenticate with AP 00:24:01:98:1c:f0 (try 1)
[ 65.574397] wlan0: authenticated
[ 65.574424] wlan0: associate with AP 00:24:01:98:1c:f0 (try 1)
[ 65.579391] wlan0: RX AssocResp from 00:24:01:98:1c:f0 (capab=0x431 status=0 aid=3)
[ 65.579394] wlan0: associated
[ 75.640055] wlan0: deauthenticating from 00:24:01:98:1c:f0 by local choice (reason=3)
[ 75.831616] ath9k: Two wiphys trying to scan at the same time
[ 75.831651] wlan0: deauthenticating from 00:24:01:98:1c:f0 by local choice (reason=3)
[ 76.028083] wlan0: direct probe to AP 00:24:01:98:1c:f0 (try 1)
[ 76.031374] wlan0: direct probe responded
[ 76.031380] wlan0: authenticate with AP 00:24:01:98:1c:f0 (try 1)
[ 76.033550] wlan0: authenticated
[ 76.033572] wlan0: associate with AP 00:24:01:98:1c:f0 (try 1)
[ 76.036245] wlan0: RX AssocResp from 00:24:01:98:1c:f0 (capab=0x431 status=0 aid=3)
[ 76.036250] wlan0: associated
[ 86.090043] wlan0: deauthenticating from 00:24:01:98:1c:f0 by local choice (reason=3)
[ 86.290329] ath9k: Two wiphys trying to scan at the same time
[ 86.290361] wlan0: deauthenticating from 00:24:01:98:1c:f0 by local choice (reason=3)
[ 86.488210] wlan0: direct probe to AP 00:24:01:98:1c:f0 (try 1)
[ 86.680036] wlan0: direct probe to AP 00:24:01:98:1c:f0 (try 2)
[ 86.683460] wlan0: direct probe responded
[ 86.683463] wlan0: authenticate with AP 00:24:01:98:1c:f0 (try 1)
[ 86.686727] wlan0: authenticated
[ 86.686750] wlan0: associate with AP 00:24:01:98:1c:f0 (try 1)
[ 86.689409] wlan0: RX AssocResp from 00:24:01:98:1c:f0 (capab=0x431 status=0 aid=3)
[ 86.689411] wlan0: associated
[ 96.750124] wlan0: deauthenticating from 00:24:01:98:1c:f0 by local choice (reason=3)
[ 96.951596] ath9k: Two wiphys trying to scan at the same time
[ 96.951670] wlan0: deauthenticating from 00:24:01:98:1c:f0 by local choice (reason=3)
[ 97.158306] wlan0: direct probe to AP 00:24:01:98:1c:f0 (try 1)
[ 97.161725] wlan0: direct probe responded
[ 97.161732] wlan0: authenticate with AP 00:24:01:98:1c:f0 (try 1)
[ 97.163933] wlan0: authenticated
[ 97.163957] wlan0: associate with AP 00:24:01:98:1c:f0 (try 1)
[ 97.166722] wlan0: RX AssocResp from 00:24:01:98:1c:f0 (capab=0x431 status=0 aid=3)
[ 97.166725] wlan0: associated
[ 107.240106] wlan0: deauthenticating from 00:24:01:98:1c:f0 by local choice (reason=3)

Sometimes a next attempt is successful, sometimes I have to perform further 2-3 attempts so that connection can be established. Then the network works well.

Used SW:
-------------
Ubuntu 10.04, amd64
kernel 2.6.32-17-generic #26 (it happened even with older 2.6.32 kernels)
network-manager: 0.8-0ubuntu2

Used HW:
-------------
WiFi Atheros Communications Inc. AR928X Wireless Network Adapter
driver ath9k
WPA2 connection
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: SB [HDA ATI SB], device 0: ALC268 Analog [ALC268 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: mira 1759 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'SB'/'HDA ATI SB at 0xd6400000 irq 16'
   Mixer name : 'Realtek ALC268'
   Components : 'HDA:10ec0268,1179ff62,00100003'
   Controls : 18
   Simple ctrls : 10
CheckboxSubmission: ca8cd8511cd050bd957f6b0d37298435
CheckboxSystem: 5202e7ee197af4942baf4f50cf4120c6
DistroRelease: Ubuntu 10.04
Frequency: Once a week.
HibernationDevice: RESUME=UUID=1fbf246d-5d08-41fe-bd7e-ad4cd8a192ce
MachineType: TOSHIBA Satellite A300D
Package: linux (not installed)
ProcCmdLine: root=UUID=5564d628-8fc2-42b9-ba8d-cb1b7937a3e8 ro
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
Regression: No
RelatedPackageVersions: linux-firmware 1.33
Reproducible: No
Tags: lucid needs-upstream-testing
TestedUpstream: No
Uname: Linux 2.6.32-17-generic x86_64
UserGroups: adm admin cdrom dialout kqemu kvm libvirtd lpadmin netdev plugdev sambashare
WpaSupplicantLog:

dmi.bios.date: 07/29/2009
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 2.00
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: AMD
dmi.chassis.version: None
dmi.modalias: dmi:bvnInsydeCorp.:bvr2.00:bd07/29/2009:svnTOSHIBA:pnSatelliteA300D:pvrPSAHCE-00F00JCZ:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnAMD:ct10:cvrNone:
dmi.product.name: Satellite A300D
dmi.product.version: PSAHCE-00F00JCZ
dmi.sys.vendor: TOSHIBA

[Jaromir Obr (jaromir-obr)]

apport information

[Jaromir Obr (jaromir-obr)]

apport information

[Jaromir Obr (jaromir-obr)]

apport information

[Jaromir Obr (jaromir-obr)]

apport information

[Jaromir Obr (jaromir-obr)]

apport information

[Jaromir Obr (jaromir-obr)]

apport information

[Jaromir Obr (jaromir-obr)]

apport information

[Jaromir Obr (jaromir-obr)]

apport information

[Jaromir Obr (jaromir-obr)]

apport information

[Jaromir Obr (jaromir-obr)]

apport information

[Jaromir Obr (jaromir-obr)]

apport information

[Jaromir Obr (jaromir-obr)]

apport information

[Jaromir Obr (jaromir-obr)]

apport information

[Jaromir Obr (jaromir-obr)]

apport information

[Jaromir Obr (jaromir-obr)]

apport information

[Jaromir Obr (jaromir-obr)]

apport information

[Jaromir Obr (jaromir-obr)]

apport information

[Bernhard (b.a.koenig)]

Please compare with bug 496093. You seem to have a different wireless card, but it still looks like a duplicate.

[Jaromir Obr (jaromir-obr)]

In reply to comment 18:
It's hard to say if it is the same bug. Most users affected by bug #496093 have set mixed mode (WPA/WPA2) on their router, whereas I'm using "WPA2 only" mode.

[Guillaume Millet (guimillet)]

Is it a WPA enterprise?

[Jaromir Obr (jaromir-obr)]

No, it is WPA personal.

[Jeremy Foshee (jeremyfoshee)]

Hi Jaromir,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 549827

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . 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.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Jaromir Obr (jaromir-obr)]

I haven't hit this issue for long time since I reported it. I suppose it could be fixed somehow.

My current configuration:
--------------------------------
OS: Ubuntu 10.04, amd64
kernel: 2.6.32-22-generic #33
network-manager: 0.8-0ubuntu3

[Ilya Volvovski (ilya-volvovski)]

I have very similar behavior, happens several time during a day. It happen with 9.10 but it became more frequent with 10.4.The major difference with the original report that a successful connection is always established after reboot.

On some occasions both wireless and wired connection exist, but no ip is accessible. eth0 always restores normal operations as soon as I restart networking service (disable/enable through Network manager applet), but it doesn't help wireless connection could not be established, even though a network is available and signal strength is around 50%.

After I tried to reload ath9k driver and I could reconnect, though it takes 10-15 seconds (is it normal?)

Linux volvovski-home 2.6.32-22-generic #33-Ubuntu SMP Wed Apr 28 13:28:05 UTC 2010 x86_64 GNU/Linux

04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02)05:00.0 Network controller: Atheros Communications Inc. AR928X Wireless Network Adapter (PCI-Express) (rev 01)

dmesg is very similar to what was presented in the original report. Any other information you need?

Thank you

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu development release http://cdimage.ubuntu.com/daily-live/current/ . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]