From: Aaron Blair <aaron@aaronpb.me>
To: Arend Van Spriel <arend.vanspriel@broadcom.com>
Cc: 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>,
"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 22:11:57 +0000 [thread overview]
Message-ID: <20190213221219.umjtvsx5aaguqgmj@datkip> (raw)
In-Reply-To: <43fcfb23-9c35-cdf4-18ea-69212612c460@broadcom.com>
[-- Attachment #1: Type: text/plain, Size: 563 bytes --]
19-02-13 23:01:46 Arend Van Spriel:
>[...]
>The "reserve space" issue has been reported before although I have not
>looking into it yet.
No worries, the only reason I included it is that it seems to appear as soon as traffic starts to fail, which then prompts me to `rmmod brcmfmac`, which triggers the oops.
>[...]
>I will look into the NULL pointer access.
Great news. Please let me know if you require me to gather any more information.
Thank you.
--
- Aaron
PGP Key: 0x136159E6
https://pgp.mit.edu/pks/lookup?op=get&search=0x0B551238136159E6
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-02-13 22:12 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 [this message]
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=20190213221219.umjtvsx5aaguqgmj@datkip \
--to=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).