ath9k: work around AR_CFG 0xdeadbeef chip hang
RFC 1/2 ath9k: work around AR_CFG 0xdeadbeef chip hang
From: Simon Wunderlich <[email protected]>
QCA 802.11n chips (especially AR9330/AR9340) sometimes end up in a state in which a read of AR_CFG always returns 0xdeadbeef. This should not happen when when the power_mode of the device is ATH9K_PM_AWAKE.
This problem is not yet detected by any other workaround in ath9k. No way is known to reproduce the problem easily.
---
This was discussed 4 years ago on the OpenWrt mailing list. The most relevant post is
https://lists.openwrt.org/pipermail/openwrt-devel/2012-September/016708.html
--- drivers/net/wireless/ath/ath9k/ath9k.h | 3 +++ drivers/net/wireless/ath/ath9k/debug.c | 1 + drivers/net/wireless/ath/ath9k/debug.h | 1 + drivers/net/wireless/ath/ath9k/init.c | 1 + drivers/net/wireless/ath/ath9k/link.c | 33 +++++++++++++++++++++++++++++++++ drivers/net/wireless/ath/ath9k/main.c | 4 ++++ 6 files changed, 43 insertions(+)
drivers/net/wireless/ath/ath9k/ath9k.h +3 -0
@@ -710,11 +710,13 @@ void ath9k_csa_update(struct ath_softc *sc);#define ATH_ANI_MAX_SKIP_COUNT 10#define ATH_PAPRD_TIMEOUT 100/* msecs */ #define ATH_PLL_WORK_INTERVAL 100 +#define ATH_HANG_WORK_INTERVAL 30000void ath_tx_complete_poll_work (struct work_struct *work);void ath_reset_work (struct work_struct *work);bool ath_hw_check (struct ath_softc *sc);void ath_hw_pll_work (struct work_struct *work); +void ath_hw_hang_work (struct work_struct *work);void ath_paprd_calibrate (struct work_struct *work);void ath_ani_calibrate (unsigned long data);void ath_start_ani (struct ath_softc *sc);
@@ -1014,6 +1016,7 @@ struct ath_softc {#endif struct delayed_work tx_complete_work;struct delayed_work hw_pll_work; +struct delayed_work hw_hang_work;struct timer_list sleep_timer;#ifdef CONFIG_ATH9K_BTCOEX_SUPPORT
drivers/net/wireless/ath/ath9k/debug.c +1 -0
@@ -767,6 +767,7 @@ static int read_file_reset(struct seq_file *file, void *data) [RESET_TYPE_CALIBRATION] = "Calibration error", [RESET_TX_DMA_ERROR] = "Tx DMA stop error", [RESET_RX_DMA_ERROR] = "Rx DMA stop error", + [RESET_TYPE_DEADBEEF] = "deadbeef hang", };int i;
drivers/net/wireless/ath/ath9k/debug.h +1 -0
@@ -52,6 +52,7 @@ enum ath_reset_type {RESET_TYPE_CALIBRATION ,RESET_TX_DMA_ERROR ,RESET_RX_DMA_ERROR , +RESET_TYPE_DEADBEEF , __RESET_TYPE_MAX };
drivers/net/wireless/ath/ath9k/init.c +1 -0
@@ -638,6 +638,7 @@ static int ath9k_init_softc(u16 devid, struct ath_softc *sc,INIT_WORK (&sc->hw_reset_work, ath_reset_work);INIT_WORK (&sc->paprd_work, ath_paprd_calibrate);INIT_DELAYED_WORK (&sc->hw_pll_work, ath_hw_pll_work); +INIT_DELAYED_WORK (&sc->hw_hang_work, ath_hw_hang_work);ath9k_init_channel_context (sc);
drivers/net/wireless/ath/ath9k/link.c +33 -0
@@ -138,6 +138,39 @@ void ath_hw_pll_work(struct work_struct *work) msecs_to_jiffies(ATH_PLL_WORK_INTERVAL)); } +static bool ath_hw_hang_deadbeef (struct ath_softc *sc) +{ +struct ath_common *common =ath9k_hw_common (sc->sc_ah); +u32 reg; + +/* check for stucked MAC */ +ath9k_ps_wakeup (sc); + reg =REG_READ (sc->sc_ah,AR_CFG ); +ath9k_ps_restore (sc); + +if (reg !=0xdeadbeef ) +return false; + +ath_dbg (common,RESET , +"0xdeadbeef hang is detected. Schedule chip reset\n" ); +ath9k_queue_reset (sc,RESET_TYPE_DEADBEEF ); + +return true; +} + +void ath_hw_hang_work (struct work_struct *work) +{ + struct ath_softc *sc = container_of(work, struct ath_softc, + hw_hang_work.work); + +if (ath_hw_hang_deadbeef (sc)) + goto requeue_worker; + +requeue_worker: +ieee80211_queue_delayed_work (sc->hw, &sc->hw_hang_work, +msecs_to_jiffies (ATH_HANG_WORK_INTERVAL )); +} +/* * PA Pre-distortion. */
drivers/net/wireless/ath/ath9k/main.c +4 -0
@@ -183,6 +183,7 @@ static void __ath_cancel_work(struct ath_softc *sc)cancel_work_sync (&sc->paprd_work);cancel_delayed_work_sync (&sc->tx_complete_work);cancel_delayed_work_sync (&sc->hw_pll_work); +cancel_delayed_work_sync (&sc->hw_hang_work);#ifdef CONFIG_ATH9K_BTCOEX_SUPPORT if (ath9k_hw_mci_is_enabled (sc->sc_ah))
@@ -204,6 +205,9 @@ void ath_restart_work(struct ath_softc *sc)ieee80211_queue_delayed_work (sc->hw, &sc->hw_pll_work,msecs_to_jiffies (ATH_PLL_WORK_INTERVAL )); +ieee80211_queue_delayed_work (sc->hw, &sc->hw_hang_work, +msecs_to_jiffies (ATH_HANG_WORK_INTERVAL )); +ath_start_ani (sc); }
Signature · 1 line
2.10.2
RFC 2/2 ath9k: Reset chip on potential deaf state
From: Simon Wunderlich <[email protected]>
The chip is switching seemingly random into a state which can be described as "deaf". No or nearly no interrupts are generated anymore for incoming packets. Existing links either break down after a while and new links will not be established.
The driver doesn't know if there is no other device available or if it ended up in an "deaf" state. Resetting the chip proactively avoids permanent problems in case the chip really was in its "deaf" state but maybe causes unnecessary resets in case it wasn't "deaf".
---
This problem was discovered in mesh setups. It was noticed that some nodes were not able to see their neighbors (mostly after running for a while) - even when those neighbors received data from them via IBSS. A simple iw dev wlan0 scan fixed the problem for them. But the problem seems to reappear after while(tm) in a large enough(tm) mesh.
This patch is a little bit obscure because it requires CONFIG_ATH9K_DEBUGFS to actually work. But there still seems to be potential interest in Freifunk communities or Freifunk meta-projects (e.g. freifunk-gluon). It is currently not known if it helps them but publishing this to allow them to test and play around with it will not hurt :)
--- drivers/net/wireless/ath/ath9k/ath9k.h | 3 +++ drivers/net/wireless/ath/ath9k/debug.c | 1 + drivers/net/wireless/ath/ath9k/debug.h | 1 + drivers/net/wireless/ath/ath9k/link.c | 45 ++++++++++++++++++++++++++++++++++ 4 files changed, 50 insertions(+)
drivers/net/wireless/ath/ath9k/ath9k.h +3 -0
@@ -996,6 +996,9 @@ struct ath_softc {short nbcnvifs;unsigned long ps_usecount; +unsigned long last_check_time; +u32 last_check_interrupts; +struct ath_rx rx;struct ath_tx tx;struct ath_beacon beacon;
drivers/net/wireless/ath/ath9k/debug.c +1 -0
@@ -768,6 +768,7 @@ static int read_file_reset(struct seq_file *file, void *data) [RESET_TX_DMA_ERROR] = "Tx DMA stop error", [RESET_RX_DMA_ERROR] = "Rx DMA stop error", [RESET_TYPE_DEADBEEF] = "deadbeef hang", + [RESET_TYPE_DEAF] = "deaf hang", };int i;
drivers/net/wireless/ath/ath9k/debug.h +1 -0
@@ -53,6 +53,7 @@ enum ath_reset_type {RESET_TX_DMA_ERROR ,RESET_RX_DMA_ERROR ,RESET_TYPE_DEADBEEF , +RESET_TYPE_DEAF , __RESET_TYPE_MAX };
drivers/net/wireless/ath/ath9k/link.c +45 -0
57 lines not on this page · raw message
Signature · 1 line
2.10.2
Valo
RFC 1/2 ath9k: work around AR_CFG 0xdeadbeef chip hang
In reply to Sven EckelmannQuoted 12 lines · Sven Eckelmann
From: Simon Wunderlich <[email protected]>
QCA 802.11n chips (especially AR9330/AR9340) sometimes end up in a state in which a read of
AR_CFGalways returns0xdeadbeef. This should not happen when when thepower_modeof the device isATH9K_PM_AWAKE.This problem is not yet detected by any other workaround in ath9k. No way is known to reproduce the problem easily.
Signed-off-by Simon Wunderlich <[email protected]>[sven.eckelmann at open-mesh.com: port to recent ath9k, add commit message]Signed-off-by Sven Eckelmann <[email protected]>
[...]
drivers/net/wireless/ath/ath9k/link.c void ath_hw_pll_work(struct work_struct *work) · line 172
Quoted 12 lines
drivers/net/wireless/ath/ath9k/link.c +12
-0+void ath_hw_hang_work (struct work_struct *work) +{ + struct ath_softc *sc = container_of(work, struct ath_softc, + hw_hang_work.work); + +if (ath_hw_hang_deadbeef (sc)) + goto requeue_worker; + +requeue_worker: +ieee80211_queue_delayed_work (sc->hw, &sc->hw_hang_work, +msecs_to_jiffies (ATH_HANG_WORK_INTERVAL )); +}
The goto doesn't make any sense, either me or the function is missing something :)
Signature · 1 line
Kalle Valo
RFC 1/2 ath9k: work around AR_CFG 0xdeadbeef chip hang
Quoted 17 lines · Kalle
Quoted 12 lines · Sven Eckelmann
From: Simon Wunderlich <[email protected]>
QCA 802.11n chips (especially AR9330/AR9340) sometimes end up in a state in which a read of
AR_CFGalways returns0xdeadbeef. This should not happen when when thepower_modeof the device isATH9K_PM_AWAKE.This problem is not yet detected by any other workaround in ath9k. No way is known to reproduce the problem easily.
Signed-off-by Simon Wunderlich <[email protected]>[sven.eckelmann at open-mesh.com: port to recent ath9k, add commit message]Signed-off-by Sven Eckelmann <[email protected]>[...]
Quoted 17 lines
drivers/net/wireless/ath/ath9k/link.c void ath_hw_pll_work(struct work_struct *work) · line 172
Quoted 12 lines
drivers/net/wireless/ath/ath9k/link.c +12
-0+void ath_hw_hang_work (struct work_struct *work) +{ + struct ath_softc *sc = container_of(work, struct ath_softc, + hw_hang_work.work); + +if (ath_hw_hang_deadbeef (sc)) + goto requeue_worker; + +requeue_worker: +ieee80211_queue_delayed_work (sc->hw, &sc->hw_hang_work, +msecs_to_jiffies (ATH_HANG_WORK_INTERVAL )); +}The goto doesn't make any sense, either me or the function is missing something :)
It is just for the next patch. And yes, could be done differently.
Kind regards,
Sven
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 801 bytes
Desc: This is a digitally signed message part.
Url : http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20161117/acc1b70e/attachment.pgp