Linux Power Management development
 help / color / mirror / Atom feed
From: Mario Limonciello <mario.limonciello@amd.com>
To: Akram Boulahia <akram02st@gmail.com>
Cc: kprateek.nayak@amd.com, linux-kernel@vger.kernel.org,
	linux-pm@vger.kernel.org, perry.yuan@amd.com, rafael@kernel.org,
	ray.huang@amd.com, scardracs@disroot.org, stable@vger.kernel.org,
	viresh.kumar@linaro.org
Subject: Re: [PATCH] cpufreq/amd-pstate: Don't fail active mode init on read-only auto_sel
Date: Mon, 12 Oct 2026 10:16:45 -0500	[thread overview]
Message-ID: <9c76b6ac-114c-40ed-9f2a-e3f8fff68059@amd.com> (raw)
In-Reply-To: <20261009001022.6660-1-akram02st@gmail.com>



On 10/8/26 19:10, Akram Boulahia wrote:
> On Thu, Oct 8, 2026 at 10:12 PM Mario Limonciello wrote:
>> You're in a really weird path if you have an 8945HS that is using
>> shared memory.  That system has MSR access.
>>
>> IE this sounds like a severe BIOS bug.  Let's see what happens after
>> you update BIOS.  If it's still failing please share an acpidump
>> somewhere (like a kernel bugzilla).
>>
>> Need to make sure we understand why your system is behaving this way
>> before making code changes.
> 
> Thanks, you were right. After updating the BIOS from 308 to 311,
> amd-pstate works on this GA403UV with an unpatched 7.2.8 kernel. Active
> mode loads as amd-pstate-epp, amd_pstate=passive loads as amd-pstate,
> and the "CPPC feature is supported but currently disabled by the BIOS"
> line is gone.
> 
> So the BIOS update was the real fix, and this patch only worked around
> the old BIOS state. It also doesn't handle passive mode properly. Please
> drop it.

Thanks, less quirks or unintended codepaths is the best outcome.

      reply	other threads:[~2026-10-12 15:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-08  4:07 [PATCH] cpufreq/amd-pstate: Don't fail active mode init on read-only auto_sel Akram Boulahia
2026-10-08 21:12 ` Mario Limonciello
2026-10-09  0:10   ` Akram Boulahia
2026-10-12 15:16     ` Mario Limonciello [this message]

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=9c76b6ac-114c-40ed-9f2a-e3f8fff68059@amd.com \
    --to=mario.limonciello@amd.com \
    --cc=akram02st@gmail.com \
    --cc=kprateek.nayak@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=perry.yuan@amd.com \
    --cc=rafael@kernel.org \
    --cc=ray.huang@amd.com \
    --cc=scardracs@disroot.org \
    --cc=stable@vger.kernel.org \
    --cc=viresh.kumar@linaro.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