From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 217023] [Intel AX200] hci0: Malformed MSFT vendor event: 0x02
Date: Fri, 10 Mar 2023 07:27:42 +0000 [thread overview]
Message-ID: <bug-217023-62941-j2S6p6Tj97@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217023-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=217023
Mathias Bavay (bavay@slf.ch) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bavay@slf.ch
--- Comment #2 from Mathias Bavay (bavay@slf.ch) ---
Same error on newer Intel hardware (AX210), since I've started using kernel
5.19.x (compiled by Ubuntu). My bluetooth keyboard and mouse also now need ~1
second when the desktop is loaded before being usable. With my previous kernel
(5.15.x), this error message did not appear and I could use the keyboard right
away, without the small lag that I now experience.
$ lsusb | grep Bluetooth
Bus 001 Device 002: ID 8087:0032 Intel Corp. AX210 Bluetooth
$ dmesg | grep hci0
[ 18.025550] Bluetooth: hci0: Device revision is 0
[ 18.025553] Bluetooth: hci0: Secure boot is enabled
[ 18.025554] Bluetooth: hci0: OTP lock is enabled
[ 18.025555] Bluetooth: hci0: API lock is enabled
[ 18.025556] Bluetooth: hci0: Debug lock is disabled
[ 18.025557] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 18.025558] Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1 build
38
[ 18.026909] Bluetooth: hci0: Found device firmware: intel/ibt-0041-0041.sfi
[ 18.026936] Bluetooth: hci0: Boot Address: 0x100800
[ 18.026938] Bluetooth: hci0: Firmware Version: 132-5.22
[ 19.585644] Bluetooth: hci0: Waiting for firmware download to complete
[ 19.585655] Bluetooth: hci0: Firmware loaded in 1522209 usecs
[ 19.585821] Bluetooth: hci0: Waiting for device to boot
[ 19.612549] Bluetooth: hci0: Device booted in 26194 usecs
[ 19.612617] Bluetooth: hci0: Malformed MSFT vendor event: 0x02
[ 19.613943] Bluetooth: hci0: Found Intel DDC parameters:
intel/ibt-0041-0041.ddc
[ 19.615693] Bluetooth: hci0: Applying Intel DDC parameters completed
[ 19.618707] Bluetooth: hci0: Firmware timestamp 2022.5 buildtype 1 build
38020
[ 19.865890] Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0)
[ 19.866093] Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0)
$ uname -a
Linux 5.19.0-35-generic #36~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb 17
15:17:25 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
$ lscpu
Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
--
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-10 7:27 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 [this message]
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-j2S6p6Tj97@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).