public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
* [Bug 220391] New: Headset is disconnected immediately
@ 2025-08-01 15:24 bugzilla-daemon
  2025-08-02 15:43 ` [Bug 220391] " bugzilla-daemon
  2025-08-02 19:30 ` bugzilla-daemon
  0 siblings, 2 replies; 3+ messages in thread
From: bugzilla-daemon @ 2025-08-01 15:24 UTC (permalink / raw)
  To: linux-bluetooth

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

            Bug ID: 220391
           Summary: Headset is disconnected immediately
           Product: Drivers
           Version: 2.5
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Bluetooth
          Assignee: linux-bluetooth@vger.kernel.org
          Reporter: antti.garding.oss@gmail.com
        Regression: No

Created attachment 308433
  --> https://bugzilla.kernel.org/attachment.cgi?id=308433&action=edit
Output of dmesg after a boot-up and an attempt to connect the headset and
output of btmon

A little foreword as this is not an issue with the upstream kernel... I asked
about this issue on the linux-bluetooth mailing list and was told to create a
bug report here in order to share logs. What follows in this report is what I
originally wrote on that mailing list.

I am having a issue using my Bluetooth headset (Sony WH-1000XM3) in
Linux. When I turn it on, the headset is immediately connected, but
after that, it is also immediately disconnected. This
connect-disconnect is automatically repeated three times with some
seconds between the occasions.

My environment is a Lenovo Thinkpad E14 Gen 4 laptop running Xubuntu
22.04. The computer has an integrated WLAN + Bluetooth adapter based
on Intex AX201, connected on USB bus. WLAN works fine and also the
Bluetooth works when running Windows. I have read on Intel’s forum
that the driver for the chip should have been ok since kernel version
5.10. My distribution comes with 6.8 so this issue shouldn’t be about
that.

Log time ago, I managed to pair the headset and it is still listed as
a paired device. Trying to unpair it in the bluetoothctl console
results in error message saying the device doesn’t exist.

Here is what happens in bluetoothctl console when I try to connect the
headset manually:

[bluetooth]# connect 38:18:4C:D4:C2:94
Attempting to connect to 38:18:4C:D4:C2:94
[CHG] Device 38:18:4C:D4:C2:94 Connected: yes
Failed to connect: org.bluez.Error.Failed br-connection-canceled
[CHG] Device 38:18:4C:D4:C2:94 Connected: no
[CHG] Device 38:18:4C:D4:C2:94 Connected: yes
[CHG] Device 38:18:4C:D4:C2:94 Connected: no
[CHG] Device 38:18:4C:D4:C2:94 Connected: yes
[CHG] Device 38:18:4C:D4:C2:94 Connected: no

Here are some log prints related to Bluetooth in general:

sudo dmesg | grep -i blue
[    2.899284] Bluetooth: Core ver 2.22
[    2.899534] NET: Registered PF_BLUETOOTH protocol family
[    2.899535] Bluetooth: HCI device and connection manager initialized
[    2.899574] Bluetooth: HCI socket layer initialized
[    2.899593] Bluetooth: L2CAP socket layer initialized
[    2.899601] Bluetooth: SCO socket layer initialized
[    2.951909] Bluetooth: hci0: Device revision is 2
[    2.951914] Bluetooth: hci0: Secure boot is enabled
[    2.951915] Bluetooth: hci0: OTP lock is enabled
[    2.951916] Bluetooth: hci0: API lock is enabled
[    2.951917] Bluetooth: hci0: Debug lock is disabled
[    2.951918] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[    2.951920] Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype
1 build 38
[    2.952008] Bluetooth: hci0: DSM reset method type: 0x00
[    2.960708] Bluetooth: hci0: Found device firmware: intel/ibt-0040-4150.sfi
[    2.960752] Bluetooth: hci0: Boot Address: 0x100800
[    2.960754] Bluetooth: hci0: Firmware Version: 107-51.22
[    3.272512] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio
is blocked
[    4.012759] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    4.012763] Bluetooth: BNEP filters: protocol multicast
[    4.012770] Bluetooth: BNEP socket layer initialized
[    4.684563] Bluetooth: hci0: Waiting for firmware download to complete
[    4.684902] Bluetooth: hci0: Firmware loaded in 1683777 usecs
[    4.685041] Bluetooth: hci0: Waiting for device to boot
[    4.700965] Bluetooth: hci0: Malformed MSFT vendor event: 0x02
[    4.701034] Bluetooth: hci0: Device booted in 15702 usecs
[    4.701904] Bluetooth: hci0: Found Intel DDC parameters:
intel/ibt-0040-4150.ddc
[    4.704071] Bluetooth: hci0: Applying Intel DDC parameters completed
[    4.707146] Bluetooth: hci0: Firmware timestamp 2022.51 buildtype 1
build 56683
[    4.707151] Bluetooth: hci0: Firmware SHA1: 0xe2305c5c
[    4.776168] Bluetooth: MGMT ver 1.22
[    6.448715] Bluetooth: RFCOMM TTY layer initialized
[    6.448724] Bluetooth: RFCOMM socket layer initialized
[    6.448727] 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.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug 220391] Headset is disconnected immediately
  2025-08-01 15:24 [Bug 220391] New: Headset is disconnected immediately bugzilla-daemon
@ 2025-08-02 15:43 ` bugzilla-daemon
  2025-08-02 19:30 ` bugzilla-daemon
  1 sibling, 0 replies; 3+ messages in thread
From: bugzilla-daemon @ 2025-08-02 15:43 UTC (permalink / raw)
  To: linux-bluetooth

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
     Kernel Version|                            |vmlinuz-6.8.0-64-generic
         Resolution|---                         |ANSWERED

--- Comment #1 from Artem S. Tashkinov (aros@gmx.com) ---
Vendor kernels are not supported here.

Please test kernel 6.16.0 with the latest firmware.

If that's reproducible please reopen.

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

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug 220391] Headset is disconnected immediately
  2025-08-01 15:24 [Bug 220391] New: Headset is disconnected immediately bugzilla-daemon
  2025-08-02 15:43 ` [Bug 220391] " bugzilla-daemon
@ 2025-08-02 19:30 ` bugzilla-daemon
  1 sibling, 0 replies; 3+ messages in thread
From: bugzilla-daemon @ 2025-08-02 19:30 UTC (permalink / raw)
  To: linux-bluetooth

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

Paul Menzel (pmenzel+bugzilla.kernel.org@molgen.mpg.de) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pmenzel+bugzilla.kernel.org
                   |                            |@molgen.mpg.de

--- Comment #2 from Paul Menzel (pmenzel+bugzilla.kernel.org@molgen.mpg.de) ---
@Antti, thank you for opening the report here. I actually do not know what the
rule for the Bluetooth subsystem is. I believe, the Intel folks are interested
in having their hardware work on all distributions.

On Ubuntu, you can easily use their linux-mainline PPA [1]. Copy the
*linux-image-unsigned-…* and *linux-modules-…* packages, and install them with
`dpkg -i …`.


[1]: https://kernel.ubuntu.com/mainline/v6.16/

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

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2025-08-02 19:30 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-08-01 15:24 [Bug 220391] New: Headset is disconnected immediately bugzilla-daemon
2025-08-02 15:43 ` [Bug 220391] " bugzilla-daemon
2025-08-02 19:30 ` bugzilla-daemon

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox