linux-kernel - Re: Regression, thermal: core: battery reading wrong after wake from S3 [Was: Bug Report according to thermal

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Thu, 30 May 2024 12:49:52 +0200
From: "fhortner@...oo.de" <fhortner@...oo.de>
To: Linux regressions mailing list <regressions@...ts.linux.dev>,
 "Rafael J. Wysocki" <rafael.j.wysocki@...el.com>
Cc: linux-pm@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: Regression, thermal: core: battery reading wrong after wake from
 S3 [Was: Bug Report according to thermal_core.c]

Thanks Thorsten for the side note.

I have compiled kernel 6.8.11 with reverted commit 
5a5efdaffda5d23717d9117cf36cda9eafcf2fae.

Battery Status works fine now with reverted commit after S3 Sleep and 
Wake cycles.

Best, Reinhard


Am 30.05.24 um 12:21 schrieb Linux regression tracking (Thorsten Leemhuis):
> [adding the culprits author, LKML, and the regression mailing list to
> the list of recipients; changing subject, too]
>
> On 29.05.24 21:52, fhortner@...oo.de wrote:
>> After bisection I have reported a bug according to thermal_core.c:
>> After "Resume thermal zones asynchronously" commit: Wrong Battery
>> Reading after Wake from S3 Sleep - Lenovo Thinkpad P1 Gen2
>>
>> https://bugzilla.kernel.org/show_bug.cgi?id=218881
>> Could you please have a look at it
>>
>> I have performed a bisection and the culprit is this commit: Resume
>> thermal zones asynchronously
>> git bisect bad 5a5efdaffda5d23717d9117cf36cda9eafcf2fae
>> # first bad commit: [5a5efdaffda5d23717d9117cf36cda9eafcf2fae] thermal:
>> core: Resume thermal zones asynchronously
>>
>> I have also verified it by compiling a kernel
> Side note: not critical at all, but would have been good if you had
> specified which kernel version you build.
>
>> without this commit.
> Thanks for the report. To be sure the issue doesn't fall through the
> cracks unnoticed, I'm adding it to regzbot, the Linux kernel regression
> tracking bot:
>
> #regzbot ^introduced 5a5efdaffda5d23717d9117cf36cda9eafcf2
> #regzbot dup: https://bugzilla.kernel.org/show_bug.cgi?id=218881
> #regzbot title
> #regzbot ignore-activity
>
> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
> --
> Everything you wanna know about Linux kernel regression tracking:
> https://linux-regtracking.leemhuis.info/about/#tldr
> That page also explains what to do if mails like this annoy you.