From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 219088] bluetooth scanning doesn't work in 6.10.0
Date: Wed, 24 Jul 2024 06:56:42 +0000 [thread overview]
Message-ID: <bug-219088-62941-1W35sKDWiu@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219088-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=219088
--- Comment #1 from Eugene Shalygin (eugene.shalygin@gmail.com) ---
$ dmesg | grep -e 'iwlwifi\|Bluetooth'
[ 2.633116] iwlwifi 0000:03:00.0: enabling device (0000 -> 0002)
[ 2.643454] Bluetooth: Core ver 2.22
[ 2.646521] Bluetooth: HCI device and connection manager initialized
[ 2.647920] Bluetooth: HCI socket layer initialized
[ 2.648885] Bluetooth: L2CAP socket layer initialized
[ 2.649972] Bluetooth: SCO socket layer initialized
[ 2.658734] iwlwifi 0000:03:00.0: Detected crf-id 0x400410, cnv-id 0x400410
wfpm id 0x80000000
[ 2.660717] iwlwifi 0000:03:00.0: PCI dev 2725/0024, rev=0x420,
rfid=0x10d000
[ 2.662120] Loading firmware: iwlwifi-ty-a0-gf-a0-89.ucode
[ 2.667789] iwlwifi 0000:03:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version:
0.0.2.42
[ 2.668164] iwlwifi 0000:03:00.0: loaded firmware version 89.202a2f7b.0
ty-a0-gf-a0-89.ucode op_mode iwlmvm
[ 2.693021] Bluetooth: hci0: Device revision is 0
[ 2.694469] Bluetooth: hci0: Secure boot is enabled
[ 2.698894] Bluetooth: hci0: OTP lock is enabled
[ 2.700339] Bluetooth: hci0: API lock is enabled
[ 2.701262] Bluetooth: hci0: Debug lock is disabled
[ 2.702069] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 2.702719] Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1 build
38
[ 2.703431] Bluetooth: hci0: No support for _PRR ACPI method
[ 2.708740] Bluetooth: hci0: Found device firmware: intel/ibt-0041-0041.sfi
[ 2.711227] Bluetooth: hci0: Boot Address: 0x100800
[ 2.711230] Bluetooth: hci0: Firmware Version: 120-18.24
[ 2.773104] iwlwifi 0000:03:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz,
REV=0x420
[ 2.783598] iwlwifi 0000:03:00.0: WRT: Invalid buffer destination
[ 2.943521] iwlwifi 0000:03:00.0: WFPM_UMAC_PD_NOTIFICATION: 0x20
[ 2.943552] iwlwifi 0000:03:00.0: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[ 2.943578] iwlwifi 0000:03:00.0: WFPM_AUTH_KEY_0: 0x90
[ 2.943602] iwlwifi 0000:03:00.0: CNVI_SCU_SEQ_DATA_DW9: 0x0
[ 2.943608] Loading firmware: iwlwifi-ty-a0-gf-a0.pnvm
[ 2.944080] iwlwifi 0000:03:00.0: loaded PNVM version 35148b80
[ 2.959773] iwlwifi 0000:03:00.0: Detected RF GF, rfid=0x10d000
[ 3.029643] iwlwifi 0000:03:00.0: base HW address: 2c:33:58:e9:d5:1d
[ 3.822131] Bluetooth: hci0: Waiting for firmware download to complete
[ 3.822963] Bluetooth: hci0: Firmware loaded in 1085762 usecs
[ 3.822999] Bluetooth: hci0: Waiting for device to boot
[ 3.848969] Bluetooth: hci0: Device booted in 25377 usecs
[ 3.848982] Bluetooth: hci0: Malformed MSFT vendor event: 0x02
[ 3.858349] Bluetooth: hci0: Found Intel DDC parameters:
intel/ibt-0041-0041.ddc
[ 3.864001] Bluetooth: hci0: Applying Intel DDC parameters completed
[ 3.872025] Bluetooth: hci0: Firmware timestamp 2024.18 buildtype 1 build
81528
[ 3.872028] Bluetooth: hci0: Firmware SHA1: 0xa8bb3f39
[ 3.882989] Bluetooth: hci0: Fseq status: Success (0x00)
[ 3.883003] Bluetooth: hci0: Fseq executed: 00.00.02.41
[ 3.883014] Bluetooth: hci0: Fseq BT Top: 00.00.02.41
[ 6.943128] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 6.943131] Bluetooth: BNEP filters: protocol multicast
[ 6.943133] Bluetooth: BNEP socket layer initialized
[ 6.943661] Bluetooth: MGMT ver 1.22
[ 6.946103] Bluetooth: ISO socket layer initialized
[ 7.068883] iwlwifi 0000:03:00.0: WRT: Invalid buffer destination
[ 7.224190] iwlwifi 0000:03:00.0: WFPM_UMAC_PD_NOTIFICATION: 0x20
[ 7.225614] iwlwifi 0000:03:00.0: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[ 7.226232] iwlwifi 0000:03:00.0: WFPM_AUTH_KEY_0: 0x90
[ 7.226803] iwlwifi 0000:03:00.0: CNVI_SCU_SEQ_DATA_DW9: 0x0
[ 7.384675] iwlwifi 0000:03:00.0: WRT: Invalid buffer destination
[ 7.539920] iwlwifi 0000:03:00.0: WFPM_UMAC_PD_NOTIFICATION: 0x20
[ 7.541272] iwlwifi 0000:03:00.0: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[ 7.541861] iwlwifi 0000:03:00.0: WFPM_AUTH_KEY_0: 0x90
[ 7.542422] iwlwifi 0000:03:00.0: CNVI_SCU_SEQ_DATA_DW9: 0x0
[ 16.078066] Bluetooth: RFCOMM TTY layer initialized
[ 16.078073] Bluetooth: RFCOMM socket layer initialized
[ 16.078077] Bluetooth: RFCOMM ver 1.11
--
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-07-24 6:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-23 19:39 [Bug 219088] New: bluetooth scanning doesn't work in 6.10.0 bugzilla-daemon
2024-07-24 6:56 ` bugzilla-daemon [this message]
2024-07-24 10:54 ` [Bug 219088] " bugzilla-daemon
2024-07-25 0:13 ` bugzilla-daemon
2024-07-25 8:29 ` bugzilla-daemon
2024-07-25 8:32 ` bugzilla-daemon
2024-07-25 13:44 ` bugzilla-daemon
2024-07-25 20:49 ` bugzilla-daemon
2024-07-25 20:50 ` bugzilla-daemon
2024-07-25 20:50 ` bugzilla-daemon
2024-07-25 20:52 ` bugzilla-daemon
2024-07-25 21:28 ` bugzilla-daemon
2024-07-25 21:31 ` bugzilla-daemon
2024-07-25 21:33 ` bugzilla-daemon
2024-07-25 21:43 ` bugzilla-daemon
2024-07-25 21:53 ` bugzilla-daemon
2024-07-25 22:09 ` bugzilla-daemon
2024-07-25 22:38 ` bugzilla-daemon
2024-07-25 22:39 ` bugzilla-daemon
2024-07-25 23:39 ` bugzilla-daemon
2024-07-26 10:08 ` 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-219088-62941-1W35sKDWiu@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.