From: Paul Menzel <pmenzel@molgen.mpg.de>
To: "Kris Karas (Bug Reporting)" <bugs-a21@moonlit-rail.com>
Cc: Bagas Sanjaya <bagasdotme@gmail.com>,
linux-bluetooth@vger.kernel.org, regressions@lists.linux.dev,
linux-kernel@vger.kernel.org,
Marcel Holtmann <marcel@holtmann.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
Zach <zacheryvig@outlook.com>
Subject: Re: Regression: Inoperative bluetooth, Intel chipset, mainline kernel 6.6.2+
Date: Fri, 1 Dec 2023 09:27:47 +0100 [thread overview]
Message-ID: <d095bcbe-af0c-4eb3-99c8-32371136dd2c@molgen.mpg.de> (raw)
In-Reply-To: <115e819b-0271-403c-b034-ef3aebbb85cd@moonlit-rail.com>
Dear Kris,
Am 01.12.23 um 09:19 schrieb Kris Karas (Bug Reporting):
> 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.
>
> 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.
Nice, that is often the fastest way to fix something.
To avoid the time rebooting the system, you could try to expose the
drive to a virtual machine [1].
Kind regards,
Paul
[1]:
https://lore.kernel.org/all/331ae35c-7d48-46fc-c4ae-1e60cb0f3378@molgen.mpg.de/
(The failure in the VM was due to another regression in the Linux
kernel, so the how-to actually worked for me.)
next prev parent reply other threads:[~2023-12-01 8:28 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 ` Bagas Sanjaya
2023-12-01 8:19 ` Kris Karas (Bug Reporting)
2023-12-01 8:27 ` Paul Menzel [this message]
2023-12-03 12:17 ` Oleksandr Natalenko
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=d095bcbe-af0c-4eb3-99c8-32371136dd2c@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--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=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
all inboxes | Powered by JetHome®