All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 218305] Ryzen 7 7840HS gets stuck at 544MHz frequency after a random number of suspend/resume cycles
Date: Tue, 26 Dec 2023 15:18:22 +0000	[thread overview]
Message-ID: <bug-218305-215701-cGJe32bRaD@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218305-215701@https.bugzilla.kernel.org/>

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

--- Comment #10 from Artem S. Tashkinov (aros@gmx.com) ---
This is reproducible without the amd-pmf module:

[root@hp policy0]# lsmod | grep pmf
[root@hp policy0]# cpupower frequency-info
analyzing CPU 13:
  driver: amd-pstate-epp
  CPUs which run at the same hardware frequency: 13
  CPUs which need to have their frequency coordinated by software: 13
  maximum transition latency:  Cannot determine or is not supported.
  hardware limits: 400 MHz - 5.76 GHz
  available cpufreq governors: performance powersave
  current policy: frequency should be within 400 MHz and 5.76 GHz.
                  The governor "powersave" may decide which speed to use
                  within this range.
  current CPU frequency: Unable to call hardware
  current CPU frequency: 542 MHz (asserted by call to kernel)
  boost state support:
    Supported: yes
    Active: yes
    AMD PSTATE Highest Performance: 220. Maximum Frequency: 5.76 GHz.
    AMD PSTATE Nominal Performance: 145. Nominal Frequency: 3.80 GHz.
    AMD PSTATE Lowest Non-linear Performance: 42. Lowest Non-linear Frequency:
1.10 GHz.
    AMD PSTATE Lowest Performance: 16. Lowest Frequency: 400 MHz.

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

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2023-12-26 15:18 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-24  7:21 [Bug 218305] New: Ryzen 7 7840HS gets stuck at 544MHz frequency after a random number of suspend/resume cycles bugzilla-daemon
2023-12-24  7:27 ` [Bug 218305] " bugzilla-daemon
2023-12-24  7:30 ` bugzilla-daemon
2023-12-24 15:03 ` bugzilla-daemon
2023-12-24 15:12 ` bugzilla-daemon
2023-12-24 15:37 ` bugzilla-daemon
2023-12-24 15:38 ` bugzilla-daemon
2023-12-25 10:46 ` bugzilla-daemon
2023-12-25 10:53 ` bugzilla-daemon
2023-12-25 14:42 ` bugzilla-daemon
2023-12-26  4:21 ` bugzilla-daemon
2023-12-26 15:18 ` bugzilla-daemon [this message]
2023-12-26 15:25 ` bugzilla-daemon
2023-12-26 15:29 ` bugzilla-daemon
2024-01-03  0:03 ` bugzilla-daemon
2024-01-17  4:10 ` bugzilla-daemon
2024-01-17 19:33 ` bugzilla-daemon
2024-01-19  7:31 ` bugzilla-daemon
2024-01-19 12:45 ` bugzilla-daemon
2024-01-19 13:52 ` bugzilla-daemon
2024-01-19 15:25 ` bugzilla-daemon
2024-01-20  0:21 ` bugzilla-daemon
2024-01-21 18:05 ` bugzilla-daemon
2024-01-22  1:48 ` bugzilla-daemon
2024-01-22  1:53 ` bugzilla-daemon
2024-01-22  3:22 ` bugzilla-daemon
2024-01-22 17:50 ` bugzilla-daemon
2024-01-22 17:54 ` bugzilla-daemon
2024-03-05 16:57 ` bugzilla-daemon
2024-03-05 19:03 ` bugzilla-daemon
2024-03-06  9:59 ` bugzilla-daemon
2024-03-06 16:20 ` bugzilla-daemon
2024-03-06 16:31 ` bugzilla-daemon
2024-03-06 17:17 ` [Bug 218305] Ryzen 7 7840HS gets stuck at 544MHz frequency after resuming after unplugging the power cord during sleep bugzilla-daemon
2024-03-06 17:38 ` bugzilla-daemon
2024-03-06 17:46 ` bugzilla-daemon
2024-03-06 17:50 ` bugzilla-daemon
2024-03-06 17:55 ` bugzilla-daemon
2024-03-06 18:03 ` bugzilla-daemon
2024-03-06 18:06 ` bugzilla-daemon
2024-03-06 18:08 ` bugzilla-daemon
2024-03-06 18:09 ` bugzilla-daemon
2024-03-06 18:10 ` bugzilla-daemon
2024-04-01  8:00 ` bugzilla-daemon
2024-04-01 13:19 ` bugzilla-daemon
2024-04-01 13:37 ` bugzilla-daemon
2024-04-01 14:04 ` bugzilla-daemon
2024-04-01 14:14 ` bugzilla-daemon
2024-04-01 14:23 ` bugzilla-daemon
2024-04-05  2:20 ` bugzilla-daemon
2024-04-05  8:09 ` bugzilla-daemon
2024-04-05 11:15 ` bugzilla-daemon
2024-04-06  7:48 ` bugzilla-daemon
2024-04-15 17:42 ` bugzilla-daemon
2024-04-15 19:01 ` bugzilla-daemon
2024-04-15 19:35 ` bugzilla-daemon
2024-04-15 20:43 ` bugzilla-daemon
2024-05-06 14:20 ` bugzilla-daemon
2024-05-06 14:23 ` bugzilla-daemon
2024-05-06 14:52 ` bugzilla-daemon
2024-05-06 14:55 ` bugzilla-daemon
2024-05-06 15:16 ` bugzilla-daemon
2024-05-06 17:26 ` bugzilla-daemon
2024-05-07  8:24 ` bugzilla-daemon
2024-05-08  7:39 ` bugzilla-daemon
2024-05-08 11:14 ` bugzilla-daemon
2024-05-08 11:21 ` bugzilla-daemon
2024-05-08 11:42 ` bugzilla-daemon
2024-05-08 22:38 ` bugzilla-daemon
2024-05-09  7:49 ` bugzilla-daemon
2024-05-09  8:46 ` bugzilla-daemon
2024-05-09 13:31 ` bugzilla-daemon
2024-05-11  9:23 ` bugzilla-daemon
2024-05-11 10:25 ` 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-218305-215701-cGJe32bRaD@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=platform-driver-x86@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.