Bug 198699 - Kernel regularly logs: Bluetooth: hci0: last event is not cmd complete (0x0f)
Summary: Kernel regularly logs: Bluetooth: hci0: last event is not cmd complete (0x0f)
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: Bluetooth (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: linux-bluetooth@vger.kernel.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-02-06 17:21 UTC by Cristian Aravena Romero
Modified: 2019-02-01 21:28 UTC (History)
31 users (show)

See Also:
Kernel Version: 4.15.1-041501-generic
Tree: Mainline
Regression: No


Attachments
dmesg_4.15.1-041501-generic.txt (58.79 KB, text/plain)
2018-02-06 17:21 UTC, Cristian Aravena Romero
Details
#lspci -vvnn (20.87 KB, text/plain)
2018-02-06 17:24 UTC, Cristian Aravena Romero
Details
bluetooth pcap during pair (626 bytes, application/vnd.tcpdump.pcap)
2018-03-12 19:57 UTC, Bernd Buschinski
Details
imagea50acc.PNG (5.91 KB, image/png)
2018-05-13 13:40 UTC, Danny
Details
image1de678.PNG (4.89 KB, image/png)
2018-05-13 13:40 UTC, Danny
Details

Description Cristian Aravena Romero 2018-02-06 17:21:41 UTC
Created attachment 274023 [details]
dmesg_4.15.1-041501-generic.txt

Hello,

dmesg:
[16913.264855] Bluetooth: hci0: last event is not cmd complete (0x0f)
[16929.268759] Bluetooth: hci0: last event is not cmd complete (0x0f)
[16945.268709] Bluetooth: hci0: last event is not cmd complete (0x0f)
[16961.269687] Bluetooth: hci0: last event is not cmd complete (0x0f)
[16977.268584] Bluetooth: hci0: last event is not cmd complete (0x0f)
[16993.271505] Bluetooth: hci0: last event is not cmd complete (0x0f)
[17009.270469] Bluetooth: hci0: last event is not cmd complete (0x0f)
[17025.271301] Bluetooth: hci0: last event is not cmd complete (0x0f)
[17041.272302] Bluetooth: hci0: last event is not cmd complete (0x0f)
[17057.272169] Bluetooth: hci0: last event is not cmd complete (0x0f)
[17073.273102] Bluetooth: hci0: last event is not cmd complete (0x0f)
[17089.274086] Bluetooth: hci0: last event is not cmd complete (0x0f)
[17105.275068] Bluetooth: hci0: last event is not cmd complete (0x0f)
[17121.272849] Bluetooth: hci0: last event is not cmd complete (0x0f)
[17137.273809] Bluetooth: hci0: last event is not cmd complete (0x0f)
[17153.272709] Bluetooth: hci0: last event is not cmd complete (0x0f)
[17169.272609] Bluetooth: hci0: last event is not cmd complete (0x0f)
[17185.274537] Bluetooth: hci0: last event is not cmd complete (0x0f)
[17201.273468] Bluetooth: hci0: last event is not cmd complete (0x0f)
[17217.273402] Bluetooth: hci0: last event is not cmd complete (0x0f)
[17233.275352] Bluetooth: hci0: last event is not cmd complete (0x0f)
[17249.275230] Bluetooth: hci0: last event is not cmd complete (0x0f)
[17265.276188] Bluetooth: hci0: last event is not cmd complete (0x0f)
[17281.276125] Bluetooth: hci0: last event is not cmd complete (0x0f)
[17297.278061] Bluetooth: hci0: last event is not cmd complete (0x0f)
[17313.277950] Bluetooth: hci0: last event is not cmd complete (0x0f)
[17329.276863] Bluetooth: hci0: last event is not cmd complete (0x0f)
[17345.275835] Bluetooth: hci0: last event is not cmd complete (0x0f)
[17361.278702] Bluetooth: hci0: last event is not cmd complete (0x0f)

Regards,
--
Cristian
Comment 1 Cristian Aravena Romero 2018-02-06 17:24:54 UTC
Created attachment 274025 [details]
#lspci -vvnn
Comment 2 Cristian Aravena Romero 2018-02-09 23:38:57 UTC
Hello,

Open bug in launchpad.net
https://bugs.launchpad.net/bugs/1748565

Regards,
--
Cristian
Comment 3 Bernd Buschinski 2018-03-12 19:56:24 UTC
Hello,

I have the same issue, reproduce able with a cheap Wii controller.
It works fine with the Wii/Wii U itself but refuses to pair with my Bluetooth dongle:

"Broadcom Corp. BCM20702A0 Bluetooth 4.0"
(not intel)

All I get is
"Bluetooth: hci0: last event is not cmd complete (0x0f)"


kernel: 4.15.8

I will attach a pcap which hopefully shows what is going on.
Comment 4 Bernd Buschinski 2018-03-12 19:57:11 UTC
Created attachment 274695 [details]
bluetooth pcap during pair
Comment 5 Stefan Assmann 2018-03-14 07:57:03 UTC
Seeing similar messages with 4.16-rc4
[   17.617214] Bluetooth: hci0: BCM: chip id 90
[   17.620448] Bluetooth: hci0: BCM: features 0x0f
[   17.626236] Bluetooth: hci0: BCM4324B5
[   18.320710] Bluetooth: hci0: BCM (002.006.006) build 1170
[...]
[   59.373938] Bluetooth: hci0: last event is not cmd complete (0x0f)
Comment 6 Danny 2018-05-01 10:12:30 UTC
I've the same issue with Airconsole Pro 2.0 

[ 5939.146759] Bluetooth: hci0: last event is not cmd complete (0x0f)
Comment 7 David 2018-05-13 13:33:44 UTC
For me it happens in my laptop with a ath3k bluetooth:

(rmmod and modprobe btusb)

[ 6660.407324] usbcore: registered new interface driver btusb
[ 6696.003058] Bluetooth: hci0: last event is not cmd complete (0x0f)

When trying to discover a cheap Bluetooth audio headphones, however they work in Android mobile, but is not discoverable in my laptop due to this message.
Comment 8 Danny 2018-05-13 13:40:18 UTC
Created attachment 275955 [details]
imagea50acc.PNG

Hartelijk dank voor uw email-bericht.

Ik ben afwezig t/m maandag 28 mei 2018 en heb beperkt toegang tot mijn mail.
Voor dringende zaken kunt u contact opnemen met de Servicedesk op 085 1110777 of via servicedesk@itcreation.nl.

Met vriendelijke groet,
Danny Rotmeijer

Met vriendelijke groet,

IT creation | Danny Rotmeijer
technisch consultant

[https://www.itcreation.nl]<https://www.itcreation.nl>
T               +31 (0) 85 111 0 777
W               www.itcreation.nl
E               danny.rotmeijer@itcreation.nl
S               servicedesk@itcreation.nl

[cid:image1de678.PNG@550de897.439dd27f]



________________________________

Disclaimer

1. This e-mail is meant for the intended recipient only. If you have received this by mistake, you are kindly requested to notify the sender and then delete the e-mail from your system; access to, disclosure, copying and/or distribution of this e-mail by anyone other than the intended recipient is prohibited.

2. If you, as intended recipient, have received this e-mail incorrectly, please notify the sender immediately. This e-mail is confidential and may be legally privileged. IT Creation B.V. does not guarantee that the information disclosed in or attached to this e-mail is correct and does not accept any liability for damages related thereto.
Comment 9 Danny 2018-05-13 13:40:19 UTC
Created attachment 275957 [details]
image1de678.PNG
Comment 10 SlayerProof32 2018-05-18 01:27:29 UTC
Kernel 4.16.8 on lenovo t410 -- same issue

See bug report
https://bugzilla.redhat.com/show_bug.cgi?id=1578612
Comment 11 Hans de Goede 2018-05-18 08:23:11 UTC
Hi All,

What might help for those of yoy with a broadcom wifi/bt combo card is making sure you've a so called patch-ram for your BT controller in place.

Run "dmesg > dmesg.log" shortly after a boot. Likely you will find a message about missing firmware for the bluetooth in dmesg.log. If the bluetooth part of your wifi/bt combo card is USB based (it likely is) you can find firmware files for it here:
https://github.com/winterheart/broadcom-bt-firmware

Please try putting a firmware file from there (with the right name) under /lib/firmware/brcm and then reboot. Please do a second:

dmesg > dmesg2.log

After the reboot with the firmware in place and check that the firmware now is being loaded. Once you've confirmed that the firmware is being loaded, you can check if the problem is now fixed.

Regards,

Hans
Comment 12 Szymon Janc 2018-05-18 09:50:49 UTC
This error can be ignored as code is same as before message was changed from debug to error. We need to figure out if this code should also handle Command Status event.

https://www.spinics.net/lists/linux-bluetooth/msg75102.html
Comment 13 Luca Tagliacozzo 2018-05-26 12:45:16 UTC
In my case the error actually effects my ability to pair with several devices, 
my card is 
Bus 001 Device 003: ID 413c:8187 Dell Computer Corp. DW375 Bluetooth Module
I can see the device from older distributions.
Comment 14 Julien 2018-09-26 21:39:01 UTC
I am facing the same trouble.
I can't air with some devices.
My card is : 

08:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev 73)
	Subsystem: Intel Corporation Wireless-N 7260 [8086:4062]
	Kernel driver in use: iwlwifi
Comment 15 Matthias Pritschet 2018-10-22 12:43:41 UTC
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".
Comment 16 Nadal Gonzalo García Zavala 2018-10-27 04:08:37 UTC
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.
Comment 18 Nadal Gonzalo García Zavala 2018-10-27 04:17:22 UTC
sudo lsusb -vvv
https://paste.pound-python.org/raw/vfIi8iqFxDaI5Mofjruq/
Comment 19 Jonathan Dunlap 2018-10-30 19:15:59 UTC
Same issue here with Fedora 28 and 29, using Gigabyte x470 Gaming 7 motherboard with an Intel Wifi and Bluetooth chipset.
Comment 20 Oleksandr Pylypenko 2018-11-04 12:00:36 UTC
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.
Comment 21 Jakub Jankiewicz 2018-11-12 14:22:42 UTC
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.
Comment 22 Alex ARNAUD 2018-11-12 17:34:24 UTC
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.
Comment 23 Ishan Kulkarni 2019-01-18 06:31:13 UTC
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)
Comment 24 Johan Hedberg 2019-01-18 07:22:11 UTC
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.
Comment 25 Paul Menzel 2019-02-01 21:28:33 UTC
Should this be added to the stable series too?

Note You need to log in before you can comment on or make changes to this bug.