mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Evgeny Sagatov <evgeny.sagatov@gmail.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: regressions@lists.linux.dev, linux-acpi@vger.kernel.org,
	 Thorsten Leemhuis <regressions@leemhuis.info>,
	LKML <linux-kernel@vger.kernel.org>,
	 Wysocki Rafael J <rafael.j.wysocki@intel.com>
Subject: Re: Pressing the power button causes the device to freeze completely
Date: Sat, 25 Apr 2026 00:18:02 +0300	[thread overview]
Message-ID: <CAGAxtY13R3F6M4HFiwwsx8SEbcUsu5mQKJrayaCGFp14cEB2wg@mail.gmail.com> (raw)
In-Reply-To: <12895688.O9o76ZdvQC@rafael.j.wysocki>

dmesg | grep "Fast frequency"
Nothing was displayed.

The PC froze when I pressed the power button. Nothing in the log.

I applied this patch after deleting all the previous ones. Is this correct?

I received this message when applying a patch. Perhaps we have
different versions of the source code? I'm using 7.0.0.
patching file drivers/acpi/acpica/evevent.c
patching file drivers/cpufreq/acpi-cpufreq.c
Hunk #1 succeeded at 895 (offset -17 lines).
patching file drivers/cpufreq/cpufreq.c

пт, 24 апр. 2026 г. в 22:45, Rafael J. Wysocki <rafael@kernel.org>:
>
> On Friday, April 24, 2026 7:06:50 PM CEST Evgeny Sagatov wrote:
> > dmesg | grep "Fast frequency"
> > [    8.903099] cpufreq: CPU0: Fast frequency switching enabled
> > [    8.903181] cpufreq: CPU1: Fast frequency switching enabled
> > [    8.903247] cpufreq: CPU2: Fast frequency switching enabled
> > [    8.903316] cpufreq: CPU3: Fast frequency switching enabled
>
> If it is enabled, let's try to disable it and see what happens.
>
> > When I pressed the power button, the PC froze. Nothing in the log.
>
> Below is an updated version of the previous patch which additionally
> disables fast frequency switching in the ACPI cpufreq driver that is
> in use on your system.
>
> The "Fast frequency switching enabled" messages should not be there
> any more in the log with this patch applied (please verify) and
> please check if pressing the power button will still lock up the
> system.
>
> ---
>  drivers/acpi/acpica/evevent.c  |    5 +++++
>  drivers/cpufreq/acpi-cpufreq.c |    3 +--
>  drivers/cpufreq/cpufreq.c      |    1 +
>  3 files changed, 7 insertions(+), 2 deletions(-)
>
> --- a/drivers/acpi/acpica/evevent.c
> +++ b/drivers/acpi/acpica/evevent.c
> @@ -243,6 +243,11 @@ static u32 acpi_ev_fixed_event_dispatch(
>         (void)acpi_write_bit_register(acpi_gbl_fixed_event_info[event].
>                                       status_register_id, ACPI_CLEAR_STATUS);
>
> +       if (event == ACPI_EVENT_POWER_BUTTON) {
> +               pr_info("ACPI power button event\n");
> +               return (ACPI_INTERRUPT_HANDLED);
> +       }
> +
>         /*
>          * Make sure that a handler exists. If not, report an error
>          * and disable the event to prevent further interrupts.
> --- a/drivers/cpufreq/acpi-cpufreq.c
> +++ b/drivers/cpufreq/acpi-cpufreq.c
> @@ -912,8 +912,7 @@ static int acpi_cpufreq_cpu_init(struct
>          */
>         data->resume = 1;
>
> -       policy->fast_switch_possible = !acpi_pstate_strict &&
> -               !(policy_is_shared(policy) && policy->shared_type != CPUFREQ_SHARED_TYPE_ANY);
> +       policy->fast_switch_possible = false;
>
>         if (perf->states[0].core_frequency * 1000 != freq_table[0].frequency)
>                 pr_warn(FW_WARN "P-state 0 is not max freq\n");
> --- a/drivers/cpufreq/cpufreq.c
> +++ b/drivers/cpufreq/cpufreq.c
> @@ -473,6 +473,7 @@ void cpufreq_enable_fast_switch(struct c
>         if (cpufreq_fast_switch_count >= 0) {
>                 cpufreq_fast_switch_count++;
>                 policy->fast_switch_enabled = true;
> +               pr_info("CPU%u: Fast frequency switching enabled\n", policy->cpu);
>         } else {
>                 pr_warn("CPU%u: Fast frequency switching not enabled\n",
>                         policy->cpu);
>
>
>

  reply	other threads:[~2026-04-24 21:18 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <184091776095270@mail.yandex.ru>
2026-04-16  8:22 ` Thorsten Leemhuis
     [not found]   ` <186071776359023@mail.yandex.ru>
2026-04-16 17:35     ` Thorsten Leemhuis
     [not found]       ` <26521776666243@mail.yandex.ru>
2026-04-20  6:41         ` Sagatov, Evgeniy
2026-04-20  6:54           ` Thorsten Leemhuis
2026-04-20 19:34             ` Sagatov, Evgeniy
2026-04-20 22:20               ` Sagatov, Evgeniy
2026-04-21  5:01                 ` Thorsten Leemhuis
2026-04-21  9:28                   ` Sagatov, Evgeniy
2026-04-21 15:11 ` Wysocki, Rafael J
2026-04-21 20:41   ` Rafael J. Wysocki
     [not found]     ` <168591776860440@mail.yandex.ru>
2026-04-22 12:36       ` Evgeny Sagatov
2026-04-22 13:26         ` Rafael J. Wysocki
2026-04-22 13:34           ` Evgeny Sagatov
2026-04-22 14:04             ` Rafael J. Wysocki
2026-04-22 14:48               ` Evgeny Sagatov
2026-04-23 13:17                 ` Rafael J. Wysocki
2026-04-23 14:51                   ` Evgeny Sagatov
2026-04-23 18:21                     ` Rafael J. Wysocki
2026-04-23 20:07                       ` Evgeny Sagatov
2026-04-24 14:40                         ` Rafael J. Wysocki
2026-04-24 17:06                           ` Evgeny Sagatov
2026-04-24 19:45                             ` Rafael J. Wysocki
2026-04-24 21:18                               ` Evgeny Sagatov [this message]
2026-04-26 14:50                                 ` Rafael J. Wysocki
2026-04-26 14:54                                   ` Rafael J. Wysocki
2026-04-26 20:45                                     ` Evgeny Sagatov
2026-04-27 18:48                                       ` Rafael J. Wysocki
2026-04-27 20:12                                         ` Evgeny Sagatov
2026-04-27 20:31                                           ` Rafael J. Wysocki
2026-04-27 21:49                                             ` Evgeny Sagatov
2026-04-28 17:40                                               ` Rafael J. Wysocki
2026-04-28 19:11                                                 ` Evgeny Sagatov
2026-04-28 19:58                                                   ` Rafael J. Wysocki
2026-04-28 21:05                                                     ` Evgeny Sagatov
2026-04-29 18:24                                                       ` Pressing the power button causes the device to freeze completely (schedutil involved) Rafael J. Wysocki
2026-04-29 20:22                                                         ` Rafael J. Wysocki
2026-04-29 21:16                                                           ` Evgeny Sagatov
2026-04-30 10:40                                                             ` Rafael J. Wysocki
2026-04-30 10:53                                                               ` Rafael J. Wysocki
2026-04-30 11:41                                                                 ` Evgeny Sagatov
2026-04-30 11:57                                                                   ` Evgeny Sagatov
2026-04-30 14:10                                                                     ` Rafael J. Wysocki
2026-04-30 16:04                                                                       ` Evgeny Sagatov
2026-04-30 13:57                                                                   ` Rafael J. Wysocki
2026-04-30 14:42                                                                     ` Rafael J. Wysocki
2026-04-30 23:05                                                                       ` Evgeny Sagatov
2026-04-30 23:17                                                                       ` Evgeny Sagatov
2026-05-01 12:00                                                                         ` Rafael J. Wysocki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAGAxtY13R3F6M4HFiwwsx8SEbcUsu5mQKJrayaCGFp14cEB2wg@mail.gmail.com \
    --to=evgeny.sagatov@gmail.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=rafael@kernel.org \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®