From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: BCM4356 does not initalize after firmware update
Date: Fri, 15 Dec 2017 12:10:34 +0100 [thread overview]
Message-ID: <5A33ADAA.9060008@broadcom.com> (raw)
In-Reply-To: <20171215103215.GA2742@redhat.com>
On 12/15/2017 11:32 AM, Stanislaw Gruszka wrote:
> On Fri, Dec 15, 2017 at 10:58:10AM +0100, Arend van Spriel wrote:
>> On 12/14/2017 3:22 PM, Stanislaw Gruszka wrote:
>>> On Thu, Dec 14, 2017 at 10:13:29AM +0100, Arend van Spriel wrote:
>>>> The cur_etheraddr is the first piece of info we try to get from the
>>>> firmware. Could you build the driver with CONFIG_BRCMDBG and load
>>>> the module with 'debug=0x181416'.
>>>
>>> dmesg attached.
>>
>> So the firmware console output in the dmesg shows partial stack
>> trace which clearly means the firmware crashed.
>>
>> [ 2685.701602] brcmfmac: brcmf_pcie_isr_thread Enter 100
>> [ 2685.701613] brcmfmac: brcmf_pcie_handle_mb_data D2H_MB_DATA: 0x10000000
>> [ 2685.701634] brcmfmac: CONSOLE: 0d
>> [ 2685.701706] brcmfmac: CONSOLE: 000000.049 sp+ec 00184635
>> [ 2685.701778] brcmfmac: CONSOLE: 000000.049 sp+f4 00182ca7
>> [ 2685.701854] brcmfmac: CONSOLE: 000000.049 sp+100 000001df
>> [ 2685.701928] brcmfmac: CONSOLE: 000000.049 sp+140 0000823f
>> [ 2685.702003] brcmfmac: CONSOLE: 000000.049 sp+150 0018b8d9
>> [ 2687.642667] brcmfmac: brcmf_msgbuf_query_dcmd: Timeout on
>> response for query command
>> [ 2687.650464] brcmfmac: brcmf_fil_cmd_data Failed: BCME_NOTDOWN (-5)
>> [ 2687.650469] brcmfmac: brcmf_fil_iovar_data_get ifidx=0,
>> name=cur_etheraddr, len=6
>> [ 2687.650471] brcmutil: data
>> [ 2687.650475] 00000000: 00 00 00 00 00 00 ......
>> [ 2687.650479] brcmfmac: brcmf_c_preinit_dcmds: Retreiving
>> cur_etheraddr failed, -5
>>
>> I noticed you are not using a nvram file. Do you know if one was
>> orignally provided with the device?
>
> I think it was not. The device was bought and setup in Fedora/RHEL
> machine, which do not include any extra brcmfmac nvram file.
If the supplier of the device did not include such file it is probably
not needed.
When using the old (working) firmware could you dump revinfo file in
debugfs, ie.:
# cat /sys/kernel/debug/brcmfmac/0000:03:00.0/revinfo
Thanks,
Arend
next prev parent reply other threads:[~2017-12-15 11:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 16:12 BCM4356 does not initalize after firmware update Stanislaw Gruszka
2017-12-14 9:13 ` Arend van Spriel
2017-12-14 14:22 ` Stanislaw Gruszka
2017-12-15 9:58 ` Arend van Spriel
2017-12-15 10:32 ` Stanislaw Gruszka
2017-12-15 11:10 ` Arend van Spriel [this message]
2017-12-15 12:20 ` Stanislaw Gruszka
2017-12-19 11:36 ` Arend van Spriel
2017-12-19 12:23 ` Stanislaw Gruszka
2017-12-20 8:46 ` Arend van Spriel
2017-12-20 10:15 ` Stanislaw Gruszka
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=5A33ADAA.9060008@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=sgruszka@redhat.com \
/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).