From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Aditya Garg <gargaditya08@live.com>,
Hector Martin <marcan@marcan.st>, Sven Peter <sven@svenpeter.dev>,
Alyssa Rosenzweig <alyssa@rosenzweig.io>,
Marcel Holtmann <marcel@holtmann.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: Orlando Chamberlain <orlandoch.dev@gmail.com>,
Kerem Karabay <kekrby@gmail.com>,
Aun-Ali Zaidi <admin@kodeit.net>,
Asahi Linux Mailing List <asahi@lists.linux.dev>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Bluetooth <linux-bluetooth@vger.kernel.org>
Subject: Re: [REGRESSION] Bluetooth is not working on Macs with BCM4377 chip starting from kernel 6.5
Date: Tue, 14 Nov 2023 06:31:00 +0700 [thread overview]
Message-ID: <ZVKxtD2Mt_eVyttJ@archie.me> (raw)
In-Reply-To: <22582194-DE99-45E5-ABEE-C1C7900DA523@live.com>
[-- Attachment #1: Type: text/plain, Size: 2588 bytes --]
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?
>
> Some relevant bits imo:
>
> • Sep 19 21:24:36 RudyUbuMbp kernel: hci_bcm4377 0000:73:00.1: can't disable ASPM; OS doesn't have ASPM control
>
> • Nov 14 01:29:28 RudyUbuMbp kernel: Call Trace:
> • Nov 14 01:29:28 RudyUbuMbp kernel: <TASK>
> • Nov 14 01:29:28 RudyUbuMbp kernel: dump_stack_lvl+0x48/0x70
> • Nov 14 01:29:28 RudyUbuMbp kernel: dump_stack+0x10/0x20
> • Nov 14 01:29:28 RudyUbuMbp kernel: __ubsan_handle_shift_out_of_bounds+0x156/0x310
> • Nov 14 01:29:28 RudyUbuMbp kernel: ? ttwu_do_activate+0x80/0x290
> • Nov 14 01:29:28 RudyUbuMbp kernel: ? raw_spin_rq_unlock+0x10/0x40
> • Nov 14 01:29:28 RudyUbuMbp kernel: ? try_to_wake_up+0x292/0x6c0
> • Nov 14 01:29:28 RudyUbuMbp kernel: ? sched_slice+0x76/0x140
> • Nov 14 01:29:28 RudyUbuMbp kernel: ? reweight_entity+0x15c/0x170
> • Nov 14 01:29:28 RudyUbuMbp kernel: __reg_op.cold+0x14/0x38
> • Nov 14 01:29:28 RudyUbuMbp kernel: bitmap_release_region+0xe/0x20
> • Nov 14 01:29:28 RudyUbuMbp kernel: bcm4377_handle_ack+0x8c/0x130 [hci_bcm4377]
> • Nov 14 01:29:28 RudyUbuMbp kernel: bcm4377_poll_completion_ring+0x196/0x330 [hci_bcm4377]
> • Nov 14 01:29:28 RudyUbuMbp kernel: ? rcu_gp_kthread_wake+0x57/0x90
> • Nov 14 01:29:28 RudyUbuMbp kernel: bcm4377_irq+0x77/0x140 [hci_bcm4377]
> • Nov 14 01:29:28 RudyUbuMbp kernel: __handle_irq_event_percpu+0x4c/0x1b0
> • Nov 14 01:29:28 RudyUbuMbp kernel: handle_irq_event+0x39/0x80
> • Nov 14 01:29:28 RudyUbuMbp kernel: handle_edge_irq+0x8c/0x250
> • Nov 14 01:29:28 RudyUbuMbp kernel: __common_interrupt+0x4f/0x110
> • Nov 14 01:29:28 RudyUbuMbp kernel: common_interrupt+0x45/0xb0
> • Nov 14 01:29:28 RudyUbuMbp kernel: asm_common_interrupt+0x27/0x40
> • Nov 14 01:29:28 RudyUbuMbp kernel: RIP: 0033:0x7f17b5fd8bca
Anyway, thanks for the regression report. I'm adding it to regzbot:
#regzbot ^introduced: v6.4..v6.5
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-11-13 23:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 20:57 [REGRESSION] Bluetooth is not working on Macs with BCM4377 chip starting from kernel 6.5 Aditya Garg
2023-11-13 23:31 ` Bagas Sanjaya [this message]
2023-11-14 6:23 ` Aditya Garg
2023-11-14 6:59 ` Hector Martin
2023-11-14 7:58 ` Hector Martin
2023-11-14 8:18 ` Aditya Garg
2023-11-14 9:03 ` Aditya Garg
2023-11-14 9:44 ` Hector Martin
2023-11-14 10:05 ` Aditya Garg
2023-11-18 19:31 ` Aditya Garg
2023-11-20 11:07 ` Hector Martin
2023-11-21 11:42 ` Aditya Garg
2023-11-21 12:16 ` Hector Martin
2023-11-14 8:35 ` Janne Grunau
2023-12-24 18:04 ` Felix Zhang
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=ZVKxtD2Mt_eVyttJ@archie.me \
--to=bagasdotme@gmail.com \
--cc=admin@kodeit.net \
--cc=alyssa@rosenzweig.io \
--cc=asahi@lists.linux.dev \
--cc=gargaditya08@live.com \
--cc=johan.hedberg@gmail.com \
--cc=kekrby@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcan@marcan.st \
--cc=marcel@holtmann.org \
--cc=orlandoch.dev@gmail.com \
--cc=sven@svenpeter.dev \
/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).