From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 216580] Jabra Elite 75t (ear buds):Unable to connect and use (`hci0: Opcode 0x 401 failed: -16`)
Date: Thu, 13 Oct 2022 19:44:44 +0000 [thread overview]
Message-ID: <bug-216580-62941-mXpEmuDDsk@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216580-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216580
Luiz Von Dentz (luiz.dentz@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |luiz.dentz@gmail.com
--- Comment #3 from Luiz Von Dentz (luiz.dentz@gmail.com) ---
This looks suspicious:
< HCI Command: Microsoft SW RF Kill (0x3f|0x003f) plen 0
#844 [hci0] 226.575196
> HCI Event: Command Complete (0x0e) plen 4
> #845 [hci0] 226.576116
Microsoft SW RF Kill (0x3f|0x003f) ncmd 1
Status: Success (0x00)
Which comes from:
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/tree/drivers/bluetooth/btintel.c#n2600
The problem is that after sending RFKILL we need to reset again in order for
the firmware to become operation again as explained bellow:
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/tree/drivers/bluetooth/btintel.c#n2361
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2022-10-13 19:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 15:36 [Bug 216580] New: Jabra Elite 75t (ear buds):Unable to connect and use (`hci0: Opcode 0x 401 failed: -16`) bugzilla-daemon
2022-10-13 15:39 ` [Bug 216580] " bugzilla-daemon
2022-10-13 15:40 ` bugzilla-daemon
2022-10-13 19:44 ` bugzilla-daemon [this message]
2022-10-13 21:04 ` bugzilla-daemon
2022-10-13 21:52 ` [Bug,216580] " bluez.test.bot
2022-10-21 13:58 ` [Bug 216580] " bugzilla-daemon
2022-10-21 19:40 ` 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-216580-62941-mXpEmuDDsk@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.