Bug 218881
| Summary: | After "Resume thermal zones asynchronously" commit: Wrong Battery Reading after Wake from S3 Sleep - Lenovo Thinkpad P1 Gen2 | ||
|---|---|---|---|
| Product: | Power Management | Reporter: | fhortner |
| Component: | Thermal | Assignee: | Rafael J. Wysocki (rjw) |
| Status: | RESOLVED PATCH_ALREADY_AVAILABLE | ||
| Severity: | normal | CC: | agurenko, axel.braun, bugzilla.i22av, lngtmg, regressions, rjw |
| Priority: | P3 | ||
| Hardware: | Intel | ||
| OS: | Linux | ||
| Kernel Version: | Subsystem: | ||
| Regression: | Yes | Bisected commit-id: | 5a5efdaffda5d23717d9117cf36cda9eafcf2fae |
| Attachments: |
kernel log with @kernel-vanilla/stable - 6.9.1-351
bisection log |
||
|
Description
fhortner
2024-05-24 10:43:20 UTC
This could be a problem in the ACPI code, a platform specific driver, or some other related code – which is why no developer might look into this. You might want to perform a bisection to find the cause (see https://docs.kernel.org/admin-guide/verify-bugs-and-bisect-regressions.html ), as the culprits author then has to look into the problem. Thanks Thorsten for your feedback. Thanks to your reply I am already working on bisection. I hope this will help identifying the issue. Created attachment 306369 [details]
bisection log
git bisect bad 5a5efdaffda5d23717d9117cf36cda9eafcf2fae
# first bad commit: [5a5efdaffda5d23717d9117cf36cda9eafcf2fae] thermal: core: Resume thermal zones asynchronously
I have verified this. with reverted commit 5a5efdaffda5d23717d9117cf36cda9eafcf2fae Battery Status is find after S3 Sleep and Wake cycles To change the actual component, does anyone know the component of Product "drivers"? I have compiled kernel 6.8.11 with reverted commit 5a5efdaffda5d23717d9117cf36cda9eafcf2fae. Battery Status works fine with reverted commit after S3 Sleep and Wake cycles. (In reply to fhortner from comment #4) > To change the actual component, does anyone know the component of Product > "drivers"? Most likely nobody will care; bringing it to the list and the culprits author should do the trick (for the bystanders: that was done here: https://lore.kernel.org/all/435867b5-029b-419f-bb7f-2d4902c62556@leemhuis.info/) Same issue here for my ThinkPad X1 Extreme (Gen 2). I hadn't seen this report yet and went through the bisection process and ended up at the same bad commit. @slip Thanks for your confirmation. Could you also bring this to the mailing list. see Reply instructions at the bottom here: https://lore.kernel.org/all/435867b5-029b-419f-bb7f-2d4902c62556@leemhuis.info/ @Thorsten Could we somehow synchronise this bug with the mailinglist? *** Bug 218915 has been marked as a duplicate of this bug. *** (In reply to fhortner from comment #8) > Could you also bring this to the mailing list. Won't hurt, but there is no pressing need either for now; but if nothing happens in a day or two it's likely a wise move. > @Thorsten > Could we somehow synchronise this bug with the mailinglist? That's not easy (that's a longer story short). But you (and slip) could allow me to use your emails addresses in a reply, then we could let this ticket rest. (In reply to The Linux kernel's regression tracker (Thorsten Leemhuis) from comment #10) > But you (and slip) And Axel, too. > could allow me to use your emails addresses in a reply, > then we could let this ticket rest. And yes, that all not ideal, I know; with a bit of luck this will become easier in a few months. (In reply to The Linux kernel's regression tracker (Thorsten Leemhuis) from comment #10) > But you (and slip) could allow me to use your emails addresses in a reply, I am already in CC > But you (and slip) could allow me to use your emails addresses in a reply,
> then we could let this ticket rest.
This works for me! Happy to keep it centralized.
Patch submitted: https://lore.kernel.org/linux-pm/3317718.44csPzL39Z@kreacher/ Patch introduced with Kernel 6.10.rc5 Patch added and available since Kernel 6.9.7 stable Thanks to Rafael and Greg Could the fix be ported to 6.8.0 ? (to become available for Ubuntu 22.04.4) No, as 6.8.y is EOL for months now (reminder, this is a bug tracker for the upstream kernel; if any downstreams are still using 6.8 you have to ask them) |