From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 218305] Ryzen 7 7840HS gets stuck at 544MHz frequency after resuming after unplugging the power cord during sleep
Date: Mon, 15 Apr 2024 17:42:21 +0000 [thread overview]
Message-ID: <bug-218305-215701-fEbV7ZcQVU@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218305-215701@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=218305
Pedro (voidpointertonull+kernelorgbugzilla@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |voidpointertonull+kernelorg
| |bugzilla@gmail.com
--- Comment #50 from Pedro (voidpointertonull+kernelorgbugzilla@gmail.com) ---
Coming from Bug #217931 , I found the mentions of being stuck at low frequency
odd as I couldn't observe that despite managing multiple hosts, but then here I
am.
The twist is that I have a 7950X3D desktop setup, not a laptop one, and I
apparently I just ran into the same low frequency issue others experienced.
Unfortunately the usefulness of my information will be limited as I'm on a not
really customized Kubuntu 23.10 setup with kernel 6.5.0 , but on the other hand
I haven't touched anything relevant, not even setting a frequency limit.
I'm observing the CPU being stuck in the 400 MHz - 549 MHz range which is quite
fitting for this bug report, and the host was never suspended / hibernated.
The only relevant oddity I've found so far is that
/sys/devices/system/cpu/cpu4/cpufreq/scaling_max_freq was sticking out like a
sore thumb with 400000 set while other cores had the value of 5759000, but
changing that didn't make a difference.
Not really sure when did this manifest itself, but highly likely after (or
during?) a case of Bug #204253 as I brushed away the slowness for a while as
the usual heavy I/O (over NFS) problem which even used to freeze the desktop
for more than a minute on a weaker setup, but the current higher performance
CPU seemed to take it better, although the experience was still disruptive.
Is this really a laptop bug then instead of a more generic problem with a large
stutter causing some logic to get upset possibly due to timing problems? Heavy
CPU usage alone surely doesn't do the trick as I've seen hosts doing fine with
that, but heavy I/O seems more brutal with possibly similar "world stopping
power" as suspending.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2024-04-15 17:42 UTC|newest]
Thread overview: 57+ 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
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 [this message]
2024-04-15 19:01 ` bugzilla-daemon
2024-04-15 19:35 ` bugzilla-daemon
2024-04-15 20:43 ` 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-fEbV7ZcQVU@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.