From: Arend Van Spriel <arend.vanspriel@broadcom.com>
To: Aaron Blair <aaron@aaronpb.me>,
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: Wed, 13 Feb 2019 14:01:46 +0100 [thread overview]
Message-ID: <43fcfb23-9c35-cdf4-18ea-69212612c460@broadcom.com> (raw)
In-Reply-To: <20190212055731.gxy3e3uulztketbf@datkip>
On 2/12/2019 6:57 AM, Aaron Blair wrote:
> I apologise if my report is lacking in detail; it is my first attempt at
> bug/issue reporting in the kernel.
> Please follow up if something is missing, or more detail/testing is
> required.
> It is certainly possible for me to provide more oops reports if
> required, as they generally surface at least once a day.
No apologies needed. I am generally happy with kernel log and short
context description.
> Thank you.
>
> [1.] Oops - Null pointer dereference in brcm80211/brcmfmac [BCM4350]
>
> [2.] Seemingly randomly, when connected to a wireless network, my laptop
> will begin failing to tx/rx data, and begin repeatedly reporting the
> following messages in the kernel ring buffer:
>
> ```
> [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)
> ```
The "reserve space" issue has been reported before although I have not
looking into it yet.
> 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.
>
> This does not appear to have a pattern, except that it usually happens
> at least once throughout a day of work.
>
> It has been happening at least since 4.20.4, but potentially earlier
> (this machine wasn't in heavy use before then).
I will look into the NULL pointer access.
Regards,
Arend
next prev parent reply other threads:[~2019-02-13 13:01 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 [this message]
2019-02-13 22:11 ` Aaron Blair
2019-02-14 12:25 ` Rafał Miłecki
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=43fcfb23-9c35-cdf4-18ea-69212612c460@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=aaron@aaronpb.me \
--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).