Matt Behrens, 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? If so, could you please test for this with the latest development
release of Ubuntu? ISO CD images are available from
http://cdimage.ubuntu.com/daily-live/current/ .
If it remains an issue, could you please run the following command in
the development release from a Terminal
(Applications-Accessories-Terminal), as it will automatically gather
and attach updated debug information to this report:
apport-collect -p linux replace-with-bug-number
Also, could you please test the latest upstream kernel available following
https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional
upstream developers to examine the issue. Please do not test the kernel in the
mainline kernels archive directory daily folder, but the one all the way at the
bottom. Once you've tested the upstream kernel, please comment on which kernel
version specifically you tested. If this bug is fixed in the mainline kernel,
please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER
where VERSION-NUMBER is the version number of the kernel you tested. For
example:
kernel-fixed-upstream-v3.8-rc5
This can be done by clicking on the yellow circle with a black pencil icon next
to the word Tags located at the bottom of the bug description. As well, please
remove the tag:
needs-upstream-testing
If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER
As well, please remove the tag:
needs-upstream-testing
If you are unable to test the mainline kernel, please comment as to why
specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER
Once testing of the upstream kernel is complete, please mark this bug's
Status as Confirmed. Please let us know your results. Thank you for your
understanding.
** Summary changed:
- ath9k disassociates/reassociates a lot
+ 168c:002a ath9k disassociates/reassociates a lot
** Description changed:
I cannot find any rhyme or reason to this, but my
-
- 01:00.0 Network controller: Atheros Communications Inc. AR928X Wireless
- Network Adapter (PCI-Express) (rev 01)
+ 01:00.0 Network controller: Atheros Communications Inc. AR928X Wireless
Network Adapter (PCI-Express) (rev 01)
seems to like to disassociate/reassociate a lot since I started testing
karmic as of alpha 4.
A typical dmesg excerpt:
-
[ 1881.988111] wlan0: no probe response from AP 00:15:e9:13:47:60 -
disassociating
[ 1883.367859] wlan0: authenticate with AP 00:15:e9:13:47:60
[ 1883.370161] wlan0: authenticated
[ 1883.370181] wlan0: associate with AP 00:15:e9:13:47:60
[ 1883.372802] wlan0: RX ReassocResp from 00:15:e9:13:47:60 (capab=0x431
status=0 aid=1)
[ 1883.372822] wlan0: associated
[ 1892.008117] wlan0: no probe response from AP 00:15:e9:13:47:60 -
disassociating
[ 1893.385338] wlan0: authenticate with AP 00:15:e9:13:47:60
[ 1893.385521] wlan0: authenticate with AP 00:15:e9:13:47:60
[ 1893.388175] wlan0: authenticated
[ 1893.388196] wlan0: associate with AP 00:15:e9:13:47:60
[ 1893.391563] wlan0: RX ReassocResp from 00:15:e9:13:47:60 (capab=0x431
status=0 aid=1)
[ 1893.391585] wlan0: associated
[ 1926.988135] wlan0: no probe response from AP 00:15:e9:13:47:60 -
disassociating
[ 1928.365306] wlan0: authenticate with AP 00:15:e9:13:47:60
[ 1928.367426] wlan0: authenticated
[ 1928.367442] wlan0: associate with AP 00:15:e9:13:47:60
[ 1928.370948] wlan0: RX ReassocResp from 00:15:e9:13:47:60 (capab=0x431
status=0 aid=1)
[ 1928.370969] wlan0: associated
[ 1966.988114] wlan0: no probe response from AP 00:15:e9:13:47:60 -
disassociating
[ 1968.366568] wlan0: authenticate with AP 00:15:e9:13:47:60
[ 1968.368624] wlan0: authenticated
[ 1968.368643] wlan0: associate with AP 00:15:e9:13:47:60
[ 1968.371872] wlan0: RX ReassocResp from 00:15:e9:13:47:60 (capab=0x431
status=0 aid=1)
[ 1968.371893] wlan0: associated
Performance drops significantly when this starts going on. At times it
becomes impossible to look up hosts, etc. Other times, it will run fine
for hours on end.
+ WORKAROUND: ndiswrapper.
+
ProblemType: Bug
AplayDevices:
- List of PLAYBACK Hardware Devices
- card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
-Subdevices: 1/1
-Subdevice #0: subdevice #0
+ List of PLAYBACK Hardware Devices
+ card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
+ Subdevices: 1/1
+ Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
- List of CAPTURE Hardware Devices
- card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
-Subdevices: 1/1
-Subdevice #0: subdevice #0
+ List of CAPTURE Hardware Devices
