From: "Rafał Miłecki" <zajec5@gmail.com>
To: Aaron Blair <aaron@aaronpb.me>,
Arend van Spriel <arend.vanspriel@broadcom.com>,
Franky Lin <franky.lin@broadcom.com>,
Hante Meuleman <hante.meuleman@broadcom.com>,
Chi-Hsien Lin <chi-hsien.lin@cypress.com>,
Wright Feng <wright.feng@cypress.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"brcm80211-dev-list.pdl@broadcom.com"
<brcm80211-dev-list.pdl@broadcom.com>,
"brcm80211-dev-list@cypress.com" <brcm80211-dev-list@cypress.com>
Subject: Re: PROBLEM: Oops - Null pointer dereference in brcm80211/brcmfmac [BCM4350]
Date: Thu, 14 Feb 2019 13:25:08 +0100 [thread overview]
Message-ID: <6f2061fe-b734-1bb4-6608-db8c3fcd1363@gmail.com> (raw)
In-Reply-To: <20190212055731.gxy3e3uulztketbf@datkip>
On 12.02.2019 06:57, Aaron Blair wrote:
> [18990.872335] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -12
> [18990.872433] brcmfmac: brcmf_msgbuf_tx_ioctl: Failed to reserve space in commonring
> [18990.872439] brcmfmac: brcmf_cfg80211_get_tx_power: error (-12)
FullMAC firmware (the one running on card's ARM CPU) has crashed.
> Upon trying to rmmod && modload brcmfmac, I receive the oops dump included below, and am unable to continue using the wireless NIC until I reboot.
Interestingly I've experienced the same problem (for the first time)
last week. I started working on it but didn't achieve anything yet.
prev parent reply other threads:[~2019-02-14 12:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 5:57 PROBLEM: Oops - Null pointer dereference in brcm80211/brcmfmac [BCM4350] Aaron Blair
2019-02-13 13:01 ` Arend Van Spriel
2019-02-13 22:11 ` Aaron Blair
2019-02-14 12:25 ` Rafał Miłecki [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=6f2061fe-b734-1bb4-6608-db8c3fcd1363@gmail.com \
--to=zajec5@gmail.com \
--cc=aaron@aaronpb.me \
--cc=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=brcm80211-dev-list@cypress.com \
--cc=chi-hsien.lin@cypress.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=wright.feng@cypress.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).