From: Chris Clayton <chris2553@googlemail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>, rafael.j.wysocki@intel.com
Subject: Re: Intel bluetooth regression in 5.15.3
Date: Fri, 19 Nov 2021 15:32:28 +0000 [thread overview]
Message-ID: <3212e538-f846-40ba-7a2a-a687c24c8b1a@googlemail.com> (raw)
In-Reply-To: <YZe2iVBCPIdsWmZd@kroah.com>
On 19/11/2021 14:36, Greg Kroah-Hartman wrote:
> On Fri, Nov 19, 2021 at 01:43:32PM +0000, Chris Clayton wrote:
>> Hi,
>>
>> I built and installed 5.15.3 this morning and found that my bluetooth devices no longer work. 5.15.2 and 5.10.80 are
>> both OK.
>>
>> I've bisected it and landed on:
>>
>> cfc1a472a8d89c0d0bbb3600501eeeebc5ec8039 is the first bad commit
>> commit cfc1a472a8d89c0d0bbb3600501eeeebc5ec8039
>> Author: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>> Date: Sat Oct 9 16:22:09 2021 +0200
>>
>> ACPI: scan: Release PM resources blocked by unused objects
>>
>> [ Upstream commit c10383e8ddf4810b9a5c1595404c2724d925a0a6 ]
>>
>> On some systems the ACPI namespace contains device objects that are
>> not used in certain configurations of the system. If they start off
>> in the D0 power state configuration, they will stay in it until the
>> system reboots, because of the lack of any mechanism possibly causing
>> their configuration to change. If that happens, they may prevent
>> some power resources from being turned off or generally they may
>> prevent the platform from getting into the deepest low-power states
>> thus causing some energy to be wasted.
>>
>> Address this issue by changing the configuration of unused ACPI
>> device objects to the D3cold power state one after carrying out
>> the ACPI-based enumeration of devices.
>>
>> BugLink: https://bugzilla.kernel.org/show_bug.cgi?id=214091
>> Link: https://lore.kernel.org/linux-acpi/20211007205126.11769-1-mario.limonciello@amd.com/
>> Reported-by: Mario Limonciello <mario.limonciello@amd.com>
>> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>> Tested-by: Mario Limonciello <mario.limonciello@amd.com>
>> Signed-off-by: Sasha Levin <sashal@kernel.org>
>>
>> drivers/acpi/glue.c | 25 +++++++++++++++++++++++++
>> drivers/acpi/internal.h | 1 +
>> drivers/acpi/scan.c | 6 ++++++
>> 3 files changed, 32 insertions(+)
>>
>> 5.15.3 with that commit reverted works fine.
>>
>> Let me know if you need any additional diagnostics or patches tested but please cc me as I'm not subscribed.
>
> Is 5.16-rc1 also a problem for you and your devices?
>
> thanks,
>
No, 5.16-rc1+, built after a git pull just a few minutes ago, woks fine. Looking at Linus's tree, the commit I
identified in the bisection was reverted a couple of days ago (commit 3b2b49e6dfdcf423506a771bf44cee842596351a).
Thanks
Chris
> greg k-h
>
next prev parent reply other threads:[~2021-11-19 15:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-19 13:43 Intel bluetooth regression in 5.15.3 Chris Clayton
2021-11-19 14:36 ` Greg Kroah-Hartman
2021-11-19 15:32 ` Chris Clayton [this message]
2021-11-19 17:04 ` Greg Kroah-Hartman
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=3212e538-f846-40ba-7a2a-a687c24c8b1a@googlemail.com \
--to=chris2553@googlemail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.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;
as well as URLs for NNTP newsgroup(s).