Bug 217615

Summary: Worse Battery life, with 11th gen i3 in kernels after v 5.18(may be even earlier)
Product: Platform Specific/Hardware Reporter: prosparety
Component: x86-64Assignee: platform_x86_64 (platform_x86_64)
Status: RESOLVED DUPLICATE    
Severity: normal CC: regressions
Priority: P3    
Hardware: Intel   
OS: Linux   
Kernel Version: Subsystem:
Regression: No Bisected commit-id:

Description prosparety 2023-06-30 02:11:14 UTC 
I have posted same thing on debian user forums, and linking that so as to reduce duplication
[url]https://forums.debian.net/viewtopic.php?t=154875[/url]

I will summarise a little, there is an increase in power usage going from kernel 5.10.x to something newer (have tried many of them between 5.18.x to 6.3.x), and since these tests were done on kernels from many sources, it seems an upstream thing, On newer kernels, if we set /sys/devices/system/cpu/intel_pstate/status to active (default by kernel), then cpu freq is almost stuck to 2GHz, if we set it to passive, it goes to 0.4GHz and increases when needed, in either cases the power usage is not decreased, and is higher that that achieved in older kernel, where pstate works thee best and scaling happens as it is expected to be, sometimes evenwithout tlp installed/enabled (this is a newer observation after my original post after some tweaking and testing), i have also tested all other cpu scaling driver also with newer kernel, and acpi_cpufreq gave better scaling whereas intel_cpufreq (intel_pstate in passive) got least power, i have almost no clue on where to begin fixing this and any help is appreciated (if output of some command is required, kindly check the refered debian user forum post)

Thank you in advance, and please forgive my spelling and grammatical mistakes, and if this is a duplicate issue(which may or may not have been resolved), i only search for a few words, intel pstate, cpu scaling, power draw, and did  not read many. i also apologize if this is not an upstream thing, and will post somewhere
Comment 1 The Linux kernel's regression tracker (Thorsten Leemhuis) 2023-06-30 12:34:32 UTC 
Increased power usage is considered a regression that must be fixed. But to claim that, you need to bisect this with an upstream kernel, one configuration, and one distro; and you also need to check if the problem is still present in the latest upstream kernel https://docs.kernel.org/admin-guide/reporting-regressions.html

Maybe some developer will look into this report without this. But I doubt it for reasons outlined here:
https://linux-regtracking.leemhuis.info/post/frequent-reasons-why-linux-kernel-bug-reports-are-ignored/

I know these are likely answers that you don't like to hear, but I think it'S better to tell you this then to get no reply at all.
Comment 2 The Linux kernel's regression tracker (Thorsten Leemhuis) 2023-06-30 12:44:09 UTC 

*** This bug has been marked as a duplicate of bug 217616 ***