Received: by 2002:a05:6a10:af89:0:0:0:0 with SMTP id iu9csp3586758pxb; Mon, 24 Jan 2022 12:54:08 -0800 (PST) X-Google-Smtp-Source: ABdhPJzlNHOCNHVyYBXODh7OIxnbVD9upZqkOUXxLO402qqYlCuuH12qQZeM6Cfza+MCi/g9FsCU X-Received: by 2002:a17:90b:3106:: with SMTP id gc6mr61270pjb.77.1643057648248; Mon, 24 Jan 2022 12:54:08 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1643057648; cv=none; d=google.com; s=arc-20160816; b=lUmBd1QVXH28hgHOYftw7lJuYUClYdf9inNWJitwHCJG4vWZPSPyU0ge0HhXRIJp9d EvfdusINmhSzJxbHIS6FLI8cuNpfU0hOG7wUTvQVCxV8U5dQq3tQ67JRQqdnBxtcvNDn XXAwy9pml0UKr1ZVUGNY4bp8o4vzOpBCgVR227HHgwnfJzvZ8kx/98vvly6O+ir5H3vg uOQlZ53DwxYlPBPlHHybmtWsRjF+WkBUEciysRwqV/a563rrAyQ+vQDCDySoAi/T7n/h l9c/Vi1HhcSRjnKLWcjtoa2Bj7hqtnDFCcNHk/6WcV0HfaE0x+OI3LZK7JUgJqcRp/jI a+RQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:references:message-id:in-reply-to :subject:cc:to:reply-to:from:date:dkim-signature; bh=s5VkimkBBVefEXSWJ1Xn/iuQh/cb7IGQbJI5hDwLIwI=; b=jMPlIJJydcOO1AmJjW8W3GkdlDMYZwFw2NckNZF7ht4I2b6LpcL3XfilOAoMzWcJll kinB5MRENaBk68I+AcjeCig8zkuS2YZc/EdyqRZhLcrtq9Z1FFE7KlY3e8HVxoooSyR5 ZLrXUOfHUZqoXoEMyndxV6+V+xBOGiLriL3qtpV7iOp0w5VVnOM9E2GOLWHhWYM7Qjwq XG3ZnUkrLzx8bTkNM2VxlfYDcJo7CDNi1Vri05uv6BOQQsLGqRWup4RPMo6ynyH7YNbb VXi5MOtvGcPVBhgyIJo+dDNuxsBzwsVhswfu1vn3DZvs3wfaIkFoID6kGV2ufHfhLLXZ jueQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@panix.com header.s=panix header.b=EixlpbFf; spf=pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-bluetooth-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id e15si15844342plh.547.2022.01.24.12.53.36; Mon, 24 Jan 2022 12:54:08 -0800 (PST) Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=fail header.i=@panix.com header.s=panix header.b=EixlpbFf; spf=pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-bluetooth-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1355147AbiAXULy (ORCPT + 99 others); Mon, 24 Jan 2022 15:11:54 -0500 Received: from mailbackend.panix.com ([166.84.1.89]:39867 "EHLO mailbackend.panix.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1359386AbiAXT7k (ORCPT ); Mon, 24 Jan 2022 14:59:40 -0500 Received: from xps-7390.local (ip98-164-213-246.oc.oc.cox.net [98.164.213.246]) by mailbackend.panix.com (Postfix) with ESMTPSA id 4JjLRZ3Vh8z3l7M; Mon, 24 Jan 2022 14:59:38 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=panix.com; s=panix; t=1643054379; bh=ZFwyVBxFNWzqkyy+Kt9VvR1ApRt4kZ9zmG7uWNPaBmM=; h=Date:From:Reply-To:To:cc:Subject:In-Reply-To:References; b=EixlpbFfS6UbZZZaHTXXteKPcscjywPCTGjco8DDpVSOqXOsFpj0bT42MT8dfhwOa cVG1NhKi7cN+cyHznBN881XzLj1T4QoPyFwpQNGl8DmF0FXA1FeNF3PBMZ8cq3jpBu qb1qpe8rJ1JiKGnjVT6gzXTFVXDvQ/h8nT9c2QQs= Date: Mon, 24 Jan 2022 11:59:37 -0800 (PST) From: "Kenneth R. Crudup" Reply-To: "Kenneth R. Crudup" To: Luiz Augusto von Dentz cc: Luiz Augusto Von Dentz , "linux-bluetooth@vger.kernel.org" , "Kenneth R. Crudup" Subject: Re: Commit ad383c2c6 ("Bluetooth: hci_sync: Enable advertising when LL privacy is enabled") breaks my MS ArcTouch mouse In-Reply-To: Message-ID: <91c1e9ef-4786-b9f5-8bb8-b93c84c0874b@panix.com> References: <4124ccb8-11f-21e9-982e-7fb07f23225@panix.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Precedence: bulk List-ID: X-Mailing-List: linux-bluetooth@vger.kernel.org On Mon, 24 Jan 2022, Luiz Augusto von Dentz wrote: > > I'm running Linus' master (as of today, 1c52283265a462a100). With this commit in > > place I get no bluetooth ("hcitool dev" shows no adapters) and/or I can't see my > > MS ArcTouch mouse. > It would be great to have some logs, btmon, dmesg, etc. That's just it- nothing shows up in any log/dmesg; unlike when a non-MS mouse is detected and I get the notification from the HID layer. I even did an s/{bt}_debug/{bt}_info/g over all the files in the commit, and when that mouse is power-cycled it doesn't even make a peep in the logs- it's like it's not even being seen (vs. several lines when I use my ordinary mouse). What params should I use for "btmon" so I can send you the output? > If the adapter doesn't work this might be related to firmware loading Turns out this was a red herring; I always have the adapter. > anymore the LL privacy feature is not > enabled by default so I wonder if you had it enabled in userspace? Where would I go to check that? -Kenny -- Kenneth R. Crudup / Sr. SW Engineer, Scott County Consulting, Orange County CA