From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 19644C433EF for ; Mon, 21 Feb 2022 22:34:01 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235667AbiBUWeX (ORCPT ); Mon, 21 Feb 2022 17:34:23 -0500 Received: from mxb-00190b01.gslb.pphosted.com ([23.128.96.19]:36334 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235668AbiBUWeW (ORCPT ); Mon, 21 Feb 2022 17:34:22 -0500 Received: from mail-wm1-x32c.google.com (mail-wm1-x32c.google.com [IPv6:2a00:1450:4864:20::32c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 51161E093 for ; Mon, 21 Feb 2022 14:33:56 -0800 (PST) Received: by mail-wm1-x32c.google.com with SMTP id i19so10287581wmq.5 for ; Mon, 21 Feb 2022 14:33:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20210112; h=message-id:date:mime-version:user-agent:subject:content-language:to :cc:references:from:in-reply-to:content-transfer-encoding; bh=kby3PNa2Owh2Gu1TRCvl+evsgj7HxbpNl9YbTkLaljw=; b=ppr41cJmihFf5hW1e9+ots1hq5N2GDNepZo/K/Fc4PdU6XN2ld0Cu2axJmSf3kh8Y8 Z4Acv9eaxV6cfSl61W1eNig+6hc/O7d+i6TxK89iEPmUaaaGFksFnwk5/c9W13zrOD5N zKO8/QRXXDQ2cJh4/RF1pT4RJo+GyDOQwYXHtZq07NhlXbCvmPxgdb7jcKV+F9FbDUUJ SBqvTsEjAxMUVstc4bBLgzfI8caN60FqsHqMdKX6XKMk7/AapBXhvpFC61CpTvAGZcBb VpSsnhL+PvPyjYsSSnLrbZqM1eptxZUyEzPX18m+ODU6JjprD0k2AXiUgOV4nqmoHxz7 gFWg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:in-reply-to :content-transfer-encoding; bh=kby3PNa2Owh2Gu1TRCvl+evsgj7HxbpNl9YbTkLaljw=; b=IKV8BCK37Tia+dOou8dy3q8deAfNkXVcHmiw4GWOmfCfhQ1x9EY8M9SHIi5PVZB3eI DHz4rsbtzj94DYgaEF1qyemuGcjzJkHNivTuppI7wFexbwNop5VQVwFN/JjFx3t8Upr4 c8e6PyVWYsr6w1WWBD+BkwO8S+Bdyo4JLoMz381gd7/NDbpHYEKT+jKUC72WBs8f3q8P GShY/cCNkrcCy4eRouWbA/GOINUjQNO5q3Lz4WK3fF020kQno9DWvYrolvBBBeI4E538 Qhd56jfBKRtLUaHRxfS9HOxFeVxUILiUos+bFibqktLBGwEfQpvfxYCH7VBrsdHfbgTf pO6A== X-Gm-Message-State: AOAM531B/eAGEvgEdKNlTGShpD8efBUcDFkEwidcxwX1d5x0MWtR97xz t5p00Qm5/8LTpLwWqVzcVj4= X-Google-Smtp-Source: ABdhPJwmVpNApOJZ2es28Zs/zom4ArUnT2iLIjO/JMVaOJ6F5L9m0HMjXfKavdZT3zz/Clw3GwEHJg== X-Received: by 2002:a05:600c:4c27:b0:37b:fa17:899a with SMTP id d39-20020a05600c4c2700b0037bfa17899amr882310wmp.126.1645482834707; Mon, 21 Feb 2022 14:33:54 -0800 (PST) Received: from [192.168.1.10] (4e691f2a.skybroadband.com. [78.105.31.42]) by smtp.googlemail.com with ESMTPSA id f14sm707004wmq.3.2022.02.21.14.33.53 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 21 Feb 2022 14:33:54 -0800 (PST) Message-ID: Date: Mon, 21 Feb 2022 22:33:49 +0000 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.6.1 Subject: Re: bug kernel 5.17, qualcom and intel adapters, unable to reliably connect to bluetooth devices Content-Language: en-GB To: Luiz Augusto von Dentz Cc: Chris Murphy , Bluetooth References: <9ad505e1-7b59-7ebf-378b-23a6c0e25802@googlemail.com> From: Chris Clayton In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-bluetooth@vger.kernel.org Thanks Luiz. On 21/02/2022 21:27, Luiz Augusto von Dentz wrote: > Hi Chris, > > On Mon, Feb 21, 2022 at 12:23 PM Chris Clayton wrote: >> >> Hi Luiz, >> >> On 21/02/2022 17:11, Luiz Augusto von Dentz wrote: >>> Hi Chris, >>> >>> On Mon, Feb 21, 2022 at 5:22 AM Chris Clayton wrote: >>>> >>>> Sorry folks, clicked Send instead of Save Draft in my earlier message. >>>> >>>> Anyway... >>>> >>>> On 18/02/2022 03:49, Chris Murphy wrote: >>>>> On Thu, Feb 17, 2022 at 5:15 PM Luiz Augusto von Dentz >>>>> wrote: >>>>>> >>>>>> Hi Chris, >>>>>> >>>>>> On Thu, Feb 17, 2022 at 3:36 PM Chris Murphy wrote: >>>>>>> >>>>>>> OK I started over, and for now keeping the reporting constrained to >>>>>>> the hardware I personally have on hand. >>>>>>> >>>>>>> Hardware: >>>>>>> Lenovo Thinkpad X1 Carbon Gen 7 >>>>>>> Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 >>>>>>> Jefferson Peak (JfP) >>>>>>> Sony 1000XM3 headset >>>>>>> bluez-5.63-3.fc36.x86_64 >>>>>>> >>>>>>> kernel 5.17.0-rc4 >>>>>>> * remove the paired headset with bluetoothctl >>>>>>> * reset the headset so it's not longer paired either >>>>>>> * put the headset in pairing mode >>>>>>> * GNOME Settings Bluetooth panel sees -> LE_WH-1000XM3, Not Setup >>>>>>> * click on Not Setup and nothing happens >>>>>> >>>>>> Well from the logs it doesn't seem the GNOME Setting is trying to do >>>>>> anything, have you tried bluetoothctl> connect
>>>>> >>>>> `bluetoothctl scan on` does see the device >>>>> $ bluetoothctl pair 38:18:4C:24:2D:1D >>>>> Device 38:18:4C:24:2D:1D not available >>>>> $ bluetoothctl connect 38:18:4C:24:2D:1D >>>>> Device 38:18:4C:24:2D:1D not available >>>>> >>>>> $ journalctl -b -o short-monotonic --no-hostname | grep -i blue >>>>> https://drive.google.com/file/d/1x9EDvDx6XUowyRy2056n6uW-4PLx5KRb/view?usp=sharing >>>>> >>>>> >>>> >>>> I too am experiencing the problem that already-paired devices fail to connect to my laptop when running a 5.17 kernel. >>>> >>>> Extract from dmesg shows: >>>> [ 3.825684] Bluetooth: hci0: Waiting for firmware download to complete >>>> [ 3.825910] Bluetooth: hci0: Firmware loaded in 1551910 usecs >>>> [ 3.825910] Bluetooth: hci0: unexpected event 0xff length: 5 > 0 >>>> [ 3.825936] Bluetooth: hci0: Waiting for device to boot >>>> [ 3.839948] Bluetooth: hci0: unexpected event 0xff length: 7 > 0 >>>> [ 3.839973] Bluetooth: hci0: Device booted in 13715 usecs >>>> [ 3.840205] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc >>>> [ 3.843002] Bluetooth: hci0: Applying Intel DDC parameters completed >>>> [ 3.843926] Bluetooth: hci0: Firmware revision 0.4 build 125 week 46 2021 >>>> >>>> Extract from lshw shows: >>>> description: Bluetooth wireless interface >>>> product: AX201 Bluetooth >>>> vendor: Intel Corp. >>>> physical id: e >>>> bus info: usb@1:e >>>> version: 0.02 >>>> capabilities: bluetooth usb-2.01 >>>> configuration: driver=btusb maxpower=100mA speed=12Mbit/s >>>> >>>> I don't know whether this will help, but I've found that the problem only occurs when boot from cold (i.e power on the >>>> laptop. If I then do a warm reboot, my bluetooh devices connect successfully. The significant difference may be that on >>>> a cold start, the firmware needs to loaded whereas on a warm reboot I see: >>>> >>>> [ 2.000989] Bluetooth: hci0: Firmware already loaded >>>> >>>> Hope this helps. I am happy to test any fixes or provide additional diagnostics, but I'm not subscribed so please cc me. >>> >>> What exactly doesn't work? Can't you power up the controller, etc? >> >> I have two bluetooth audio devices. One is a set of headphones and the other is a speaker. Both are paired with my >> laptop and, normally, both automatically connect to the laptop when I power them on. I've had the speaker for three >> years or more is has worked fine with all kernels that I have used up to and including the latest stable series - >> 5.16.10. The headphones were acquired a year or so ago and to date have worked with all kernels I have had installed >> since then. Consequently, this problem is a 5,17 regression. >> >> After a cold (power-on) boot with a 5.17 kernel, they do no connect automatically when switched on. Furthermore, if I >> use the blueman application to attempt to connect, that attempt fails. The only way that I have found to connect >> successfully is to do a reboot, after which the devices can connect automatically when I switch them on. >> >> I'm sorry, I have no idea what you mean by "Can't you power up the controller, etc?" > > Use btmon to capture the trace when you attempt to connect, it also > would be a good idea to use bluetoothctl when attempting to connect. It's getting late now, so I'll do a btmon trace tomorrow. From it's name, I assume bluetoothctl is part of the systemd suite. I don't have systemd on the laptop but use sysvinit to start userspace including, of course, bluetoothd. Chris >