New: scaling_max_freq cannot be set to values larger than bios_limit
https://bugzilla.kernel.org/show_bug.cgi?id=60839
Bug ID: 60839
Summary: scaling_max_freq cannot be set to values larger than
bios_limit
Product: Power Management
Version: 2.5
Kernel Version: 3.10.10
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: cpufreq
Assignee: [email protected]
Reporter: [email protected]
Regression: NoBackground:
On my Dell Latitude E6410, the following happens if the power supply is plugged in or plugged out: The value of bios_limit drops for all CPUs to cpuinfo_min_freq. Within seconds, it is then gradually increased until bios_limit is equal to cpuinfo_max_freq. I assume, that this serves the purpose of detecting the type of attached power supply. The BIOS temporarely limits the CPU frequency in order to keep the power consumption low until it is determined that the power supply is the correct one.
Problem description:
Assume that nobody is writing to scaling_max_freq and that scaling_max_freq=cpuinfo_max_freq initially. Upon switching the power supply, you observe that the value of scaling_max_freq decreases and then gradually increases along with bios_limit. From this I conclude that
(a) internally, the value for scaling_max_freq can assume values larger than bios_limit. However, when reading scaling_max_freq through sysfs the value is clipped by bios_limit
(b) there is no good reason, why the internal value of scaling_max_freq shouldn't be set to a value larger than bios_limit.
However, any write to scaling_max_freq through sysfs will also be clipped by bios_limit. In result, if the value of cpuinfo_max_freq is written to scaling_max_freq while bios_limit is low, then the internal value of scaling_max_freq will be set to whatever the value of bios_limit is.
In my case, this was causing the following problems:
laptop-mode-tools would write to scaling_max_freq shortly after the power supply was plugged in / unplugged. As the bios_limit would be low at that point, the internal value of scaling_max_freq would be set to a low value. Hence, cpufreq would never raise the frequencies of my CPUs again even after bios_limit increased. I solved it my disabling the cpufreq related parts of laptop-mode-tools.
Also note, that it isn't currently possible to determine the true value of scaling_max_freq as the value returned through sysfs is clipped by bios_limit.
Signature · 2 lines
You are receiving this mail because: You are the assignee for the bug.
[Bug 60839] scaling_max_freq cannot be set to values larger than bios_limit
https://bugzilla.kernel.org/show_bug.cgi?id=60839
Lan Tianyu <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
CC| |[email protected]--- Comment #1 from Lan Tianyu <[email protected]> --- (In reply to Sven Köhler from comment #0)
Quoted 27 lines
Background:
On my Dell Latitude E6410, the following happens if the power supply is plugged in or plugged out: The value of
bios_limitdrops for all CPUs tocpuinfo_min_freq. Within seconds, it is then gradually increased untilbios_limitis equal tocpuinfo_max_freq. I assume, that this serves the purpose of detecting the type of attached power supply. The BIOS temporarely limits the CPU frequency in order to keep the power consumption low until it is determined that the power supply is the correct one.Problem description:
Assume that nobody is writing to
scaling_max_freqand that scaling_max_freq=cpuinfo_max_freq initially. Upon switching the power supply, you observe that the value ofscaling_max_freqdecreases and then gradually increases along withbios_limit. From this I conclude that
(a) internally, the value forscaling_max_freqcan assume values larger thanbios_limit. However, when readingscaling_max_freqthrough sysfs the value is clipped bybios_limit
(b) there is no good reason, why the internal value ofscaling_max_freqshouldn't be set to a value larger thanbios_limit.However, any write to
scaling_max_freqthrough sysfs will also be clipped bybios_limit. In result, if the value ofcpuinfo_max_freqis written toscaling_max_freqwhilebios_limitis low, then the internal value ofscaling_max_freqwill be set to whatever the value ofbios_limitis.
Quoted 7 lines
In my case, this was causing the following problems:
laptop-mode-tools would write toscaling_max_freqshortly after the power supply was plugged in / unplugged. As thebios_limitwould be low at that point, the internal value ofscaling_max_freqwould be set to a low value. Hence, cpufreq would never raise the frequencies of my CPUs again even afterbios_limitincreased. I solved it my disabling the cpufreq related parts of laptop-mode-tools.
Hi:
This sounds like a user space issue. Bios limit will rise after
plugging/unplugging AC and laptop-mode-tools also should update scaling_max_freq. Cpufreq core schedules freq scope according user space configuration. If user space tool doesn't extend the scope according bios limit after plugging/unplugging AC, the scope will keep low cpufreq.
Quoted 4 lines
Also note, that it isn't currently possible to determine the true value of
scaling_max_freqas the value returned through sysfs is clipped bybios_limit.
Signature · 2 lines
You are receiving this mail because: You are the assignee for the bug.
[Bug 60839] scaling_max_freq cannot be set to values larger than bios_limit
In reply to [email protected]https://bugzilla.kernel.org/show_bug.cgi?id=60839
Lan Tianyu <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |INVALIDSignature · 2 lines
You are receiving this mail because: You are the assignee for the bug.
[Bug 60839] scaling_max_freq cannot be set to values larger than bios_limit
In reply to [email protected]https://bugzilla.kernel.org/show_bug.cgi?id=60839
Sven Köhler <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|INVALID |------ Comment #2 from Sven Köhler <[email protected]> --- (In reply to Lan Tianyu from comment #1)
Quoted 6 lines
Hi:
This sounds like a user space issue. Bios limit will rise after
plugging/unplugging AC and laptop-mode-tools also should updatescaling_max_freq. Cpufreq core schedules freq scope according user space configuration. If user space tool doesn't extend the scope according bios limit after plugging/unplugging AC, the scope will keep low cpufreq.
First of all, does the kernel provide any hook to run a script every time bios_limit changes or do you expect userspace to do polling?
Second, you can't be serious that the sysfs interface should remain as inconsistent as it is now. Clearly, the internal state of scaling_max_freq and bios_limit can be one, where scaling_max_freq is larger than bios_limit. This is very clear since I observed that (unless userspace tries to change scaling_max_freq) the value of scaling_max_freq will increase as bios_limit increases. At time when bios_limit is low, userspace cannot even find out about the true state of scaling_max_freq (which is larger than bios_limit) as the value obtainable via sysfs is always clipped. Obviously, knowing that such a state exists, it is dubious why it can't be configured.
Thirdly, I'd really like know the rational behind the decision to that
a) userspace should never be able to observe, that scaling_max_freq is actually kernel internally larger than bios_limit
b) userspace should never be able to set scaling_max_freq to a value larger than bios_limit
IMHO, both (a) and (b) are wrong, in the sense that there is no good reason in favour of (a) and (b) and many reasons against (a) and (b). A very strong reason against (a) is the very simple fact that userspace cannot tell whether the current maximum CPU frequency is limited by the BIOS or the value of scaling_max_freq.
Signature · 2 lines
You are receiving this mail because: You are the assignee for the bug.
[Bug 60839] scaling_max_freq cannot be set to values larger than bios_limit
In reply to [email protected]https://bugzilla.kernel.org/show_bug.cgi?id=60839
Lan Tianyu <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |ASSIGNED
--- Comment #3 from Lan Tianyu <[email protected]> --- (In reply to Sven Köhler from comment #2)
Quoted 10 lines
(In reply to Lan Tianyu from comment #1)
Quoted 6 lines
Hi:
This sounds like a user space issue. Bios limit will rise after
plugging/unplugging AC and laptop-mode-tools also should updatescaling_max_freq. Cpufreq core schedules freq scope according user space configuration. If user space tool doesn't extend the scope according bios limit after plugging/unplugging AC, the scope will keep low cpufreq.First of all, does the kernel provide any hook to run a script every time
bios_limitchanges or do you expect userspace to do polling?
When bios limit is changed, ACPI processor driver will send an ACPI event to user space.
Quoted 3 lines
Second, you can't be serious that the sysfs interface should remain as inconsistent as it is now.
The scaling_max/min_freq shows current policy limit. Kernel side also will change the limit besides user space configuration and so it's inconsistent with the data set to the attribute.
Quoted 2 lines
Clearly, the internal state of
scaling_max_freq
andbios_limitcan be one,
No, actually there are some other factors that may change policy limit(E,G, processor throttling controlled by thermal core).
Quoted 8 lines
where
scaling_max_freqis larger thanbios_limit.
This is very clear since I observed that (unless userspace tries to changescaling_max_freq) the value ofscaling_max_freqwill increase asbios_limitincreases. At time whenbios_limitis low, userspace cannot even find out about the true state ofscaling_max_freq(which is larger thanbios_limit) as the value obtainable via sysfs is always clipped. Obviously, knowing that such a state exists, it is dubious why it can't be configured.
Kernel will store the userspace configuration but not show. I think we can introduce some new attributs to show user space configurations if necessory.
Quoted 3 lines
Thirdly, I'd really like know the rational behind the decision to that
a) userspace should never be able to observe, thatscaling_max_freqis actually kernel internally larger thanbios_limit
I think you said the user space configuration rather than current policy(scaling_min/max_freq shows). The current policy should take the bios_limit into account.
Quoted 2 lines
b) userspace should never be able to set
scaling_max_freqto a value larger thanbios_limit
Actually, you can set the value larger than bios_limit and it will works when bios_limit raises.
Quoted 6 lines
IMHO, both (a) and (b) are wrong, in the sense that there is no good reason in favour of (a) and (b) and many reasons against (a) and (b). A very strong reason against (a) is the very simple fact that userspace cannot tell whether the current maximum CPU frequency is limited by the BIOS or the value of
scaling_max_freq.
Actually, the cpu freq may be limited by other factors besides bios limit. So new attributes may be helpful to identify whether kernel side has changed the cpufreq scope.
Signature · 2 lines
You are receiving this mail because: You are the assignee for the bug.
[Bug 60839] scaling_max_freq cannot be set to values larger than bios_limit
In reply to [email protected]https://bugzilla.kernel.org/show_bug.cgi?id=60839
--- Comment #4 from Sven Köhler <[email protected]> --- (In reply to Lan Tianyu from comment #3)
Quoted 5 lines
Quoted 2 lines
b) userspace should never be able to set
scaling_max_freqto a value larger thanbios_limitActually, you can set the value larger than
bios_limitand it will works whenbios_limitraises.
That is exactly what didn't work! A write to the scaling_max_freq via sysfs was clipped by bios_limit, as far as I can tell. It never want up again, after a write to scaling_max_freq occured. I reproduced this having a small while loop in the bash shell, that wrote the maximum CPU frequency to scaling_max_freq while bios_limit was low.
I will try to reproduce the issue again and post the bash loop code here.
Signature · 2 lines
You are receiving this mail because: You are the assignee for the bug.
[Bug 60839] scaling_max_freq cannot be set to values larger than bios_limit
In reply to [email protected]https://bugzilla.kernel.org/show_bug.cgi?id=60839
--- Comment #5 from Lan Tianyu <[email protected]> --- Ok. I was confused and please try the following patch.
drivers/cpufreq/cpufreq.c +1 -1
@@ -449,7 +449,7 @@ static ssize_t store_##file_name \return -EINVAL ; \ \ ret =__cpufreq_set_policy (policy, &new_policy); \ - policy->user_policy.object = policy->object; \ + policy->user_policy.object = new_policy.object; \ \return ret ? ret : count; \
}
Signature · 2 lines
You are receiving this mail because: You are the assignee for the bug.
[Bug 60839] scaling_max_freq cannot be set to values larger than bios_limit
In reply to [email protected]https://bugzilla.kernel.org/show_bug.cgi?id=60839
--- Comment #6 from Sven Köhler <[email protected]> --- Nope, the patch didn't help. Here's the bash-code I used to test:
cmax=$(cat cpuinfo_max_freq)
echo $cmax >scaling_max_freq
bmax=$cmax
while [ $bmax -ge $cmax ]; do
bmax=$(cat bios_limit)
smax=$(cat scaling_max_freq)
echo $cmax >scaling_max_freq
echo $bmax $smax
done
while true; do
echo $(cat bios_limit) $(cat scaling_max_freq)
sleep 0.5
done
The output is like this:
2534000 2534000
2534000 2534000
2534000 2534000
2534000 2534000
2534000 1199000
1199000 1199000
1199000 1199000
1199000 1199000
1199000 1199000
1199000 1199000
1199000 1199000
1199000 1199000
1199000 1199000
1199000 1199000
1199000 1199000
1199000 1199000
1199000 1199000
1199000 1199000
1333000 1199000
1333000 1199000
1333000 1199000
1333000 1199000
1466000 1199000
1466000 1199000
As you can see, scaling_max_freq remains low. When the script is not running, scaling_max_freq increases along with bios_limit.
Signature · 2 lines
You are receiving this mail because: You are the assignee for the bug.
[Bug 60839] scaling_max_freq cannot be set to values larger than bios_limit
In reply to [email protected]https://bugzilla.kernel.org/show_bug.cgi?id=60839
--- Comment #7 from Lan Tianyu <[email protected]> --- Created attachment 108201
--> https://bugzilla.kernel.org/attachment.cgi?id=108201&action=edit
cpufreq_sys.patch
Please apply this patch with previous one. This patch will add two new attributes user_min/max_freq which show user space configuration. Change your scripts and show their values.
Signature · 2 lines
You are receiving this mail because: You are the assignee for the bug.
[Bug 60839] scaling_max_freq cannot be set to values larger than bios_limit
In reply to [email protected]https://bugzilla.kernel.org/show_bug.cgi?id=60839
Lan Tianyu <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |NEEDINFO
--- Comment #8 from Lan Tianyu <[email protected]> ---
Please also provide dmesg after testing with cpufreq debug opening. Run "echo "file cpufreq.c +p" > /sys/kernel/debug/dynamic_debug/control to open debug.
Signature · 2 lines
You are receiving this mail because: You are the assignee for the bug.
[Bug 60839] scaling_max_freq cannot be set to values larger than bios_limit
In reply to [email protected]https://bugzilla.kernel.org/show_bug.cgi?id=60839
--- Comment #9 from Lan Tianyu <[email protected]> --- ping ...
Signature · 2 lines
You are receiving this mail because: You are the assignee for the bug.
[Bug 60839] scaling_max_freq cannot be set to values larger than bios_limit
In reply to [email protected]https://bugzilla.kernel.org/show_bug.cgi?id=60839
Zhang Rui <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |CLOSED
CC| |[email protected]
Resolution|--- |INSUFFICIENT_DATA--- Comment #10 from Zhang Rui <[email protected]> ---
Bug closed as there is no response for more than a month.
please feel free to reopen it when you can provide the information request in comment #7
Signature · 2 lines
You are receiving this mail because: You are the assignee for the bug.