From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 221521] New: Bluetooth: btusb/mt7921 - Failed to send wmt func ctrl (-22) on MediaTek MT7921 combo adapter
Date: Fri, 15 May 2026 07:01:36 +0000 [thread overview]
Message-ID: <bug-221521-62941@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=221521
Bug ID: 221521
Summary: Bluetooth: btusb/mt7921 - Failed to send wmt func ctrl
(-22) on MediaTek MT7921 combo adapter
Product: Drivers
Version: 2.5
Hardware: All
OS: Linux
Status: NEW
Severity: blocking
Priority: P3
Component: Bluetooth
Assignee: linux-bluetooth@vger.kernel.org
Reporter: txxlc@pm.me
Regression: No
On kernel 7.0.7, the Bluetooth portion of the MediaTek MT7921 PCIe combo
adapter fails to initialize. The btusb driver detects the device (hci0), but
initialization aborts with:
Bluetooth: hci0: Failed to send wmt func ctrl (-22)
As a result, bluetoothd starts successfully but reports no available
controllers. bluetoothctl list returns empty, and GUI managers (blueman,
bluedevil) cannot enable the adapter. RFKill shows no software/hardware blocks.
The Wi-Fi portion (mt7921e) initializes and works correctly.
Steps to Reproduce
1. Boot system with kernel 7.0.7
2. Check dmesg | grep -iE 'bluetooth|btusb|mt7921'
3. Run bluetoothctl list
4. Observe Failed to send wmt func ctrl (-22) in kernel log and No default
controller available in BlueZ
Relevant logs:
% sudo dmesg | grep -A2 -B2 'wmt func ctrl'
[ 6.063435] input: HD-Audio Generic Mic as
/devices/pci0000:00/0000:00:08.1/0000:04:00.6/sound/card1/input16
[ 6.063488] input: HD-Audio Generic Headphone as
/devices/pci0000:00/0000:00:08.1/0000:04:00.6/sound/card1/input17
[ 6.078123] Bluetooth: hci0: Failed to send wmt func ctrl (-22)
[ 6.078129] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection
command is advertised, but not supported.
[ 6.133913] mt7921e 0000:03:00.0: HW/SW Version: 0x8a108a10, Build Time:
20260224110909a
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2026-05-15 7:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 7:01 bugzilla-daemon [this message]
2026-05-15 7:03 ` [Bug 221521] Bluetooth: btusb/mt7921 - Failed to send wmt func ctrl (-22) on MediaTek MT7921 combo adapter bugzilla-daemon
2026-05-15 7:04 ` bugzilla-daemon
2026-05-15 7:16 ` bugzilla-daemon
2026-05-15 7:18 ` bugzilla-daemon
2026-05-15 8:24 ` bugzilla-daemon
2026-05-15 9:15 ` bugzilla-daemon
2026-05-15 9:17 ` bugzilla-daemon
2026-05-15 10:13 ` bugzilla-daemon
2026-05-15 10:20 ` bugzilla-daemon
2026-05-15 13:25 ` bugzilla-daemon
2026-05-15 18:58 ` bugzilla-daemon
2026-05-16 7:48 ` 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=bug-221521-62941@https.bugzilla.kernel.org/ \
--to=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.