From: Aaron Rainbolt <arainbolt@kfocus.org>
To: yumpusamongus@gmail.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,
srinivas.pandruvada@linux.intel.com
Subject: Re: [BUG] intel_pstate: CPU frequencies miscalculated/incorrectly detected on Arrow Lake hardware
Date: Mon, 26 Jan 2026 10:14:37 -0600 [thread overview]
Message-ID: <20260126101437.338255f3@kf-m2g5> (raw)
In-Reply-To: <ddfa4153-023a-4f48-bff9-6d6a211b6d52@gmail.com>
> It also sounds similar to a situation I reported here [1]. My machine
> is a desktop 265K in an ASRock motherboard.
>
> The problem was fixed when I updated the firmware to version 3.11,
> which contained microcode 0x11a. That firmware was released in
> September. The latest 3.15 from Dec 29 contains microcode 0x11d. You
> can check by grepping dmesg for "microcode".
> 1.
> https://lore.kernel.org/all/53027db5-f750-4b6f-8ac5-a849dff2524b@gmail.com/
Thanks! We'll take a look at this and see if a microcode update
resolves the issue.
--
Aaron
prev parent reply other threads:[~2026-01-26 16:14 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
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 [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=20260126101437.338255f3@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=rjw@rjwysocki.net \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=yumpusamongus@gmail.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