public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 219405] New: [regression] mt7922 bluetooth scanning does not work in 6.11.4
Date: Mon, 21 Oct 2024 09:29:20 +0000	[thread overview]
Message-ID: <bug-219405-62941@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 219405
           Summary: [regression] mt7922 bluetooth scanning does not work
                    in 6.11.4
           Product: Drivers
           Version: 2.5
          Hardware: AMD
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Bluetooth
          Assignee: linux-bluetooth@vger.kernel.org
          Reporter: eugene.shalygin@gmail.com
        Regression: No

6.11.3 -> 6.11.4 update broke bluetooth scanning for mt7922. 

09:00.0 Network controller: MEDIATEK Corp. MT7922 802.11ax PCI Express Wireless
Network Adapter
    Subsystem: Foxconn International, Inc. Device e0cd
    Kernel driver in use: mt7921e
    Kernel modules: mt7921e

With 6.11.3:
$ dmesg| grep -i bluetooth                                                     
                                                                               
                                                                [    5.170554]
Bluetooth: Core ver 2.22
[    5.170762] NET: Registered PF_BLUETOOTH protocol family
[    5.170949] Bluetooth: HCI device and connection manager initialized
[    5.171130] Bluetooth: HCI socket layer initialized
[    5.171313] Bluetooth: L2CAP socket layer initialized
[    5.171495] Bluetooth: SCO socket layer initialized
[    6.574657] Bluetooth: hci0: HW/SW Version: 0x008a008a, Build Time:
20240716163633
[    6.614305] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    6.614311] Bluetooth: BNEP filters: protocol multicast
[    6.614316] Bluetooth: BNEP socket layer initialized
[   27.410062] Bluetooth: hci0: Device setup in 20480957 usecs
[   27.410070] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection
command is advertised, but not supported.
[   27.687794] Bluetooth: hci0: AOSP extensions version v1.00
[   27.687800] Bluetooth: hci0: AOSP quality report is supported
[   27.687914] Bluetooth: MGMT ver 1.23
[   27.687951] Bluetooth: ISO socket layer initialized
[   27.784423] Bluetooth: RFCOMM TTY layer initialized
[   27.784430] Bluetooth: RFCOMM socket layer initialized
[   27.784432] Bluetooth: RFCOMM ver 1.11
[   27.955038] Bluetooth: hci0: Invalid LTK for a8:79:8d:fe:ef:cb

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

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

             reply	other threads:[~2024-10-21  9:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-21  9:29 bugzilla-daemon [this message]
2024-10-21  9:35 ` [Bug 219405] [regression] mt7922 bluetooth scanning does not work in 6.11.4 bugzilla-daemon
2024-10-21 11:03 ` bugzilla-daemon
2024-10-22  9:20 ` bugzilla-daemon
2024-10-22  9:21 ` bugzilla-daemon
2024-10-22  9:21 ` bugzilla-daemon
2024-10-22  9:34 ` bugzilla-daemon
2024-10-22 10:15 ` 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-219405-62941@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