[Bug 219088] New: bluetooth scanning doesn't work in 6.10.0

[Bug 219088] New: bluetooth scanning doesn't work in 6.10.0

[bugzilla-daemon]

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

            Bug ID: 219088
           Summary: bluetooth scanning doesn't work in 6.10.0
           Product: Drivers
           Version: 2.5
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Bluetooth
          Assignee: linux-bluetooth@vger.kernel.org
          Reporter: eugene.shalygin@gmail.com
        Regression: No

With kernel 6.10.0 bluetooth scanning finds no devices (Intel AX210). 6.9.9
works.

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

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

[Bug 219088] bluetooth scanning doesn't work in 6.10.0

[bugzilla-daemon]

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.

[Bug 219088] bluetooth scanning doesn't work in 6.10.0

[bugzilla-daemon]

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

Artem S. Tashkinov (aros@gmx.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Kernel Version|                            |6.10
         Regression|No                          |Yes

--- Comment #2 from Artem S. Tashkinov (aros@gmx.com) ---
Please perform regression testing:

https://docs.kernel.org/admin-guide/bug-bisect.html

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

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

[Bug 219088] bluetooth scanning doesn't work in 6.10.0

[bugzilla-daemon]

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

--- Comment #3 from Eugene Shalygin (eugene.shalygin@gmail.com) ---
Converges to 2e2515c1ba384ae44f6bf13dd64b9a0a950798c4

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

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

[Bug 219088] bluetooth scanning doesn't work in 6.10.0

[bugzilla-daemon]

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

The Linux kernel's regression tracker (Thorsten Leemhuis) (regressions@leemhuis.info) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |regressions@leemhuis.info

--- Comment #4 from The Linux kernel's regression tracker (Thorsten Leemhuis) (regressions@leemhuis.info) ---
(In reply to Eugene Shalygin from comment #3)
> Converges to 2e2515c1ba384ae44f6bf13dd64b9a0a950798c4

thx; I would like to forward this report by mail; can I CC you? this would
expose name and email address to the public

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

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

[Bug 219088] bluetooth scanning doesn't work in 6.10.0

[bugzilla-daemon]

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

--- Comment #5 from Eugene Shalygin (eugene.shalygin@gmail.com) ---
(In reply to The Linux kernel's regression tracker (Thorsten Leemhuis) from
comment #4)
> thx; I would like to forward this report by mail; can I CC you? this would
> expose name and email address to the public

Thanks, no problem.

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

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

[Bug 219088] bluetooth scanning doesn't work in 6.10.0

[bugzilla-daemon]

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

Luiz Von Dentz (luiz.dentz@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |luiz.dentz@gmail.com

--- Comment #6 from Luiz Von Dentz (luiz.dentz@gmail.com) ---
I wasn't able to reproduce with current bluetooth-next:

https://gist.github.com/Vudentz/da22fb40ad55091b4a1e67f14a8ad033

@Eugene please collect the btmon traces.

That change should actually help to detect scanning had started so it would be
quite surprising if it caused events to not be submitted to userspace.

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

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

[Bug 219088] bluetooth scanning doesn't work in 6.10.0

[bugzilla-daemon]

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

--- Comment #7 from Eugene Shalygin (eugene.shalygin@gmail.com) ---
(In reply to Luiz Von Dentz from comment #6)
> I wasn't able to reproduce with current bluetooth-next:

I now have two machines with this issue.

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

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

[Bug 219088] bluetooth scanning doesn't work in 6.10.0

[bugzilla-daemon]

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

--- Comment #8 from Eugene Shalygin (eugene.shalygin@gmail.com) ---
Created attachment 306619
  --> https://bugzilla.kernel.org/attachment.cgi?id=306619&action=edit
btmon trace 6.10.0

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

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

[Bug 219088] bluetooth scanning doesn't work in 6.10.0

[bugzilla-daemon]

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

--- Comment #9 from Eugene Shalygin (eugene.shalygin@gmail.com) ---
Created attachment 306620
  --> https://bugzilla.kernel.org/attachment.cgi?id=306620&action=edit
btmon trace 6.9.9

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

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

[Bug 219088] bluetooth scanning doesn't work in 6.10.0

[bugzilla-daemon]

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

--- Comment #10 from Eugene Shalygin (eugene.shalygin@gmail.com) ---
(In reply to Luiz Von Dentz from comment #6)
> @Eugene please collect the btmon traces.

Please find the traces attached. The Samsung phone device is paired, the HTC
one is not.

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

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

[Bug 219088] bluetooth scanning doesn't work in 6.10.0

[bugzilla-daemon]

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

--- Comment #11 from Luiz Von Dentz (luiz.dentz@gmail.com) ---
On 6.9 there is the Start Discovery but on 6.10 there is nothing which
indicates the userspace is not even attempting to start it for some reason:

bluetoothd[945]: @ MGMT Command: Start Discovery (0x0023) plen 1               
                                                                               
                                                                    {0x0001}
[hci0] 12.038247
        Address type: 0x07
          BR/EDR
          LE Public
          LE Random

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

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

[Bug 219088] bluetooth scanning doesn't work in 6.10.0

[bugzilla-daemon]

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

--- Comment #12 from Eugene Shalygin (eugene.shalygin@gmail.com) ---
How can I learn why is that?

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

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

[Bug 219088] bluetooth scanning doesn't work in 6.10.0

[bugzilla-daemon]

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

--- Comment #13 from Luiz Von Dentz (luiz.dentz@gmail.com) ---
(In reply to Eugene Shalygin from comment #12)
> How can I learn why is that?

Are you sure you are issuing any command? Or you are using some UI that perhaps
thinks it is scanning for some reason?

Anyway if you try bluetoothctl> scan on that should trigger the command above.

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

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

[Bug 219088] bluetooth scanning doesn't work in 6.10.0

[bugzilla-daemon]

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

--- Comment #14 from Eugene Shalygin (eugene.shalygin@gmail.com) ---
Yes, I'm sure. Nothing new appears in the btmon log after issuing scan on in
bluetoothctl, scan off results in:

@ MGMT Event: Command Complete (0x0001) plen 4                                 
                                                                               
                                                                    {0x0001}
[hci0] 89.970607
      Stop Discovery (0x0024) plen 1
        Status: Rejected (0x0b)
        Address type: 0x00

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

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

[Bug 219088] bluetooth scanning doesn't work in 6.10.0

[bugzilla-daemon]

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

--- Comment #15 from Luiz Von Dentz (luiz.dentz@gmail.com) ---
(In reply to Eugene Shalygin from comment #14)
> Yes, I'm sure. Nothing new appears in the btmon log after issuing scan on in
> bluetoothctl, scan off results in:
> 
> @ MGMT Event: Command Complete (0x0001) plen 4                              
> {0x0001} [hci0] 89.970607
>       Stop Discovery (0x0024) plen 1
>         Status: Rejected (0x0b)
>         Address type: 0x00

Hmm, this sounds like the states are no in sync then, bluetoothd thinks Start
Discovery has been triggered but when it tries to stop the kernel don't think
it is discovering. Do you see anything like Discovering events when starting
bluetoothd or have Discovering: yes when you do bluetoothctl> show?

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

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

[Bug 219088] bluetooth scanning doesn't work in 6.10.0

[bugzilla-daemon]

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

--- Comment #16 from Eugene Shalygin (eugene.shalygin@gmail.com) ---
Seems like it's more complicated. 

In attempt to get a clean btmon log, I reloaded the btusb module a few times.
And it turns out if I issue the scan command right after reloading the module,
before moving my Bluetooth mouse, scan works. But if it gets busy with the
mouse, scanning can not even be stopped (Discovering: yes is still present
after multiple "scan off").

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

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

[Bug 219088] bluetooth scanning doesn't work in 6.10.0

[bugzilla-daemon]

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

--- Comment #17 from Luiz Von Dentz (luiz.dentz@gmail.com) ---
Looks like I found what it was, is is passive scanning triggering
DISCOVERY_FINDING state when in fact it shouldn't because passive scanning
doesn't generate events such as MGMT Device Found, it is just meant to
auto-connect devices already know/paired/bonded.

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

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

[Bug 219088] bluetooth scanning doesn't work in 6.10.0

[bugzilla-daemon]

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

--- Comment #18 from Luiz Von Dentz (luiz.dentz@gmail.com) ---
Created attachment 306621
  --> https://bugzilla.kernel.org/attachment.cgi?id=306621&action=edit
Bluetooth: hci_event: Fix setting DISCOVERY_FINDING for passive scanning

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

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

[Bug 219088] bluetooth scanning doesn't work in 6.10.0

[bugzilla-daemon]

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

--- Comment #19 from Eugene Shalygin (eugene.shalygin@gmail.com) ---
(In reply to Luiz Von Dentz from comment #18)
> Created attachment 306621 [details]
> Bluetooth: hci_event: Fix setting DISCOVERY_FINDING for passive scanning

Applied that to 6.10.0 and it helped. Thank you!

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

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

[Bug 219088] bluetooth scanning doesn't work in 6.10.0

[bugzilla-daemon]

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

Artem S. Tashkinov (aros@gmx.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Bisected commit-id|                            |2e2515c1ba384ae44f6bf13dd64
                   |                            |b9a0a950798c4
             Status|NEW                         |RESOLVED
         Resolution|---                         |CODE_FIX

--- Comment #20 from Artem S. Tashkinov (aros@gmx.com) ---
(In reply to Luiz Von Dentz from comment #18)
> Created attachment 306621 [details]
> Bluetooth: hci_event: Fix setting DISCOVERY_FINDING for passive scanning

Please push to stable.

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

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