From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 217023] [Intel AX200] hci0: Malformed MSFT vendor event: 0x02
Date: Fri, 25 Oct 2024 06:46:22 +0000 [thread overview]
Message-ID: <bug-217023-62941-HjInAfQxNx@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217023-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=217023
Avraham Hollander (anhollander516@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |anhollander516@gmail.com
--- Comment #12 from Avraham Hollander (anhollander516@gmail.com) ---
I'm also seeing this on an 8087:0026 Intel Corp. AX201 Bluetooth:
[ 1.992294] Bluetooth: Core ver 2.22
[ 1.992314] NET: Registered PF_BLUETOOTH protocol family
[ 1.992315] Bluetooth: HCI device and connection manager initialized
[ 1.992319] Bluetooth: HCI socket layer initialized
[ 1.992321] Bluetooth: L2CAP socket layer initialized
[ 1.992322] Bluetooth: SCO socket layer initialized
[ 1.995616] Bluetooth: hci0: Bootloader revision 0.4 build 0 week 30 2018
[ 1.996616] Bluetooth: hci0: Device revision is 2
[ 1.996618] Bluetooth: hci0: Secure boot is enabled
[ 1.996619] Bluetooth: hci0: OTP lock is enabled
[ 1.996620] Bluetooth: hci0: API lock is enabled
[ 1.996621] Bluetooth: hci0: Debug lock is disabled
[ 1.996622] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 1.997639] Bluetooth: hci0: Found device firmware: intel/ibt-19-0-4.sfi
[ 1.997756] Bluetooth: hci0: Boot Address: 0x24800
[ 1.997758] Bluetooth: hci0: Firmware Version: 132-3.24
[ 2.031013] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 2.031016] Bluetooth: BNEP filters: protocol multicast
[ 2.031019] Bluetooth: BNEP socket layer initialized
[ 3.645752] Bluetooth: hci0: Waiting for firmware download to complete
[ 3.646590] Bluetooth: hci0: Firmware loaded in 1610318 usecs
[ 3.646617] Bluetooth: hci0: Waiting for device to boot
[ 3.661799] Bluetooth: hci0: Device booted in 14842 usecs
[ 3.661800] Bluetooth: hci0: Malformed MSFT vendor event: 0x02
[ 3.662091] Bluetooth: hci0: Found Intel DDC parameters:
intel/ibt-19-0-4.ddc
[ 3.663689] Bluetooth: hci0: Applying Intel DDC parameters completed
[ 3.664765] Bluetooth: hci0: Firmware revision 0.4 build 132 week 3 2024
[ 3.666790] Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its
usage is not supported.
[ 3.743089] Bluetooth: MGMT ver 1.23
[ 6.806362] Bluetooth: RFCOMM TTY layer initialized
[ 6.806368] Bluetooth: RFCOMM socket layer initialized
[ 6.806368] Bluetooth: RFCOMM ver 1.11
This is on (albeit a custom configuration + patches) Linux 6.11.5.
--
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:[~2024-10-25 6:46 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
2024-03-29 17:59 ` bugzilla-daemon
2024-09-11 2:37 ` bugzilla-daemon
2024-10-25 6:46 ` bugzilla-daemon [this message]
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-HjInAfQxNx@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).