From: Hector Martin <marcan@marcan.st>
To: Aditya Garg <gargaditya08@live.com>,
Arend van Spriel <aspriel@gmail.com>,
Arend van Spriel <arend.vanspriel@broadcom.com>,
Kalle Valo <kvalo@kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"brcm80211-dev-list.pdl@broadcom.com"
<brcm80211-dev-list.pdl@broadcom.com>,
"brcm80211-dev-list@broadcom.com"
<brcm80211-dev-list@broadcom.com>,
LKML <linux-kernel@vger.kernel.org>,
Orlando Chamberlain <orlandoch.dev@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [REGRESSION] Unable to connect to Internet since kernel 6.2.3 on T2 Macs
Date: Sun, 12 Mar 2023 01:06:54 +0900 [thread overview]
Message-ID: <e5d36d19-624e-ad0e-cd90-8b188771e41d@marcan.st> (raw)
In-Reply-To: <MA0P287MB02178C2B6AFC2E96F261FB2CB8BB9@MA0P287MB0217.INDP287.PROD.OUTLOOK.COM>
On 12/03/2023 00.56, Aditya Garg wrote:
> A weird regression has been affecting the T2 Macs since kernel 6.2.3. The users are unable to connect to both wireless as well as wired Internet. As far as wireless is concerned, the patches for T2 Macs that have been upstreamed in kernel 6.3 have been working well till 6.2.2, but after that the network has stopped working.
>
> Interesting, the driver shows no errors in journalctl. The wifi firmware loads well and the networks even appear on scan list. But, the connection to a network fails. Ethernet/USB tethering has also stopped working.
>
> If I you need some logs from me, please do ask.
>
> Also, Hector, I’d like to know whether this affects the M1/2 Macs as well or not.
This is already reported, identified, and a patch submitted.
https://lore.kernel.org/linux-wireless/20230124141856.356646-1-alexander@wetzel-home.de/
- Hector
next prev parent reply other threads:[~2023-03-11 16:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-11 15:56 Aditya Garg
2023-03-11 16:06 ` Hector Martin [this message]
2023-03-11 16:14 ` Aditya Garg
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=e5d36d19-624e-ad0e-cd90-8b188771e41d@marcan.st \
--to=marcan@marcan.st \
--cc=arend.vanspriel@broadcom.com \
--cc=aspriel@gmail.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=brcm80211-dev-list@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gargaditya08@live.com \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=orlandoch.dev@gmail.com \
--cc=pabeni@redhat.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
all inboxes | Powered by JetHome®