[FS#13] Ath9k AP stays up for connected clients but doesn't show in scan on new ones

LEDE Bugs lede-bugs at lists.infradead.org
Sat Jul 30 05:11:48 PDT 2016


The following task has a new comment added:

FS#13 - Ath9k AP stays up for connected clients but doesn't show in scan on new ones
User who did this - Borromini (Borromini)

----------
I have tried to replicate Bluse-Blue's observations. The TL-WR1043ND v1 here has been up for over 11 days, I don't know when wifi crapped out (it's at my brother's place) - but it typically does so fairly early after (re)booting.

A single 'wifi' command brought ath9k back up. I have no /sys/kernel/debug/ieee80211/phy0/ath9k/debug file (this is my own build off the vanilla LEDE main git tree).

Prior to running 'wifi', the ath9k interrupt was stuck on 2460703. After running it, the interrupt value (I'm not too familiar with this) steadily increases.

If there's anything else I can check - let me know. This was tested on Lede r1003.
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=13#comment155



More information about the lede-bugs mailing list