From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 217023] [Intel AX200] hci0: Malformed MSFT vendor event: 0x02
Date: Thu, 05 Oct 2023 00:21:29 +0000 [thread overview]
Message-ID: <bug-217023-62941-E4gM9aizvx@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217023-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=217023
Nelson (nelson@live.cl) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |nelson@live.cl
--- Comment #9 from Nelson (nelson@live.cl) ---
- 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.
--
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-10-05 0:21 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 ` [Bug 217023] " bugzilla-daemon
2023-03-10 7:27 ` 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 [this message]
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-E4gM9aizvx@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;
as well as URLs for NNTP newsgroup(s).