* Reizer, Eyal <eyalr@xxxxxx> [180603 06:07]: > I have noticed the following recovery a couple of times on my setup when the board was > just sitting for a long time with just pings > It starts with a firmware recovery started from the interrupt handler but the recovery fails Sounds like the recovery needs some more work :) > leaving the sdio stuck. > At this stage the only way to get out of it is unload/load of the driver modules. > Have you seen this on your side as well? Hmm I don't think I've seen this one yet. > 64 bytes from 192.168.100.1: seq=32772 ttl=64 time=9.644 ms > 64 bytes from 192.168.100.1: seq=32773 ttl=64 time=9.572 ms > 64 bytes from 192.168.100.1: seq=32774 ttl=64 time=10.974 ms > 64 bytes from 192.168.100.1: seq=32775 ttl=64 time=9.618 ms > [127899.040526] wlcore: ERROR SW watchdog interrupt received! starting recovery. Do you know what does the SW watchdog means here? Does it mean the interrupt did not get delivered to wlcore? Or a spurious IRQ to wlcore? Or a timeout waiting for the ELP wake interrupt? Regards, Tony
