From: bugzilla-daemon@kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 219851] [amd-pstate 6.15] Frequency Scaling Will Not Scale Above Lowest Non-Linear Performance on Ryzen 7 5700U
Date: Tue, 11 Mar 2025 04:27:18 +0000 [thread overview]
Message-ID: <bug-219851-137361-gVkotPYIsm@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219851-137361@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=219851
--- Comment #4 from Eric Naim (dnaim@cachyos.org) ---
(In reply to Dhananjay Ugwekar (AMD) from comment #2)
Hi Dhananjay,
> Hello Eric,
>
> 1. Could you please give more details on how to reproduce the issue? which
> governor, amd-pstate mode (when the issue was observed), workload. Are you
> able to reproduce the issue on your machine as well?
> 2. Just to confirm, does the user have
> https://web.git.kernel.org/pub/scm/linux/kernel/git/superm1/linux.git/commit/
> ?h=amd-pstate-v6.15-2025-03-03&id=f6c0b760290951688697d9debbb2b8462c423a48,
> in his tree, it fixed a corner case in the culprit commit that you pointed
> to.
It looks like the user didn't have that commit after all. They were using an
older revision of the patchset that didn't have the updated amd-pstate commits.
I should've asked them to crosscheck their issue with the kernel in our
repositories first. Sorry to have wasted your time. I'm going to close this as
invalid.
>
> Thanks,
> Dhananjay
Regards,
Eric
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2025-03-11 4:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-08 12:52 [Bug 219851] New: [amd-pstate 6.15] Frequency Scaling Will Not Scale Above Lowest Non-Linear Performance on Ryzen 7 5700U bugzilla-daemon
2025-03-08 12:52 ` [Bug 219851] " bugzilla-daemon
2025-03-10 5:13 ` bugzilla-daemon
2025-03-10 15:41 ` bugzilla-daemon
2025-03-11 4:27 ` bugzilla-daemon [this message]
2025-03-11 4:27 ` bugzilla-daemon
2025-03-11 6:21 ` bugzilla-daemon
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=bug-219851-137361-gVkotPYIsm@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-pm@vger.kernel.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 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.