[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJZ5v0hcX0JAMBA+EVZURDH1BTQ2zL-W_4BjSx0a=1oRaR90ug@mail.gmail.com>
Date: Wed, 12 Jun 2024 19:23:26 +0200
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: "fhortner@...oo.de" <fhortner@...oo.de>
Cc: Linux PM <linux-pm@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux regressions mailing list <regressions@...ts.linux.dev>
Subject: Re: Regression, thermal: core: battery reading wrong after wake from
S3 [Was: Bug Report according to thermal_core.c]
Restored list CCs.
On Wed, Jun 12, 2024 at 3:41 PM Rafael J. Wysocki <rafael@...nel.org> wrote:
>
> On Wed, Jun 12, 2024 at 11:56 AM fhortner@...oo.de <fhortner@...oo.de> wrote:
> >
> > Am 11.06.24 um 16:42 schrieb Rafael J. Wysocki:
> >
> > This doesn't make them run in a different order, it just delays both
> > of them, because the notifiers are called sequentially.
> >
> > However, if you added the msleep() at the beginning of
> > thermal_zone_device_resume(), it would change the ordering of this
> > function with respect to the PM notifiers, so please try doing this.
> >
> > I did so and added msleep(1000) to thermal_core.c line 1634
> > I have also reverted the patch you sent me.
> >
> > The battery readings after resume from S3 sleep where fine.
> > I have tried 2 reboots with 4 sleep/wake cycles, respectively
>
> Thanks!
>
> This means that the two code paths in question somehow interfere
> destructively when they are running in parallel with each other.
One more thing to try is the attached patch (independent of the
previous one) to lower the priority of the thermal PM notifier to make
it run always after the ACPI battery one.
Please test this one too and let me know if it works for you.
View attachment "thermal-core-resume-prio.patch" of type "text/x-patch" (499 bytes)
Powered by blists - more mailing lists