Arch Linux

Brain

Member

Registered: 2020-07-29

Posts: 58

Error "Bluetooth: hci0: Malformed MSFT vendor event: 0x02"

Hello.

I am getting this error message every time my laptop boots up:

Bluetooth: hci0: Malformed MSFT vendor event: 0x02

This is very annoying, because it always appears while logging in via tty, which looks annoying.

journalctl shows this:

May 29 22:22:37 x1 kernel: Bluetooth: hci0: Waiting for firmware download to complete
May 29 22:22:37 x1 kernel: Bluetooth: hci0: Firmware loaded in 2132192 usecs
May 29 22:22:37 x1 kernel: Bluetooth: hci0: Waiting for device to boot
May 29 22:22:37 x1 kernel: Bluetooth: hci0: Device booted in 14599 usecs
May 29 22:22:37 x1 kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
May 29 22:22:37 x1 kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc
May 29 22:22:37 x1 kernel: Bluetooth: hci0: Applying Intel DDC parameters completed
May 29 22:22:37 x1 kernel: Bluetooth: hci0: Firmware revision 0.4 build 50 week 12 2022

Does anyone have an idea what this error message even means and how I can either get rid of entirely or at least not log it into my tty?

Thanks in advance.

Last edited by Brain (2022-05-30 22:16:37)

Brain

Member

Registered: 2020-07-29

Posts: 58

Re: Error "Bluetooth: hci0: Malformed MSFT vendor event: 0x02"

This issue seems to have been fixed by a kernel or hidap update just now.

Brain

Member

Registered: 2020-07-29

Posts: 58

Re: Error "Bluetooth: hci0: Malformed MSFT vendor event: 0x02"

Well, nope. Seems like it hasn't been fixed after all. Sorry.
After a second reboot it's there again.

iyanmv

Member

Registered: 2016-11-08

Posts: 39

Website

Re: Error "Bluetooth: hci0: Malformed MSFT vendor event: 0x02"

I just saw the same error

May 31 01:09:00 thinkpad kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02

Lenovo ThinkPad X1 Yoga Gen 6 with an Intel Corporation Wi-Fi 6 AX201 (WF + BT)

coss

Member

Registered: 2022-01-13

Posts: 4

Re: Error "Bluetooth: hci0: Malformed MSFT vendor event: 0x02"

I also have the same prompt, in different versions 5.15 and 5.18.

---

Arch + DWM
MSI Z590I Unify + i9-10900K + RX5600XT

fyb

Member

Registered: 2022-05-31

Posts: 1

Website

Re: Error "Bluetooth: hci0: Malformed MSFT vendor event: 0x02"

I have the exact same error on 5.18.1-arch1-1. Bluetooth functionality is not affected but seeing error messages while logging in on tty1 is pretty annoying.

Asus ROG Strix G513 with Intel Corp. AX200 Bluetooth (WIFI + Bluetooth)

Last edited by fyb (2022-05-31 15:47:44)

---

ASUS ROG Strix G513 with AMD Ryzen 7-5800H and NVIDIA RTX3050Ti

joonhyuk

Member

Registered: 2022-05-31

Posts: 1

Re: Error "Bluetooth: hci0: Malformed MSFT vendor event: 0x02"

+1

5.18.1-arch1-1
Lenovo Thinkbook 14 G3 ACL
(Intel AX200 rev 1a)

And, no problem with ubuntu 22.04, Windows 11

Last edited by joonhyuk (2022-06-03 11:31:39)

---

Noooooooooob

kriansa

Member

Registered: 2019-01-26

Posts: 5

Re: Error "Bluetooth: hci0: Malformed MSFT vendor event: 0x02"

Would you mind showing your `lspci` for the sake of identifying the adapter?

I'm also using Intel AX201 and having the same issue, but it goes further to not allowing me to use Bluetooth at all. Do any of you have the same issue?

Brain

Member

Registered: 2020-07-29

Posts: 58

Re: Error "Bluetooth: hci0: Malformed MSFT vendor event: 0x02"

My bluetooth seems to be working fine, except the annoying error message.
Here is the output of `lspci` on my Lenovo ThinkPad X1 Carbon Gen 9:

00:00.0 Host bridge: Intel Corporation 11th Gen Core Processor Host Bridge/DRAM Registers (rev 01)
00:02.0 VGA compatible controller: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (rev 01)
00:04.0 Signal processing controller: Intel Corporation TigerLake-LP Dynamic Tuning Processor Participant (rev 01)
00:06.0 PCI bridge: Intel Corporation 11th Gen Core Processor PCIe Controller (rev 01)
00:07.0 PCI bridge: Intel Corporation Tiger Lake-LP Thunderbolt 4 PCI Express Root Port #1 (rev 01)
00:07.2 PCI bridge: Intel Corporation Tiger Lake-LP Thunderbolt 4 PCI Express Root Port #2 (rev 01)
00:08.0 System peripheral: Intel Corporation GNA Scoring Accelerator module (rev 01)
00:0a.0 Signal processing controller: Intel Corporation Tigerlake Telemetry Aggregator Driver (rev 01)
00:0d.0 USB controller: Intel Corporation Tiger Lake-LP Thunderbolt 4 USB Controller (rev 01)
00:0d.2 USB controller: Intel Corporation Tiger Lake-LP Thunderbolt 4 NHI #0 (rev 01)
00:0d.3 USB controller: Intel Corporation Tiger Lake-LP Thunderbolt 4 NHI #1 (rev 01)
00:14.0 USB controller: Intel Corporation Tiger Lake-LP USB 3.2 Gen 2x1 xHCI Host Controller (rev 20)
00:14.2 RAM memory: Intel Corporation Tiger Lake-LP Shared SRAM (rev 20)
00:14.3 Network controller: Intel Corporation Wi-Fi 6 AX201 (rev 20)
00:15.0 Serial bus controller: Intel Corporation Tiger Lake-LP Serial IO I2C Controller #0 (rev 20)
00:15.3 Serial bus controller: Intel Corporation Tiger Lake-LP Serial IO I2C Controller #3 (rev 20)
00:16.0 Communication controller: Intel Corporation Tiger Lake-LP Management Engine Interface (rev 20)
00:1f.0 ISA bridge: Intel Corporation Tiger Lake-LP LPC Controller (rev 20)
00:1f.3 Audio device: Intel Corporation Tiger Lake-LP Smart Sound Technology Audio Controller (rev 20)
00:1f.4 SMBus: Intel Corporation Tiger Lake-LP SMBus Controller (rev 20)
00:1f.5 Serial bus controller: Intel Corporation Tiger Lake-LP SPI Controller (rev 20)
04:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller PM9A1/PM9A3/980PRO

GTRONICK

Member

Registered: 2016-07-17

Posts: 41

Re: Error "Bluetooth: hci0: Malformed MSFT vendor event: 0x02"

Having the same issue on ROG Strix G513QY with

Network controller: Intel Corporation Wi-Fi 6 AX210/AX211/AX411 160MHz

Sometimes, after boot, the Bluetooth adapter seems to work and scan for devices, but all the previously paired devices disappear. It is fixed by rebooting again though, but it annoying.

o_caino

Member

Registered: 2013-06-06

Posts: 167

Re: Error "Bluetooth: hci0: Malformed MSFT vendor event: 0x02"

I'm having the same issue on my Asus Vivobook Pro 16X, currently running kernel 5.18.3-arch1-1
The adapter is

0000:00:14.3 Network controller: Intel Corporation Wi-Fi 6 AX201 (rev 20)

script-kiddy

Member

Registered: 2022-06-13

Posts: 2

Re: Error "Bluetooth: hci0: Malformed MSFT vendor event: 0x02"

Sorry for newbie question, im new to linux. I have this problem too and dmesg shows exactly the same problem, but bluetooth doesnt seem to work at all. I was wondering is there a possibility to load older module/driver for bluetooth? Ive already booted arch with lts kernel, but it did not help.

Network controller: Intel Corporation Wireless 8260 (rev 3a)
5.18.3-arch1-1

Last edited by script-kiddy (2022-06-14 18:37:24)

kriansa

Member

Registered: 2019-01-26

Posts: 5

Re: Error "Bluetooth: hci0: Malformed MSFT vendor event: 0x02"

Sorry for newbie question, im new to linux. I have this problem too and dmesg shows exactly the same problem, but bluetooth doesnt seem to work at all. I was wondering is there a possibility to load older module/driver for bluetooth? Ive already booted arch with lts kernel, but it did not help.

Network controller: Intel Corporation Wireless 8260 (rev 3a)
5.18.3-arch1-1

Have you tried `systemctl enable bluetooth`? In my case it worked and I can at least use it, regardless of the error message.

script-kiddy

Member

Registered: 2022-06-13

Posts: 2

Re: Error "Bluetooth: hci0: Malformed MSFT vendor event: 0x02"

Sorry for newbie question, im new to linux. I have this problem too and dmesg shows exactly the same problem, but bluetooth doesnt seem to work at all. I was wondering is there a possibility to load older module/driver for bluetooth? Ive already booted arch with lts kernel, but it did not help.

Network controller: Intel Corporation Wireless 8260 (rev 3a)
5.18.3-arch1-1

Have you tried `systemctl enable bluetooth`? In my case it worked and I can at least use it, regardless of the error message.

It helped just as much as now i can turn on bluetooth in settings in gnome, but devices aren't appearing. Do u think i can load some older modules for bluetooth to see if it can help? If yes, then where i can search for them?

Last edited by script-kiddy (2022-06-14 20:06:20)

zesko

Member

Registered: 2021-08-22

Posts: 10

Re: Error "Bluetooth: hci0: Malformed MSFT vendor event: 0x02"

I have the same issue on Thinkpad p15v (Intel AX201 Bluetooth ) using Gnome and Linux Kernel 5.18

amy.sh

Member

Registered: 2022-06-30

Posts: 1

Re: Error "Bluetooth: hci0: Malformed MSFT vendor event: 0x02"

i have this issue on void linux with
linux5.18-5.18.7_1
Intel Corporation Wi-Fi 6 AX201 (rev 20)

JoeyCorleone

Member

Registered: 2022-01-22

Posts: 88

Re: Error "Bluetooth: hci0: Malformed MSFT vendor event: 0x02"

Sorry for newbie question, im new to linux. I have this problem too and dmesg shows exactly the same problem, but bluetooth doesnt seem to work at all. I was wondering is there a possibility to load older module/driver for bluetooth? Ive already booted arch with lts kernel, but it did not help.

Network controller: Intel Corporation Wireless 8260 (rev 3a)
5.18.3-arch1-1

Have you tried `systemctl enable bluetooth`? In my case it worked and I can at least use it, regardless of the error message.

It helped just as much as now i can turn on bluetooth in settings in gnome, but devices aren't appearing. Do u think i can load some older modules for bluetooth to see if it can help? If yes, then where i can search for them?

Most people in this thread report not having actual problems with "Bluetooth: hci0: Malformed MSFT vendor event: 0x02" which appears to be a rather cosmetic issue.

If bluetooth does not work for you at all:
- study the arch wiki step-by-step,
- and open a new thread with some basic info attached, like

lsusb #usb-utils
rfkill list
sudo dmesg

dohoainam

Member

Registered: 2022-07-20

Posts: 1

Re: Error "Bluetooth: hci0: Malformed MSFT vendor event: 0x02"

I had the same problem on Thinkpad T490 but the message gone after

rfkill block bluetooth

and

sudo systemctl disable bluetooth

benedictjohannes

Member

Registered: 2022-08-10

Posts: 1

Re: Error "Bluetooth: hci0: Malformed MSFT vendor event: 0x02"

I also have Intel AX201 and have this happen in dmesg:

[235886.037239] Bluetooth: hci0: Malformed MSFT vendor event: 0x02
[235886.047254] Bluetooth: hci0: Hardware error 0x0c
[235886.061268] Bluetooth: hci0: Retrieving Intel exception info failed (-16)

Whenever this happened, bluetooth will stop working.

I usually have some luck re-enabling it using

systemctl restart bluetooth

It's so much of a hassle I might decide to write a program monitoring dmesg and perform the bluetooth restart command automatically.

MocusEZ

Member

Registered: 2022-10-05

Posts: 1

Re: Error "Bluetooth: hci0: Malformed MSFT vendor event: 0x02"

I also have same issue, although it does not affect me using bluetooth audio.
It often appears during startup, I just wonder what is happen

kernel version： 5.19.12-arch1-1

[    6.461779] Bluetooth: hci0: Waiting for firmware download to complete
[    6.461893] Bluetooth: hci0: Firmware loaded in 1498153 usecs
[    6.461957] Bluetooth: hci0: Waiting for device to boot
[    6.477903] Bluetooth: hci0: Device booted in 15611 usecs
[    6.478276] Bluetooth: hci0: Malformed MSFT vendor event: 0x02
[    6.479628] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-20-1-3.ddc
[    6.485009] Bluetooth: hci0: Applying Intel DDC parameters completed
[    6.488005] Bluetooth: hci0: Firmware revision 0.3 build 20 week 28 2022

82B6 Lenovo Legion R7000 2020

SilverlightningY

Member

Registered: 2022-10-14

Posts: 1

Re: Error "Bluetooth: hci0: Malformed MSFT vendor event: 0x02"

This issue still exists for me too.

kernel version: 6.0.1-arch1-1

Bluetooth: hci0: Waiting for firmware download to complete
Bluetooth: hci0: Firmware loaded in 1622804 usecs
Bluetooth: hci0: Waiting for device to boot
Bluetooth: hci0: Device booted in 14736 usecs
Bluetooth: hci0: Malformed MSFT vendor event: 0x02
Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-20-1-3.ddc
Bluetooth: hci0: Applying Intel DDC parameters completed
Bluetooth: hci0: Firmware revision 0.3 build 20 week 28 2022

network controller:

Intel Corporation Wi-Fi 6 AX200 (rev 1a)

Brocellous

Member

Registered: 2017-11-27

Posts: 146

Re: Error "Bluetooth: hci0: Malformed MSFT vendor event: 0x02"

Has anyone thought to write the mailing list for advice? MSFT event 0x02 appears to be https://learn.microsoft.com/en-us/windo … vice_event and it looks like bluetooth at least tries to handle it properly https://git.kernel.org/pub/scm/linux/ke … sft.c#n648. So it would seem there is either an error here or a lot of devices out there not following the spec.

CxOrg2

Member

Registered: 2022-02-17

Posts: 3

Re: Error "Bluetooth: hci0: Malformed MSFT vendor event: 0x02"

On a Lenovo Yoga 920 I managed to swap in an Intel AX910 wireless card which works well giving WiFi 6 speeds. However, to solve suspend/resume issues with the Bluetooth part, I block Bluetooth before sleep and unblock on resume. This is done with the file /usr/lib/systemd/system-sleep/suspend.sh as follows:

#!/bin/sh
# 
# This script should prevent suspend errors
# Put it in /usr/lib/systemd/system-sleep/xhci.sh
# The PCI 00:14.0 device is the usb xhci controller.
#

if [ "${1}" == "pre" ]; then
#  Do the thing you want before suspend here, e.g.:
   echo "Disable broken xhci module before suspending at $(date)..." > /tmp/systemd_suspend_test
   rfkill block 0
   systemctl stop python3-validity
   grep XHC.*enable /proc/acpi/wakeup && echo XHC > /proc/acpi/wakeup
elif [ "${1}" == "post" ]; then
#  Do the thing you want after resume here, e.g.:
   echo "Enable broken xhci module at wakeup from $(date)" >> /tmp/systemd_suspend_test
   grep XHC.*disable /proc/acpi/wakeup && echo XHC > /proc/acpi/wakeup
   systemctl start python3-validity
   rfkill unblock 0  
   /usr/local/bin/screen-man.sh
fi

I have included my current suspend.sh which contains some other useful suspend actions including "rfkill block 0" for bluetooth,   "systemctl stop python3-validity" for the fingerprint reader (original replaced with Thinkpad T480 reader) and suspend of USB3 (XHC) "grep XHC.*enable /proc/acpi/wakeup && echo XHC > /proc/acpi/wakeup". These may be useful for owners of similar laptops.

The "Bluetooth: hci0: Malformed MSFT vendor event: 0x02" persists but seems harmless. The dmesg output of this section suggests it may be to do with the current linux firmware which may fix the problem in the future.

[45746.639863] Bluetooth: hci0: Waiting for firmware download to complete
[45746.640292] Bluetooth: hci0: Firmware loaded in 1253762 usecs
[45746.640309] Bluetooth: hci0: Waiting for device to boot
[45746.667335] Bluetooth: hci0: Malformed MSFT vendor event: 0x02
[45746.667356] Bluetooth: hci0: Device booted in 26426 usecs
[45746.668279] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-0041-0041.ddc
[45746.670346] Bluetooth: hci0: Applying Intel DDC parameters completed
[45746.673351] Bluetooth: hci0: Firmware timestamp 2022.28 buildtype 1 build 47489
[45746.741508] Bluetooth: MGMT ver 1.22
[45746.799384] Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0)
[45746.799454] Bluetooth: hci0: Bad flag given (0x2) vs supported (0x1)

Last edited by CxOrg2 (2022-10-30 10:20:53)

KasTasMykolas

Member

Registered: 2022-10-27

Posts: 4

Re: Error "Bluetooth: hci0: Malformed MSFT vendor event: 0x02"

Still persists on

6.0.6-arch1-1

, Lenovo T14s with the same darn

AX201 (rev 20)

elmuz

Member

Registered: 2015-04-19

Posts: 16

Re: Error "Bluetooth: hci0: Malformed MSFT vendor event: 0x02"

Still present on

6.0.6-arch1-1

on my System76 Lemur Pro with device

Intel Corporation Wi-Fi 6 AX201 (rev 20)

this is relevant dmesg log

[    1.798682] Bluetooth: Core ver 2.22
[    1.798706] NET: Registered PF_BLUETOOTH protocol family
[    1.798708] Bluetooth: HCI device and connection manager initialized
[    1.798713] Bluetooth: HCI socket layer initialized
[    1.798718] Bluetooth: L2CAP socket layer initialized
[    1.798723] Bluetooth: SCO socket layer initialized
[    2.052420] Bluetooth: hci0: Bootloader revision 0.4 build 0 week 30 2018
[    2.053430] Bluetooth: hci0: Device revision is 2
[    2.053432] Bluetooth: hci0: Secure boot is enabled
[    2.053433] Bluetooth: hci0: OTP lock is enabled
[    2.053433] Bluetooth: hci0: API lock is enabled
[    2.053434] Bluetooth: hci0: Debug lock is disabled
[    2.053435] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[    2.089186] Bluetooth: hci0: Found device firmware: intel/ibt-19-0-4.sfi
[    2.089271] Bluetooth: hci0: Boot Address: 0x24800
[    2.089273] Bluetooth: hci0: Firmware Version: 20-28.22
[    2.146463] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    2.146466] Bluetooth: BNEP filters: protocol multicast
[    2.146469] Bluetooth: BNEP socket layer initialized
[    4.286601] Bluetooth: hci0: Waiting for firmware download to complete
[    4.287527] Bluetooth: hci0: Firmware loaded in 2146815 usecs
[    4.287606] Bluetooth: hci0: Waiting for device to boot
[    4.302677] Bluetooth: hci0: Device booted in 14753 usecs
[    4.302703] Bluetooth: hci0: Malformed MSFT vendor event: 0x02
[    4.311232] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc
[    4.313679] Bluetooth: hci0: Applying Intel DDC parameters completed
[    4.314589] Bluetooth: hci0: Firmware revision 0.4 build 20 week 28 2022
[    4.374810] Bluetooth: MGMT ver 1.22
[    4.424804] Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0)
[    4.424865] Bluetooth: hci0: Bad flag given (0x2) vs supported (0x1)

Last edited by elmuz (2022-11-02 08:20:14)