New: JBL GO 2 only recognized after restarting `bluetoothd`

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

            Bug ID: 216845
           Summary: JBL GO 2 only recognized after restarting `bluetoothd`
           Product: Drivers
           Version: 2.5
    Kernel Version: 6.1-rc8
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Bluetooth
          Assignee: [email protected]
          Reporter: [email protected]
        Regression: No

Created attachment 303469
--> https://bugzilla.kernel.org/attachment.cgi?id=303469&action=edit
sudo btmon -w /dev/shm/linux-6.1-rc8-btmon.txt

Using Debian sid/unstable with Linux 6.1-rc8, *bluez* 5.66-1 and gnome-control-center *1:43.1-2*, going into the Bluetooth section of *gnome-control-center* and starting bluetoothd with sudo systemctl start bluetooth.service the *JBL GO 2* is not shown (pairing mode is activated). Only stopping bluetooth and starting it again, it’s showing up. Please find the btmon trace attached.

You may reply to this email to add a comment.

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

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

--- Comment #1 from Paul Menzel ([email protected]) ---

```
[Sa Dez 24 21:32:00 2022] calling  af_alg_init+0x0/0x1000 [af_alg] @ 41404
[Sa Dez 24 21:32:00 2022] NET: Registered PF_ALG protocol family
[Sa Dez 24 21:32:00 2022] initcall af_alg_init+0x0/0x1000 [af_alg] returned 0
after 1 usecs
[Sa Dez 24 21:32:00 2022] calling  algif_skcipher_init+0x0/0x1000
[algif_skcipher] @ 41405
[Sa Dez 24 21:32:00 2022] initcall algif_skcipher_init+0x0/0x1000
[algif_skcipher] returned 0 after 0 usecs
[Sa Dez 24 21:32:00 2022] calling  algif_hash_init+0x0/0x1000 [algif_hash] @
41411
[Sa Dez 24 21:32:00 2022] initcall algif_hash_init+0x0/0x1000 [algif_hash]
returned 0 after 0 usecs
[Sa Dez 24 21:32:00 2022] calling  crypto_cmac_module_init+0x0/0x1000 [cmac] @
41415
[Sa Dez 24 21:32:00 2022] initcall crypto_cmac_module_init+0x0/0x1000 [cmac]
returned 0 after 0 usecs
[Sa Dez 24 21:32:06 2022] calling  bnep_init+0x0/0xc0 [bnep] @ 41430
[Sa Dez 24 21:32:06 2022] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[Sa Dez 24 21:32:06 2022] Bluetooth: BNEP filters: protocol multicast
[Sa Dez 24 21:32:06 2022] Bluetooth: BNEP socket layer initialized
[Sa Dez 24 21:32:06 2022] initcall bnep_init+0x0/0xc0 [bnep] returned 0 after 6
usecs
[Sa Dez 24 21:32:06 2022] Bluetooth: MGMT ver 1.22
[Sa Dez 24 21:32:06 2022] calling  rfcomm_init+0x0/0xda [rfcomm] @ 41433
[Sa Dez 24 21:32:06 2022] Bluetooth: RFCOMM TTY layer initialized
[Sa Dez 24 21:32:06 2022] Bluetooth: RFCOMM socket layer initialized
[Sa Dez 24 21:32:06 2022] Bluetooth: RFCOMM ver 1.11
[Sa Dez 24 21:32:06 2022] initcall rfcomm_init+0x0/0xda [rfcomm] returned 0
after 87 usecs
[Sa Dez 24 21:34:42 2022] calling  uinput_misc_init+0x0/0x1000 [uinput] @ 41567
[Sa Dez 24 21:34:42 2022] initcall uinput_misc_init+0x0/0x1000 [uinput]
returned 0 after 112 usecs
[Sa Dez 24 21:34:42 2022] input: JBL GO 2 (AVRCP) as
/devices/virtual/input/input20
[Sa Dez 24 21:35:58 2022] input: JBL GO 2 (AVRCP) as
/devices/virtual/input/input21
[Sa Dez 24 21:36:10 2022] Bluetooth: hci0: Opcode 0x2005 failed: -22
[Sa Dez 24 21:36:10 2022] Bluetooth: hci0: Opcode 0x200b failed: -22
[Sa Dez 24 21:36:12 2022] Bluetooth: hci0: command 0x200b tx timeout
[Sa Dez 24 21:36:31 2022] input: JBL GO 2 (AVRCP) as
/devices/virtual/input/input22
[Sa Dez 24 21:48:47 2022] Bluetooth: hci0: Opcode 0x2005 failed: -22
[Sa Dez 24 21:48:47 2022] Bluetooth: hci0: Opcode 0x200b failed: -22
[Sa Dez 24 21:48:49 2022] Bluetooth: hci0: command 0x200b 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.