linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Fri, 21 Oct 2022 19:40:12 +0000	[thread overview]
Message-ID: <bug-216580-62941-sge7plh3Ky@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216580-62941@https.bugzilla.kernel.org/>

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

--- Comment #6 from Luiz Von Dentz (luiz.dentz@gmail.com) ---
(In reply to Paul Menzel from comment #5)
> Created attachment 303066 [details]
> `sudo btmon -w /dev/shm/20221021-linux-6.1-rc1+-ge35184f32151-with-patch.log`
> 
> I tested this on a different system, Dell XPS 13 9360, with the Qualcomm
> Atheros Communications QCA1x4 Bluetooth 4.0 (0cf3:e300), and Debian
> sid/unstable with KDE Plasma 5.25/5.26 and *bluez* 5.65-1+b1. Please find
> the `btmon` output attached.

Well the patch above is intel specific and it probably does make any difference
for a Qualcomm controller and it doesn't seem there is any attempt to connect
to anything in this logs.

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

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

      parent reply	other threads:[~2022-10-21 19:40 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
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 [this message]

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-sge7plh3Ky@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;
as well as URLs for NNTP newsgroup(s).