From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Aditya Garg <gargaditya08@live.com>,
"arend.vanspriel@broadcom.com" <arend.vanspriel@broadcom.com>,
"aspriel@gmail.com" <aspriel@gmail.com>,
"ranky.lin@broadcom.com" <ranky.lin@broadcom.com>,
"hante.meuleman@broadcom.com" <hante.meuleman@broadcom.com>,
"kvalo@kernel.org" <kvalo@kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"lina@asahilina.net" <lina@asahilina.net>,
"marcan@marcan.st" <marcan@marcan.st>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"brcm80211-dev-list.pdl@broadcom.com"
<brcm80211-dev-list.pdl@broadcom.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Orlando Chamberlain <redecorating@protonmail.com>
Subject: Re: [REGRESSION] Wi-Fi fails to work on BCM4364B2 chips since kernel 6.1
Date: Mon, 2 Jan 2023 11:27:21 +0100 [thread overview]
Message-ID: <0a518ebf-4609-992f-fb00-105c68427967@leemhuis.info> (raw)
In-Reply-To: <e780abc0-f8e6-5dd2-0926-05d54d85ccd7@leemhuis.info>
On 02.01.23 09:21, Linux kernel regression tracking (#info) wrote:
> [TLDR: I'm adding this report to the list of tracked Linux kernel
> regressions; all text you find below is based on a few templates
> paragraphs you might have encountered already already in similar form.
> See link in footer if these mails annoy you.]
>
> On 02.01.23 08:46, Aditya Garg wrote:
>> Since kernel 6.1, Wi-Fi is failing to work on Macs with the BCM4364 rev 3 chips and journalctl reports that the firmware has crashed.
>>
>> The complete journalctl is given here :- https://gist.github.com/AdityaGarg8/a25b187e7f1462798de87e048f4840db
>>
>> This bug has been reported by users of iMac19,1 as well as Macmini8,1.
>
> Thanks for the report. To be sure the issue doesn't fall through the
> cracks unnoticed, I'm adding it to regzbot, the Linux kernel regression
> tracking bot:
>
> #regzbot ^introduced v6.0..v6.1
> #regzbot title net: brcmfmac: Wi-Fi is failing to work on Macs with the
> BCM4364 rev 3 chips
> #regzbot ignore-activity
#regzbot inconclusive: problem happens with a downstream tree that
patched this driver, hence might not be a upstream issue
Sorry for the noise, that wasn't obvious from the report.
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
Did I miss something or do something stupid? Then reply and tell me:
https://linux-regtracking.leemhuis.info/about/#stupid
next prev parent reply other threads:[~2023-01-02 10:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-02 7:46 [REGRESSION] Wi-Fi fails to work on BCM4364B2 chips since kernel 6.1 Aditya Garg
2023-01-02 8:21 ` Linux kernel regression tracking (#info)
2023-01-02 10:27 ` Thorsten Leemhuis [this message]
2023-01-02 8:47 ` Hector Martin
2023-01-02 8:57 ` Aditya Garg
2023-01-02 9:13 ` Hector Martin
2023-01-02 14:40 ` [PATCH 1/2] brcmfmac: Use separate struct to declare firmware names for Apple OTP chips Aditya Garg
2023-01-02 14:41 ` [PATCH 2/2] brcmfmac: Add PCIe ID of BCM4355 chip found on T2 Macs Aditya Garg
2023-01-02 14:46 ` Aditya Garg
2023-01-03 2:08 ` kernel test robot
2023-01-02 14:46 ` [PATCH v2 1/2] brcmfmac: Use separate struct to declare firmware names for Apple OTP chips Aditya Garg
2023-01-02 14:48 ` [PATCH v2 2/2] brcmfmac: Add PCIe ID of BCM4355 chip found on T2 Macs Aditya Garg
2023-01-02 15:15 ` [PATCH 1/2] brcmfmac: Use separate struct to declare firmware names for Apple OTP chips Hector Martin
2023-01-02 15:24 ` Aditya Garg
2023-01-02 18:27 ` Arend Van Spriel
2023-01-03 3:55 ` Hector Martin
2023-01-03 13:30 ` Arend van Spriel
2023-01-03 13:46 ` Hector Martin
2023-01-04 9:32 ` Arend van Spriel
2023-01-03 19:59 ` Zzy Wysm
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=0a518ebf-4609-992f-fb00-105c68427967@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=arend.vanspriel@broadcom.com \
--cc=aspriel@gmail.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gargaditya08@live.com \
--cc=hante.meuleman@broadcom.com \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=lina@asahilina.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=marcan@marcan.st \
--cc=pabeni@redhat.com \
--cc=ranky.lin@broadcom.com \
--cc=redecorating@protonmail.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).