Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #94273 > unrolled thread

Bug#1149377: linux-image-6.12.111+deb13-amd64: Bluetooth no longer works after kernel upgrade

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#1149377: linux-image-6.12.111+deb13-amd64: Bluetooth no longer works after kernel upgrade Salvatore Bonaccorso <carnil@debian.org> - 2026-09-30 17:10 +0200
    Processed: Re: Bug#1149377: linux-image-6.12.111+deb13-amd64:  Bluetooth no longer works after kernel upgrade "Debian Bug Tracking System" <owner@bugs.debian.org> - 2026-09-30 17:10 +0200
    Bug#1149377: linux-image-6.12.111+deb13-amd64: Bluetooth no longer works after kernel upgrade Salvatore Bonaccorso <carnil@debian.org> - 2026-09-30 22:30 +0200
      Processed: Re: Bug#1149377: linux-image-6.12.111+deb13-amd64:  Bluetooth no longer works after kernel upgrade "Debian Bug Tracking System" <owner@bugs.debian.org> - 2026-09-30 22:30 +0200
      Bug#1149377: linux-image-6.12.111+deb13-amd64: Bluetooth no longer works after kernel upgrade Salvatore Bonaccorso <carnil@debian.org> - 2026-10-01 09:40 +0200

#94273 — Bug#1149377: linux-image-6.12.111+deb13-amd64: Bluetooth no longer works after kernel upgrade

Control: tags -1 + moreinfo

Hi Erik

On Tue, Sep 29, 2026 at 08:05:02PM +0200, Erik Brangs wrote:
> Package: src:linux
> Version: 6.12.111-1
> Severity: normal
> X-Debbugs-Cc: debian-amd64@lists.debian.org, erik.brangs@gmx.de
> User: debian-amd64@lists.debian.org
> Usertags: amd64
> 
> Dear Maintainer,
> 
> #   * What led up to the situation?
> I upgraded to the kernel 6.12.111 on my desktop computer. After the upgrade, bluetooth no longer worked.
> #   * What exactly did you do (or not do) that was effective (or
> #     ineffective)?
> 
> I rebooted the computer and selected the old kernel, 6.12.107, from the boot menu. After booting the old kernel, bluetooth worked again.
> #   * What outcome did you expect instead?
> 
> I would expect bluetooth to work with the current kernel.

Yes understandable. It would be great if you could bisect the problem. That would involve
compiling and testing a few kernels

    git clone --single-branch -b linux-6.12.y https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
    cd linux-stable
    git checkout v6.12.107
    cp /boot/config-$(uname -r) .config
    yes '' | make localmodconfig
    make savedefconfig
    mv defconfig arch/x86/configs/my_defconfig

    # test 6.12.107 to ensure this is "good"
    make my_defconfig
    make -j $(nproc) bindeb-pkg
    ... install the resulting .deb package and confirm problem does not exist

    # test 6.12.111 to ensure this is "bad"
    git checkout v6.12.111
    make my_defconfig
    make -j $(nproc) bindeb-pkg
    ... install the resulting .deb package and confirm problem exists

With that confirmed, the bisection can start:

    git bisect start
    git bisect good v6.12.107
    git bisect bad v6.12.111

In each bisection step git checks out a state between the oldest
known-bad and the newest known-good commit. In each step test using:

    make my_defconfig
    make -j $(nproc) bindeb-pkg
    ... install, verify if problem exists

and if the problem is hit run:

    git bisect bad

and if the problem doesn't trigger run:

    git bisect good

. Please pay attention to always select the just built kernel for
booting, it won't always be the default kernel picked up by grub.

Iterate until git announces to have identified the first bad commit.

Then provide the output of

    git bisect log

In the course of the bisection you might have to uninstall previous
kernels again to not exhaust the disk space in /boot. Also in the end
uninstall all self-built kernels again.

Regards,
Salvatore

[toc] | [next] | [standalone]

#94274 — Processed: Re: Bug#1149377: linux-image-6.12.111+deb13-amd64: Bluetooth no longer works after kernel upgrade

Processing control commands:

> tags -1 + moreinfo
Bug #1149377 [src:linux] linux-image-6.12.111+deb13-amd64: Bluetooth no longer works after kernel upgrade
Added tag(s) moreinfo.

-- 
1149377: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1149377
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#94294

Control: tags -1 + moreinfo
Control: forwarded -1 https://lore.kernel.org/regressions/9ac1c05b-e9f2-49e9-af63-9cd0e42115fc@gmail.com/

Hi Erik

On Wed, Sep 30, 2026 at 09:59:11PM +0200, Erik Brangs wrote:
> Hi,
> 
> the output of git bisect log is
> 
> git bisect start
> # status: waiting for both good and bad commits
> # bad: [e2acc2211022246c77740d5df08265cc27eedcc5] Linux 6.12.111
> git bisect bad e2acc2211022246c77740d5df08265cc27eedcc5
> # status: waiting for good commit(s), bad commit known
> # good: [f717995cb7dcd8998ab15516b8006aea09cfde0d] Linux 6.12.107
> git bisect good f717995cb7dcd8998ab15516b8006aea09cfde0d
> # bad: [2e3d827cd56865c14f6ca118bbccd7801091fb21] Bluetooth: hci_sync: free the advertising instance on the failure and cancel paths
> git bisect bad 2e3d827cd56865c14f6ca118bbccd7801091fb21
> # bad: [ebc41dfc59d190956e0113e8bd90c28f6f21e8b9] scsi: qla2xxx: Bound rsp_info_len to avoid OOB sense-data read
> git bisect bad ebc41dfc59d190956e0113e8bd90c28f6f21e8b9
> # bad: [af3ce383ba0d0d48957a22ac7058ff5698775898] power: supply: charger-manager: register regulators before exposing sysfs
> git bisect bad af3ce383ba0d0d48957a22ac7058ff5698775898
> # good: [58bcdfb2b2e412088839ae740b1a95154dc0b8d0] nfsd: clear opcnt on compound arg release to prevent OOB read
> git bisect good 58bcdfb2b2e412088839ae740b1a95154dc0b8d0
> # bad: [f4fde735a813705875e836e1dea41a93e994c779] Bluetooth: hci_conn: re-enable advertising only for peripheral role
> git bisect bad f4fde735a813705875e836e1dea41a93e994c779
> # good: [b11a78646c104df205e7eb5903bcce7590396dea] eCryptfs: bound the packet-length peek to the user buffer
> git bisect good b11a78646c104df205e7eb5903bcce7590396dea
> # good: [2ae970ad5adc254360b25d153956009a7d9ee8a2] ARM: 9477/1: Disable broken eBPF JIT on the Risc PC
> git bisect good 2ae970ad5adc254360b25d153956009a7d9ee8a2
> # bad: [d66ceeefb87ddb097b0546bafc581380b816b048] dm-era: fix shadowed superblock leak on take-snap failure
> git bisect bad d66ceeefb87ddb097b0546bafc581380b816b048
> # bad: [32412aff8d11d00672053cb10750869f2de94a1f] Bluetooth: btusb: Add ASUS USB-BT600 for Realtek 8761CU
> git bisect bad 32412aff8d11d00672053cb10750869f2de94a1f
> # good: [fe7ba73dde94c5f413b1588cd444b49105015dda] auxdisplay: charlcd: cancel backlight work on registration failure
> git bisect good fe7ba73dde94c5f413b1588cd444b49105015dda
> # bad: [f05baf6e0680d8c10d2fbbc5953848fc3e3db957] Bluetooth: btusb: Add ASUS USB-BT540 for Realtek 8761CU
> git bisect bad f05baf6e0680d8c10d2fbbc5953848fc3e3db957
> # good: [48ca2b8c8a6ba5c26269120c8092db0b617a18a7] block: set QUEUE_FLAG_DYING unconditionally in blk_mark_disk_dead()
> git bisect good 48ca2b8c8a6ba5c26269120c8092db0b617a18a7
> # first bad commit: [f05baf6e0680d8c10d2fbbc5953848fc3e3db957] Bluetooth: btusb: Add ASUS USB-BT540 for Realtek 8761CU

Thanks for bisecting, so this looks relatd to the reported regression
https://lore.kernel.org/regressions/9ac1c05b-e9f2-49e9-af63-9cd0e42115fc@gmail.com/
.

Upstrema has queued 4a23ce935f74 ("Bluetooth: btrtl: Add the support
for RTL8761CUV") for the next 6.12.y, can you verify in advance if
that fixes your issue and pick the patch on top?

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]

#94296 — Processed: Re: Bug#1149377: linux-image-6.12.111+deb13-amd64: Bluetooth no longer works after kernel upgrade

Processing control commands:

> tags -1 + moreinfo
Bug #1149377 [src:linux] linux-image-6.12.111+deb13-amd64: Bluetooth no longer works after kernel upgrade
Added tag(s) moreinfo.
> forwarded -1 https://lore.kernel.org/regressions/9ac1c05b-e9f2-49e9-af63-9cd0e42115fc@gmail.com/
Bug #1149377 [src:linux] linux-image-6.12.111+deb13-amd64: Bluetooth no longer works after kernel upgrade
Set Bug forwarded-to-address to 'https://lore.kernel.org/regressions/9ac1c05b-e9f2-49e9-af63-9cd0e42115fc@gmail.com/'.

-- 
1149377: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1149377
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#94298

Hi Erik,

On Wed, Sep 30, 2026 at 10:51:54PM +0200, Erik Brangs wrote:
> Hi,
> 
> 4a23ce935f74 does not apply cleanly to v6.12.111
> 
> diff --cc drivers/bluetooth/btrtl.c
> index 6bb068dee6d2,5603b282f9bc..000000000000
> --- a/drivers/bluetooth/btrtl.c
> +++ b/drivers/bluetooth/btrtl.c
> @@@ -1317,7 -1317,7 +1317,11 @@@ void btrtl_set_quirks(struct hci_dev *h
>         case CHIP_ID_8922A:
>         case CHIP_ID_8852BT:
>         case CHIP_ID_8761C:
> ++<<<<<<< HEAD
>  +              set_bit(HCI_QUIRK_WIDEBAND_SPEECH_SUPPORTED, &hdev->quirks);
> ++=======
> +               hci_set_quirk(hdev, HCI_QUIRK_WIDEBAND_SPEECH_SUPPORTED);
> ++>>>>>>> 4a23ce935f74 (Bluetooth: btrtl: Add the support for RTL8761CUV)
>                 /* RTL8852C needs to transmit mSBC data continuously without
>                  * the zero length of USB packets for the ALT 6 supported chips
> 
> 
> or to the first bad commit f05baf6e0680d8c10d2fbbc5953848fc3e3db957
> 
> diff --cc drivers/bluetooth/btrtl.c
> index 49b74827344c,5603b282f9bc..000000000000
> --- a/drivers/bluetooth/btrtl.c
> +++ b/drivers/bluetooth/btrtl.c
> @@@ -1306,7 -1316,8 +1317,12 @@@ void btrtl_set_quirks(struct hci_dev *h
>         case CHIP_ID_8851B:
>         case CHIP_ID_8922A:
>         case CHIP_ID_8852BT:
> ++<<<<<<< HEAD
>  +              set_bit(HCI_QUIRK_WIDEBAND_SPEECH_SUPPORTED, &hdev->quirks);
> ++=======
> +       case CHIP_ID_8761C:
> +               hci_set_quirk(hdev, HCI_QUIRK_WIDEBAND_SPEECH_SUPPORTED);
> ++>>>>>>> 4a23ce935f74 (Bluetooth: btrtl: Add the support for RTL8761CUV)
>                 /* RTL8852C needs to transmit mSBC data continuously without
>                  * the zero length of USB packets for the ALT 6 supported chips

Apologies, this is my error. The mentioned commit 4a23ce935f74 *is*
already part of 6.12.111 upstream, so we have here a different issue
to report upstream caused by the
f05baf6e0680d8c10d2fbbc5953848fc3e3db957 commit.

I'm looping in Ben, who said yesterday in the kernel-team meeting to
look into this issue as well.

but I think we should bring this new problem to upstream regressions
list as wel.

Regards,
Salvatore

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web