This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

WL1835MOD: wlcore: ERROR Tx stuck (in FW) for 5000 ms. Starting recovery core dump

Part Number: WL1835MOD

https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/830024/wl1835mod-wlcore-error-tx-stuck-in-fw-for-5000-ms-starting-recovery

We are using WL1835MODGB AM335x chip set. We are seeing similar observation even after applying driver patches as recommended in the above thread.

our FW version is 8.9.0.0.79

We didn't made any changes except the patches mentioned in the thread above.

kernel version:4.9.31-gf9f6f0db2d

Coredump:

Dec 6 11:13:44 ml5 user.err kernel: [ 4964.399871] wlcore: ERROR Tx stuck (in FW) for 5000 ms. Starting recovery
Dec 6 11:13:44 ml5 user.warn kernel: [ 4964.399960] ------------[ cut here ]------------
Dec 6 11:13:44 ml5 user.warn kernel: [ 4964.400230] WARNING: CPU: 0 PID: 24173 at drivers/net/wireless/ti/wlcore/main.c:796 wl12xx_queue_recovery_work.part.10+0x6c/0x70 [wlcore]
Dec 6 11:13:44 ml5 user.warn kernel: [ 4964.400296] Modules linked in: wl12xx ctr ccm xt_tcpudp xt_state ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_limit iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat qcserial(O) nf_conntrack op
Dec 6 11:13:44 ml5 user.warn kernel: [ 4964.400854] libcomposite configfs udc_core usb_common
Dec 6 11:13:44 ml5 user.warn kernel: [ 4964.400907] CPU: 0 PID: 24173 Comm: kworker/u2:4 Tainted: G W O 4.9.31-gf9f6f0db2d #29
Dec 6 11:13:44 ml5 user.warn kernel: [ 4964.400963] Hardware name: Generic AM33XX (Flattened Device Tree)
Dec 6 11:13:44 ml5 user.warn kernel: [ 4964.401082] Workqueue: phy0 wl12xx_tx_watchdog_work [wlcore]
Dec 6 11:13:44 ml5 user.warn kernel: [ 4964.401120] Backtrace:
Dec 6 11:13:44 ml5 user.warn kernel: [ 4964.401182] [<c010b6c8>] (dump_backtrace) from [<c010b984>] (show_stack+0x18/0x1c)
Dec 6 11:13:44 ml5 user.warn kernel: [ 4964.401241] r7:00000009 r6:00000000 r5:bf249700 r4:00000000
Dec 6 11:13:44 ml5 user.warn kernel: [ 4964.401299] [<c010b96c>] (show_stack) from [<c03d5fa4>] (dump_stack+0x24/0x28)
Dec 6 11:13:44 ml5 user.warn kernel: [ 4964.401368] [<c03d5f80>] (dump_stack) from [<c012b03c>] (__warn+0xe8/0x100)
Dec 6 11:13:44 ml5 user.warn kernel: [ 4964.401417] [<c012af54>] (__warn) from [<c012b10c>] (warn_slowpath_null+0x28/0x30)
Dec 6 11:13:44 ml5 user.warn kernel: [ 4964.401478] r9:00000003 r8:cf002800 r7:cf46cce0 r6:cf46cce8 r5:cf46cd18 r4:cf46cce0
Dec 6 11:13:44 ml5 user.warn kernel: [ 4964.401612] [<c012b0e4>] (warn_slowpath_null) from [<bf232d00>] (wl12xx_queue_recovery_work.part.10+0x6c/0x70 [wlcore])
Dec 6 11:13:44 ml5 user.warn kernel: [ 4964.401820] [<bf232c94>] (wl12xx_queue_recovery_work.part.10 [wlcore]) from [<bf232e28>] (wl12xx_tx_watchdog_work+0x124/0x128 [wlcore])
Dec 6 11:13:44 ml5 user.warn kernel: [ 4964.401886] r5:cf46cd18 r4:cf46d988
Dec 6 11:13:44 ml5 user.warn kernel: [ 4964.401999] [<bf232d04>] (wl12xx_tx_watchdog_work [wlcore]) from [<c0141eb4>] (process_one_work+0x144/0x41c)
Dec 6 11:13:44 ml5 user.warn kernel: [ 4964.402968] r7:cf476b00 r6:00000000 r5:ca978800 r4:cf46d988
Dec 6 11:13:44 ml5 user.warn kernel: [ 4964.403022] [<c0141d70>] (process_one_work) from [<c01421f8>] (worker_thread+0x6c/0x618)
Dec 6 11:13:44 ml5 user.warn kernel: [ 4964.403086] r10:ca978800 r9:00000088 r8:cf002814 r7:c0c14d40 r6:ca978818 r5:c8382000
Dec 6 11:13:44 ml5 user.warn kernel: [ 4964.403139] r4:cf002800
Dec 6 11:13:44 ml5 user.warn kernel: [ 4964.403181] [<c014218c>] (worker_thread) from [<c0147de8>] (kthread+0xf8/0x110)
Dec 6 11:13:44 ml5 user.warn kernel: [ 4964.403241] r10:00000000 r9:00000000 r8:c014218c r7:ca978800 r6:c8382000 r5:c839b6c0
Dec 6 11:13:44 ml5 user.warn kernel: [ 4964.403293] r4:00000000
Dec 6 11:13:44 ml5 user.warn kernel: [ 4964.403332] [<c0147cf0>] (kthread) from [<c0107c38>] (ret_from_fork+0x14/0x3c)
Dec 6 11:13:44 ml5 user.warn kernel: [ 4964.403389] r8:00000000 r7:00000000 r6:00000000 r5:c0147cf0 r4:c839b6c0
Dec 6 11:13:44 ml5 user.warn kernel: [ 4964.403428] ---[ end trace f31c1af84a64e9bd ]---
Dec 6 11:13:44 ml5 user.info kernel: [ 4964.403516] wlcore: Hardware recovery in progress. FW ver: Rev 8.9.0.0.79
Dec 6 11:13:44 ml5 user.info kernel: [ 4964.404045] wlcore: pc: 0x0, hint_sts: 0x00000000 count: 2
Dec 6 11:13:44 ml5 user.info kernel: [ 4964.404397] wlcore: down
Dec 6 11:13:44 ml5 user.info kernel: [ 4964.404440] wlcore: down
Dec 6 11:13:44 ml5 user.info kernel: [ 4964.404473] wlcore: down
Dec 6 11:13:44 ml5 user.info kernel: [ 4964.405865] ieee80211 phy0: Hardware restart was requested
Dec 6 11:13:45 ml5 user.info kernel: [ 4964.961088] wlcore: PHY firmware version: Rev 8.2.0.0.242
Dec 6 11:13:45 ml5 user.info kernel: [ 4965.276252] wlcore: firmware booted (Rev 8.9.0.0.79) 

Thanks,

Naresh