public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric B Munson <eric@munsonfam.org>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Johan Hedberg <johan.hedberg@gmail.com>,
	Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
	linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Problem: Bluetooth stops connecting to paired devices after commit 6a98e3836fa207
Date: Tue, 8 Mar 2022 14:19:03 -0500	[thread overview]
Message-ID: <YiesJ4sLv010CpsA@munsonfam.org> (raw)
In-Reply-To: <Yh/HKSW05IfXCGbR@munsonfam.org>

[-- Attachment #1: Type: text/plain, Size: 926 bytes --]

On Wed, 02 Mar 2022, Eric B Munson wrote:

> Hi,
> 
> When testing the latest upstream this morning, my bluetooth mouse
> stopped working. Further inspection showed that my laptop is failing to
> connect, but I didn't see anything relevant in dmesg, the driver seemed
> to load firmware and intialize fine.
> 
> A bisect turned up commit 6a98e3836fa207 as the first bad one, but
> unfortunately there was another problem discovered during the bisect
> where my bluetooth radio failed to come up at all.
> 
> I am using a 5 year old Lenovo X1 carbon which is using the Intel
> Wireless 8265 / 8275 card and the btintel driver.
> 
> I can easily reproduce, and would be happy to test patches or help
> diagnose if I can. Is this a known issue?
> 
> Regards,
> Eric

This problem remains with the latest 5.17-rc7 kernel. Is there anything
I can offer to help pinpoint what the cause is?

Regards,
Eric

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2022-03-08 19:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-02 19:36 Problem: Bluetooth stops connecting to paired devices after commit 6a98e3836fa207 Eric B Munson
2022-03-08 19:19 ` Eric B Munson [this message]

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=YiesJ4sLv010CpsA@munsonfam.org \
    --to=eric@munsonfam.org \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.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