All of
 help / color / mirror / Atom feed
From: Oleksandr Natalenko <>
To: Mario Limonciello <>,
Cc: Perry Yuan <>,
	"Rafael J. Wysocki" <>,
	Sasha Levin <>,, "H. Peter Anvin" <>,
	Greg Kroah-Hartman <>
Subject: [REGRESSION] amd-pstate doesn't work since v5.18.11
Date: Tue, 12 Jul 2022 19:40:29 +0200	[thread overview]
Message-ID: <> (raw)

Hello Mario.

The following commits were pulled into v5.18.11:

$ git log --oneline --no-merges v5.18.10..v5.18.11 | grep ACPI
2783414e6ef7 ACPI: CPPC: Don't require _OSC if X86_FEATURE_CPPC is supported
3068cfeca3b5 ACPI: CPPC: Only probe for _CPC if CPPC v2 is acked
8beb71759cc8 ACPI: bus: Set CPPC _OSC bits for all and when CPPC_LIB is supported
13bb696dd2f3 ACPI: CPPC: Check _OSC for flexible address space

and now this happens:

$ sudo modprobe amd-pstate shared_mem=1
modprobe: ERROR: could not insert 'amd_pstate': No such device

With v5.18.10 this worked just fine.

In your upstream commit 8b356e536e69f3a4d6778ae9f0858a1beadabb1f you write:

If there is additional breakage on the shared memory designs also
missing this _OSC, additional follow up changes may be needed.

So the question is what else should be pulled into the stable tree to unbreak amd-pstate?


Oleksandr Natalenko (post-factum)

             reply	other threads:[~2022-07-12 17:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-12 17:40 Oleksandr Natalenko [this message]
2022-07-12 17:49 ` [REGRESSION] amd-pstate doesn't work since v5.18.11 Yuan, Perry
2022-07-12 17:50   ` Limonciello, Mario
2022-07-12 17:54     ` Oleksandr Natalenko
2022-07-12 20:07       ` Limonciello, Mario
2022-07-12 21:55         ` Oleksandr Natalenko
2022-07-13  2:40         ` Yuan, Perry
2022-07-13  3:10           ` Mario Limonciello

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \

* 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.