From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 217903] Bluetooth doesn't work after trigger bluetoothctl scan on
Date: Tue, 12 Sep 2023 07:46:27 +0000 [thread overview]
Message-ID: <bug-217903-62941-dxizS5nA5L@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217903-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=217903
KobaKo (koba.ko@canonical.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |koba.ko@canonical.com
--- Comment #1 from KobaKo (koba.ko@canonical.com) ---
even the error isn't triggered,
just switch power off/on and wait a while the devices were deleted.
1. power off/on
2. wait a while
3. devices are deleted
*discovering: yes
*hci0 rx counter keeps increasing
~~~
ubuntu@ubuntu:~$ hciconfig -a
hci0: Type: Primary Bus: USB
BD Address: 50:28:4A:FA:9D:11 ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING
RX bytes:25930 acl:39 sco:0 events:828 errors:0
TX bytes:10395 acl:36 sco:0 commands:598 errors:0
Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH SNIFF
Link mode: PERIPHERAL ACCEPT
Name: 'ubuntu'
Class: 0x6c0104
Service Classes: Rendering, Capturing, Audio, Telephony
Device Class: Computer, Desktop workstation
HCI Version: (0xc) Revision: 0x46c8
LMP Version: (0xc) Subversion: 0x46c8
Manufacturer: Intel Corp. (2)
ubuntu@ubuntu:~$ hciconfig -a
hci0: Type: Primary Bus: USB
BD Address: 50:28:4A:FA:9D:11 ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING
RX bytes:26207 acl:39 sco:0 events:831 errors:0
TX bytes:10404 acl:36 sco:0 commands:601 errors:0
Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH SNIFF
Link mode: PERIPHERAL ACCEPT
Name: 'ubuntu'
Class: 0x6c0104
Service Classes: Rendering, Capturing, Audio, Telephony
Device Class: Computer, Desktop workstation
HCI Version: (0xc) Revision: 0x46c8
LMP Version: (0xc) Subversion: 0x46c8
Manufacturer: Intel Corp. (2)
~~~
[bluetooth]# show
Controller 50:28:4A:FA:9D:11 (public)
Name: ubuntu
Alias: ubuntu
Class: 0x006c0104
Powered: yes
Discoverable: no
DiscoverableTimeout: 0x000000b4
Pairable: yes
Modalias: usb:v1D6Bp0246d0540
Discovering: yes
Roles: central
~~~
--
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:[~2023-09-12 7:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 6:00 [Bug 217903] New: Bluetooth doesn't work after trigger bluetoothctl scan on bugzilla-daemon
2023-09-12 7:46 ` bugzilla-daemon [this message]
2023-09-14 2:08 ` [Bug 217903] " 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-dxizS5nA5L@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.