Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <0015e594-d888-f664-56c3-f4022286c736@hartkopp.net>
In-Reply-To: <0015e594-d888-f664-56c3-f4022286c736@hartkopp.net>
From:   Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Date:   Wed, 12 Jan 2022 12:55:56 -0800
Message-ID: <CABBYNZLLDip=q4VGP5Mx8fNrdxd8oHfzDJY9+XYxe11nLCU+yw@mail.gmail.com>
Subject: Re: Latest Linux tree (merge window): BT mouse does not work
To:     Oliver Hartkopp <socketcan@hartkopp.net>
Cc:     "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

Hi Oliver,

On Wed, Jan 12, 2022 at 12:07 PM Oliver Hartkopp <socketcan@hartkopp.net> wrote:
>
> 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

These are vendor events which I don't think were being handled anyway,
so it is likely something else that is preventing it to work.

> 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

Can you attach the bluetoothd and btmon logs when you attempt to
connect the mouse, at least for the logs above it does seem the
firmware is being loaded properly.

>


-- 
Luiz Augusto von Dentz