From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 198699] Kernel regularly logs: Bluetooth: hci0: last event is not cmd complete (0x0f)
Date: Mon, 22 Oct 2018 12:43:41 +0000 [thread overview]
Message-ID: <bug-198699-62941-NacUFtsZlQ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-198699-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=198699
Matthias Pritschet (bugzilla.kernel.org@pritschet.eu) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bugzilla.kernel.org@pritsch
| |et.eu
--- Comment #15 from Matthias Pritschet (bugzilla.kernel.org@pritschet.eu) ---
This Bug seems to affect even basic HCI functionality:
"hcitool inq" is never returning in my case. dmesg gives me said error message.
I have tried two different USB-Bluetooth Dongles:
[ ] usb 2-2: New USB device found, idVendor=04b4, idProduct=f901, bcdDevice=
1.12
[ ] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ ] usb 2-2: Product: CYW20704A2
[ ] usb 2-2: Manufacturer: Cypress Semi
[ ] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ ] usb 2-2: New USB device found, idVendor=0a12, idProduct=0001,
bcdDevice=88.91
[ ] usb 2-2: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[ ] usb 2-2: Product: CSR8510 A10
[ ] Bluetooth: hci0: last event is not cmd complete (0x0f)
Also btmon/hcidump just seem to freeze:
< HCI Command: Inquiry (0x01|0x0001) plen 5 #1 [hci0] 10.211282
Access code: 0x9e8b33 (General Inquiry)
Length: 10.24s (0x08)
Num responses: 0
> HCI Event: Command Status (0x0f) plen 4 #2 [hci0] 10.314299
Inquiry (0x01|0x0001) ncmd 1
Status: Success (0x00)
The only way to recover from this state is to issue a "hciconfig hci0 reset".
--
You are receiving this mail because:
You are the assignee for the bug.
next parent reply other threads:[~2018-10-22 12:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-198699-62941@https.bugzilla.kernel.org/>
2018-10-22 12:43 ` bugzilla-daemon [this message]
2018-10-27 4:08 ` [Bug 198699] Kernel regularly logs: Bluetooth: hci0: last event is not cmd complete (0x0f) bugzilla-daemon
2018-10-27 4:13 ` bugzilla-daemon
2018-10-27 4:17 ` bugzilla-daemon
2018-10-30 19:15 ` bugzilla-daemon
2018-11-04 12:00 ` bugzilla-daemon
2018-11-12 14:22 ` bugzilla-daemon
2018-11-12 17:34 ` bugzilla-daemon
2019-01-18 6:31 ` bugzilla-daemon
2019-01-18 7:22 ` bugzilla-daemon
2019-02-01 21:28 ` bugzilla-daemon
2019-03-27 2:10 ` 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-198699-62941-NacUFtsZlQ@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).