linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 215938] amd-pstate ignoring scaling_max_freq after waking from suspend
Date: Tue, 31 May 2022 02:55:41 +0000	[thread overview]
Message-ID: <bug-215938-137361-uLCaQBjWw8@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215938-137361@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=215938

--- Comment #7 from perry_yuan@outlook.com ---
(In reply to Alex Maras from comment #6)
> Hey Perry,
> 
> I've attached the /proc/cpuinfo output and dmesg output after the listed
> process. Do you want anything more for the moment? Let me know if you need
> anything, happy to help.
> 
> Alex

Thanks for your info.
Could you try this kernel ?

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/log/drivers/cpufreq/amd-pstate.c?h=v5.18

add this to grub.

amd-pstate.dyndbg=+p  acpi-cpufreq.dyndbg=+p freq_table.dyndbg=+p
cpufreq.dyndbg=+p cpufreq_governor.dyndbg=+p

I didn't find amd pstate driver related log in your last dmesg.
more debug logs will be helpful.

Thanks.
Perry.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2022-05-31  2:55 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-03 15:09 [Bug 215938] New: amd-pstate ignoring scaling_max_freq after waking from suspend bugzilla-daemon
2022-05-04  6:16 ` [Bug 215938] " bugzilla-daemon
2022-05-04 13:46 ` bugzilla-daemon
2022-05-20  8:37 ` bugzilla-daemon
2022-05-20  9:55 ` bugzilla-daemon
2022-05-20  9:56 ` bugzilla-daemon
2022-05-20  9:57 ` bugzilla-daemon
2022-05-31  2:55 ` bugzilla-daemon [this message]
2022-05-31  7:32 ` bugzilla-daemon
2022-06-09 14:59 ` bugzilla-daemon
2022-06-09 15:00 ` bugzilla-daemon
2022-06-09 15:15 ` bugzilla-daemon
2022-06-10 17:03 ` bugzilla-daemon
2022-06-11  3:33 ` bugzilla-daemon
2022-06-11  4:11 ` bugzilla-daemon
2022-06-13  1:56 ` bugzilla-daemon
2022-06-13 16:25 ` bugzilla-daemon
2022-06-29 15:35 ` bugzilla-daemon
2022-07-05  1:16 ` bugzilla-daemon
2022-07-05  7:36 ` bugzilla-daemon
2022-07-05  9:28 ` bugzilla-daemon
2022-07-06  6:00 ` bugzilla-daemon
2022-07-07 22:36 ` bugzilla-daemon
2025-04-04 13:09 ` bugzilla-daemon
2025-04-04 13:36 ` 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-215938-137361-uLCaQBjWw8@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 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).