WFX_FIRMWARE_VERSION = FW3.17.0
WFX_LINUX_DRIVER_VERSION = 2.14.1-public
Was doing some testing on various wifi-provisioning to various APs.
We are enabling a WFX AP on wlan1, then setting wlan0 to connect to our router AP. Then disabling wlan1.
I have added +ccflags-y = -DDEBUG to the makefile to add in debug mode to the wifi-driver. I do not have tracing enabled so I can't take HIF_traces. I can try and repo this with HIF_traces enabled if that would help?
We are seeing repeated wfx-spi spi0.0: hardware request START_SCAN (0x07) on vif 0 returned status 23 which I assume the scan has not completed and is busy. The error went away when I brought down the wlan1 AP. This doesn't happen regularly.
One suggestion from silabs to check for wfx driver lock up was to check cat /sys/kernel/debug/ieee80211/phy*/wfx/counters
But that doesn't appear to catch this issue.
What can I check to see if wfx is stuck in this state? I need a way to know how to restart the driver with any user input (IOT) device. I can't just restart the wfx driver whenever I see status 23 because that happens regularly, but usually just for a scan. Is there any problem leaving debug on?
dmesg(1).txt
Had the question on the silabs forum here as well, but haven't received any response back: https://community.silabs.com/s/question/0D5Vm00000KzrclKAB/repeated-wfxspi-spi00-hardware-request-startscan-0x07-on-vif-0-returned-status-23?language=en_US
WFX_FIRMWARE_VERSION = FW3.17.0
WFX_LINUX_DRIVER_VERSION = 2.14.1-public
Was doing some testing on various wifi-provisioning to various APs.
We are enabling a WFX AP on wlan1, then setting wlan0 to connect to our router AP. Then disabling wlan1.
I have added +ccflags-y = -DDEBUG to the makefile to add in debug mode to the wifi-driver. I do not have tracing enabled so I can't take HIF_traces. I can try and repo this with HIF_traces enabled if that would help?
We are seeing repeated wfx-spi spi0.0: hardware request START_SCAN (0x07) on vif 0 returned status 23 which I assume the scan has not completed and is busy. The error went away when I brought down the wlan1 AP. This doesn't happen regularly.
One suggestion from silabs to check for wfx driver lock up was to check cat /sys/kernel/debug/ieee80211/phy*/wfx/counters
But that doesn't appear to catch this issue.
What can I check to see if wfx is stuck in this state? I need a way to know how to restart the driver with any user input (IOT) device. I can't just restart the wfx driver whenever I see status 23 because that happens regularly, but usually just for a scan. Is there any problem leaving debug on?
dmesg(1).txt
Had the question on the silabs forum here as well, but haven't received any response back: https://community.silabs.com/s/question/0D5Vm00000KzrclKAB/repeated-wfxspi-spi00-hardware-request-startscan-0x07-on-vif-0-returned-status-23?language=en_US