Control: reassign -2 src:linux 6.1.192-2
Control: tags -1 + moreinfo

On Fri, Nov 20, 2026 at 10:11:03AM +0100, Vin_ c'e wrote:
> Package: linux-image-6.1.0-56-amd64
> 
> Version: 6.1.192-2
> Severity: important
> Tags: regression

FYI: There is no such tag, please use reportbug to fill bugs.

> Dear Maintainer,
> 
> After upgrading from linux-image-6.1.0-55 (6.1.192-1) to
> linux-image-6.1.0-56 (6.1.192-2), Bluetooth stops working: the kernel
> hits a BUG as soon as bluetoothd closes an L2CAP socket, which taints
> the kernel (G D) and kills the Bluetooth stack. The adapter is detected
> and the Intel firmware loads fine, but the stack is dead afterwards.
> 
> Booting 6.1.0-55 (6.1.192-1) makes Bluetooth work normally again.
> 100% reproducible at every boot with -56.
> 
> Crash signature:
> 
>   kernel BUG at lib/list_debug.c:56!
>   invalid opcode: 0000 [#1] PREEMPT SMP NOPTI
>   Comm: bluetoothd Tainted: G OE 6.1.0-56-amd64 #1 Debian 6.1.192-2
>   RIP: __list_del_entry_valid.cold+0x4b/0x6f
>   Call Trace:
>    hci_chan_del+0x18/0x90 [bluetooth]
>    l2cap_chan_put+0x106/0x130 [bluetooth]
>    l2cap_sock_release+0xca/0x100 [bluetooth]
>    __sock_release+0x3d/0xb0
>    sock_close+0x11/0x20
>    __fput+0x93/0x250
>    task_work_run+0x56/0x90
> 
> Hardware:
>   HP EliteBook x360 1040 G8, BIOS T93 Ver. 01.24.02
>   Intel Wi-Fi 6 AX201 160MHz (REV=0x351)
>   Bluetooth firmware: intel/ibt-19-0-4.sfi, rev 0.4 build 15 week 45 2022
> 
> Steps to reproduce:
>   1. Boot linux-image-6.1.0-56-amd64 (6.1.192-2)
>   2. bluetoothd starts / use a BT device (Logitech M720)
>   3. Kernel BUG, Bluetooth unusable
> 
> Workaround: boot 6.1.0-55 (6.1.192-1).

That sounds quite unlikely though, because the only change between
6.1.192-1 and 6.1.192-2 was to fix the ext4 regression. 

How easily can you reproduce the problme? If so can you please bisect
the changes between 6.1.190 and 6.1.192 to identify the offending
commit?

Regards,
Salvatore

Reply via email to