From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 215659] New: "Unexpected continuation frame" spam in kernel log
Date: Fri, 04 Mar 2022 09:53:07 +0000 [thread overview]
Message-ID: <bug-215659-62941@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=215659
Bug ID: 215659
Summary: "Unexpected continuation frame" spam in kernel log
Product: Drivers
Version: 2.5
Kernel Version: 5.17
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Bluetooth
Assignee: linux-bluetooth@vger.kernel.org
Reporter: smurf@smurf.noris.de
Regression: No
My kernel log gets spammed by these messages:
Mär 04 10:46:18 s-asi kernel: Bluetooth: Unexpected continuation frame (len 0)
Mär 04 10:46:18 s-asi kernel: Bluetooth: Unexpected continuation frame (len 0)
Mär 04 10:46:18 s-asi kernel: Bluetooth: Unexpected continuation frame (len 0)
Mär 04 10:46:19 s-asi kernel: Bluetooth: Unexpected continuation frame (len 0)
Mär 04 10:46:19 s-asi kernel: Bluetooth: Unexpected continuation frame (len 0)
Mär 04 10:46:19 s-asi kernel: Bluetooth: Unexpected continuation frame (len 0)
Mär 04 10:46:19 s-asi kernel: Bluetooth: Unexpected continuation frame (len 0)
Mär 04 10:46:19 s-asi kernel: Bluetooth: Unexpected continuation frame (len 0)
Please skip when len==0 and/or rate limit
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2022-03-04 9:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 9:53 bugzilla-daemon [this message]
2022-03-04 9:53 ` [Bug 215659] "Unexpected continuation frame" spam in kernel log 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-215659-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox