thermald is spamming the log with messages there are essentially debug messages. These have been fixed upstream and are in the Wily version of thermald 1.4.3-5 and are the only changes in patches between that and the current vivid and trusty versions. Therefore a backport of the wily version seems like a sane way forward.
[Test Case]
Without the patches, once can observe debug messages such as
Sep 10 14:13:48 xxxx thermald[981]: Set : 71000, 26800, 10, 0, 0
Sep 10 14:13:52 xxxx thermald[981]: set cdev state index 10 state 0
Wit the fix these messages are only observable when the loglevel is set to debug
[Regression Potential]
Since this is a change in a log message type there is minimal change. This code is already fixed upstream and working in Wily with no regressions observed.
These warnings were fixed and landed upstream with commits:
https:/ /github. com/01org/ thermal_ daemon/ commit/ 6529d07e4dfdac4 8b34aabbbc5ace8 6570da6bc6 /github. com/01org/ thermal_ daemon/ commit/ 830c56c0143d24a a65de820c4ba9ee a249e66616
https:/
[SRU Justification] (Vivid, Trusty)
thermald is spamming the log with messages there are essentially debug messages. These have been fixed upstream and are in the Wily version of thermald 1.4.3-5 and are the only changes in patches between that and the current vivid and trusty versions. Therefore a backport of the wily version seems like a sane way forward.
[Test Case]
Without the patches, once can observe debug messages such as
Sep 10 14:13:48 xxxx thermald[981]: Set : 71000, 26800, 10, 0, 0
Sep 10 14:13:52 xxxx thermald[981]: set cdev state index 10 state 0
Wit the fix these messages are only observable when the loglevel is set to debug
[Regression Potential]
Since this is a change in a log message type there is minimal change. This code is already fixed upstream and working in Wily with no regressions observed.