From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 215528] Excessive logging from Intel Bluetooth "Bluetooth: hci0: sending frame failed" "hci0: urb 00000000xxxxxxxx submission failed (90)"
Date: Tue, 25 Jan 2022 10:35:10 +0000 [thread overview]
Message-ID: <bug-215528-62941-HlpYTF0JDJ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215528-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=215528
--- Comment #6 from Artem S. Tashkinov (aros@gmx.com) ---
Looks like I have to reboot, now I get hundreds of messages like this:
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 48
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 48
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 48
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 257
Bluetooth: hci0: SCO packet for unknown connection handle 257
Bluetooth: hci0: SCO packet for unknown connection handle 257
I'm kinda appalled by how logging in the BT module is handled. Has it ever
occurred to anyone that there's no need to dump hundreds of nearly exactly the
same messages?
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2022-01-25 10:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 21:55 [Bug 215528] New: Excessive logging from Intel Bluetooth "Bluetooth: hci0: sending frame failed" "hci0: urb 00000000xxxxxxxx submission failed (90)" bugzilla-daemon
2022-01-24 21:58 ` [Bug 215528] " bugzilla-daemon
2022-01-24 22:27 ` bugzilla-daemon
2022-01-25 10:15 ` bugzilla-daemon
2022-01-25 10:20 ` bugzilla-daemon
2022-01-25 10:35 ` bugzilla-daemon [this message]
2022-01-25 10:42 ` bugzilla-daemon
2022-01-25 15:06 ` bugzilla-daemon
2022-01-25 15:13 ` bugzilla-daemon
2022-02-15 11:32 ` bugzilla-daemon
2022-02-15 21:51 ` bugzilla-daemon
2022-02-16 22:50 ` bugzilla-daemon
2022-03-25 10:48 ` bugzilla-daemon
2022-03-25 18:24 ` bugzilla-daemon
2022-03-25 18:26 ` 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-215528-62941-HlpYTF0JDJ@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).