[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e780abc0-f8e6-5dd2-0926-05d54d85ccd7@leemhuis.info>
Date: Mon, 2 Jan 2023 09:21:37 +0100
From: "Linux kernel regression tracking (#info)"
<regressions@...mhuis.info>
To: Aditya Garg <gargaditya08@...e.com>,
"arend.vanspriel@...adcom.com" <arend.vanspriel@...adcom.com>,
"aspriel@...il.com" <aspriel@...il.com>,
"ranky.lin@...adcom.com" <ranky.lin@...adcom.com>,
"hante.meuleman@...adcom.com" <hante.meuleman@...adcom.com>,
"kvalo@...nel.org" <kvalo@...nel.org>,
"davem@...emloft.net" <davem@...emloft.net>,
"edumazet@...gle.com" <edumazet@...gle.com>,
"kuba@...nel.org" <kuba@...nel.org>,
"pabeni@...hat.com" <pabeni@...hat.com>,
"lina@...hilina.net" <lina@...hilina.net>,
"marcan@...can.st" <marcan@...can.st>
Cc: "linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
"brcm80211-dev-list.pdl@...adcom.com"
<brcm80211-dev-list.pdl@...adcom.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Orlando Chamberlain <redecorating@...tonmail.com>
Subject: Re: [REGRESSION] Wi-Fi fails to work on BCM4364B2 chips since kernel
6.1
[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
This isn't a regression? This issue or a fix for it are already
discussed somewhere else? It was fixed already? You want to clarify when
the regression started to happen? Or point out I got the title or
something else totally wrong? Then just reply and tell me -- ideally
while also telling regzbot about it, as explained by the page listed in
the footer of this mail.
Reminder for developers: When fixing the issue, add 'Link:' tags
pointing to the report (see page linked in footer for details).
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
Annoyed by mails like this? Feel free to send them to /dev/null:
https://linux-regtracking.leemhuis.info/about/#infomails
Powered by blists - more mailing lists