From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 215528] New: Excessive logging from Intel Bluetooth "Bluetooth: hci0: sending frame failed" "hci0: urb 00000000xxxxxxxx submission failed (90)"
Date: Mon, 24 Jan 2022 21:55:43 +0000 [thread overview]
Message-ID: <bug-215528-62941@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=215528
Bug ID: 215528
Summary: Excessive logging from Intel Bluetooth "Bluetooth:
hci0: sending frame failed" "hci0: urb
00000000xxxxxxxx submission failed (90)"
Product: Drivers
Version: 2.5
Kernel Version: 5.15.16
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: Bluetooth
Assignee: linux-bluetooth@vger.kernel.org
Reporter: aros@gmx.com
Regression: No
Sometimes bluetooth here fails spectacularly for no reasons and I get literally
thousands of lines in dmesg log.
PLEASE implement rate limiting or something.
$ journalctl -b | grep hci0 | wc -l
4257
This is all within three seconds!
...
Bluetooth: hci0: urb 000000001aab8aa3 submission failed (90)
Bluetooth: hci0: sending frame failed (-90)
Bluetooth: hci0: urb 000000001aab8aa3 submission failed (90)
Bluetooth: hci0: sending frame failed (-90)
Bluetooth: hci0: urb 000000001aab8aa3 submission failed (90)
Bluetooth: hci0: sending frame failed (-90)
Bluetooth: hci0: urb 000000001aab8aa3 submission failed (90)
Bluetooth: hci0: sending frame failed (-90)
Bluetooth: hci0: urb 000000001aab8aa3 submission failed (90)
Bluetooth: hci0: sending frame failed (-90)
Bluetooth: hci0: urb 000000001aab8aa3 submission failed (90)
Bluetooth: hci0: sending frame failed (-90)
Bluetooth: hci0: urb 000000001aab8aa3 submission failed (90)
Bluetooth: hci0: sending frame failed (-90)
Bluetooth: hci0: urb 000000001aab8aa3 submission failed (90)
Bluetooth: hci0: sending frame failed (-90)
Bluetooth: hci0: urb 000000001aab8aa3 submission failed (90)
Bluetooth: hci0: sending frame failed (-90)
Bluetooth: hci0: urb 000000001aab8aa3 submission failed (90)
Bluetooth: hci0: sending frame failed (-90)
Bluetooth: hci0: urb 000000001aab8aa3 submission failed (90)
Bluetooth: hci0: sending frame failed (-90)
Bluetooth: hci0: urb 000000001aab8aa3 submission failed (90)
Bluetooth: hci0: sending frame failed (-90)
Bluetooth: hci0: urb 000000001aab8aa3 submission failed (90)
Bluetooth: hci0: sending frame failed (-90)
Bluetooth: hci0: urb 000000001aab8aa3 submission failed (90)
Bluetooth: hci0: sending frame failed (-90)
Bluetooth: hci0: urb 000000001aab8aa3 submission failed (90)
Bluetooth: hci0: sending frame failed (-90)
Bluetooth: hci0: urb 000000001aab8aa3 submission failed (90)
Bluetooth: hci0: sending frame failed (-90)
Bluetooth: hci0: urb 000000001aab8aa3 submission failed (90)
Bluetooth: hci0: sending frame failed (-90)
Bluetooth: hci0: urb 000000001aab8aa3 submission failed (90)
Bluetooth: hci0: sending frame failed (-90)
...
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
Bluetooth: hci0: Found device firmware: intel/ibt-18-16-1.sfi
Bluetooth: hci0: Boot Address: 0x40800
Bluetooth: hci0: Firmware Version: 207-35.21
Bluetooth: hci0: Firmware already loaded
The device is: Bus 003 Device 002: ID 8087:0025 Intel Corp. Wireless-AC 9260
Bluetooth Adapter
--
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-01-25 2:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 21:55 bugzilla-daemon [this message]
2022-01-24 21:58 ` [Bug 215528] Excessive logging from Intel Bluetooth "Bluetooth: hci0: sending frame failed" "hci0: urb 00000000xxxxxxxx submission failed (90)" 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
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@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).