Got regular crashes of the wl18xx module...
Closed this issue · 2 comments
[165691.002707] wlan0: AP f4:06:8d:31:37:a0 changed bandwidth, new config is 2462 MHz, width 1 (2462/0 MHz)
[165796.106234] wlcore: ERROR SW watchdog interrupt received! starting recovery.
[165796.113469] ------------[ cut here ]------------
[165796.118544] WARNING: CPU: 0 PID: 181 at drivers/net/wireless/ti/wlcore/main.c:796 wl12xx_queue_recovery_work.part.10+0x68/0x6c [wlcore]
[165796.130907] Modules linked in: nfnetlink_queue nfnetlink_log nfnetlink aes_arm_bs crypto_simd cryptd wl18xx wlcore mac80211 cfg80211 wlcore_sdio dht11 uio_pdrv_genirq uio evdev
[165796.146911] CPU: 0 PID: 181 Comm: irq/64-wl18xx Tainted: G W 4.14.56 #1
[165796.154776] Hardware name: Generic AM33XX (Flattened Device Tree)
[165796.161023] [] (unwind_backtrace) from [] (show_stack+0x20/0x24)
[165796.168900] [] (show_stack) from [] (dump_stack+0x8c/0xa0)
[165796.176251] [] (dump_stack) from [] (__warn+0xf8/0x110)
[165796.183338] [] (__warn) from [] (warn_slowpath_null+0x30/0x38)
[165796.191183] [] (warn_slowpath_null) from [] (wl12xx_queue_recovery_work.part.10+0x68/0x6c [wlcore])
[165796.202324] [] (wl12xx_queue_recovery_work.part.10 [wlcore]) from [] (wlcore_irq+0x174/0x190 [wlcore])
[165796.213618] [] (wlcore_irq [wlcore]) from [] (irq_thread_fn+0x2c/0x64)
[165796.222016] [] (irq_thread_fn) from [] (irq_thread+0x170/0x234)
[165796.229808] [] (irq_thread) from [] (kthread+0x144/0x174)
[165796.237079] [] (kthread) from [] (ret_from_fork+0x14/0x2c)
[165796.244498] ---[ end trace ce00e780572c5cd8 ]---
[165796.252864] wlcore: Hardware recovery in progress. FW ver: Rev 8.9.0.0.76
[165796.260546] wlcore: pc: 0x116424, hint_sts: 0x00000000 count: 136
[165796.267898] wlcore: down
[165796.271955] ieee80211 phy0: Hardware restart was requested
[165796.709632] wlcore: PHY firmware version: Rev 8.2.0.0.240
[165796.761652] wlcore: firmware booted (Rev 8.9.0.0.76)
@ledav-net which kernel is this? Can you update to the latest image at https://beagleboard.org/latest-images, namely, the 2018-10-07 image?
Hi jadonk, thanks for your reply and sorry for the delay...
It was fixed in the meantime so, I'm closing the issue. Thx anyway :)