All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 216845] JBL GO 2 only recognized after restarting `bluetoothd`
Date: Sat, 24 Dec 2022 22:03:30 +0000	[thread overview]
Message-ID: <bug-216845-62941-ijCTGU8hcU@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216845-62941@https.bugzilla.kernel.org/>

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

--- Comment #1 from Paul Menzel (pmenzel+bugzilla.kernel.org@molgen.mpg.de) ---
```
[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.

      reply	other threads:[~2022-12-24 22:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-24 22:01 [Bug 216845] New: JBL GO 2 only recognized after restarting `bluetoothd` bugzilla-daemon
2022-12-24 22:03 ` bugzilla-daemon [this message]

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-216845-62941-ijCTGU8hcU@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.