From: bugzilla-daemon@kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 217361] AMD P-state driver is too aggressive by default
Date: Sun, 23 Apr 2023 06:42:29 +0000 [thread overview]
Message-ID: <bug-217361-137361-t8qBePxNGb@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217361-137361@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=217361
--- Comment #2 from ahmedmohsin6@gmail.com ---
(In reply to Artem S. Tashkinov from comment #1)
> You've not specified what issues you have and what it means "aggressive".
Sorry I should have explained better. CPU Frequency goes down to around 400MHz
when using the AMD p-state driver as you can see in the info from cpupower.
Running anything is slow and takes a long time. This isn't the case when using
acpi_cpufreq.
--
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:[~2023-04-23 6:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-217361-137361@https.bugzilla.kernel.org/>
2023-04-23 6:38 ` [Bug 217361] AMD P-state driver is too aggressive by default bugzilla-daemon
2023-04-23 6:42 ` bugzilla-daemon [this message]
2023-04-23 7:28 ` bugzilla-daemon
2023-04-23 8:41 ` 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-217361-137361-t8qBePxNGb@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.