| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| 0002-Don-t-keep-on-reading-a-sensor-if-the-temperature-is.patch | [PATCH] Don't keep on reading a sensor if the temperature is unreadable (LP: #1764320) Some broken thermal zone drivers may have broken temp interfaces that cannot be read. If these occur, don't keep on reading this and but instead log that it is unreadable and defaulting to zero just one and don't spam the log any further with messages. Don't disable the sensor as it has may have valuable interfaces that can be used to adjust passive cooling. |
Colin Ian King <colin.king@canonical.com> | no | 2018-04-17 | ||
| 0003-thermald-fix-uninitialised-member.patch | Bug#896132: thermald uninitialised member causes loss of temperature control Dear Maintainer, 0002-Don-t-keep-on-reading-a-sensor-if-the-temperature-is.patch, added in 1.7.0-5, introduces a new cthd_sensor data member temp_unreadable but fails to initialise it. This causes nondeterministic behaviour. If any bits of the uninitialised boolean are nonzero, it will be evaluate to true, and the sensor will be silently disabled, causing loss of temperature control. This bug is critical because loss of temperature control risks physical hardware damage. Attached patch initialises temp_unreadable to restore temperature control. Kind regards, Ben. |
Ben Caradoc-Davies <ben@transient.nz> | no | 2018-04-20 | ||
| 0004-Remove-processing-when-trip-was-not-activates.patch | [PATCH] Remove processing when trip was not activates When trip was not activated, don't poll cooling device status. This will save some CPU cycles. |
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com> | no | 2018-04-29 |