From: mly19891201 <mly19891201@163.com>
To: linux-bluetooth@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: [Bluetooth] BUG: New Opcode sent before the previous one completed
Date: Mon, 9 Jun 2025 03:02:26 +0800 (CST) [thread overview]
Message-ID: <5d20a61d.298e.19750ec34ab.Coremail.mly19891201@163.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2253 bytes --]
Hello.
System: 6.12.31-gentoo-dist
Bluetooth adapter: UGREEN BT5.4 CM748.
Bluetooth Chip: Barrot.
ID 33fa:0010
System log:
2025/6/8 00:39 kernel usb 5-4: new full-speed USB device number 5 using xhci_hcd
2025/6/8 00:39 kernel usb 5-4: New USB device found, idVendor=33fa, idProduct=0010, bcdDevice=88.91
2025/6/8 00:39 kernel usb 5-4: New USB device strings: Mfr=0, Product=2, SerialNumber=0
2025/6/8 00:39 kernel usb 5-4: Product: UGREEN BT5.4 Adapter
2025/6/8 00:39 systemd Starting Load/Save RF Kill Switch Status...
2025/6/8 00:39 systemd Reached target Bluetooth.
2025/6/8 00:39 systemd Reached target Bluetooth Support.
2025/6/8 00:39 systemd Started Load/Save RF Kill Switch Status.
2025/6/8 00:39 kernel Bluetooth: hci0: Opcode 0x1005 failed: -110
2025/6/8 00:39 kernel Bluetooth: hci0: command 0x1005 tx timeout
2025/6/8 00:39 systemd systemd-rfkill.service: Deactivated successfully.
Wireshark (Email attachments):
120 16.079306 host 5.4.1 USB 64 URB_INTERRUPT in
121 16.079332 host controller HCI_CMD 68 Sent Read Local Extended Features
122 16.087475 5.4.0 host HCI_USB 64 Rcvd
123 16.096297 5.4.1 host HCI_USB 81 Rcvd Fragment
124 16.096303 host 5.4.1 USB 64 URB_INTERRUPT in
125 16.096329 host controller HCI_CMD 67 Sent Read Buffer Size
126 16.099104 5.4.0 host HCI_USB 64 Rcvd
127 16.099303 controller host HCI_EVT 77 Rcvd Command Complete (Read Local Extended Features)
128 16.099305 host 5.4.1 USB 64 URB_INTERRUPT in
129 18.221695 5.4.1 host USB 64 URB_INTERRUPT in
130 18.221726 5.4.2 host USB 64 URB_BULK in
131 18.221783 5.4.2 host USB 64 URB_BULK in
132 20.721814 host 5.1.0 USBHUB 64 SET_FEATURE Request [Port 4: PORT_SUSPEND]
133 20.734946 5.1.0 host USBHUB 64 SET_FEATURE Response [Port 4: PORT_SUSPEND]
134 20.748294 5.1.1 host USB 64 URB_INTERRUPT in
Line 121 sent command, the response size 17, larger than maxsize, so we get line 123 and line 127.
After line 123, possibly, hci system get the complete signal, new command sent in line 125. this command never get response.
I patch my kernel source to cancel 'hci_read_local_ext_features' in the hci_init2[] and hci_init3[] in file hci_sync.c.
It worked.
[-- Attachment #1.2: Type: text/html, Size: 2806 bytes --]
[-- Attachment #2: wireshark_log.pcapng --]
[-- Type: application/octet-stream, Size: 14332 bytes --]
reply other threads:[~2025-06-08 19:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5d20a61d.298e.19750ec34ab.Coremail.mly19891201@163.com \
--to=mly19891201@163.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®