You are not logged in.

#26 2022-11-17 06:03:39

tonnys
Member
Registered: 2022-11-17
Posts: 1

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

HP Elitebook 820 G4
Kernel 6.0.2-arch1-1
Intel Wireless-AC 8265
KDE Plasma

Same case. From my observation, about ~1 year ago, the bluetooth state is not this problematic. It worsen. Now, it sometimes:
- Cannot connect.
- Connected, but unusable.
- Connected, then the bluetooth devices turn off by itself while the notification's still showed that the device's connected (bluetooth speaker)
- Rare: bluetooth device disappear. If lucky, restart multiple times will bring it back. Not so lucky? wait 24 hours or more until the bluetooth show up again.

The quickest way for me to reconnect my devices, with > 95% success rate, is with forgetting then re-pairing those devices. I don't know if it's just the case with Arch or it's affecting all distros. Or it's just the case with Intel Wireless-AC PCIe. Or maybe the driver/kernel. At the least, it's not affecting windows 10.

I fire up my qemu  windows 10 VM, mount the bluetooth and pair with my bluetooth speaker, forced disconnect the bluetooth in my laptop and/or the paired bluetooth devices. But they'll connected successfully when I turn it on/ mount the bluetooth again.

Offline

#27 2023-01-20 12:00:05

mimozin
Member
Registered: 2023-01-20
Posts: 1

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

Some problems here too. In my case, the bluetooth in Manjaro doesn't discover a headset which is paired in the same machine with Windows and Ubuntu.

OS: Manjaro Linux x86_64
Host: Slimbook PROX15-AMD Standard
Kernel: 6.1.1-1-MANJARO
DE: Plasma 5.26.4

dmesg

....
[   31.136198] Bluetooth: hci0: Malformed MSFT vendor event: 0x02
....
[ 2230.294762] Bluetooth: hci0: Opcode 0x2042 failed: -22
....

Here, more information:

https://forum.manjaro.org/t/bluetooth-d … set/129710

Offline

#28 2023-01-23 12:01:56

Jenny08
Member
Registered: 2023-01-23
Posts: 1

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

Same problem here!
```
Bluetooth: hci0: Malformed MSFT vendor event: 0x02
```

OS: Manjaro Linux x86_64
Kernel: 6.1.1-1-MANJARO
Host: DELL Inspiron 7501

But my bluetooth works fine.
About one out of three times, my system crashes, either when I start it or when I shut it down. But I can't guarantee that it's coming from this message.

Offline

#29 2023-02-18 13:28:52

Pyntux
Member
From: Serbia
Registered: 2008-12-21
Posts: 394

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

Problem still here:

Kernel: 6.1.12-arch1-1
Host: Thinkpad t460


I do not speak English, but I understand...

Offline

#30 2023-02-18 16:48:03

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,881

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

Sorry to rain on the parade, Like Jenny08, I get the message

Feb 17 17:08:30 odin kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02

  Regardless, the functionality with my phone, speaker and headset are seamless.
I think this message is a red herring unrelated to the problems you are encountering.

To everyone in the thread -- do you have other devices in the vicinity that may also be paired to the target device?  I can get nondeterministic behavior if both my phone and Arch laptop are both associated with my headset.  I've had the phone ring in the middle of a Teams meeting and had the headset drop the meeting as the headset is captured by the phone.   Or, if i have been playing music to the speaker from my phone, then try from Linux, Bluetooth will connect, but there will be no audio,


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Online

#31 2023-02-20 23:13:29

shamanstk
Member
Registered: 2009-11-11
Posts: 35

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

I am getting this error on a brand new Lenovo X1 Carbon that has never had anything paired to it.

Offline

#32 2023-03-15 13:42:06

saeziae
Member
Registered: 2023-03-15
Posts: 1

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

I get

Bluetooth: hci0: Malformed MSFT vendor event: 0x02

everytime on boot.
However, Bluetooth works well as if nothing happened.
Device is Intel Wi-Fi 6 AX210 on MSI Laptop Delta 15. Kernel is 6.2.6-arch1-1.

Last edited by saeziae (2023-03-15 13:43:15)

Offline

#33 2023-05-03 13:00:11

dcy3rka
Member
Registered: 2022-01-19
Posts: 52

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

I don't see it anymore on Thinkpad T16 G1 with 6.2.13

Offline

#34 2023-05-03 14:10:51

Sathors
Member
Registered: 2011-02-23
Posts: 56

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

It has disappeared for me as well, on XPS 9520 with 6.2.10.

Offline

#35 2023-07-26 17:23:53

audiores
Member
Registered: 2021-09-06
Posts: 9

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

I just have this problem on Lenovo Thinkpad L14 Gen2 AMD.
bluetooth: hci0: Malformed MSFT vendor event: 0x02

Did any of you ever find out what was the issue?

Offline

#36 2023-07-27 11:43:52

Brain
Member
Registered: 2020-07-29
Posts: 54

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

OP here. I still get the same error message, but everything else seems to be working fine. This has been a long standing issue now. Does anyone know where to report this?

Offline

#37 2023-08-09 17:20:41

oz
Member
Registered: 2004-05-20
Posts: 102

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

As far as I can tell the MSFT error is "harmless." Maybe it harms something but not anything I notice so far.

Apparently newer kernels (6.4?) have broken Bluetooth, maybe just the Intel AX2xx drivers.

Reverting to the LTS kernel 6.1 and the Bluetooth instantly pairs perfectly. The confusing thing is, if you pair devices on an older kernel then boot to a newer kernel they will still work. It appears to only be the scanning/discovery and pairing that is broken in new kernels.

Not sure which kernel broke things. This is getting really annoying because this is just one of countless regressions introduced in the kernel the last few years. I have a stack of kernels I have to maintain for different machines because newer kernels are still broken to this day.

Last edited by oz (2023-08-10 14:44:46)

Offline

#38 2023-08-10 12:55:21

kloga
Member
Registered: 2023-08-10
Posts: 1

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

I had the same problem (warning message, BT working), but after doing this:

dohoainam wrote:

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

rfkill block bluetooth

and

sudo systemctl disable bluetooth

And after rebooting, reenabling bluetooth service:

sudo systemctl enable bluetooth

And rebooting again, everything works properly and the warning message on boot is gone. Thanks! Hope it helps other people.

Edit: it seems this fix only lasts one boot. After rebooting again the warning message is back, but bluetooth still works normally.

Last edited by kloga (2023-08-10 19:50:56)

Offline

#39 2023-08-10 15:31:55

cloverskull
Member
Registered: 2018-09-30
Posts: 181

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

This didn't actually clear the issue for me. In fact, now my journald is spammed with the following:

Aug 10 08:28:39 sys76 kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
Aug 10 08:28:46 sys76 bluetoothd[931]: Failed to add UUID: Failed (0x03)
Aug 10 08:28:46 sys76 bluetoothd[931]: Failed to add UUID: Failed (0x03)
Aug 10 08:28:46 sys76 bluetoothd[931]: Failed to add UUID: Failed (0x03)
Aug 10 08:28:46 sys76 bluetoothd[931]: Failed to add UUID: Failed (0x03)
Aug 10 08:28:46 sys76 bluetoothd[931]: Failed to add UUID: Failed (0x03)
Aug 10 08:28:46 sys76 bluetoothd[931]: Failed to add UUID: Failed (0x03)
Aug 10 08:28:46 sys76 bluetoothd[931]: Failed to add UUID: Failed (0x03)
Aug 10 08:28:47 sys76 bluetoothd[931]: Failed to add UUID: Failed (0x03)
Aug 10 08:28:47 sys76 bluetoothd[931]: Failed to add UUID: Failed (0x03)
Aug 10 08:28:47 sys76 bluetoothd[931]: Failed to add UUID: Failed (0x03)
Aug 10 08:28:47 sys76 bluetoothd[931]: Failed to add UUID: Failed (0x03)
Aug 10 08:28:47 sys76 bluetoothd[931]: Failed to set mode: Failed (0x03)

It's worth mentioning bluetooth does appear to work, but I can't seem to get rid of the log spam. I've even tried unblocking bluetooth with rfkill and the log spamming persists.

Offline

#40 2023-08-22 08:32:53

andrisas
Member
Registered: 2023-08-22
Posts: 2

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

This patch seems to fix it. Should i submit it to the mailing list?

diff --git a/net/bluetooth/msft.c b/net/bluetooth/msft.c
index bf5cee48916c..266aaa8dceed 100644
--- a/net/bluetooth/msft.c
+++ b/net/bluetooth/msft.c
@@ -724,6 +724,10 @@ void msft_vendor_evt(struct hci_dev *hdev, void *data, struct sk_buff *skb)
 
        switch (*evt) {
        case MSFT_EV_LE_MONITOR_DEVICE:
+               // Some intel devices are not following the spec
+               if (skb->len == 6)
+                       break;
+
                msft_monitor_device_evt(hdev, skb);
                break;

Offline

#41 2023-08-24 12:16:21

batbrat
Member
Registered: 2023-08-24
Posts: 1

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

@andrisas, is this a patch for the kernel? Can you explain more about how this patch works?

I have the same issue with the intel controller on my motherboard - Intel Corporation Wi-Fi 6 AX200 (rev 1a), so I too am trying to find the solution. If, indeed, your patch fixes things, you should submit it for consideration and review. Thanks for your work in fixing this problem.

Offline

#42 2023-08-24 19:59:11

cloverskull
Member
Registered: 2018-09-30
Posts: 181

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

I may be misreading things but I think the patch is basically just avoiding spamming the error message, it's essentially causing the kernel to ignore it instead of writing it out. So it's not really a 'fix' per se but I am not convinced anything actually needs fixing.

Offline

#43 2023-08-25 06:00:54

andrisas
Member
Registered: 2023-08-22
Posts: 2

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

cloverskull wrote:

I may be misreading things but I think the patch is basically just avoiding spamming the error message, it's essentially causing the kernel to ignore it instead of writing it out. So it's not really a 'fix' per se

Yes that is why i asked about submitting it to the mailing list.

cloverskull wrote:

but I am not convinced anything actually needs fixing.

It confuses people about other unrelated bluetooth errors.

Offline

#44 2023-09-02 02:46:48

Razek
Member
From: Chile
Registered: 2017-02-12
Posts: 4
Website

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

Same issue here:

- LT: HP ProBook 430 G8
- Kernel Version: 6.4.12-zen1-1-zen

lsusb | grep -i bluetooth

Bus 003 Device 005: ID 8087:0026 Intel Corp. AX201 Bluetooth

rfkill list

0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
1: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no

journalctl -p err -b:

sep 01 22:07:54 amida kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02

dmesg | grep Bluetooth

[    2.135878] Bluetooth: Core ver 2.22
[    2.135896] Bluetooth: HCI device and connection manager initialized
[    2.135901] Bluetooth: HCI socket layer initialized
[    2.135904] Bluetooth: L2CAP socket layer initialized
[    2.135907] Bluetooth: SCO socket layer initialized
[    2.215220] Bluetooth: hci0: Bootloader revision 0.4 build 0 week 30 2018
[    2.216228] Bluetooth: hci0: Device revision is 2
[    2.216231] Bluetooth: hci0: Secure boot is enabled
[    2.216232] Bluetooth: hci0: OTP lock is enabled
[    2.216233] Bluetooth: hci0: API lock is enabled
[    2.216234] Bluetooth: hci0: Debug lock is disabled
[    2.216235] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[    2.224767] Bluetooth: hci0: Found device firmware: intel/ibt-19-0-4.sfi
[    2.224796] Bluetooth: hci0: Boot Address: 0x24800
[    2.224797] Bluetooth: hci0: Firmware Version: 206-22.23
[    2.312520] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    2.312523] Bluetooth: BNEP filters: protocol multicast
[    2.312527] Bluetooth: BNEP socket layer initialized
[    3.954983] Bluetooth: hci0: Waiting for firmware download to complete
[    3.955209] Bluetooth: hci0: Firmware loaded in 1689881 usecs
[    3.955250] Bluetooth: hci0: Waiting for device to boot
[    3.970455] Bluetooth: hci0: Device booted in 14875 usecs
[    3.970474] Bluetooth: hci0: Malformed MSFT vendor event: 0x02
[    3.980165] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc
[    3.982432] Bluetooth: hci0: Applying Intel DDC parameters completed
[    3.983427] Bluetooth: hci0: Firmware revision 0.4 build 206 week 22 2023
[    4.052609] Bluetooth: MGMT ver 1.22
[   42.896475] Bluetooth: RFCOMM TTY layer initialized
[   42.896481] Bluetooth: RFCOMM socket layer initialized
[   42.896484] Bluetooth: RFCOMM ver 1.11

Despite the error, my Bluetooth devices seem to be functioning correctly. However, I'd like to address this error if possible.

Any insights would be appreciated.

Thanks!

Last edited by Razek (2023-09-02 02:56:28)

Offline

#45 2023-09-04 22:29:43

tkyjpn
Member
Registered: 2023-09-04
Posts: 1

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

SAME PROBLEM, Plus,
this is just one line; and,
there are about 50 lines consisting for some numbers etc and TRACEPC.

WHAT IS TRACE PC.

Same problem, when
Logging in (to encrypted brand new  kubuntu on brand new laptop)
Logiing out
Shutting down

When logging in it disappears quickly enough.
When LOGGING OUT: it freezes the computer permanently, and I have to FORCE-SHUTDOWN with on-off key.
When shutting down, I need to wait for 10+ minutes.
............................................
But WORSE:

I can remain connected to WIRED INTERNET only for about 10 minutes.

No such problem on the "same" computer with its default windows, I mean interneet connection part.

......................
I suspect, hardware or software is unhappy that they can't spy so easily, because
I blocked many things, including blutooth, wireless, and all other unnecessary junk.

Things were ok for a few weeks, and , suddenly for no reason such a problem pops up out of nowhere.

How can brand new kubuntu on brand new laptop can fail so easily.

Who is the evil guy here (if any).

Offline

#46 2023-09-05 02:48:25

cloverskull
Member
Registered: 2018-09-30
Posts: 181

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

Hey tkyjpn, FYI folks here won't be able to assist with anything kubuntu. This is an Arch only forum.

Offline

#47 2023-09-29 13:44:59

oleg_ua
Member
Registered: 2023-09-29
Posts: 1

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

I have the same issue on brand new Lenovo Thinkpad P15v Gen 3 Intel. Kernel: 6.5.5. Same error on every boot. From what I can see so far it is harmless in my case -- WiFi and Bluetooth both working fine. The network card is Intel® Wi-Fi 6E AX211.

Offline

#48 2023-09-29 18:31:41

sudoku
Member
Registered: 2012-10-31
Posts: 95

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

I can also see it on a Tuxedo Stellaris 17 with bluetooth disabled, every boot and every time the machine wakes up from sleep (multiple times actually).

$ uname -r
6.5.5-arch1-1

$ lspci | grep Network
Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a)

As others say it's a cosmetic issue.

Last edited by sudoku (2023-09-29 18:37:13)

Offline

#49 2023-09-29 23:50:40

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 22,093

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

Closing this, there's no point to everyone bumping this every time someone sees this message . If you have actual problems that are unrelated to this cosmetic message, open a new thread.

Offline

Board footer

Powered by FluxBB