Bug 217903 - Bluetooth doesn't work after trigger bluetoothctl scan on
Summary: Bluetooth doesn't work after trigger bluetoothctl scan on
Status: RESOLVED INVALID
Alias: None
Product: Drivers
Classification: Unclassified
Component: Bluetooth (show other bugs)
Hardware: Intel Linux
: P3 blocking
Assignee: linux-bluetooth@vger.kernel.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-09-12 06:00 UTC by KaiChuan-Hsieh
Modified: 2023-09-14 02:08 UTC (History)
2 users (show)

See Also:
Kernel Version:
Subsystem:
Regression: No
Bisected commit-id:


Attachments
journalctl_-b log (249.08 KB, text/plain)
2023-09-12 06:00 UTC, KaiChuan-Hsieh
Details

Description KaiChuan-Hsieh 2023-09-12 06:00:58 UTC
Created attachment 305093 [details]
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
Comment 1 KobaKo 2023-09-12 07:46:27 UTC
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
~~~
Comment 2 KaiChuan-Hsieh 2023-09-14 02:08:01 UTC
The issue won't happen with QS BE200 module.

Note You need to log in before you can comment on or make changes to this bug.