Re: Pressing the power button causes the device to freeze completely (schedutil involved)

[Rafael J. Wysocki]

On Thu, Apr 30, 2026 at 12:40 PM Rafael J. Wysocki <rafael@xxxxxxxxxx> wrote:
>
> On Wed, Apr 29, 2026 at 11:17 PM Evgeny Sagatov
> <evgeny.sagatov@xxxxxxxxx> wrote:
> >
> > The PC froze when I pressed the power button.
>
> Well, we need to dig more I guess.
>
> > grep -r . /sys/devices/system/cpu/cpufreq/
> > /sys/devices/system/cpu/cpufreq/schedutil/rate_limit_us:240
> > /sys/devices/system/cpu/cpufreq/policy0/scaling_min_freq:2000000
> > /sys/devices/system/cpu/cpufreq/policy0/scaling_available_governors:performance
> > schedutil
> > /sys/devices/system/cpu/cpufreq/policy0/freqdomain_cpus:0 1 2 3
> > /sys/devices/system/cpu/cpufreq/policy0/scaling_governor:schedutil
> > /sys/devices/system/cpu/cpufreq/policy0/cpuinfo_max_freq:2834000
> > /sys/devices/system/cpu/cpufreq/policy0/scaling_available_frequencies:2834000
> > 2000000
> > /sys/devices/system/cpu/cpufreq/policy0/related_cpus:0 1 2 3
> > /sys/devices/system/cpu/cpufreq/policy0/scaling_cur_freq:1999759
>
> This kind of calls for some investigation.  It should not be less than
> scaling_min_freq, even though this looks like a rounding error.
>
> > /sys/devices/system/cpu/cpufreq/policy0/scaling_setspeed:<unsupported>
> > grep: /sys/devices/system/cpu/cpufreq/policy0/stats/reset: Отказано в доступе
> > /sys/devices/system/cpu/cpufreq/policy0/stats/trans_table:   From  :    To
> > /sys/devices/system/cpu/cpufreq/policy0/stats/trans_table:         :
> > 2834000   2000000
> > /sys/devices/system/cpu/cpufreq/policy0/stats/trans_table:  2834000:
> >       0       844
> > /sys/devices/system/cpu/cpufreq/policy0/stats/trans_table:  2000000:
> >     843         0
> > /sys/devices/system/cpu/cpufreq/policy0/stats/total_trans:1687
> > /sys/devices/system/cpu/cpufreq/policy0/stats/time_in_state:2834000 1164
> > /sys/devices/system/cpu/cpufreq/policy0/stats/time_in_state:2000000 14130
> > /sys/devices/system/cpu/cpufreq/policy0/affected_cpus:0 1 2 3
> > /sys/devices/system/cpu/cpufreq/policy0/scaling_max_freq:2834000
> > /sys/devices/system/cpu/cpufreq/policy0/cpuinfo_transition_latency:160000
> > /sys/devices/system/cpu/cpufreq/policy0/scaling_driver:acpi-cpufreq
> > /sys/devices/system/cpu/cpufreq/policy0/cpuinfo_min_freq:2000000
> > /sys/devices/system/cpu/cpufreq/policy0/cpuinfo_avg_freq:1999759
> > /sys/devices/system/cpu/cpufreq/policy0/bios_limit:2834000
>
> So with the same patch applied (because I think that the one-policy
> configuration is suitable for this platform), please capture the
> output of
>
> grep -r . /sys/devices/system/cpu/cpufreq/

Actually, the step above isn't necessary.

> switch over to the ondemand governor,

It is better to reset the cpufreq statistics after switching over to
ondemand by writing 1 to

/sys/devices/system/cpu/cpufreq/policy0/stats/reset

as root.  Then, wait for some time and capture the output of

grep -r . /sys/devices/system/cpu/cpufreq/

just once.

> wait for some time, capture the
> output of the above command again and send both.
>
> Also, please send the output of
>
> grep . /sys/firmware/acpi/interrupts/sci*
>
> acquired after doing all of the above.
>
> You may as well check again if the power button works after switching
> to ondemand.