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:20:18 +0000 [thread overview]
Message-ID: <bug-215528-62941-HyHOiJcb5a@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 #5 from Artem S. Tashkinov (aros@gmx.com) ---
dmesg will have to wait, I don't want to reboot yet.
After all these errors I've updated the firmware just in case:
...
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)
usbcore: deregistering interface driver btusb
usbcore: registered new interface driver btusb
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
show_signal_msg: 20 callbacks suppressed
Bluetooth: hci0: Ignoring error of Inquiry Cancel command
usbcore: deregistering interface driver btusb
Bluetooth: hci0: urb 000000009344aaa5 failed to resubmit (2)
usbcore: registered new interface driver btusb
Bluetooth: hci0: Found device firmware: intel/ibt-18-16-1.sfi
Bluetooth: hci0: Boot Address: 0x40800
Bluetooth: hci0: Firmware Version: 86-46.21
usb 3-5: USB disconnect, device number 2
Bluetooth: hci0: command 0xfc01 tx timeout
usbcore: deregistering interface driver btusb
Bluetooth: hci0: FW download error recovery failed (-110)
usb 3-5: new full-speed USB device number 4 using xhci_hcd
usb 3-5: New USB device found, idVendor=8087, idProduct=0025, bcdDevice= 0.02
usb 3-5: New USB device strings: Mfr=0, Product=0, SerialNumber=0
usbcore: registered new interface driver btusb
Bluetooth: hci0: Bootloader revision 0.1 build 42 week 52 2015
Bluetooth: hci0: Device revision is 2
Bluetooth: hci0: Secure boot is enabled
Bluetooth: hci0: OTP lock is enabled
Bluetooth: hci0: API lock is enabled
Bluetooth: hci0: Debug lock is disabled
Bluetooth: hci0: Minimum firmware build 1 week 10 2014
Bluetooth: hci0: Found device firmware: intel/ibt-18-16-1.sfi
Bluetooth: hci0: Waiting for firmware download to complete
Bluetooth: hci0: Firmware loaded in 1142406 usecs
Bluetooth: hci0: Waiting for device to boot
Bluetooth: hci0: Device booted in 14837 usecs
Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-18-16-1.ddc
Bluetooth: hci0: Applying Intel DDC parameters completed
Bluetooth: hci0: Firmware revision 0.1 build 86 week 46 2021
usbcore: deregistering interface driver btusb
usbcore: registered new interface driver btusb
Bluetooth: hci0: Found device firmware: intel/ibt-18-16-1.sfi
Bluetooth: hci0: Boot Address: 0x40800
Bluetooth: hci0: Firmware Version: 86-46.21
Bluetooth: hci0: Firmware already loaded
--
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:23 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 [this message]
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-HyHOiJcb5a@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).