Skip to contentSkip to conversation

Kernel regularly logs: Bluetooth: hci0: last event is not cmd complete (0x0f)

Bug 198699 [email protected] 1 participant 12 messages Oct 22, 2018 – Mar 27, 2019 1 message not in the archive Bluetooth drivers

lore
Share & tools
lore

[email protected]

author
#1 lore raw
In reply to a message not in the archive

https://bugzilla.kernel.org/show_bug.cgi?id=198699

Matthias Pritschet ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------

                 CC|                            |bugzilla.kernel.org@pritsch
                   |                            |et.eu

--- Comment #15 from Matthias Pritschet ([email protected]) --- 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
Quoted 1 line

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".

Signature · 2 lines
You are receiving this mail because:
You are the assignee for the bug.
author
#2 lore raw
In reply to a message not in the archive

https://bugzilla.kernel.org/show_bug.cgi?id=198699

Nadal Gonzalo García Zavala ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #16 from Nadal Gonzalo García Zavala ([email protected]) --- Same here with rtl8723de 4.18.16 latest rtl_bt firmware.

Pairing fails with an Edifier r2000db speaker.
I'm not sure, but i think pairing with an android device worked.

On failure bluezctl says something like connect attempt failed.

Signature · 2 lines
You are receiving this mail because:
You are the assignee for the bug.
author
#3 lore raw
In reply to a message not in the archive

https://bugzilla.kernel.org/show_bug.cgi?id=198699

--- Comment #17 from Nadal Gonzalo García Zavala ([email protected]) --- dmesg
https://paste.pound-python.org/raw/Z0A2xHsgA3ePo8rmIL7L/

lspci -vvv
https://paste.pound-python.org/raw/9mPWBx1BJfar6yROQOVu/

lsmod
https://paste.pound-python.org/raw/TASuig0MdPwOmWiEUWeh/

sha256sum /lib/firmware/rtl_bt/rtl8723d_*
https://paste.pound-python.org/raw/XkFQ6c6f9HpqmUhCEJOn/

uname -a
https://paste.pound-python.org/raw/y7YgUPIhCHGnnUipGG9q/

Signature · 2 lines
You are receiving this mail because:
You are the assignee for the bug.
author
#5 lore raw
In reply to a message not in the archive

https://bugzilla.kernel.org/show_bug.cgi?id=198699

Jonathan Dunlap ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #19 from Jonathan Dunlap ([email protected]) ---
Same issue here with Fedora 28 and 29, using Gigabyte x470 Gaming 7 motherboard with an Intel Wifi and Bluetooth chipset.

Signature · 2 lines
You are receiving this mail because:
You are the assignee for the bug.
author
#6 lore raw
In reply to a message not in the archive

https://bugzilla.kernel.org/show_bug.cgi?id=198699

Oleksandr Pylypenko ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #20 from Oleksandr Pylypenko ([email protected]) --- Confirming the issue on Dell Vostro 5468 with Intel Bluetooth adapter (8087:0a2a), OS Ubuntu 18.04.1, kernel version. 4.15.0-36-generic. Audio output appears to clog and tear second after log line shows in dmesg. This goes for 4-5 seconds, after which playback continues normally for another ~10 seconds.

Signature · 2 lines
You are receiving this mail because:
You are the assignee for the bug.
author
#7 lore raw
In reply to a message not in the archive

https://bugzilla.kernel.org/show_bug.cgi?id=198699

Jakub Jankiewicz ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #21 from Jakub Jankiewicz ([email protected]) ---
I also have the issue in Fedora 27 on Dell Inspiron 15 5570 with Qualcomm bluetooth (hciconfig -a hci0 shows that)

But in my case the sound from bluetooth speakers JBL Flip 4 is fine. I dind't experience any issues, only there are lot of messages in dmesg logs.

Signature · 2 lines
You are receiving this mail because:
You are the assignee for the bug.
author
#8 lore raw
In reply to a message not in the archive

https://bugzilla.kernel.org/show_bug.cgi?id=198699

Alex ARNAUD ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #22 from Alex ARNAUD ([email protected]) ---
I'm experiencing the same issue on Debian 8 "Jessie" with a backported Kernel 4.18 and latest Intel Firmware for my Wireless card.

I'm testing on a Clevo compute with Intel Corporation Dual Band Wireless-AC 3168NGW.

Let me know if I can help, it's really annoying, I couldn't make the Bluetooth working on this computer.

Best regards,
Alex.

Signature · 2 lines
You are receiving this mail because:
You are the assignee for the bug.
author
#9 lore raw
In reply to a message not in the archive

https://bugzilla.kernel.org/show_bug.cgi?id=198699

Ishan Kulkarni ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #23 from Ishan Kulkarni ([email protected]) --- Observing the issue on Fedora 29 Cinnamon. I have Lenovo T440P laptop on which I am trying to connect my Bluetooth headsets (Sony MDR-XB650BT).

The Bluetooth is failing to even detect the headsets. At the same time, it can detect my smart bands, mobile phones, other laptops etc. The same headphones connect correctly on my Windows laptop.

In dmesg, I can see the messages as :

[717817.195781] Bluetooth: hci0: read Intel version: 3707100180012d0d00
[717817.198527] Bluetooth: hci0: Intel Bluetooth firmware file:
intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq
[717817.394926] Bluetooth: hci0: Intel firmware patch completed and activated
[717818.100820] Bluetooth: hci0: last event is not cmd complete (0x0f)
[717849.196840] Bluetooth: hci0: last event is not cmd complete (0x0f)
[717906.393910] Bluetooth: hci0: last event is not cmd complete (0x0f)
[717922.201017] Bluetooth: hci0: last event is not cmd complete (0x0f)
Signature · 2 lines
You are receiving this mail because:
You are the assignee for the bug.
author
#10 lore raw
In reply to a message not in the archive

https://bugzilla.kernel.org/show_bug.cgi?id=198699

Johan Hedberg ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #24 from Johan Hedberg ([email protected]) --- The "last event is not cmd complete" is in most/all cases a red herring, so please don't focus on that. There's a patch in mainline that will remove it for all valid situations (i.e. when the command completed with command status instead of command complete):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1629db9c75342325868243d6bca5853017d91cf8

It seems like this issue has probably lots of different bugs mixed into it, all incorrectly attributing themselves to this misleading warning message, when in fact there's something unrelated going wrong. Those that are experiencing issues even after applying the patch I referred to, please open new issues, especially if the "last event is not cmd complete" message goes away for you with the patch. This one can probably be closed since the misleading message should now be gone.

Signature · 2 lines
You are receiving this mail because:
You are the assignee for the bug.
author
#11 lore raw
In reply to a message not in the archive

https://bugzilla.kernel.org/show_bug.cgi?id=198699

Paul Menzel ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------

                 CC|                            |pmenzel+bugzilla.kernel.org
                   |                            |@molgen.mpg.de

--- Comment #25 from Paul Menzel ([email protected]) --- Should this be added to the stable series too?

Signature · 2 lines
You are receiving this mail because:
You are the assignee for the bug.
author
#12 lore raw
In reply to a message not in the archive

https://bugzilla.kernel.org/show_bug.cgi?id=198699

Daniel van Vugt ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------

                 CC|                            |[email protected]
                   |                            |om

--- Comment #26 from Daniel van Vugt ([email protected]) --- Comment 24 suggests to me that this bug should be closed (?). Because it seems to eliminate the possibility of the message appearing with (0x0f).

Signature · 2 lines
You are receiving this mail because:
You are the assignee for the bug.