Re: hci0: Malformed MSFT vendor event: 0x02

Re: hci0: Malformed MSFT vendor event: 0x02

[Johannes Berg]

On Wed, 2023-02-08 at 12:21 +0300, Arda Demir wrote:
> Hello,
> 
> First of all, my bluetooth adapter is;
> 04:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a)

You've reached the Wi-Fi team here though - adding the BT list.

> I see the following message everytime when i boot the pc on tty.
> 
> "Bluetooth: hci0: Malformed MSFT vendor event: 0x02"
> 
> But bluetooth works well. If it is not critical it shouldn't print on
> tty, right?

That's generic from net/bluetooth/hci_event.c, not related to the device
(apart from the fact that the device might be broken if it's sending
this?)

johannes

Re: hci0: Malformed MSFT vendor event: 0x02

[Arda Demir]

I don't think the device is broken since bluetooth + wi-fi is fully
functional and i also read on arch linux forum people get the same
message on tty with the same hardware. (AX200)

https://bbs.archlinux.org/viewtopic.php?id=276815

On Wed, Feb 8, 2023 at 12:29 PM Johannes Berg <johannes@sipsolutions.net> wrote:
>
> On Wed, 2023-02-08 at 12:21 +0300, Arda Demir wrote:
> > Hello,
> >
> > First of all, my bluetooth adapter is;
> > 04:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a)
>
> You've reached the Wi-Fi team here though - adding the BT list.
>
> > I see the following message everytime when i boot the pc on tty.
> >
> > "Bluetooth: hci0: Malformed MSFT vendor event: 0x02"
> >
> > But bluetooth works well. If it is not critical it shouldn't print on
> > tty, right?
>
> That's generic from net/bluetooth/hci_event.c, not related to the device
> (apart from the fact that the device might be broken if it's sending
> this?)
>
> johannes
>

Re: hci0: Malformed MSFT vendor event: 0x02

[Paul Menzel]

Dear Arda,


Please use interleaved style when replying.

Am 08.02.23 um 10:54 schrieb Arda Demir:
> I don't think the device is broken since bluetooth + wi-fi is fully
> functional and i also read on arch linux forum people get the same
> message on tty with the same hardware. (AX200)
> 
> https://bbs.archlinux.org/viewtopic.php?id=276815
> 
> On Wed, Feb 8, 2023 at 12:29 PM Johannes Berg <johannes@sipsolutions.net> wrote:
>>
>> On Wed, 2023-02-08 at 12:21 +0300, Arda Demir wrote:
>>> Hello,
>>>
>>> First of all, my bluetooth adapter is;
>>> 04:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a)
>>
>> You've reached the Wi-Fi team here though - adding the BT list.
>>
>>> I see the following message everytime when i boot the pc on tty.
>>>
>>> "Bluetooth: hci0: Malformed MSFT vendor event: 0x02"
>>>
>>> But bluetooth works well. If it is not critical it shouldn't print on
>>> tty, right?
>>
>> That's generic from net/bluetooth/hci_event.c, not related to the device
>> (apart from the fact that the device might be broken if it's sending
>> this?)

The message seems to originate from `net/bluetooth/msft.c`:

```
static void *msft_skb_pull(struct hci_dev *hdev, struct sk_buff *skb,
                            u8 ev, size_t len)
{
         void *data;

         data = skb_pull_data(skb, len);
         if (!data)
                 bt_dev_err(hdev, "Malformed MSFT vendor event: 0x%02x", 
ev);

         return data;
}
```

I recommend to create a bug report at the Linux kernel Bugzilla [1], 
where you attach the output of `dmesg`.

Additionally, I suggest to not load the Bluetooth modules like btusb 
during startup, and only later load it with `btmon` running.

Please reply with the bug report number/URL, if you created the bug report.


Kind regards,

Paul


[1]: https://bugzilla.kernel.org/

Re: hci0: Malformed MSFT vendor event: 0x02

[Luiz Augusto von Dentz]

Hi Arda,

On Wed, Feb 8, 2023 at 2:00 AM Arda Demir <ddmirarda@gmail.com> wrote:
>
> I don't think the device is broken since bluetooth + wi-fi is fully
> functional and i also read on arch linux forum people get the same
> message on tty with the same hardware. (AX200)
>
> https://bbs.archlinux.org/viewtopic.php?id=276815

I suspect it is some vendor event other than MSFT that we are trying
to parse as MSFT, this normally can be ignored silently when not
understood, but I will check internally what we can do about it.

> On Wed, Feb 8, 2023 at 12:29 PM Johannes Berg <johannes@sipsolutions.net> wrote:
> >
> > On Wed, 2023-02-08 at 12:21 +0300, Arda Demir wrote:
> > > Hello,
> > >
> > > First of all, my bluetooth adapter is;
> > > 04:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a)
> >
> > You've reached the Wi-Fi team here though - adding the BT list.
> >
> > > I see the following message everytime when i boot the pc on tty.
> > >
> > > "Bluetooth: hci0: Malformed MSFT vendor event: 0x02"
> > >
> > > But bluetooth works well. If it is not critical it shouldn't print on
> > > tty, right?
> >
> > That's generic from net/bluetooth/hci_event.c, not related to the device
> > (apart from the fact that the device might be broken if it's sending
> > this?)
> >
> > johannes
> >



-- 
Luiz Augusto von Dentz

Re: hci0: Malformed MSFT vendor event: 0x02

[Arda Demir]

On Wed, 2023-02-08 at 12:21 +0300, Arda Demir wrote:
> Hello,
>
> First of all, my bluetooth adapter is;
> 04:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a)
>
> I see the following message everytime when i boot the pc on tty.
>
> "Bluetooth: hci0: Malformed MSFT vendor event: 0x02"
>
> But bluetooth works well. If it is not critical it shouldn't print on
> tty, right?

On Wed, Feb 8, 2023 at 12:29 PM Johannes Berg <johannes@sipsolutions.net> wrote:
>
> On Wed, 2023-02-08 at 12:21 +0300, Arda Demir wrote:
> > Hello,
> >
> > First of all, my bluetooth adapter is;
> > 04:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a)
>
> You've reached the Wi-Fi team here though - adding the BT list.
>
> > I see the following message everytime when i boot the pc on tty.
> >
> > "Bluetooth: hci0: Malformed MSFT vendor event: 0x02"
> >
> > But bluetooth works well. If it is not critical it shouldn't print on
> > tty, right?
>
> That's generic from net/bluetooth/hci_event.c, not related to the device
> (apart from the fact that the device might be broken if it's sending
> this?)
>
> johannes
>

On Wed, Feb 8, 2023 at 2:00 AM Arda Demir <ddmirarda@gmail.com> wrote:
>
> I don't think the device is broken since bluetooth + wi-fi is fully
> functional and i also read on arch linux forum people get the same
> message on tty with the same hardware. (AX200)
>
> https://bbs.archlinux.org/viewtopic.php?id=276815

On Wed, Feb 8, 2023 at 1:17 PM Paul Menzel <pmenzel@molgen.mpg.de> wrote:
>
> The message seems to originate from `net/bluetooth/msft.c`:
>
> ...
>
> ```
> static void *msft_skb_pull(struct hci_dev *hdev, struct sk_buff *skb,
>                             u8 ev, size_t len)
> {
>          void *data;
>
>          data = skb_pull_data(skb, len);
>          if (!data)
>                  bt_dev_err(hdev, "Malformed MSFT vendor event: 0x%02x",
> ev);
>
>          return data;
> }
> ```
>
> I recommend to create a bug report at the Linux kernel Bugzilla [1],
> where you attach the output of `dmesg`.
>
> Additionally, I suggest to not load the Bluetooth modules like btusb
> during startup, and only later load it with `btmon` running.
>
> Please reply with the bug report number/URL, if you created the bug report.
>
>
> Kind regards,
>
> Paul
>
>
> [1]: https://bugzilla.kernel.org/

On Thu, Feb 9, 2023 at 2:43 AM Luiz Augusto von Dentz
<luiz.dentz@gmail.com> wrote:
>
> Hi Arda,
>
> On Wed, Feb 8, 2023 at 2:00 AM Arda Demir <ddmirarda@gmail.com> wrote:
> > I don't think the device is broken since bluetooth + wi-fi is fully
> > functional and i also read on arch linux forum people get the same
> > message on tty with the same hardware. (AX200)
> >
> > https://bbs.archlinux.org/viewtopic.php?id=276815
>
> I suspect it is some vendor event other than MSFT that we are trying
> to parse as MSFT, this normally can be ignored silently when not
> understood, but I will check internally what we can do about it.

I've created a bug report about this:
https://bugzilla.kernel.org/show_bug.cgi?id=217023