From: Emanuele Ghidoli <ghidoliemanuele@gmail.com>
To: bugzilla-daemon@kernel.org, linux-bluetooth@vger.kernel.org
Subject: Re: [Bug 222177] New: Bluetooth AX201 device does not work on Debian 13 on Kernel 6.12.114, works on 6.12.113
Date: Thu, 22 Oct 2026 13:23:40 +0200 [thread overview]
Message-ID: <c0938cf3-3166-438c-b4e3-942e44ccaabc@gmail.com> (raw)
In-Reply-To: <bug-222177-62941@https.bugzilla.kernel.org/>
On 10/21/26 17:34, bugzilla-daemon@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=222177
>
> Bug ID: 222177
> Summary: Bluetooth AX201 device does not work on Debian 13 on
> Kernel 6.12.114, works on 6.12.113
> Product: Drivers
> Version: 2.5
> Hardware: Intel
> OS: Linux
> Status: NEW
> Severity: normal
> Priority: P3
> Component: Bluetooth
> Assignee: linux-bluetooth@vger.kernel.org
> Reporter: kalamlacki@gmail.com
> Regression: No
>
> After compiling Kernel 6.12.114 bluetooth device is not working in blueman app
> on Debian 13, it works correctly on Kernel 6.12.113.
>
> My adapter is:
>
> 00:14.3 Network controller: Intel Corporation Wi-Fi 6 AX201 (rev 20)
> Bus 001 Device 004: ID 8087:0026 Intel Corp. AX201 Bluetooth
>
The regression is caused by a missing backport: 6.12.114 picked up "Bluetooth:
L2CAP: convert to getsockopt_iter" but not its prerequisite "net: call
getsockopt_iter if available" (upstream 5bd0dec150f5), so getsockopt() on
L2CAP sockets fails with EOPNOTSUPP and bluetoothd cannot register the adapter.
See
https://lore.kernel.org/stable/20261022111535.528099-1-ghidoliemanuele@gmail.com/.
If someone can test it, a Tested-by in reply to the patch would help.
Emanuele
next prev parent reply other threads:[~2026-10-22 11:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 15:34 [Bug 222177] New: Bluetooth AX201 device does not work on Debian 13 on Kernel 6.12.114, works on 6.12.113 bugzilla-daemon
2026-10-21 15:49 ` [Bug 222177] " bugzilla-daemon
2026-10-22 11:23 ` Emanuele Ghidoli [this message]
2026-10-22 11:23 ` bugzilla-daemon
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=c0938cf3-3166-438c-b4e3-942e44ccaabc@gmail.com \
--to=ghidoliemanuele@gmail.com \
--cc=bugzilla-daemon@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.