Skip to contentSkip to conversation

New: Bluetooth doesn't work after trigger bluetoothctl scan on

Bug 217903 [email protected] 1 participant 3 messages Sep 12, 2023 – Sep 14, 2023 Bluetooth drivers

lore
Share & tools
lore
#0 lore 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: [email protected]
          Reporter: [email protected]
        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
Quoted 1 line

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
Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.
#1 lore raw

[Bug 217903] Bluetooth doesn't work after trigger bluetoothctl scan on

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

KobaKo ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #1 from KobaKo ([email protected]) --- 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
~~~
Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.
#2 lore raw

[Bug 217903] Bluetooth doesn't work after trigger bluetoothctl scan on

In reply to [email protected]

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

KaiChuan-Hsieh ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------

             Status|NEW                         |RESOLVED
         Resolution|---                         |CODE_FIX

--- Comment #2 from KaiChuan-Hsieh ([email protected]) --- The issue won't happen with QS BE200 module.

Signature · 4 lines
You may reply to this email to add a comment.

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