All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 218689] New: AMD_Pstate_EPP Ryzen 7000 issues. Freezing and buzzing
Date: Sat, 06 Apr 2024 20:49:02 +0000	[thread overview]
Message-ID: <bug-218689-137361@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 218689
           Summary: AMD_Pstate_EPP Ryzen 7000 issues. Freezing and buzzing
           Product: Power Management
           Version: 2.5
          Hardware: AMD
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: cpufreq
          Assignee: linux-pm@vger.kernel.org
          Reporter: kbii.chris@gmail.com
        Regression: No

Hardware:

AMD Ryzen 9 7900x
Gigabyte b650 aero g
Corsair Dominator Platinum 2x16 6000MHz

Kernel tested on:

6.8.2 Arch
6.8.1 Arch
6.6.9 Debian

Issue:

There has been a static noise coming from my cpu as well as frequent freezes.
This is nearly constant and makes the computer impossible to use for long due
to the sound.

Remedy:

I have found the issue to disappear completely while using the passive driver
provided by amd_pstate. The scaling driver must be set to schedutil. This
completely mitigates the issue.
kernel flags: amd_pstate=passive cpufreq.default_governor=schedutil

Suspicions:

I suspect the power management implementation used by amd_pstate_epp to be
causing this issue. There is a async param found inside
/sys/devices/system/cpu/power that is always set to false whenever
amd_pstate_epp is used. My intuition tells me this must be what holds up the
system at times while changing c_states or something.

Extra:

I have seen alot of talk surrounding the fTPM and issues around it but I cannot
related these two observations together, hence why I am opening a new issue. If
this is not the right way to go about it mybad, this is my first bug report.

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

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

             reply	other threads:[~2024-04-06 20:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-06 20:49 bugzilla-daemon [this message]
2024-04-07  0:32 ` [Bug 218689] AMD_Pstate_EPP Ryzen 7000 issues. Freezing and static sound bugzilla-daemon
2024-04-07 11:21 ` bugzilla-daemon
2024-04-07 18:11 ` bugzilla-daemon
2024-04-07 19:07 ` bugzilla-daemon
2024-04-07 19:12 ` bugzilla-daemon
2024-04-07 19:40 ` bugzilla-daemon
2024-04-07 19:41 ` bugzilla-daemon
2024-04-08  9:16 ` 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-218689-137361@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.