Other Parts Discussed in Thread: AM4378, , WL1271
Hi,
We are using AM4378 with Wl1837MOD Solution. We are running AP + Mesh Dual Mode.
Linux : 4.19.59-g5f8c1c6121
PHY firmware version: Rev 8.2.0.0.243
firmware booted (Rev 8.9.0.0.81)
When we are changing Mesh Configuration in run time. We are using WpaSupplicant to Disable & Enable Mesh Configuration. But when we are doing this, we are getting some issues. Please see below 2 issues:
1. When following crash is happening, Mesh interface is not responding & mesh network is getting broken.
385.119862] ------------[ cut here ]------------
[ 385.124988] WARNING: CPU: 0 PID: 370 at drivers/net/wireless/ti/wlcore/main.c:808 wl12xx_queue_recovery_work+0x68/0x6c [wlcore]
[ 385.141504] Modules linked in: bridge stp llc wl18xx wlcore mac80211 xhci_plat_hcd xhci_hcd pru_rproc irq_pruss_intc cfg80211 pruss dwc3 udc
_core ti_am335x_adc pm33xx omap_des omap_aes_driver des_generic crypto_engine omap_crypto pruss_soc_bus omap_sham ti_emif_sram dwc3_omap wlcore
_sdio pixcir_i2c_ts snd_soc_tlv320aic3x wkup_m3_ipc phy_omap_usb2 wkup_m3_rproc remoteproc rtc_omap ti_am335x_tscadc omap_wdt sch_fq_codel
[ 385.182463] CPU: 0 PID: 370 Comm: wpa_supplicant Not tainted 4.19.59-g5f8c1c6121 #1
[ 385.192156] Hardware name: Generic AM43 (Flattened Device Tree)
[ 385.199734] Backtrace:
[ 385.202462] [<c010cb60>] (dump_backtrace) from [<c010ced0>] (show_stack+0x18/0x1c)
[ 385.211787] r7:00000009 r6:00000000 r5:bf2d8194 r4:00000000
[ 385.218751] [<c010ceb8>] (show_stack) from [<c09a48f4>] (dump_stack+0x24/0x28)
[ 385.227402] [<c09a48d0>] (dump_stack) from [<c012d3a8>] (__warn+0xe0/0xf8)
[ 385.234326] [<c012d2c8>] (__warn) from [<c012d408>] (warn_slowpath_null+0x48/0x50)
[ 385.243577] r9:0020c498 r8:0001fffc r7:c0e16720 r6:bf2c269c r5:00000328 r4:bf2d8194
[ 385.252899] [<c012d3c0>] (warn_slowpath_null) from [<bf2c269c>] (wl12xx_queue_recovery_work+0x68/0x6c [wlcore])
[ 385.264493] r6:00000074 r5:c0c7a2c4 r4:db854d20
[ 385.270621] [<bf2c2634>] (wl12xx_queue_recovery_work [wlcore]) from [<bf2c570c>] (wlcore_cmd_send_failsafe+0x18c/0x50c [wlcore])
[ 385.283626] r5:c0c7a2c4 r4:db854d20
[ 385.288754] [<bf2c5580>] (wlcore_cmd_send_failsafe [wlcore]) from [<bf2c6dfc>] (wl12xx_cmd_role_stop_ap+0x84/0xdc [wlcore])
[ 385.301374] r10:00000000 r9:d9c3ccd8 r8:bf2dfd00 r7:db854d20 r6:00000000 r5:d9681d00
[ 385.310429] r4:d9c3ce00
[ 385.313309] [<bf2c6d78>] (wl12xx_cmd_role_stop_ap [wlcore]) from [<bf2c03c8>] (wl1271_op_bss_info_changed+0xb88/0xed8 [wlcore])
[ 387.168612] ieee80211 phy0: Hardware restart was requested
[ 387.572584] wlcore: PHY firmware version: Rev 8.2.0.0.243
[ 387.769990] wlcore: firmware booted (Rev 8.9.0.0.81)
[ 387.843406] IPv6: ADDRCONF(NETDEV_UP): mesh02: link is not ready
2. When following crash is happening, Hotspot clients are getting disconnected but mesh network is sustained
root@am437x-evm:~# [ 109.500852] wlcore: down
[ 109.534792] IPv6: ADDRCONF(NETDEV_UP): mesh02: link is not ready
[ 109.541933] netlink: 'wpa_supplicant': attribute type 7 has an invalid length.
[ 109.565065] IPv6: ADDRCONF(NETDEV_CHANGE): mesh02: link becomes ready
[ 110.630065] wlcore: ERROR SW watchdog interrupt received! starting recovery.
[ 110.637241] ------------[ cut here ]------------
[ 110.642400] WARNING: CPU: 0 PID: 313 at drivers/net/wireless/ti/wlcore/main.c:808 wl12xx_queue_recovery_work+0x68/0x6c [wlcore]
[ 110.654054] Modules linked in: bridge stp llc wl18xx wlcore mac80211 xhci_plat_hcd xhci_hcd pru_rproc irq_pruss_intc cfg80211 dwc3 pruss udc
_core ti_am335x_adc pm33xx omap_des omap_aes_driver des_generic pruss_soc_bus crypto_engine omap_sham omap_crypto ti_emif_sram dwc3_omap snd_so
c_tlv320aic3x pixcir_i2c_ts wlcore_sdio wkup_m3_ipc wkup_m3_rproc phy_omap_usb2 remoteproc rtc_omap ti_am335x_tscadc omap_wdt sch_fq_codel
[ 110.691547] CPU: 0 PID: 313 Comm: irq/102-wl18xx Not tainted 4.19.59-g5f8c1c6121 #1
[ 110.699284] Hardware name: Generic AM43 (Flattened Device Tree)
[ 110.705273] Backtrace:
[ 110.707785] [<c010cb60>] (dump_backtrace) from [<c010ced0>] (show_stack+0x18/0x1c)
[ 110.715452] r7:00000009 r6:00000000 r5:bf2cf194 r4:00000000
[ 110.721181] [<c010ceb8>] (show_stack) from [<c09a48f4>] (dump_stack+0x24/0x28)
[ 110.728552] [<c09a48d0>] (dump_stack) from [<c012d3a8>] (__warn+0xe0/0xf8)
[ 110.735538] [<c012d2c8>] (__warn) from [<c012d408>] (warn_slowpath_null+0x48/0x50)
[ 110.743170] r9:00000000 r8:00000001 r7:c0172d64 r6:bf2b969c r5:00000328 r4:bf2cf194
[ 110.751250] [<c012d3c0>] (warn_slowpath_null) from [<bf2b969c>] (wl12xx_queue_recovery_work+0x68/0x6c [wlcore])
[ 110.761451] r6:db842ee8 r5:db842d58 r4:db842d20
[ 110.766473] [<bf2b9634>] (wl12xx_queue_recovery_work [wlcore]) from [<bf2b9f10>] (wlcore_irq+0x198/0x234 [wlcore])
[ 110.776932] r5:db842d58 r4:db842d20
root@am437x-evm:~# [ 111.302397] wlcore: PHY firmware version: Rev 8.2.0.0.243
[ 111.369990] wlcore: firmware booted (Rev 8.9.0.0.81)
Looking to understand the root cause of the issue.
