All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 218759] 6.9-rc kernels - with Ryzen 7840HS CPU single core never boosts to max frequency
Date: Thu, 25 Apr 2024 10:12:06 +0000	[thread overview]
Message-ID: <bug-218759-137361-elUO9ZYdPb@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218759-137361@https.bugzilla.kernel.org/>

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

--- Comment #6 from Gaha (gahabana@gmail.com) ---
hi, I've applied patches to 6.9.0-rc5 and built kernel with those.
With kernel command line being either "passive", "guided" or "active" result is
the same - single core never goes above 4.35Ghz. with 6.8 kernel it does go all
the way to 5.1Ghz.

here is the output of lscpu -ae when running Geekbench (during single core
load) and it is the same with 'cat /dev/zero > /dev/null' . As for the 'tbench
-t 100 2' - on my ubuntu system tbench is part of diskbench. If you were
referring to tbench as part of kernel testing suite
(https://docs.kernel.org/6.8/admin-guide/pm/amd-pstate.html) - i tried building
it, it produces errors as scripts are looking for amd-pstate driver not
amd-pstate-epp driver etc...

However, am 100% certain that frequencies never boost above 4.35Ghz.(went back
to 6.8.7 kernel and all is good).

Here is the (hopefully useful output) showing that new 'cpp_boost' flag is
there etc as well as lspci -ae outputs during single core loading:

zh@muc:~/kselftest/amd-pstate$ cat /sys/devices/system/cpu/amd_pstate/cpb_boost
1
zh@muc:~/kselftest/amd-pstate$ cat
/sys/devices/system/cpu/cpufreq/policy0/scaling_driver
amd-pstate-epp

zh@muc:~$ lscpu -ae
CPU NODE SOCKET CORE L1d:L1i:L2:L3 ONLINE    MAXMHZ   MINMHZ       MHZ
  0    0      0    0 0:0:0:0          yes 4350.0000 400.0000  400.0000
  1    0      0    1 1:1:1:0          yes 4350.0000 400.0000 4309.2700
  2    0      0    2 2:2:2:0          yes 4350.0000 400.0000 2416.1770
  3    0      0    3 3:3:3:0          yes 4350.0000 400.0000  400.0000
  4    0      0    4 4:4:4:0          yes 4350.0000 400.0000 1722.2209
  5    0      0    5 5:5:5:0          yes 4350.0000 400.0000  400.0000
  6    0      0    6 6:6:6:0          yes 4350.0000 400.0000  400.0000
  7    0      0    7 7:7:7:0          yes 4350.0000 400.0000  400.0000
  8    0      0    0 0:0:0:0          yes 4350.0000 400.0000 1480.4850
  9    0      0    1 1:1:1:0          yes 4350.0000 400.0000 4307.9858
 10    0      0    2 2:2:2:0          yes 4350.0000 400.0000 1751.6750
 11    0      0    3 3:3:3:0          yes 4350.0000 400.0000 1722.3180
 12    0      0    4 4:4:4:0          yes 4350.0000 400.0000  400.0000
 13    0      0    5 5:5:5:0          yes 4350.0000 400.0000  400.0000
 14    0      0    6 6:6:6:0          yes 4350.0000 400.0000  400.0000
 15    0      0    7 7:7:7:0          yes 4350.0000 400.0000  400.0000

Are there any other tests i could run to help figure out root cause of problem
with 6.9 kernel ?

-- 
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:[~2024-04-25 10:12 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-22  6:50 [Bug 218759] New: 6.9-rc kernels - with Ryzen 7840HS CPU single core never boosts to max frequency bugzilla-daemon
2024-04-22  6:54 ` [Bug 218759] " bugzilla-daemon
2024-04-22  8:12 ` bugzilla-daemon
2024-04-22  8:13 ` bugzilla-daemon
2024-04-22 10:15 ` bugzilla-daemon
2024-04-24 23:44 ` bugzilla-daemon
2024-04-25  0:39 ` bugzilla-daemon
2024-04-25 10:12 ` bugzilla-daemon [this message]
2024-04-25 15:21 ` bugzilla-daemon
2024-04-25 16:21 ` bugzilla-daemon
2024-04-25 18:15 ` bugzilla-daemon
2024-04-25 18:49 ` bugzilla-daemon
2024-04-26  0:06 ` bugzilla-daemon
2024-04-26  0:10 ` bugzilla-daemon
2024-04-26  8:18 ` bugzilla-daemon
2024-04-26  8:28 ` bugzilla-daemon
2024-04-26 13:59 ` bugzilla-daemon
2024-05-03  8:49 ` bugzilla-daemon
2024-05-03 11:08 ` bugzilla-daemon
2024-05-03 12:24 ` bugzilla-daemon
2024-05-07  8:41 ` bugzilla-daemon
2024-05-07  9:13 ` bugzilla-daemon
2024-05-07  9:14 ` bugzilla-daemon
2024-05-07 10:29 ` bugzilla-daemon
2024-05-07 10:30 ` bugzilla-daemon
2024-05-07 12:19 ` bugzilla-daemon
2024-05-07 12:21 ` bugzilla-daemon
2024-05-07 12:22 ` bugzilla-daemon
2024-05-07 13:00 ` bugzilla-daemon
2024-05-07 13:20 ` bugzilla-daemon
2024-05-07 13:23 ` bugzilla-daemon
2024-05-07 13:24 ` bugzilla-daemon
2024-05-07 17:48 ` bugzilla-daemon
2024-05-07 17:57 ` bugzilla-daemon
2024-05-07 18:50 ` bugzilla-daemon
2024-05-07 18:57 ` bugzilla-daemon
2024-05-07 19:01 ` 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-218759-137361-elUO9ZYdPb@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.