Return-path: Received: from [217.148.43.144] ([217.148.43.144]:50550 "EHLO mnementh.co.uk" rhost-flags-FAIL-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1751317AbdGQUNs (ORCPT ); Mon, 17 Jul 2017 16:13:48 -0400 Subject: Re: BUG: brcmfmac: add firmware feature detection for gscan feature breaks 43430a1 To: Arend van Spriel , "linux-wireless@vger.kernel.org" Cc: Franky Lin , Hante Meuleman References: <25c47ffe-af3e-fb85-ed5b-ff1987cfd93f@mnementh.co.uk> From: Ian Molton Message-ID: (sfid-20170717_221352_070366_68864EF3) Date: Mon, 17 Jul 2017 21:13:45 +0100 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Sender: linux-wireless-owner@vger.kernel.org List-ID: On 17/07/17 20:53, Arend van Spriel wrote: >> 2) The firmware is failing when asked to handle the new requiests, and >> is going to la-la land. > taken a wrong turn straight into la-la land. Doh! >> I have version wl0: Aug 29 2016 20:48:16 version 7.45.41.26 (r640327) >> FWID 01-4527cfab > Not so much newer firmware, but I used a different chip when > implementing the multi-scheduled scan patches. I tried some other > devices, but not the bcm4343{0,8}. Now as far as I can see over here the > brcmfmac43430-sdio.bin is not built with gscan support so it should just > return firmware errorcode, ie. -23. So it would be interesting to see > what firmware has to say. Can you load the driver with > ignore_probe_fail=1 and dump the forensics file in debugfs. I don't appear to get anything useful in debugfs. Where should I be looking? -Ian