From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Evgeny Sagatov <evgeny.sagatov@gmail.com>
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: Thu, 23 Apr 2026 20:21:29 +0200 [thread overview]
Message-ID: <5996744.DvuYhMxLoT@rafael.j.wysocki> (raw)
In-Reply-To: <CAGAxtY1eVP5y6GTDoLM2xVDt2KF7fCKxDx0Mo9QO3afTA54GgQ@mail.gmail.com>
On Thursday, April 23, 2026 4:51:36 PM CEST Evgeny Sagatov wrote:
> I removed the previous patch and installed the new one in kernel 7.0.0.
> schedutil - complete freeze, no messages in the log
> performance - log message when pressing power button, doesn't reboot
> ondemand - log message when pressing power button, doesn't reboot
>
> Log: apr 23 17:40:04 srv kernel: acpi-button LNXPWRBN:00: ACPI button event
There clearly is some unexpected interaction between the schedutil governor
(or generally what happens in cpufreq when it is used) and the ACPI power
button handling. It looks like some memory gets corrupted when schedutil
runs and it is then tripped over by the power button handling code.
Kind of on a hunch, please see if the appended schedutil patch (either with
or without the previous patch applied) makes any difference.
---
kernel/sched/cpufreq_schedutil.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/kernel/sched/cpufreq_schedutil.c
+++ b/kernel/sched/cpufreq_schedutil.c
@@ -158,7 +158,7 @@ unsigned long get_capacity_ref_freq(stru
if (freq)
return freq;
- if (arch_scale_freq_invariant())
+ if (arch_scale_freq_invariant() || policy->cur >= policy->cpuinfo.max_freq)
return policy->cpuinfo.max_freq;
/*
next prev parent reply other threads:[~2026-04-23 18:21 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 [this message]
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
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=5996744.DvuYhMxLoT@rafael.j.wysocki \
--to=rafael@kernel.org \
--cc=evgeny.sagatov@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--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®