linux-bluetooth.vger.kernel.org archive mirror
 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: Wed, 26 Apr 2023 04:41:18 +0000	[thread overview]
Message-ID: <bug-217023-62941-FaAiJSdTrh@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 #5 from einhalb@gmx.net ---
Same error on boot for me with AMD CPU und Intel Wifi AX210:

dmesg
[   12.374403] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   12.374413] Bluetooth: BNEP filters: protocol multicast
[   12.374421] Bluetooth: BNEP socket layer initialized
[   13.343660] Bluetooth: hci0: Waiting for firmware download to complete
[   13.343931] Bluetooth: hci0: Firmware loaded in 1275748 usecs
[   13.344049] Bluetooth: hci0: Waiting for device to boot
[   13.373944] Bluetooth: hci0: Malformed MSFT vendor event: 0x02
[   13.373952] Bluetooth: hci0: Device booted in 29263 usecs
[   13.374278] Bluetooth: hci0: Found Intel DDC parameters:
intel/ibt-0041-0041.ddc
[   13.382017] Bluetooth: hci0: Applying Intel DDC parameters completed
[   13.390994] Bluetooth: hci0: Firmware timestamp 2022.5 buildtype 1 build
38020
[   13.563429] loop42: detected capacity change from 0 to 8
[   13.623805] NET: Registered PF_ALG protocol family
[   13.791859] Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0)
[   13.802577] Bluetooth: RFCOMM TTY layer initialized
[   13.802593] Bluetooth: RFCOMM socket layer initialized
[   13.802605] Bluetooth: RFCOMM ver 1.11



lscpu
AMD Ryzen 7 2700U with Radeon Vega Mobile Gfx

lsusb
Bus 001 Device 002: ID 8087:0032 Intel Corp. AX210 Bluetooth

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 22.04.2 LTS
Release:        22.04
Codename:       jammy

uname -a
Linux NB-1 5.19.0-41-generic #42~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Apr 18
17:40:00 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

-- 
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:[~2023-04-26  4:41 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 [this message]
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-FaAiJSdTrh@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).