From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Ian Molton <ian@mnementh.co.uk>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: Franky Lin <franky.lin@broadcom.com>,
Hante Meuleman <hante.meuleman@broadcom.com>
Subject: Re: BUG: brcmfmac: add firmware feature detection for gscan feature breaks 43430a1
Date: Tue, 18 Jul 2017 21:49:24 +0200 [thread overview]
Message-ID: <90ba4777-dedc-1a4f-c9c5-fca58106b754@broadcom.com> (raw)
In-Reply-To: <f3b1c2a3-c2f0-2f1c-c3f6-dbcc78246dc7@mnementh.co.uk>
On 18-07-17 00:10, Ian Molton wrote:
> Hi Arend,
>
> This is all there is in the forensics file, hope its of some use.
>
> # cat /sys/kernel/debug/brcmfmac/mmc1\:0001\:1/forensics
> Enter
> hndarm_armr addr: 0x18003000, cr4_idx: 0
> 000000.000
> RTE (SDIO-CDC) 7.45.41.26 (r640327) on BCM43430 r1 @ 37.4/81.0/81.0MHz
> 000000.001 sdpcmdcdc0: Broadcom SDPCMD CDC driver
> 000000.005 reclaim section 0: Returned 47716 bytes to the heap
> 000000.007 wlc_bmac_info_init: host_enab 1
> 000000.025 wl0: Broadcom BCM43430 802.11 Wireless Controller 7.45.41.26
> (r640327)
> 000000.026 TCAM: 256 used: 179 exceed:0
> 000000.027 reclaim section 1: Returned 81268 bytes to the heap
You probably guessed it, but this does not show anything useful. The
behavior suggested a firmware crash, but that does not seem to be
happening. Maybe it is the SDIO core driver on the firmware side which
is in la-la land.
Regards,
Arend
prev parent reply other threads:[~2017-07-18 19:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-17 17:50 BUG: brcmfmac: add firmware feature detection for gscan feature breaks 43430a1 Ian Molton
2017-07-17 18:31 ` Ian Molton
2017-07-17 19:53 ` Arend van Spriel
2017-07-17 20:13 ` Ian Molton
2017-07-17 20:36 ` Arend van Spriel
2017-07-17 20:41 ` Ian Molton
2017-07-17 21:31 ` Arend van Spriel
2017-07-17 22:02 ` Ian Molton
2017-07-17 22:10 ` Ian Molton
2017-07-18 19:49 ` Arend van Spriel [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=90ba4777-dedc-1a4f-c9c5-fca58106b754@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=ian@mnementh.co.uk \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).