From: bugzilla-daemon@kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 216248] [Regression] amd-pstate stops working after [ACPI: CPPC: Check _OSC for flexible address space]
Date: Fri, 15 Jul 2022 09:21:42 +0000 [thread overview]
Message-ID: <bug-216248-137361-UYj3BJQKWV@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216248-137361@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216248
--- Comment #8 from Arek Ruśniak (arek.rusi@gmail.com) ---
# cpupower frequency-info
analyzing CPU 0:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: Cannot determine or is not supported.
hardware limits: 1.20 GHz - 3.20 GHz
available frequency steps: 3.20 GHz, 1.30 GHz, 1.20 GHz
available cpufreq governors: conservative ondemand userspace powersave
performance schedutil
current policy: frequency should be within 1.20 GHz and 3.20 GHz.
The governor "schedutil" may decide which speed to use
within this range.
current CPU frequency: 1.20 GHz (asserted by call to hardware)
boost state support:
Supported: yes
Active: yes
Boost States: 0
Total States: 3
Pstate-P0: 3200MHz
Pstate-P1: 1300MHz
Pstate-P2: 1200MHz
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2022-07-15 9:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 20:40 [Bug 216248] New: [Regression] amd-pstate stops working after [ACPI: CPPC: Check _OSC for flexible address space] bugzilla-daemon
2022-07-14 20:45 ` [Bug 216248] " bugzilla-daemon
2022-07-15 3:12 ` bugzilla-daemon
2022-07-15 3:20 ` bugzilla-daemon
2022-07-15 8:09 ` bugzilla-daemon
2022-07-15 8:11 ` bugzilla-daemon
2022-07-15 8:12 ` bugzilla-daemon
2022-07-15 8:56 ` bugzilla-daemon
2022-07-15 9:20 ` bugzilla-daemon
2022-07-15 9:21 ` bugzilla-daemon [this message]
2022-07-15 9:35 ` bugzilla-daemon
2022-07-15 9:37 ` bugzilla-daemon
2022-07-15 10:36 ` bugzilla-daemon
2022-07-15 10:43 ` bugzilla-daemon
2022-07-15 10:52 ` bugzilla-daemon
2022-07-15 11:00 ` bugzilla-daemon
2022-07-15 15:20 ` bugzilla-daemon
2022-07-15 15:20 ` bugzilla-daemon
2022-07-15 17:30 ` bugzilla-daemon
2022-07-15 17:32 ` bugzilla-daemon
2022-07-17 13:55 ` bugzilla-daemon
2022-07-17 13:57 ` bugzilla-daemon
2022-07-17 14:06 ` bugzilla-daemon
2022-07-17 17:53 ` bugzilla-daemon
2022-07-17 21:13 ` 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-216248-137361-UYj3BJQKWV@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.