From: bugzilla-daemon@kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 217810] New: Lenovo Ideapad S145 CPU frequency stuck after waking from sleep
Date: Sun, 20 Aug 2023 20:24:43 +0000 [thread overview]
Message-ID: <bug-217810-137361@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=217810
Bug ID: 217810
Summary: Lenovo Ideapad S145 CPU frequency stuck after waking
from sleep
Product: Power Management
Version: 2.5
Hardware: All
OS: Linux
Status: NEW
Severity: high
Priority: P3
Component: cpufreq
Assignee: linux-pm@vger.kernel.org
Reporter: mysignup27@proton.me
Regression: No
Lenovo Ideapad S145-14IGM
CPU: Intel Celeron N4000
Fedora 38 KDE
The problem is that after waking from sleep, the CPU frequency gets stuck on
the minimum frequency (1.1GHz for this model).
I reproduced this behavior on an old BIOS and the latest BIOS (AWCN30WW).
I found this solution to work:
sudo cpupower frequency-set -g schedutil && sudo cpupower frequency-set -g
performance
This needs to be run 4 times.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2023-08-20 20:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-217810-137361@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-pm@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).