linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 203753] Bluetooth: hci0: advertising data len corrected
Date: Fri, 26 Feb 2021 22:45:08 +0000	[thread overview]
Message-ID: <bug-203753-62941-mTKp9FHhOy@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-203753-62941@https.bugzilla.kernel.org/>

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

Priit O. (priit@ww.ee) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |priit@ww.ee

--- Comment #6 from Priit O. (priit@ww.ee) ---
uname -a : Linux Zen 5.10.15-1-MANJARO #1 SMP PREEMPT Wed Feb 10 10:42:47 UTC
2021 x86_64 GNU/Linux

$ dmesg -W
[106376.949553] Bluetooth: hci0: advertising data len corrected 31 -> 16
[106378.833756] Bluetooth: hci0: advertising data len corrected 31 -> 16
[106379.909741] Bluetooth: hci0: advertising data len corrected 31 -> 16
[106380.195521] Bluetooth: hci0: advertising data len corrected 31 -> 16
[106380.346552] Bluetooth: hci0: advertising data len corrected 31 -> 16
[106380.528606] Bluetooth: hci0: advertising data len corrected 31 -> 16
[106380.685527] Bluetooth: hci0: advertising data len corrected 31 -> 16
[106380.843539] Bluetooth: hci0: advertising data len corrected 31 -> 16
[106381.118745] Bluetooth: hci0: advertising data len corrected 31 -> 16
[106381.449509] Bluetooth: hci0: advertising data len corrected 31 -> 16
[106382.544736] Bluetooth: hci0: advertising data len corrected 31 -> 16
[106382.978739] Bluetooth: hci0: advertising data len corrected 31 -> 16
[106385.310497] bt_err_ratelimited: 4 callbacks suppressed
[106385.310499] Bluetooth: hci0: advertising data len corrected 31 -> 16
[106385.800722] Bluetooth: hci0: advertising data len corrected 31 -> 16
[106387.169452] Bluetooth: hci0: advertising data len corrected 31 -> 16
[106387.810468] Bluetooth: hci0: advertising data len corrected 31 -> 16
[106388.250687] Bluetooth: hci0: advertising data len corrected 31 -> 16
[106388.739449] Bluetooth: hci0: advertising data len corrected 31 -> 16
[106389.175451] Bluetooth: hci0: advertising data len corrected 31 -> 16
[106389.948625] Bluetooth: hci0: advertising data len corrected 31 -> 16
[106390.103438] Bluetooth: hci0: advertising data len corrected 31 -> 16
[106390.441649] Bluetooth: hci0: advertising data len corrected 31 -> 16
[106390.599420] Bluetooth: hci0: advertising data len corrected 31 -> 16

it just continiously spams this, several messages in a second.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2021-02-26 22:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-203753-62941@https.bugzilla.kernel.org/>
2020-12-09  3:27 ` [Bug 203753] Bluetooth: hci0: advertising data len corrected bugzilla-daemon
2020-12-09 12:47 ` bugzilla-daemon
2021-02-17 17:25 ` bugzilla-daemon
2021-02-26 22:45 ` bugzilla-daemon [this message]
2021-04-23 17:44 ` bugzilla-daemon
2021-05-21  8:15 ` bugzilla-daemon
2021-06-28 10:47 ` bugzilla-daemon
2021-12-04  0:35 ` bugzilla-daemon
2022-09-21 12:57 ` 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-203753-62941-mTKp9FHhOy@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.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;
as well as URLs for NNTP newsgroup(s).