All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 217023] [Intel AX200] hci0: Malformed MSFT vendor event: 0x02
Date: Tue, 11 Feb 2025 00:24:09 +0000	[thread overview]
Message-ID: <bug-217023-62941-JrrS2ibkBP@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217023-62941@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=217023

--- Comment #13 from alexknoptech@protonmail.com ---
Seeing this fixed as of kernel 6.12.11


[   11.349625] Bluetooth: hci0: Device revision is 0
[   11.349629] Bluetooth: hci0: Secure boot is enabled
[   11.349631] Bluetooth: hci0: OTP lock is enabled
[   11.349633] Bluetooth: hci0: API lock is enabled
[   11.349634] Bluetooth: hci0: Debug lock is disabled
[   11.349635] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[   11.349637] Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1 build
38
[   11.349703] Bluetooth: hci0: DSM reset method type: 0x00
[   11.395507] Bluetooth: hci0: Found device firmware: intel/ibt-0040-0041.sfi
[   11.395532] Bluetooth: hci0: Boot Address: 0x100800
[   11.395535] Bluetooth: hci0: Firmware Version: 91-33.24
[   12.733845] Bluetooth: hci0: Waiting for firmware download to complete
[   12.733847] Bluetooth: hci0: Firmware loaded in 1306968 usecs
[   12.733908] Bluetooth: hci0: Waiting for device to boot
[   12.749759] Bluetooth: hci0: Device booted in 15525 usecs
>>>Typically seen here<<<<
[   12.759485] Bluetooth: hci0: Found Intel DDC parameters:
intel/ibt-0040-0041.ddc
[   12.761879] Bluetooth: hci0: Applying Intel DDC parameters completed
[   12.764880] Bluetooth: hci0: Firmware timestamp 2024.33 buildtype 1 build
81755
[   12.764882] Bluetooth: hci0: Firmware SHA1: 0xd028ffe4
[   12.768860] Bluetooth: hci0: Fseq status: Success (0x00)
[   12.768862] Bluetooth: hci0: Fseq executed: 00.00.02.41
[   12.768863] Bluetooth: hci0: Fseq BT Top: 00.00.02.41

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2025-02-11  0:24 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
2025-02-11  0:24 ` bugzilla-daemon [this message]
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-JrrS2ibkBP@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.