linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Thu, 14 Dec 2017 10:13:29 +0100	[thread overview]
Message-ID: <5A3240B9.90007@broadcom.com> (raw)
In-Reply-To: <20171213161257.GB2811@redhat.com>

On 12/13/2017 5:12 PM, Stanislaw Gruszka wrote:
> Hi
>
> After firmware update, this device:
>
> [0280]: Broadcom Limited BCM4356 802.11ac Wireless Network Adapter [14e4:43ec] (rev 02)
>
> no longer initialize. With the firmware update I have:
>
> [  272.063814] brcmfmac: brcmf_fw_map_chip_to_name: using brcm/brcmfmac4356-pcie.bin for chip 0x004356(17238) rev 0x000002
> [  272.529582] brcmfmac 0000:03:00.0: irq 31 for MSI/MSI-X
> [  274.529476] brcmfmac: brcmf_msgbuf_query_dcmd: Timeout on response for query command
> [  274.537356] brcmfmac: brcmf_c_preinit_dcmds: Retreiving cur_etheraddr failed, -5
> [  274.544881] brcmfmac: brcmf_bus_started: failed: -5
> [  274.549854] brcmfmac: brcmf_pcie_attach_bus: dongle is not responding
>
> and no wlan device is created. With older version of the firmware I have:
>
> [   10.716878] brcmfmac: brcmf_fw_map_chip_to_name: using brcm/brcmfmac4356-pcie.bin for chip 0x004356(17238) rev 0x000002
> [   11.312875] brcmfmac 0000:03:00.0: irq 31 for MSI/MSI-X
> [   11.314735] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Oct 22 2015 06:16:41 version 7.35.180.119 (r594535) FWID 01-1a5c4016
> [   16.598211] brcmfmac: brcmf_p2p_create_p2pdev: set p2p_disc error
> [   16.604416] brcmfmac: brcmf_cfg80211_add_iface: add iface p2p-dev-wlp3s0 type 10 failed: err=-16
>
> and despite P2P errors, device works correctly.

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'.

Regards,
Arend

  reply	other threads:[~2017-12-14  9:13 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 [this message]
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
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=5A3240B9.90007@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).