Public bug reported:
We should be including this latest upstream fix:
It was observed that in the case of cooling device with min_state > max_state,
thermald doesn't set the cooling device to the intended target state per the
configuration in XML. This is because of sorting the zone_trip_limits list in
ascending order based on target value is not suitable for the case of cooling
device with min_state > max_state. Thus this issue is fixed by:
1. sorting the zone_trip_limits list in descending order based on target value
for the case of cooling device with min_state > max_state.
2. sorting the zone_trip_limits list in ascending order based on target value
for the case of cooling device with max_state > min_state.
Example cooling device configuration which caused this issue:
<CoolingDevice>
<Type>gpu_cooling</Type>
<Path>/sys/class/mali/pm/max_freq_level</Path>
<MinState>4</MinState>
<MaxState>1</MaxState>
</CoolingDevice>.
Fix commit fd0671beba14586eb3e0b0fa2247a00100e6d418
** Affects: thermald (Ubuntu)
Importance: Medium
Assignee: Colin Ian King (colin-king)
Status: In Progress
** Changed in: thermald (Ubuntu)
Importance: Undecided => Medium
** Changed in: thermald (Ubuntu)
Status: New => In Progress
** Changed in: thermald (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1627400
Title:
thermald: fix incorrect target state settting by thermald
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1627400/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
