From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 217023] [Intel AX200] hci0: Malformed MSFT vendor event: 0x02
Date: Wed, 01 Mar 2023 15:53:49 +0000 [thread overview]
Message-ID: <bug-217023-62941-8bnortQFbN@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217023-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=217023
Tanuj Bagaria (thebagarius@duck.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |thebagarius@duck.com
--- Comment #1 from Tanuj Bagaria (thebagarius@duck.com) ---
Same error, older hardware. see details below.
```
$ sudo dmesg
[ 29.392310] Bluetooth: hci0: Malformed MSFT vendor event: 0x02
```
```
$ uname -a
Linux jungle 6.1.14-hardened1-1-hardened #1 SMP PREEMPT_DYNAMIC Sat, 25 Feb
2023 13:15:09 +0000 x86_64 GNU/Linux
```
```
$ lspci
3c:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
```
```
$ lscpu
Intel(R) Core(TM) i5-7Y54 CPU @ 1.20GHz
```
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2023-03-01 15:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-11 11:27 [Bug 217023] New: [Intel AX200] hci0: Malformed MSFT vendor event: 0x02 bugzilla-daemon
2023-03-01 15:53 ` bugzilla-daemon [this message]
2023-03-10 7:27 ` [Bug 217023] " bugzilla-daemon
2023-03-10 7:54 ` bugzilla-daemon
2023-04-20 9:27 ` bugzilla-daemon
2023-04-26 4:41 ` bugzilla-daemon
2023-07-25 11:49 ` bugzilla-daemon
2023-07-25 18:44 ` bugzilla-daemon
2023-08-18 10:00 ` bugzilla-daemon
2023-10-05 0:21 ` bugzilla-daemon
2024-03-29 17:59 ` bugzilla-daemon
2024-09-11 2:37 ` bugzilla-daemon
2024-10-25 6:46 ` bugzilla-daemon
2025-02-11 0:24 ` bugzilla-daemon
2025-02-11 15:10 ` bugzilla-daemon
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=bug-217023-62941-8bnortQFbN@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--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