Linux bluetooth development
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 222250] New: v7.4-rc2: Bluetooth: hci0: Opcode 0x041a failed: -22
Date: Mon, 09 Nov 2026 10:53:12 +0000	[thread overview]
Message-ID: <bug-222250-62941@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=222250

            Bug ID: 222250
           Summary: v7.4-rc2: Bluetooth: hci0: Opcode 0x041a failed: -22
           Product: Drivers
           Version: 2.5
    Kernel Version: v7.4-rc2
          Hardware: AMD
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Bluetooth
          Assignee: linux-bluetooth@vger.kernel.org
          Reporter: frc.gabriel@gmail.com
        Regression: Yes

Hi, good morning,


I just booted v7.4-rc2 and noticed that bluetooth no longer connects to paired
headphones. Removing + trying to repair doesn't work either.


Dmesg shows:


root@localhost:~# journalctl -b -1 | grep -i "Opcode 0x041a failed:" -A2 -B100
| grep -i "kernel\|bluetooth"
Nov 09 09:50:45 localhost kernel: Bluetooth: hci0: Loading BT firmware:
mediatek/mt7925/BT_RAM_CODE_MT7925_1_1_hdr.bin
Nov 09 09:50:45 localhost kernel: Bluetooth: hci0: BT HW ver: 0x7925, SW ver:
0x0000, Build Time: 20260813113236
Nov 09 09:50:46 localhost kernel: Bluetooth: hci0: Device setup in 349484 usecs
Nov 09 09:50:46 localhost kernel: Bluetooth: hci0: HCI Enhanced Setup
Synchronous Connection command is advertised, but not supported.
Nov 09 09:50:54 localhost bluetoothd[7697]: src/service.c:btd_service_connect()
a2dp-sink profile connect failed for XX:XX:XX:XX:XX:XX: Protocol not available
Nov 09 09:51:57 localhost bluetoothd[7697]: src/service.c:btd_service_connect()
a2dp-sink profile connect failed for XX:XX:XX:XX:XX:XX:: Protocol not available
Nov 09 09:51:58 localhost bluetoothd[7697]: src/service.c:btd_service_connect()
a2dp-sink profile connect failed for XX:XX:XX:XX:XX:XX:: Protocol not available
Nov 09 09:51:58 localhost bluetoothd[7697]: src/service.c:btd_service_connect()
a2dp-sink profile connect failed for XX:XX:XX:XX:XX:XX:: Protocol not available
Nov 09 09:51:59 localhost bluetoothd[7697]: src/service.c:btd_service_connect()
a2dp-sink profile connect failed for XX:XX:XX:XX:XX:XX:: Protocol not available
Nov 09 09:51:59 localhost bluetoothd[7697]: src/service.c:btd_service_connect()
a2dp-sink profile connect failed for XX:XX:XX:XX:XX:XX:: Protocol not available
Nov 09 09:52:00 localhost bluetoothd[7697]: src/service.c:btd_service_connect()
a2dp-sink profile connect failed for XX:XX:XX:XX:XX:XX:: Protocol not available
Nov 09 09:52:00 localhost bluetoothd[7697]: src/service.c:btd_service_connect()
a2dp-sink profile connect failed for XX:XX:XX:XX:XX:XX:: Protocol not available
Nov 09 09:52:02 localhost kernel: Bluetooth: hci0: Opcode 0x041a failed: -22
Nov 09 09:52:07 localhost bluetoothd[7697]: src/service.c:btd_service_connect()
a2dp-sink profile connect failed for XX:XX:XX:XX:XX:XX:: Protocol not available
Nov 09 09:52:07 localhost kernel: Bluetooth: hci0: Opcode 0x041a failed: -22


It works OK with v7.4-rc1.

Greetings,
Gabriel Francisco

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

             reply	other threads:[~2026-11-09 10:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-09 10:53 bugzilla-daemon [this message]
2026-11-10  9:25 ` [Bug 222250] v7.4-rc2: Bluetooth: hci0: Opcode 0x041a failed: -22 bugzilla-daemon
2026-11-10 22:52 ` bugzilla-daemon
2026-11-10 22:53 ` bugzilla-daemon
2026-11-10 23:33 ` 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-222250-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox