All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 217903] New: Bluetooth doesn't work after trigger bluetoothctl scan on
Date: Tue, 12 Sep 2023 06:00:58 +0000	[thread overview]
Message-ID: <bug-217903-62941@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 217903
           Summary: Bluetooth doesn't work after trigger bluetoothctl scan
                    on
           Product: Drivers
           Version: 2.5
          Hardware: Intel
                OS: Linux
            Status: NEW
          Severity: blocking
          Priority: P3
         Component: Bluetooth
          Assignee: linux-bluetooth@vger.kernel.org
          Reporter: kaichuan.hsieh@canonical.com
        Regression: No

Created attachment 305093
  --> https://bugzilla.kernel.org/attachment.cgi?id=305093&action=edit
journalctl_-b log

The device doesn't work after trigger bluetoothctl scan on

I bt devices listed for a while, but it didn't update anymore and start
deleting the expired objects.

I first see kernel reports

Sep 12 13:48:21 ubuntu kernel: Bluetooth: hci0: unexpected cc 0x041a length: 7
> 1

then...

Sep 12 13:52:21 ubuntu kernel: Bluetooth: hci0: Opcode 0x2042 failed: -110
Sep 12 13:52:21 ubuntu kernel: Bluetooth: hci0: command 0x2042 tx timeout

-- 
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:[~2023-09-12  6:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-12  6:00 bugzilla-daemon [this message]
2023-09-12  7:46 ` [Bug 217903] Bluetooth doesn't work after trigger bluetoothctl scan on bugzilla-daemon
2023-09-14  2:08 ` 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-217903-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.