From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 217023] [Intel AX200] hci0: Malformed MSFT vendor event: 0x02
Date: Tue, 25 Jul 2023 11:49:36 +0000 [thread overview]
Message-ID: <bug-217023-62941-pXPxBeJA8G@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217023-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=217023
André Barata (andretiagob@protonmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |andretiagob@protonmail.com
--- Comment #6 from André Barata (andretiagob@protonmail.com) ---
Same error here, Intel Killer WiFi 6E AX1675
Bus 003 Device 006: ID 8087:0033 Intel Corp.
dmesg | grep hci0
[ 6.616282] Bluetooth: hci0: Device revision is 0
[ 6.616287] Bluetooth: hci0: Secure boot is enabled
[ 6.616289] Bluetooth: hci0: OTP lock is enabled
[ 6.616290] Bluetooth: hci0: API lock is enabled
[ 6.616291] Bluetooth: hci0: Debug lock is disabled
[ 6.616292] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 6.616294] Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1 build
38
[ 6.677948] Bluetooth: hci0: Found device firmware: intel/ibt-0040-0041.sfi
[ 6.677973] Bluetooth: hci0: Boot Address: 0x100800
[ 6.677975] Bluetooth: hci0: Firmware Version: 98-13.23
[ 8.301161] Bluetooth: hci0: Waiting for firmware download to complete
[ 8.301242] Bluetooth: hci0: Firmware loaded in 1585261 usecs
[ 8.301285] Bluetooth: hci0: Waiting for device to boot
[ 8.317241] Bluetooth: hci0: Device booted in 15612 usecs
[ 8.317365] Bluetooth: hci0: Malformed MSFT vendor event: 0x02
[ 8.317557] Bluetooth: hci0: Found Intel DDC parameters:
intel/ibt-0040-0041.ddc
[ 8.320382] Bluetooth: hci0: Applying Intel DDC parameters completed
[ 8.323374] Bluetooth: hci0: Firmware timestamp 2023.13 buildtype 1 build
62562
[ 8.469680] Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0)
$ uname -a
Linux MSI.Home 6.4.4-200.fc38.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Jul 19 16:32:49
UTC 2023 x86_64 GNU/Linux
$ lscpu
12th Gen Intel(R) Core(TM) i7-1280P
--
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-07-25 11:50 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 [this message]
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-pXPxBeJA8G@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).