From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Reizer, Eyal" Subject: RE: [EXTERNAL] Re: [RFT 3/6] wlcore: Add support for runtime PM Date: Tue, 5 Jun 2018 10:49:53 +0000 Message-ID: References: <20180529180605.73622-1-tony@atomide.com> <20180529180605.73622-4-tony@atomide.com> <20180531171420.GQ5705@atomide.com> <20180605042000.GA5738@atomide.com> <20180605104404.GD5738@atomide.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20180605104404.GD5738-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org> Content-Language: en-US Sender: linux-wireless-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Tony Lindgren Cc: Kalle Valo , KISHON VIJAY ABRAHAM , "Mishol, Guy" , Luca Coelho , "Hahn, Maital" , "Altshul, Maxim" , Shahar Patury , "linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , "linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" List-Id: linux-omap@vger.kernel.org >=20 > * Tony Lindgren [180605 04:22]: > > * Reizer, Eyal [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 dri= ver > 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=3D32772 ttl=3D64 time=3D9.644 ms > > > 64 bytes from 192.168.100.1: seq=3D32773 ttl=3D64 time=3D9.572 ms > > > 64 bytes from 192.168.100.1: seq=3D32774 ttl=3D64 time=3D10.974 ms > > > 64 bytes from 192.168.100.1: seq=3D32775 ttl=3D64 time=3D9.618 ms > > > [127899.040526] wlcore: ERROR SW watchdog interrupt received! startin= g > 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? >=20 > Also, can you check if patch "[RFT 7/6] wlcore: Make sure firmware is > initialized > in wl1271_op_add_interface()" already fixes this issue if you did not hav= e it > already applied? >=20 Sure will do. The firmware that showed this issue has some extra debugging = info Enabled in it and this may have been the cause of the recovery (Infernal lo= gging error). The fact that it didn't recover was the issue itself. I am now running with= the latest's=20 firmware 8.9.0.0.78 and will see if I can still replicate it. If I see it, I will try applying patch 7 and see if it helps. Right now I d= on't yet have It applied. Best Regard, Eyal