linux-kernel - Re: [REGRESSION] Bluetooth is not working on Macs with BCM4377 chip starting from kernel 6.5

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <88fcc70e-9f4b-eeb9-d826-03fa4c40e7c3@marcan.st>
Date:   Tue, 14 Nov 2023 15:59:53 +0900
From:   Hector Martin <marcan@...can.st>
To:     Aditya Garg <gargaditya08@...e.com>,
        Bagas Sanjaya <bagasdotme@...il.com>
Cc:     Sven Peter <sven@...npeter.dev>,
        Alyssa Rosenzweig <alyssa@...enzweig.io>,
        Marcel Holtmann <marcel@...tmann.org>,
        Johan Hedberg <johan.hedberg@...il.com>,
        Luiz Augusto von Dentz <luiz.dentz@...il.com>,
        Orlando Chamberlain <orlandoch.dev@...il.com>,
        Kerem Karabay <kekrby@...il.com>,
        Aun-Ali Zaidi <admin@...eit.net>,
        Asahi Linux Mailing List <asahi@...ts.linux.dev>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Bluetooth <linux-bluetooth@...r.kernel.org>
Subject: Re: [REGRESSION] Bluetooth is not working on Macs with BCM4377 chip
 starting from kernel 6.5

On 14/11/2023 15.23, Aditya Garg wrote:
> 
> 
>> On 14-Nov-2023, at 5:01 AM, Bagas Sanjaya <bagasdotme@...il.com> wrote:
>>
>> On Mon, Nov 13, 2023 at 08:57:35PM +0000, Aditya Garg wrote:
>>> Starting from kernel 6.5, a regression in the kernel is causing Bluetooth to not work on T2 Macs with BCM4377 chip.
>>>
>>> Journalctl of kernel 6.4.8 which has Bluetooth working is given here: https://pastebin.com/u9U3kbFJ
>>>
>>> Journalctl of kernel 6.5.2, which has Bluetooth broken is given here: https://pastebin.com/aVHNFMRs
>>>
>>> Also, the bug hasn’t been fixed even in 6.6.1, as reported by users.
>>
>> Can you bisect this regression please?
> 
> Since I don't have access to this hardware, it's not possible for me to bisect this regression. Let's hope someone is able to do so though.

It's not a regression, it was always broken. I'm sending a patch.

- Hector