During mesh PS operation power consumption rises to 120mA and stays at that level until ifdown (mesh leave + join does not reset it to normal state)
(~55mA is the normal current in PS mode with no activity for TL-WN721)
Hardware issue? Does the hardware expect certain managed-mode specific events (TSF out of range, AP beacon, ...)?
How to reproduce:
use kernel from ft-powersave and iw from ft-powersave
use a ath9k_htc device
setup network
iw phy phy0 interface add mesh0 type mp
ifconfig mesh0 #IP# up
iw mesh0 mesh join test
a) single node
iw mesh0 set mesh_param mesh_power_mode light
b) with mesh peer
iw mesh0 station set #peer MAC# mesh_power_mode light
The time to failure varies between seconds to 1-2 minutes.
Effect:
No obvious debug output with all ath9k debugs enabled.
Reading AR_RTC_STATUS before and after
REG_CLR_BIT(ah, AR_RTC_FORCE_WAKE, AR_RTC_FORCE_WAKE_EN);
reveals the following
Issue:
During mesh PS operation power consumption rises to 120mA and stays at that level until ifdown (mesh leave + join does not reset it to normal state) (~55mA is the normal current in PS mode with no activity for TL-WN721)
Hardware issue? Does the hardware expect certain managed-mode specific events (TSF out of range, AP beacon, ...)?
How to reproduce:
setup network
a) single node
b) with mesh peer
The time to failure varies between seconds to 1-2 minutes.
Effect:
No obvious debug output with all ath9k debugs enabled.
Reading AR_RTC_STATUS before and after REG_CLR_BIT(ah, AR_RTC_FORCE_WAKE, AR_RTC_FORCE_WAKE_EN); reveals the following
normal:
[ 301.655141] ath: phy0: AR_RTC_STATUS before: 02 [ 301.661079] ath: phy0: AR_RTC_STATUS after: 04
when being stuck it changes to:
[ 302.677066] ath: phy0: AR_RTC_STATUS before: 02 [ 302.683085] ath: phy0: AR_RTC_STATUS after: 02
To easier follow the status use following debug prints.
Already tested: