linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: srinivas pandruvada <srinivas.pandruvada@linux.intel.com>
To: Aaron Rainbolt <arainbolt@kfocus.org>
Cc: kernel-team@lists.ubuntu.com, lenb@kernel.org,
	linux-acpi@vger.kernel.org, 	linux-pm@vger.kernel.org,
	mmikowski@kfocus.org, rjw@rjwysocki.net
Subject: Re: [BUG] intel_pstate: CPU frequencies miscalculated/incorrectly detected on Arrow Lake hardware
Date: Tue, 23 Dec 2025 11:21:51 -0800	[thread overview]
Message-ID: <08052bbd0a6fa2ca2d0c349936086cd31be87b37.camel@linux.intel.com> (raw)
In-Reply-To: <20251223114122.0227dab8@kf-m2g5>

Hi Aaron,

On Tue, 2025-12-23 at 11:41 -0600, Aaron Rainbolt wrote:
> On Wed, 17 Dec 2025 05:33:08 -0800
> srinivas pandruvada <srinivas.pandruvada@linux.intel.com> wrote:
> 
> > Hi Aaron,
> > 
> > Tested on a platform with the similar CPU (100 MHz more max). There
> > is
> > no issue in max frequency or base frequency display.
> 
> Hi Srinivas,
> 
> Thanks for taking the time to look into this. For reference, the
> X560WNR-G that we last reported has the INSYDE BIOS version
> 1.07.07S3min29. That might be useful when reaching out to Clevo.
> 
> Since we’ve seen this on hardware from Clevo, TongFang, and ASUS,
> we’ll
> want to report to all of them. Can you tell us what tool you are
> using
> to measure the max and base frequency displays?

I checked the sysfs display of base and scalig_max freq from cpufreq.
For current frequencies used turbotstat  with stress 1 CPU busy.

>  Are both P and E cores
> displaying the proper frequencies on your end?
Yes.

>  We can then share that
> with the ODMs.
> 

Sure.

Thanks,
Srinivas

> Thanks again,
> 
> --
> Aaron

      reply	other threads:[~2025-12-23 19:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-18  3:33 [BUG] intel_pstate: CPU frequencies miscalculated/incorrectly detected on Arrow Lake hardware Aaron Rainbolt
2025-05-19 12:48 ` srinivas pandruvada
2025-11-06 19:46   ` Aaron Rainbolt
2025-07-22 16:31 ` Aaron Rainbolt
2025-07-22 17:24   ` srinivas pandruvada
2025-11-26 23:00     ` Aaron Rainbolt
2025-12-03 17:38       ` Aaron Rainbolt
2025-12-05 19:10         ` srinivas pandruvada
2025-12-05 19:28           ` Rafael J. Wysocki
2025-12-05 19:50             ` srinivas pandruvada
2025-12-05 20:04               ` Rafael J. Wysocki
2025-12-15  0:45           ` Aaron Rainbolt
2025-12-15 14:16             ` srinivas pandruvada
2025-12-15 15:25               ` Aaron Rainbolt
2025-12-17 13:33                 ` srinivas pandruvada
2025-12-23 17:41                   ` Aaron Rainbolt
2025-12-23 19:21                     ` srinivas pandruvada [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=08052bbd0a6fa2ca2d0c349936086cd31be87b37.camel@linux.intel.com \
    --to=srinivas.pandruvada@linux.intel.com \
    --cc=arainbolt@kfocus.org \
    --cc=kernel-team@lists.ubuntu.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mmikowski@kfocus.org \
    --cc=rjw@rjwysocki.net \
    /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).