[regression] bluetooth scanning on AX210 stopped working
From: Thorsten Leemhuis
Date: Thu Jul 25 2024 - 04:51:26 EST
Hi, Thorsten here, the Linux kernel's regression tracker.
Luiz, I noticed a report about a regression in bugzilla.kernel.org that
appears to be caused by a change of yours:
2e2515c1ba384a ("Bluetooth: hci_event: Set DISCOVERY_FINDING on
SCAN_ENABLED") [v6.10-rc1]
As many (most?) kernel developers don't keep an eye on the bug tracker,
I decided to write this mail. To quote from █ :
> Eugene Shalygin 2024-07-23 19:39:38 UTC
>
> With kernel 6.10.0 bluetooth scanning finds no devices (Intel AX210). 6.9.9 works.
> Eugene Shalygin 2024-07-24 06:56:42 UTC
>
> $ 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
> Eugene Shalygin 2024-07-25 00:13:34 UTC
>
> [bisection] converges to 2e2515c1ba384ae44f6bf13dd64b9a0a950798c4
See the ticket for more details.
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
If I did something stupid, please tell me, as explained on that page.
P.S.: let me use this mail to also add the report to the list of tracked
regressions to ensure it's doesn't fall through the cracks:
#regzbot introduced: 2e2515c1ba384ae44f6bf13dd64b9a0a950798c4
#regzbot title: Bluetooth: hci_event: bluetooth scanning on AX210
stopped working
#regzbot from: Eugene Shalygin <eugene.shalygin@xxxxxxxxx>
#regzbot duplicate: https://bugzilla.kernel.org/show_bug.cgi?id=219088
#regzbot ignore-activity