Re: Pressing the power button causes the device to freeze completely

[Evgeny Sagatov]

> There are two cpufreq governors to choose from.  Have you decided to compile out the other ones on purpose?

Powersave is compiled into the stock Debian kernel as a module, so it
does not appear in this list.

I changed governor to powersave and pressed the power button. The PC
shut down normally.

ср, 22 апр. 2026 г. в 17:04, Rafael J. Wysocki <rafael@xxxxxxxxxx>:
>
> On Wed, Apr 22, 2026 at 3:34 PM Evgeny Sagatov <evgeny.sagatov@xxxxxxxxx> wrote:
> >
> > # grep -r . /sys/devices/system/cpu/cpufreq/
> > /sys/devices/system/cpu/cpufreq/schedutil/rate_limit_us:240
> > /sys/devices/system/cpu/cpufreq/policy2/scaling_min_freq:2000000
> > /sys/devices/system/cpu/cpufreq/policy2/scaling_available_governors:performance
> > schedutil
>
> There are two cpufreq governors to choose from.  Have you decided to
> compile out the other ones on purpose?
>
> It might be useful to compile the powersave governor in and try to
> switch over to it (on all CPUs) before pressing the power button
> (without any patches applied).
>
> > /sys/devices/system/cpu/cpufreq/policy2/freqdomain_cpus:2
> > /sys/devices/system/cpu/cpufreq/policy2/scaling_governor:schedutil
> > /sys/devices/system/cpu/cpufreq/policy2/cpuinfo_max_freq:2834000
> > /sys/devices/system/cpu/cpufreq/policy2/scaling_available_frequencies:2834000
> > 2000000
>
> The frequency scaling on this CPU is quite limited (only 2 states to
> choose from).
>
> > /sys/devices/system/cpu/cpufreq/policy2/related_cpus:2
> > /sys/devices/system/cpu/cpufreq/policy2/scaling_cur_freq:2000088
>
> Interestingly, this number doesn't match the available choices (maybe
> due to a rounding error or similar).
>
> > /sys/devices/system/cpu/cpufreq/policy2/scaling_setspeed:<unsupported>
> > grep: /sys/devices/system/cpu/cpufreq/policy2/stats/reset: Access denied
> > /sys/devices/system/cpu/cpufreq/policy2/stats/trans_table:   From  :    To
> > /sys/devices/system/cpu/cpufreq/policy2/stats/trans_table:         :
> > 2834000   2000000
> > /sys/devices/system/cpu/cpufreq/policy2/stats/trans_table:  2834000:
> >       0       762
> > /sys/devices/system/cpu/cpufreq/policy2/stats/trans_table:  2000000:
> >     761         0
> > /sys/devices/system/cpu/cpufreq/policy2/stats/total_trans:1523
> > /sys/devices/system/cpu/cpufreq/policy2/stats/time_in_state:2834000 6606
> > /sys/devices/system/cpu/cpufreq/policy2/stats/time_in_state:2000000 248733
> > /sys/devices/system/cpu/cpufreq/policy2/affected_cpus:2
> > /sys/devices/system/cpu/cpufreq/policy2/scaling_max_freq:2834000
> > /sys/devices/system/cpu/cpufreq/policy2/cpuinfo_transition_latency:160000
> > /sys/devices/system/cpu/cpufreq/policy2/scaling_driver:acpi-cpufreq
> > /sys/devices/system/cpu/cpufreq/policy2/cpuinfo_min_freq:2000000
> > /sys/devices/system/cpu/cpufreq/policy2/bios_limit:2834000
>
> The fact that acpi-cpufreq is the scaling driver may be related to the
> power button issue in principle.
>
> I'm still going to send you another debug patch for the button driver though.