From: Arend Van Spriel <arend.vanspriel@broadcom.com>
To: Aditya Garg <gargaditya08@live.com>, <devnull+j.jannau.net@kernel.org>
Cc: <asahi@lists.linux.dev>, <brcm80211-dev-list.pdl@broadcom.com>,
<brcm80211@lists.linux.dev>, <j@jannau.net>, <kvalo@kernel.org>,
<linus.walleij@linaro.org>, <linux-kernel@vger.kernel.org>,
<linux-wireless@vger.kernel.org>, <marcan@marcan.st>,
<stable@vger.kernel.org>
Subject: Re: [PATCH] wifi: brcmfmac: cfg80211: Handle SSID based pmksa deletion
Date: Sun, 04 Aug 2024 07:15:27 +0200 [thread overview]
Message-ID: <1911bd06198.279b.9b12b7fc0a3841636cfb5e919b41b954@broadcom.com> (raw)
In-Reply-To: <MA0P287MB021718EE92FC809CB2BB0F82B8BD2@MA0P287MB0217.INDP287.PROD.OUTLOOK.COM>
On August 4, 2024 5:11:00 AM Aditya Garg <gargaditya08@live.com> wrote:
> Hi
>
> wpa_supplicant 2.11 broke Wi-Fi on T2 Macs as well, but this patch doesn't
> seem to be fixing Wi-Fi. Instead, it's breaking it even on older 2.10
> wpa_supplicant. Tested by a user on bcm4364b2 wifi chip with a WPA2-PSK
> [AES] network. dmesg output:
>
> However dmesg outputs more info
Not seeing much info in this output which indicate an issue.
> [ 5.852978] usbcore: registered new interface driver brcmfmac
> [ 5.853114] brcmfmac 0000:01:00.0: enabling device (0000 -> 0002)
> [ 5.992212] brcmfmac: brcmf_fw_alloc_request: using
> brcm/brcmfmac4364b2-pcie for chip BCM4364/3
> [ 5.993923] brcmfmac 0000:01:00.0: Direct firmware load for
> brcm/brcmfmac4364b2-pcie.apple,maui-HRPN-u-7.5-X0.bin failed with error -2
> [ 5.993968] brcmfmac 0000:01:00.0: Direct firmware load for
> brcm/brcmfmac4364b2-pcie.apple,maui-HRPN-u-7.5.bin failed with error -2
> [ 5.994004] brcmfmac 0000:01:00.0: Direct firmware load for
> brcm/brcmfmac4364b2-pcie.apple,maui-HRPN-u.bin failed with error -2
> [ 5.994041] brcmfmac 0000:01:00.0: Direct firmware load for
> brcm/brcmfmac4364b2-pcie.apple,maui-HRPN.bin failed with error -2
> [ 5.994076] brcmfmac 0000:01:00.0: Direct firmware load for
> brcm/brcmfmac4364b2-pcie.apple,maui-X0.bin failed with error -2
> [ 6.162830] Bluetooth: hci0: BCM: 'brcm/BCM.hcd'
> [ 6.796637] brcmfmac: brcmf_c_process_txcap_blob: TxCap blob found, loading
> [ 6.798396] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4364/3 wl0:
> Jul 10 2023 12:30:19 version 9.30.503.0.32.5.92 FWID 01-88a8883
This message means the firmware download was completed successfully.
> [ 6.885876] brcmfmac 0000:01:00.0 wlp1s0: renamed from wlan0
> [ 8.195243] ieee80211 phy0: brcmf_p2p_set_firmware: failed to update
> device address ret -52
> [ 8.196584] ieee80211 phy0: brcmf_p2p_create_p2pdev: set p2p_disc error
> [ 8.196588] ieee80211 phy0: brcmf_cfg80211_add_iface: add iface
> p2p-dev-wlp1s0 type 10 failed: err=-52
The creation of P2P device fails, but this only disables P2P aka
WiFi-Direct. A full kernel log would be helpful. Even better to build the
driver with CONFIG_BRCMDBG and load the driver with modparam
'debug=0x9416'. That will show a lot more driver logging which may provide
more clues.
Regards,
Arend
next prev parent reply other threads:[~2024-08-04 5:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-04 3:10 Aditya Garg
2024-08-04 5:15 ` Arend Van Spriel [this message]
2024-08-04 6:19 ` Janne Grunau
2024-08-04 6:26 ` Aditya Garg
2024-08-04 11:04 ` Arend Van Spriel
2024-08-04 11:37 ` Janne Grunau
2024-08-05 6:25 ` Janne Grunau
2025-02-09 19:10 ` Aditya Garg
-- strict thread matches above, loose matches on Subject: below --
2024-08-03 19:52 Janne Grunau via B4 Relay
2024-08-07 8:09 ` Neal Gompa
2024-08-08 8:25 ` Arend van Spriel
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=1911bd06198.279b.9b12b7fc0a3841636cfb5e919b41b954@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=asahi@lists.linux.dev \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=brcm80211@lists.linux.dev \
--cc=devnull+j.jannau.net@kernel.org \
--cc=gargaditya08@live.com \
--cc=j@jannau.net \
--cc=kvalo@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=marcan@marcan.st \
--cc=stable@vger.kernel.org \
/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
all inboxes | Powered by JetHome®