eeepc wireless fails to connect after screensaver / sleep mode

[what_if]

lsb_release -rd:
Description: Ubuntu 9.04
Release: 9.04
+++++++++++++++++++++++++++++
apt-cache policy linux-image-2.6.28-14-generic:
linux-image-2.6.28-14-generic:
  Installed: 2.6.28-14.47
  Candidate: 2.6.28-14.47
  Version table:
 *** 2.6.28-14.47 0
        500 http://us.archive.ubuntu.com jaunty-updates/main Packages
        500 http://security.ubuntu.com jaunty-security/main Packages
        100 /var/lib/dpkg/status
+++++++++++++++++++++++++++++++++
apt-cache policy linux-backports-modules-2.6.28-14-generic
linux-backports-modules-2.6.28-14-generic:
  Installed: 2.6.28-14.16
  Candidate: 2.6.28-14.16
  Version table:
 *** 2.6.28-14.16 0
        500 http://us.archive.ubuntu.com jaunty-updates/main Packages
        500 http://security.ubuntu.com jaunty-security/main Packages
        100 /var/lib/dpkg/status
+++++++++++++++++++++++++++++++++++++
lspci | grep Atheros:
02:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
++++++++++++++++++++++++++++++++++++++++++++++++++++

What I expected to happen:
After opening the lid on my eeePC 1005HA and it resuming from "sleep" or "screensaver mode" I expected the wireless ethernet connection to automatically reconnect or alternatively for it to allow me to manually reconnect. Instead the wireless never connects and I get the following repeating dmesg output:
......................
[77563.832085] wlan0: beacon loss from AP f61756b8 - sending probe request
[77565.832071] wlan0: no probe response from AP f61756b8 - disassociating
[77567.394903] wlan0: authenticate with AP f61756b8
[77567.405145] wlan0: authenticate with AP f61756b8
[77567.407181] wlan0: authenticated
[77567.407195] wlan0: associate with AP f61756b8
[77567.411166] wlan0: RX ReassocResp from f3be602a (capab=0x431 status=0 aid=1)
[77567.411177] wlan0: associated
[82784.260111] wlan0: beacon loss from AP f61756b8 - sending probe request
[82786.260101] wlan0: no probe response from AP f61756b8 - disassociating
[82787.826550] wlan0: authenticate with AP f61756b8
[82787.850948] wlan0: authenticate with AP f61756b8
[82787.852982] wlan0: authenticated
[82787.852992] wlan0: associate with AP f61756b8
[82787.857115] wlan0: RX ReassocResp from e4d2202a (capab=0x431 status=0 aid=1)
[82787.857129] wlan0: associated
[82896.272082] wlan0: beacon loss from AP f61756b8 - sending probe request
[83352.584114] wlan0: beacon loss from AP f61756b8 - sending probe request
[83354.584111] wlan0: no probe response from AP f61756b8 - disassociating

The card connects and disconnects forever, never reaching the point of receiving an IP address (DHCP). The dmesg output I posted is simply the last few lines.

Known fixes:
1) Rebooting the computer.
2) Issuing command "sudo rmmod ath9k ; sudo modprobe ath9k"

It appears to me that the ath9k module does not or cannot sleep/wake or suspend/resume but I am unsure how to troubleshoot this further or how to verify that ath9k is the offender. Feel free to e-mail me for more information.

[Jason 'vanRijn' Kasper (vr-movingparts)]

I'm seeing this too. Eee PC 1005HA. Ubuntu 9.04 2.6.28-15-generic #49-Ubuntu SMP Tue Aug 18 18:40:08 UTC 2009 i686 GNU/Linux. Really annoying. I'd love to help fix this, but I don't see any kernel module options that look helpful from modinfo ath9k.

[celer (celer)]

I have the same issue, except that it doesn't seem to matter if the computer ever went to sleep.

I am running a PC 1005HA, Ubuntu 9.04, Linux raven 2.6.28-15-generic #49-Ubuntu.

[ 21.274268] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 21.274275] Bluetooth: BNEP filters: protocol multicast
[ 21.308055] Bridge firewalling registered
[ 23.235989] ppdev: user-space parallel port driver
[ 23.813689] [drm] Initialized drm 1.1.0 20060810
[ 23.846246] pci 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 23.846255] pci 0000:00:02.0: setting latency timer to 64
[ 23.846582] [drm] Initialized i915 1.6.0 20080730 on minor 0
[ 23.851750] [drm:i915_setparam] *ERROR* unknown parameter 4
[ 23.851817] [drm:i915_getparam] *ERROR* Unknown parameter 6
[ 25.126498] [drm:i915_getparam] *ERROR* Unknown parameter 6
[ 26.874978] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 39.809478] [drm:i915_getparam] *ERROR* Unknown parameter 6
[ 42.095204] [drm:i915_getparam] *ERROR* Unknown parameter 6
[ 43.768597] wlan0: authenticate with AP f64706b8
[ 43.770551] wlan0: authenticated
[ 43.770560] wlan0: associate with AP f64706b8
[ 43.776342] wlan0: RX AssocResp from f635602a (capab=0x411 status=0 aid=2)
[ 43.776353] wlan0: associated
[ 43.791028] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 43.887377] cfg80211: Calling CRDA for country: IE
[ 43.903943] cfg80211: Current regulatory domain updated by AP to: IE
[ 43.903954] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp
)
[ 43.903962] (2402000 KHz - 2477000 KHz @ 40000 KHz), (N/A, 2000 mBm)
[ 44.144362] padlock: VIA PadLock not detected.
[ 54.224048] wlan0: no IPv6 routers present
[ 76.220082] wlan0: beacon loss from AP f64706b8 - sending probe request
[ 78.220085] wlan0: no probe response from AP f64706b8 - disassociating

...

[ 1520.590103] wlan0: RX ReassocResp from f550e02a (capab=0x411 status=0 aid=2)
[ 1520.590114] wlan0: associated
[ 1936.652180] wlan0: beacon loss from AP f64706b8 - sending probe request
[ 1938.652165] wlan0: no probe response from AP f64706b8 - disassociating
[ 1939.747872] wlan0: authenticate with AP f64706b8
[ 1939.757973] wlan0: authenticate with AP f64706b8
[ 1939.759516] wlan0: authenticated
[ 1939.759525] wlan0: associate with AP f64706b8
[ 1939.766669] wlan0: RX ReassocResp from f56ec02a (capab=0x411 status=0 aid=2)
[ 1939.766680] wlan0: associated
[ 2686.060069] wlan0: beacon loss from AP f64706b8 - sending probe request
[ 2688.060072] wlan0: no probe response from AP f64706b8 - disassociating
[ 2689.155759] wlan0: authenticate with AP f64706b8
[ 2689.165908] wlan0: authenticate with AP f64706b8
[ 2689.168654] wlan0: authenticated
[ 2689.168662] wlan0: associate with AP f64706b8
[ 2689.175090] wlan0: RX ReassocResp from f51aa02a (capab=0x411 status=0 aid=2)
[ 2689.175101] wlan0: associated
[ 2716.020071] wlan0: beacon loss from AP f64706b8 - sending probe request
[ 2718.020079] wlan0: no probe response from AP f64706b8 - disassociating
[ 2719.116942] wlan0: authenticate with AP f64706b8
[ 2719.119013] wlan0: authenticated
[ 2719.119022] wlan0: associate with AP f64706b8
[ 2719.124663] wlan0: RX ...

[Philip Muškovac (yofel)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage. I have classified this bug as a bug in the linux kernel.

When reporting bugs in the future please use apport, either via the appropriate application's "Help -> Report a Problem" menu or using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

[Jeremy Foshee (jeremyfoshee)]

Hi what_if,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/releases/ . If the issue remains, please 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 417690

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.]

[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 release http://www.ubuntu.com/getubuntu/download . 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.]