From: bugzilla-daemon@bugzilla.kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 213115] New: Unable to set the lowest frequency of AMD CPUs via cpupower - while kernel 5.12.4 (or 5.3.18) is booted with "nosmt"
Date: Mon, 17 May 2021 20:48:32 +0000 [thread overview]
Message-ID: <bug-213115-137361@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=213115
Bug ID: 213115
Summary: Unable to set the lowest frequency of AMD CPUs via
cpupower - while kernel 5.12.4 (or 5.3.18) is booted
with "nosmt"
Product: Power Management
Version: 2.5
Kernel Version: 5.12.4
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: low
Priority: P1
Component: cpufreq
Assignee: linux-pm@vger.kernel.org
Reporter: yan.huang@suse.com
Regression: No
(Opening this bug as a junior team member of the SUSE Customer Support)
A SUSE customer wasn't able to set the lowest possible CPU frequency value via
cpupower on SUSE Linux Enterprise Desktop 15 SP2 (with the kernel 5.3.18) on
machines with AMD A12-9720P and AMD Ryzen 5 3550H - while they were booted with
"nosmt".
The customer said that this was working on the previous SUSE Linux Enterprise
Desktop 15 SP1 (with the kernel 4.12.14).
Just for this purpose, I purchased a laptop Lenovo IdeaPad 3-15ADA05 with AMD
Ryzen 3 3250U and was able to replicate the issue - with the kernel 5.3.18 (the
default one for SUSE Linux Enterprise Desktop 15 SP2) and the newest stable
kernel 5.12.4.
AMD Ryzen 3 3250U
- https://www.amd.com/en/products/apu/amd-ryzen-3-3250u
- 1st gen Zen
- 2 cores, 4 threads
- base frequency: 2.60 GHz
- boost frequency: 3.50 GHz
- cpupower frequency-info
-- hardware limits: 1.40 GHz - 2.60 GHz
-- available frequency steps: 2.60 GHz, 1.70 GHz, 1.40 GHz
Each time, I ran this command and expected the CPU core/thread frequencies to
be =< 1400 MHz:
modprobe cpufreq_userspace && cpupower frequency-set -g userspace && cpupower
frequency-set -f 1.40GHz && echo 0 > /sys/devices/system/cpu/cpufreq/boost
Default kernel 5.3.18
I. without "nosmt" (ok)
1) initially:
> localhost:~ # grep MHz /proc/cpuinfo
> cpu MHz : 1308.436
> cpu MHz : 1218.734
> cpu MHz : 1301.057
> cpu MHz : 1377.824
2) after running the command:
> localhost:~ # grep MHz /proc/cpuinfo
> cpu MHz : 1394.225
> cpu MHz : 1391.125
> cpu MHz : 1352.398
> cpu MHz : 1356.574
II. with "nosmt" (fail)
1) initially:
> localhost:~ # grep MHz /proc/cpuinfo
> cpu MHz : 1434.860
> cpu MHz : 1557.750
2) after running the command:
> localhost:~ # grep MHz /proc/cpuinfo
> cpu MHz : 2068.443
> cpu MHz : 1921.816
Kernel 4.12.14 - obtained from
https://download.opensuse.org/repositories/Kernel:/SLE15-SP1/standard/x86_64/
(no longer available)
I. without "nosmt" (ok)
1) initially:
> localhost:~ # grep MHz /proc/cpuinfo
> cpu MHz : 1700.000
> cpu MHz : 1400.000
> cpu MHz : 1400.000
> cpu MHz : 1400.000
2) after running the command:
> localhost:~ # grep MHz /proc/cpuinfo
> cpu MHz : 1400.000
> cpu MHz : 1400.000
> cpu MHz : 1400.000
> cpu MHz : 1400.000
II. with "nosmt" (ok)
1) initially:
> localhost:~ # grep MHz /proc/cpuinfo
> cpu MHz : 1400.000
> cpu MHz : 1400.000
2) after running the command:
> localhost:~ # grep MHz /proc/cpuinfo
> cpu MHz : 1400.000
> cpu MHz : 1400.000
Kernel 5.12.4 - obtained from
https://download.opensuse.org/repositories/Kernel:/stable/standard/x86_64/
I. without "nosmt" (ok)
1) initially:
> localhost:~ # grep MHz /proc/cpuinfo
> cpu MHz : 1400.000
> cpu MHz : 1400.000
> cpu MHz : 2263.054
> cpu MHz : 1269.757
2) after running the command:
> localhost:~ # grep MHz /proc/cpuinfo
> cpu MHz : 1400.000
> cpu MHz : 1340.634
> cpu MHz : 1400.000
> cpu MHz : 1400.000
II. with "nosmt" (fail)
1) initially:
> localhost:~ # grep MHz /proc/cpuinfo
> cpu MHz : 1494.915
> cpu MHz : 2600.000
2) after running the command:
> localhost:~ # grep MHz /proc/cpuinfo
> cpu MHz : 1731.255
> cpu MHz : 1400.000
I also tested various kernel versions from
http://download.opensuse.org/repositories/home:/tiwai:/kernel:/ - it seems that
the issue started in 5.1.x or earlier (I wasn't able to boot every kernel
version).
I opened a SUSE Bugzilla bug bsc#1175231, but it was decided to not pursue a
fix for this corner-case issue at SUSE's level (the solution is to just avoid
"nosmt").
The issue should be replicable even on openSUSE Leap 15.2 with the above
mentioned kernels.
It is possible that the issue is limited to the 1st generation of AMD Ryzen
CPUs (and AMD's pre-Ryzen CPUs).
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2021-05-17 20:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 20:48 bugzilla-daemon [this message]
2021-05-17 20:52 ` [Bug 213115] Unable to set the lowest frequency of AMD CPUs via cpupower - while kernel 5.12.4 (or 5.3.18) is booted with "nosmt" bugzilla-daemon
2021-05-17 20:59 ` bugzilla-daemon
2021-05-17 21:01 ` bugzilla-daemon
2023-11-23 8:30 ` bugzilla-daemon
2023-11-24 6:47 ` bugzilla-daemon
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-213115-137361@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.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).