Linux Power Management development
 help / color / mirror / Atom feed
From: Aaron Rainbolt <arainbolt@kfocus.org>
To: srinivas.pandruvada@linux.intel.com
Cc: arainbolt@kfocus.org, kernel-team@lists.ubuntu.com,
	lenb@kernel.org, linux-acpi@vger.kernel.org,
	linux-pm@vger.kernel.org, rjw@rjwysocki.net,
	mmikowski@kfocus.org
Subject: Re: [BUG] intel_pstate: CPU frequencies miscalculated/incorrectly detected on Arrow Lake hardware
Date: Wed, 26 Nov 2025 17:00:31 -0600	[thread overview]
Message-ID: <20251126170031.145b6a56@kf-m2g5> (raw)
In-Reply-To: <4f534cc70650111e420d5ac9040df4e546eed336.camel@linux.intel.com>

(Sorry for this rather malformed email, Claws *still* can't find the
thread for some reason so I'm having to resort to a "mailto" link off
of lore.kernel.org.)

> I asked for some dumps before. We can try to inform the OEM of the
> system as this is a BIOS tables issue. What is the make and model of
> your system?
>
> Thanks,
> Srinivas

We're actively working on getting the dumps you mentioned previously
for all three affected machines, along with the model info and some
benchmarking results with our current production kernel and the latest
mainline kernel. It's taking a bit longer than we expected, but we're
pretty close. I should have more info by Monday if all goes according
to plan on our end.

Thanks for your help!

  reply	other threads:[~2025-11-26 23:00 UTC|newest]

Thread overview: 19+ 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 [this message]
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
2026-01-11  4:53 ` Russell Haley
2026-01-26 16:14   ` Aaron Rainbolt

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=20251126170031.145b6a56@kf-m2g5 \
    --to=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 \
    --cc=srinivas.pandruvada@linux.intel.com \
    /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