Re: I haven't been able to set the chosen policy for CPU0

[Christian Flamm <alcc@gmx.de>]

> >>>I think I can now reproduce that misbehaviour. I happens when
> >>>both of my cores
> >>>are at 100%  - than min- *and* max-frequency fall down to
> >>>minimum (1000000Hz)

> >> Looks like the CPUs are being driver to lower freq due to temperature
> >> limits. CPUs being busy is increasing the temp and they go

> >to lower freq

> >> until they reach the lower temp. Looking at
> >> /proc/acpi/thermal_zone/*/*
> >> when this happens can confirm this.

> >First of all, thx for the reply.

> >Before, at, and after the freqency falls doen to minimum:

> >$ cat /proc/acpi/thermal_zone/THM0/state
> >state:                   ok

> >So its something else.

> BTW, what does other values in THM0/* look like. Temp, passive, active,
> etc..

Maybe you're right.

Temperature increases up to 83°C and then the cpu seems to get auto-throttled.

$ ls /proc/acpi/thermal_zone/THM0/
cooling_mode  polling_frequency  state  temperature  trip_points

$cat /proc/acpi/thermal_zone/THM0/cooling_mode
<setting not supported>