From: Stefan Wahren <wahrenst@gmx.net>
To: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
Chen-Yu Tsai <wens@kernel.org>
Cc: linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
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>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
brcm80211-dev-list <brcm80211-dev-list@cypress.com>,
Johannes Berg <johannes.berg@intel.com>
Subject: Re: brcmfmac: Probing regression in Linux 5.3-rc1
Date: Mon, 29 Jul 2019 07:44:03 +0200 [thread overview]
Message-ID: <b28f81b7-f812-220f-dcf0-61dbfdce50b4@gmx.net> (raw)
In-Reply-To: <3daef629-8baf-3c5c-16a4-73d67604d1e5@gmx.net>
Hi,
Am 27.07.19 um 17:17 schrieb Stefan Wahren:
> Hi,
>
> Am 24.07.19 um 10:37 schrieb Nicolas Saenz Julienne:
>>>>> Does it fix the wifi issue too?
>>>> Well it works as long as I revert this: 901bb98918 ("nl80211: require and
>>>> validate vendor command policy"). Which has nothing to do with DMA anyways.
>>>>
>>>> Was this the issue you where seeing?
>>>>
>>>> [ 4.969679] WARNING: CPU: 2 PID: 21 at net/wireless/core.c:868
>>>> wiphy_register+0x8e8/0xbdc [cfg80211]
>>>> [...]
>>>> [ 4.969974] ieee80211 phy0: brcmf_cfg80211_attach: Could not register
>>>> wiphy device (-22)
>>> We're seeing this on different platforms (allwinner / rockchip / amlogic)
>>> with Broadcom WiFi chips. So it's unlikely to be related with anything in
>>> this series.
>>>
>>> I believe a fix for this has already been queued up:
>>>
>>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211.git/commit/?id=91046d6364afde646734c7ead1f649d253c386e9
>>
>> Thanks for pointing it out, it fixes the issue alright.
>>
> i cannot confirm. I still need to revert Johannes' commit "nl80211:
> require and validate vendor command policy" to get brcmfmac probing on
> Raspberry Pi 3B+ and 4B.
>
> The commit "nl80211: fix VENDOR_CMD_RAW_DATA" didn't fix the probing
> issue (see warning above).
i rebased my series on top of Linux 5.3-rc2 and issue disappeared. I
assume the commit "wireless: fix nl80211 vendor commands" is also required.
Sorry, for the noise.
>
> Regards
> Stefan
>
>
prev parent reply other threads:[~2019-07-29 5:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1563774880-8061-1-git-send-email-wahrenst@gmx.net>
[not found] ` <96113adb5fcab9c2f4bb5fa82b84ff5f9c07fd07.camel@suse.de>
[not found] ` <bc650090-db86-ccac-01dc-23f08ad7b19b@gmx.net>
[not found] ` <20190723093442.GA27239@lst.de>
[not found] ` <04c5eaa03f3a124dbbce6186e11e19acc4539cc8.camel@suse.de>
[not found] ` <b15509d6-bc2e-3d06-0eea-943e6e456d62@gmx.net>
[not found] ` <5f9b11f54c66fd0487837f7e58af3adf7f86635f.camel@suse.de>
[not found] ` <CAGb2v66-o23CW5iH9Bn1aELymPSiKrA43eJd2q6EZ7iubcogaw@mail.gmail.com>
[not found] ` <ab7af8537ebcbc7a7bdf04d2c06152ba6821b333.camel@suse.de>
2019-07-27 15:17 ` brcmfmac: Probing regression in Linux 5.3-rc1 Stefan Wahren
2019-07-29 5:44 ` Stefan Wahren [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=b28f81b7-f812-220f-dcf0-61dbfdce50b4@gmx.net \
--to=wahrenst@gmx.net \
--cc=arend.vanspriel@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=johannes.berg@intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nsaenzjulienne@suse.de \
--cc=wens@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).