On Thu, 2016-11-10 at 10:10 +0000, Jean-Pierre van Riel wrote: > @SunBear > > I'm also having issues with these apparent errors: > > thermald[1309]: 13 CPUID levels; family:model:stepping 0x6:3c:3 > (6:60:3) > thermald[1309]: Polling mode is enabled: 4 > thermald[1309]: sysfs write failed enable
Possibly you don't have CONFIG_THERMAL_WRITABLE_TRIPS=y in your kernel. But this is not required, this is for the case when polling is disabled.
> thermald[1309]: sysfs read failed constraint_0_max_power_uw In some systems this is not provided, then we need to calculate power dynamically.
> thermald[1309]: sysfs write failed trip_point_0_temp > Thanks, Srinivas
> Not sure, might be related to > https://github.com/01org/thermal_daemon/issues/82 > > "no kernel driver to handle PCH sensor in Haswell" > > And that involved a kernel patch? > > ** Bug watch added: github.com/01org/thermal_daemon/issues #82 > https://github.com/01org/thermal_daemon/issues/82 >
On Thu, 2016-11-10 at 10:10 +0000, Jean-Pierre van Riel wrote: model:stepping 0x6:3c:3
> @SunBear
>
> I'm also having issues with these apparent errors:
>
> thermald[1309]: 13 CPUID levels; family:
> (6:60:3)
> thermald[1309]: Polling mode is enabled: 4
> thermald[1309]: sysfs write failed enable
Possibly you don't have CONFIG_ THERMAL_ WRITABLE_ TRIPS=y in your kernel.
But this is not required, this is for the case when polling is
disabled.
> thermald[1309]: sysfs read failed constraint_ 0_max_power_ uw
In some systems this is not provided, then we need to calculate power
dynamically.
> thermald[1309]: sysfs write failed trip_point_0_temp
>
Thanks,
Srinivas
> Not sure, might be related to /github. com/01org/ thermal_ daemon/ issues/ 82 com/01org/ thermal_ daemon/ issues #82 /github. com/01org/ thermal_ daemon/ issues/ 82
> https:/
>
> "no kernel driver to handle PCH sensor in Haswell"
>
> And that involved a kernel patch?
>
> ** Bug watch added: github.
> https:/
>