public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Oleksandr Natalenko <oleksandr@natalenko.name>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
	Linux Bluetooth <linux-bluetooth@vger.kernel.org>,
	Linux Regressions <regressions@lists.linux.dev>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"Kris Karas (Bug Reporting)" <bugs-a21@moonlit-rail.com>
Cc: Marcel Holtmann <marcel@holtmann.org>,
	Johan Hedberg <johan.hedberg@gmail.com>,
	Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
	Zach <zacheryvig@outlook.com>,
	Paul Menzel <pmenzel@molgen.mpg.de>
Subject: Re: Regression: Inoperative bluetooth, Intel chipset, mainline kernel 6.6.2+
Date: Sun, 03 Dec 2023 13:17:50 +0100	[thread overview]
Message-ID: <2709774.mvXUDI8C0e@natalenko.name> (raw)
In-Reply-To: <115e819b-0271-403c-b034-ef3aebbb85cd@moonlit-rail.com>

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

Hello.

On pátek 1. prosince 2023 9:19:04 CET Kris Karas (Bug Reporting) wrote:
> Bagas Sanjaya wrote:
> > Kris Karas (Bug Reporting) wrote:
> >> I have a regression going from mainline kernel 6.1.62 to 6.1.63, and also
> >> from kernel 6.6.1 to 6.6.2; I can bisect if patch authors can't locate the
> >> relevant commit.  In the most recent kernels mentioned, bluetooth won't
> >> function.
> > 
> > Then please do bisection; without it, nobody will look into this properly.
> 
> As only a few people are reporting this, it must be pretty 
> hardware-specific (or perhaps Kconfig/firmware specific).  I'll do a 
> bisect.  A bit too late here in Boston (03:00), and kiddo's birthday 
> "later today", so will probably get to this on the weekend.
> 
> > You may also want to check current mainline (v6.7-rc3) to see if this
> > regression have already been fixed.
> 
> Just tried 6.7.0-rc3, and it is also affected.

Does passing `btusb.enable_autosuspend=N` via a kernel cmdline help? [1]

[1] https://lore.kernel.org/lkml/5993222.lOV4Wx5bFT@natalenko.name/

> I hadn't git-pulled my linux-stable since May, so that gave me a good 
> chance to test the very latest.  :-)  And conveniently I'm now set for 
> the bisect.
> 
> Kris
> 
> 


-- 
Oleksandr Natalenko (post-factum)

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2023-12-03 12:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ee109942-ef8e-45b9-8cb9-a98a787fe094@moonlit-rail.com>
2023-12-01  6:27 ` Regression: Inoperative bluetooth, Intel chipset, mainline kernel 6.6.2+ Bagas Sanjaya
2023-12-01  8:19   ` Kris Karas (Bug Reporting)
2023-12-01  8:27     ` Paul Menzel
2023-12-03 12:17     ` Oleksandr Natalenko [this message]
2023-12-03 18:46       ` Kris Karas (Bug Reporting)

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=2709774.mvXUDI8C0e@natalenko.name \
    --to=oleksandr@natalenko.name \
    --cc=bagasdotme@gmail.com \
    --cc=bugs-a21@moonlit-rail.com \
    --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 \
    --cc=pmenzel@molgen.mpg.de \
    --cc=regressions@lists.linux.dev \
    --cc=zacheryvig@outlook.com \
    /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