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 03:12:51 +0000 [thread overview]
Message-ID: <bug-216248-137361-VLUBTpNKys@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 #1 from Mario Limonciello (AMD) (mario.limonciello@amd.com) ---
I believe your CPU should support the MSR approach. It should have been fixed
by "ACPI: CPPC: Don't require _OSC if X86_FEATURE_CPPC is supported". You can
see in your lscpu output the "cppc" flag is present.
That other patch won't matter. That patch was specifically to fix "ACPI: bus:
Set CPPC _OSC bits for all and when CPPC_LIB is supported".
A few asks:
1) Does acpi-cpufreq work? Or that's broken too from this commit?
2) Can you please share your full dmesg and an acpidump?
3) If you turn on dynamic debugging for drivers/acpi/cppc_acpi.c do you see
"Flexible address space capability not supported"? I would expect yes from
that bisect.
--
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 3:12 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 [this message]
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
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-VLUBTpNKys@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.