From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-yb1-f181.google.com (mail-yb1-f181.google.com [209.85.219.181]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 7283A15C1 for ; Mon, 28 Feb 2022 19:35:08 +0000 (UTC) Received: by mail-yb1-f181.google.com with SMTP id p19so22685719ybc.6 for ; Mon, 28 Feb 2022 11:35:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=gEJ3DsiDthcuH9tTzOHmbsSJefzTxI3kBK1Vok77M5Q=; b=Vs8KTM+i6iaD1kI0oT15nX/aQgfVrm2Ip5T/0PDd+miQZyMvLTdSz3/bwNMwX30Jju Hl6YAoTH5GgE+CHNLX+gAV/4NJo+K1GamfwfBbxwCfKsR4CW849RChtRL6zHblufr7Vm +8oeeYaxq2R7pJG8lzKspsLB6HucD1BmWZoeNON3pxJp66V+4/xpGKSzIntnHbeSApJl J+tT3fhOYd/Gjsct23C2wBIhRbrwVoldcEOEw2DbbC7yEa2TmqkdMoQNat5ZzAc/G6U1 P/P9v9XKFtIJ+tMI0RQ6QwK+lmZDyHwkveU0KHRgwmnvPea2xo6vN80OIY/264roMvLq X1aA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=gEJ3DsiDthcuH9tTzOHmbsSJefzTxI3kBK1Vok77M5Q=; b=534id1Sm7skBHLNoK4J/mz7BL2+cxU9O9k/UtqjttTP19kebsZWUbUCm+RmA2YiCvy HFjTZJpH+wQTCi+Dlnsj/3C6rfIzGJ7KQJyNdVD00SU3LCHkF03XUXSNCB5z8uKQYvRO jf1ECYB+UUsAS6r1MWV9xwB8GPoM3Sz+YOiWDV5XEDWah5xsHrFnQDqBLlFClROu05AU eFSJJGbRaUirU+0vZti5yElEdMQWqf6RJrYOReZbZm91F0PFYN9a+dIDrBeA6ZNztUhc fkFpAfQuQoA80wmOFcYJbmr+EZ6l/ZuA1hR4C6zmYr1wstIAE4oWK46LjK/QXerFc0Ub jjAA== X-Gm-Message-State: AOAM531jQI9ZDAME2ulFdYR7OPBxwtd6arvKbG8i1mDGtFi7TAwg/Qum rvSrbKXL4NOgG0ctic7KF1YaFJNlja6kJh2ttHs= X-Google-Smtp-Source: ABdhPJxAq1qztotGN00Wc8m7a69qhJrMtRUDojoXwziQGTTCBAOP1k9tEdKqrJYsxv2knLNV4PkHctVbs2LsxbjpOls= X-Received: by 2002:a25:d754:0:b0:627:f51d:ae0b with SMTP id o81-20020a25d754000000b00627f51dae0bmr11518626ybg.41.1646076907398; Mon, 28 Feb 2022 11:35:07 -0800 (PST) Precedence: bulk X-Mailing-List: regressions@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 References: <9ad505e1-7b59-7ebf-378b-23a6c0e25802@googlemail.com> <82216882-463a-8976-e6bc-4a8919107a31@googlemail.com> <2ce6175c-74ec-8469-80a5-374bd1429542@googlemail.com> <17f2bf7e-1d6b-e090-8926-21a408f2b496@googlemail.com> <16cac2c8-c1ca-c8d7-e3d9-5f00be511614@googlemail.com> In-Reply-To: <16cac2c8-c1ca-c8d7-e3d9-5f00be511614@googlemail.com> From: Luiz Augusto von Dentz Date: Mon, 28 Feb 2022 11:34:56 -0800 Message-ID: Subject: Re: bug kernel 5.17, qualcom and intel adapters, unable to reliably connect to bluetooth devices To: Chris Clayton Cc: Chris Murphy , Bluetooth , regressions@lists.linux.dev Content-Type: text/plain; charset="UTF-8" Hi Chris, On Sat, Feb 26, 2022 at 12:04 AM Chris Clayton wrote: > > Hi, > > On 24/02/2022 15:16, Luiz Augusto von Dentz wrote: > >> I'll try another bisection today, but limit its range to changes made in the net/bluetooth directory. > > That bisection has proved very difficult because the bluetooth "service" in kernels at some steps of the bisection were > completely borked to the extent that blueman's device-manager application wouldn't start and emitted the messages: > > blueman-manager 12.00.37 ERROR Manager:137 on_dbus_name_appeared: Default adapter not found, trying first available. > blueman-manager 12.00.37 ERROR Manager:141 on_dbus_name_appeared: No adapter(s) found, exiting > > Obviously, I don't know whether the problem I am trying to pinpoint is hiding behind this more fundamental problem with > the bluetooth "service", so being unable to say whether that kernel was good or bad, I had to skip. There seems to be a > batch of commits that mean that, whilst the kernel builds okay, hunting down a bluetooth-related problem is not > possible. Eventually and I cursed and gave up. Whatever was causing this breakage has obviously been fixed. > > > Please record the HCI with btmon, it must be producing something since > > it records even the mgmt commands. > > > > Refreshed by a good night's sleep, I started another bisection (between 5.16 and 5.17-rc1) yesterday morning but this > time did not limit it to net/bluetooth. That was going okay until I ran into what I assume is the same batch of borked > kernels. I've been more persistent this time but have just had a run of 16 steps in which the bluetooth support in the > kernel is broken so badly that testing bluetooth is not possible. I will push on today, but I've suspended that activity > to get the hci trace that Luiz has asked for. > > Using information from the bisect, I built a kernel that had tested as bad (but not borked). The commit is > f2b551fad8d8f2ac5e1f810ad595298381e0b0c5. As I've mentioned before, the problem with devices not connecting is > intermittent - for a given kernel, sometimes a connection works and other times it doesn't. On the first boot of this > kernel, my bluetooth devices could connect, Attached are 4 files related to this - the output from btmon, and the > related portions of daemon.log, kern.log and sys.log from /var/log/. Each of the these files is suffixed with ".good". > > I then powered down the laptop and booted into the same kernel. This time the bluetooth devices could not connect. Four > more files are attached for this boot and are suffixed with ".bad". I said in an earlier email that when connection > fails, there is no output from btmon, so that log is empty. That's still the case, but I guess that fact itself is a > clue to what the problem might be. What I can add, however, is that if, in that same bad kernel, I unload and then > reload the btusb module, connections start to work. Maybe that too is a clue. The same unload/load process revives > bluetooth on a kernel built after a pull of Linus' latest and greatest this morning. > > Since I now have a workround, I'm going stop the current bisection that I was doing. I've done another couple of steps > this morning and both produced kernels on which I could not test bluetooth and had to tell git bisect to skip. If > however, I can provide any other diagnostics, please let me know. > > Chris Can you try with the following patch: https://patchwork.kernel.org/project/bluetooth/patch/20220228173918.524733-1-brian.gix@intel.com/ -- Luiz Augusto von Dentz