The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	linux-bluetooth@vger.kernel.org,
	Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
	Johan Hedberg <johan.hedberg@gmail.com>,
	Marcel Holtmann <marcel@holtmann.org>
Subject: Flood of "Unexpected continuation frame (len 0)" messages
Date: Thu, 30 May 2024 14:49:49 -0700	[thread overview]
Message-ID: <e92ecd6b-ce05-41fc-8c8a-588edef551ca@gmail.com> (raw)

Hiya,

My Sony MDR-ZX770BN headset connected to an USB Bluetooth adapter with 
the following characteristics:

         ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of 
BCM2046 Bluetooth)
         |__ Port 1: Dev 10, If 0, Class=Wireless, Driver=btusb, 12M
             ID 0a5c:2111 Broadcom Corp. ANYCOM Blue USB-UHE 200/250
         |__ Port 1: Dev 10, If 1, Class=Wireless, Driver=btusb, 12M
             ID 0a5c:2111 Broadcom Corp. ANYCOM Blue USB-UHE 200/250
         |__ Port 1: Dev 10, If 2, Class=Vendor Specific Class, Driver=, 12M
             ID 0a5c:2111 Broadcom Corp. ANYCOM Blue USB-UHE 200/250
         |__ Port 1: Dev 10, If 3, Class=Application Specific Interface, 
Driver=, 12M
             ID 0a5c:2111 Broadcom Corp. ANYCOM Blue USB-UHE 200/250

keeps flooding my kernel log with:

[2413092.567730] Bluetooth: Unexpected continuation frame (len 0)

Is there a quirk that should be set for this adapter? Audio playback 
over Bluetooth A2DP works just fine.

Thanks!
-- 
Florian

                 reply	other threads:[~2024-05-30 21:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=e92ecd6b-ce05-41fc-8c8a-588edef551ca@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox