From: Aditya Garg <gargaditya08@live.com>
To: Janne Grunau <j@jannau.net>
Cc: "arend.vanspriel@broadcom.com" <arend.vanspriel@broadcom.com>,
"devnull+j.jannau.net@kernel.org"
<devnull+j.jannau.net@kernel.org>,
"asahi@lists.linux.dev" <asahi@lists.linux.dev>,
"brcm80211-dev-list.pdl@broadcom.com"
<brcm80211-dev-list.pdl@broadcom.com>,
"brcm80211@lists.linux.dev" <brcm80211@lists.linux.dev>,
"kvalo@kernel.org" <kvalo@kernel.org>,
"linus.walleij@linaro.org" <linus.walleij@linaro.org>,
LKML <linux-kernel@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Hector Martin <marcan@marcan.st>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] wifi: brcmfmac: cfg80211: Handle SSID based pmksa deletion
Date: Sun, 9 Feb 2025 19:10:59 +0000 [thread overview]
Message-ID: <PN3PR01MB96157F71FB82CF36F3146ABBB8F32@PN3PR01MB9615.INDPRD01.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <9ed78539-35ca-4643-9a38-ac2c0379f395@app.fastmail.com>
Hi Arend, Janne
Even till this date, the issue still persists with wpa_supplicant. So, will we have to use brcmfmac.feature_disable=0x82000 forever (not very ideal) or do we have another plan in mind?
> On 5 Aug 2024, at 11:56 AM, Janne Grunau <j@jannau.net> wrote:
>
> Hej,
>
>> On Sun, Aug 4, 2024, at 13:37, Janne Grunau wrote:
>>> On Sun, Aug 4, 2024, at 13:04, Arend Van Spriel wrote:
>>> On August 4, 2024 8:27:04 AM Aditya Garg <gargaditya08@live.com> wrote:
>>>>
>>>> WPA3 is broken on T2 Macs (atleast on 4364) for a long time. I was
>>>> under the impression brcmfmac doesn't support it.
>>>>
>>>> Anyways, I've asked a fedora user to compile a kernel with
>>>> CONFIG_BRCMDBG.
>>>>
>>>> If you want logs without it, look over here:
>>>> https://pastebin.com/fnhH30JA
>>>
>>> Not sure what to make of this. The interface comes up without any
>>> obvious error and then another interface is created by another
>>> driver:
>>
>> I've bisected the authentication timeouts for WPA2-PSK and WPA3-SAE
>> (and probably every other authentication method) down to
>>
>> https://w1.fi/cgit/hostap/commit/?id=41638606054a09867fe3f9a2b5523aa4678cbfa5
>
> this is reported upstream in
> http://lists.infradead.org/pipermail/hostap/2024-August/042893.html
>
> Disabling offloading in brcmfmac with "brcmfmac.feature_disable=0x82000"
> on the kernel command line works around both the kernel and
> wpa_supplicant issue.
>
> HTH,
> Janne
next prev parent reply other threads:[~2025-02-09 19:11 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
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 [this message]
-- 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=PN3PR01MB96157F71FB82CF36F3146ABBB8F32@PN3PR01MB9615.INDPRD01.PROD.OUTLOOK.COM \
--to=gargaditya08@live.com \
--cc=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=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®