FS#17183 - [kernel26] ath9k wlan loses connection after standby (suspend to ram) until reloading module

Attached to Project: Arch Linux
Opened by Freek (teek) - Wednesday, 18 November 2009, 11:40 GMT
Last edited by Allan McRae (Allan) - Wednesday, 20 January 2010, 07:28 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
When my eee 1000he wakes up from sleeping (suspend to ram) I lose my wireless connection and it doesn't return until I "sudo modprobe -r ath9k && sudo modprobe ath9k".

I use WICD but it also happens with networkmanager suggesting it is kernel related.


Additional info:
* kernel: linux-2.6.31-ARCH (each version of 2.6.31 so far)

Steps to reproduce:
Put eee 1000he (don't know of any other pc's) to sleep (for me, close the lid) and wake it up again (I hit space).
This task depends upon

Closed by  Allan McRae (Allan)
Wednesday, 20 January 2010, 07:28 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in 2.6.32
Comment by Freek (teek) - Wednesday, 18 November 2009, 11:43 GMT
Some more info:
This was never a problem with previous kernels (before 2.6.31).
Comment by Gerardo Exequiel Pozzi (djgera) - Wednesday, 18 November 2009, 14:05 GMT
  • Field changed: Summary (ath9k wlan loses connection after standby (suspend to ram) until reloading module → [kernel26] ath9k wlan loses connection after standby (suspend to ram) until reloading module)
  • Field changed: Status (Unconfirmed → Waiting on Response)
  • Field changed: Category (Packages: Core → Upstream Bugs)
  • Task assigned to Thomas Bächler (brain0), Tobias Powalowski (tpowa)
Please report to upstream but I think that this is very related to this already reported task  FS#16413  and  FS#16138 
Comment by Freek (teek) - Wednesday, 18 November 2009, 14:13 GMT
Looks like it yes, you know what would be neat, a report to upstream button in this system here :) reporting upstream really requires a lot of accounts and time to figure things out.
Comment by Thomas Bächler (brain0) - Wednesday, 18 November 2009, 14:31 GMT
First thing to do in these cases is compiling and installing the latest compat-wireless. If everything works there, then the problem has been fixed upstream and will likely be fixed automatically in the future. Until then, you can use compat-wireless and everyone is happy. If it doesn't work, then you can still report to the linux-wireless people.

Furthermore, there is a valid workaround: unload the module before suspend, load it after resume - this should be easily possible by tweaking the pm-utils configuration.
Comment by Freek (teek) - Wednesday, 18 November 2009, 14:48 GMT
True, I'll wait this one out, I work on this machine don't want to much hassle/compiling/tweaking (for now), the thing works I just "sudo modprobe -r ath9k && sudo modprobe ath9k" every time.
Comment by Freek (teek) - Monday, 18 January 2010, 11:21 GMT
BTW, 2.6.32 solves this problem for me... But I have a two new ones:
http://www.linuxquestions.org/questions/linux-general-1/arch-linux-over-time-screen-jitter-then-black-screen-782450/
and:
http://bugs.archlinux.org/task/17863?project=1&opened=3787

Seems 2.6.32 is also not treating me very well ;) But thats not for here :)
Anyways, thanks for the support! On to 2.6.33!

Loading...