All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oliver Hartkopp <socketcan@hartkopp.net>
To: linux-bluetooth@vger.kernel.org
Subject: Latest Linux tree (merge window): BT mouse does not work
Date: Tue, 11 Jan 2022 20:56:40 +0100	[thread overview]
Message-ID: <0015e594-d888-f664-56c3-f4022286c736@hartkopp.net> (raw)

Hi all,

after upgrading from Linus' tree 5.16.0-rc7-00108-g800829388818 to the 
current merge window version 5.16.0-05432-g6f38be8f2ccd my BT mouse is 
not working anymore.

I now get two new error messages:

	hci0: unexpected event 0xff length: 5 > 0

and

	hci0: unexpected event 0xff length: 7 > 0

Any idea? Any new firmware required?

Best regards,
Oliver

[    8.790201] Bluetooth: Core ver 2.22
[    8.847435] Bluetooth: hci0: Bootloader revision 0.0 build 26 week 38 
2015
[    8.853022] Bluetooth: hci0: Device revision is 16
[    8.853025] Bluetooth: hci0: Secure boot is enabled
[    8.853026] Bluetooth: hci0: OTP lock is enabled
[    8.853027] Bluetooth: hci0: API lock is enabled
[    8.853028] Bluetooth: hci0: Debug lock is disabled
[    8.853028] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[    8.855879] Bluetooth: hci0: Found device firmware: intel/ibt-12-16.sfi

[    9.422098] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    9.423532] Bluetooth: BNEP filters: protocol multicast
[    9.423537] Bluetooth: BNEP socket layer initialized
[    9.439281] iwlwifi 0000:01:00.0 wlp1s0: renamed from wlan0
[   10.391796] Bluetooth: hci0: Waiting for firmware download to complete
[   10.392752] Bluetooth: hci0: unexpected event 0xff length: 5 > 0
[   10.392789] Bluetooth: hci0: Firmware loaded in 1492456 usecs
[   10.392985] Bluetooth: hci0: Waiting for device to boot
[   10.404942] Bluetooth: hci0: unexpected event 0xff length: 7 > 0
[   10.404971] Bluetooth: hci0: Device booted in 11747 usecs
[   10.405416] Bluetooth: hci0: Found Intel DDC parameters: 
intel/ibt-12-16.ddc
[   10.407835] Bluetooth: hci0: Applying Intel DDC parameters completed
[   10.408848] Bluetooth: hci0: Firmware revision 0.1 build 50 week 12 2019
[   10.468582] NET: Registered PF_ALG protocol family
[   11.277319] Bluetooth: RFCOMM TTY layer initialized
[   11.277343] Bluetooth: RFCOMM socket layer initialized
[   11.277367] Bluetooth: RFCOMM ver 1.11



             reply	other threads:[~2022-01-11 20:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-11 19:56 Oliver Hartkopp [this message]
2022-01-12 20:55 ` Latest Linux tree (merge window): BT mouse does not work Luiz Augusto von Dentz
2022-01-13  7:41   ` Oliver Hartkopp

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=0015e594-d888-f664-56c3-f4022286c736@hartkopp.net \
    --to=socketcan@hartkopp.net \
    --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.