From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: Arda Demir <ddmirarda@gmail.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-bluetooth@vger.kernel.org
Subject: Re: hci0: Malformed MSFT vendor event: 0x02
Date: Wed, 8 Feb 2023 15:43:13 -0800 [thread overview]
Message-ID: <CABBYNZ+iz-NihAPaDCSW2TLodoH3ThDWhZdTPvQtbyx_jnMyhg@mail.gmail.com> (raw)
In-Reply-To: <CALDHRCuuZdqVorNzF+DFU8kAUU4eiuCHJgtV3Gtbvwr9mVow9Q@mail.gmail.com>
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
next prev parent reply other threads:[~2023-02-08 23:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CALDHRCt5KUezfEZCOWK+zYPM1hP32qwZqcoKw09ZjNw=oQoWKg@mail.gmail.com>
2023-02-08 9:29 ` hci0: Malformed MSFT vendor event: 0x02 Johannes Berg
2023-02-08 9:54 ` Arda Demir
2023-02-08 10:17 ` Paul Menzel
2023-02-08 23:43 ` Luiz Augusto von Dentz [this message]
2023-02-11 11:48 ` Arda Demir
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CABBYNZ+iz-NihAPaDCSW2TLodoH3ThDWhZdTPvQtbyx_jnMyhg@mail.gmail.com \
--to=luiz.dentz@gmail.com \
--cc=ddmirarda@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).