All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 215713] New: New (useless?) warning messages from BlueTooth in kernel 5.17
Date: Mon, 21 Mar 2022 12:55:16 +0000	[thread overview]
Message-ID: <bug-215713-62941@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 215713
           Summary: New (useless?) warning messages from BlueTooth in
                    kernel 5.17
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.17
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: low
          Priority: P1
         Component: Bluetooth
          Assignee: linux-bluetooth@vger.kernel.org
          Reporter: aros@gmx.com
        Regression: No

I've just upgraded from 5.15.30 to 5.17 and now upon pairing my BT headphones I
see brand new warning messages I've never seen before:

Bluetooth: hci0: unexpected event 0xff length: 25 > 0
Bluetooth: hci0: unexpected event 0xff length: 4 > 0

I wonder if it's a kernel bug or it's a valid message. 

The BT headphones work without any issues though.

The device is 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter.

# lsmod | grep bt
btusb                  40960  0
btbcm                  20480  1 btusb
btintel                32768  1 btusb
bluetooth             471040  52 btintel,btbcm,bnep,btusb,rfcomm

# dmesg -t | egrep -i "bt|blue" 
Bluetooth: Core ver 2.22
NET: Registered PF_BLUETOOTH protocol family
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO socket layer initialized
usbcore: registered new interface driver btusb
Bluetooth: hci0: Found device firmware: intel/ibt-18-16-1.sfi
Bluetooth: hci0: Boot Address: 0x40800
Bluetooth: hci0: Firmware Version: 86-46.21
Bluetooth: hci0: Firmware already loaded
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: BNEP socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.11
Bluetooth: hci0: unexpected event 0xff length: 25 > 0
Bluetooth: hci0: unexpected event 0xff length: 4 > 0

-- 
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-03-21 12:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-21 12:55 bugzilla-daemon [this message]
2022-03-21 12:55 ` [Bug 215713] New (useless?) warning messages from BlueTooth in kernel 5.17 bugzilla-daemon
2022-03-22  0:35 ` bugzilla-daemon
2022-03-22 18:15 ` bugzilla-daemon
2022-03-22 19:51 ` bugzilla-daemon
2022-03-23 12:24 ` bugzilla-daemon

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-215713-62941@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.