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: Thu, 30 Jul 2026 09:49:36 +0000 [thread overview]
Message-ID: <bug-218305-215701-8AYCriCWcA@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218305-215701@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=218305
gunnar.kistner@gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |gunnar.kistner@gmail.com
--- Comment #158 from gunnar.kistner@gmail.com ---
I can reproduce what appears to be the same issue on a different HP AMD laptop.
Hardware and software:
* HP ZBook Power 16 inch G11 A Mobile Workstation PC
* Product number: 9A818AV
* AMD Ryzen 9 PRO 8945HS with Radeon 780M Graphics
* BIOS: W85 Ver. 01.10.05
* Embedded-controller firmware: 8.82
* Ubuntu 24.04.4 LTS
* Current kernel: Ubuntu 7.0.0-28-generic
* Also observed with Ubuntu 6.17.0-35-generic
* amd-pstate active / amd-pstate-epp
The issue occurs when the AC adapter state changes while the laptop is fully
suspended.
Confirmed reproduction:
1. Suspend while connected to AC.
2. Wait until the laptop has fully entered suspend.
3. Disconnect AC while it is suspended.
4. Resume on battery.
5. All 16 logical CPUs may remain fixed at approximately 544 MHz, even under
full CPU load.
The reverse sequence has also been observed:
1. Suspend while running on battery.
2. Connect AC while fully suspended.
3. Resume while connected to AC.
4. The CPUs may again remain fixed at approximately 544 MHz.
Changing powerprofilesctl between balanced and performance does not help.
When affected, Linux still reports:
* scaling_max_freq: approximately 5.263 GHz
* cpuinfo_max_freq: approximately 5.263 GHz
* CPU boost: enabled
* amd-pstate status: active
Briefly changing the AC adapter state again after resume immediately restores
normal frequency scaling. Under the same 16-thread load, the CPU then reaches
approximately 4.39 GHz.
Ubuntu downstream report:
Launchpad Bug #2162127
I have attached a combined log containing the CPU state before and after the
recovery AC event, the cpufreq limits, and the relevant udev power-supply
events.
The complete before/after evidence is attached to Ubuntu Launchpad Bug
#2162127.
Key results from the attachment:
* Before the recovery AC event, all 16 logical CPUs remain at approximately 544
MHz under full load.
* After briefly changing the AC adapter state, the same test reaches
approximately 4.39 GHz.
* `scaling_max_freq` and `cpuinfo_max_freq` remain approximately 5.263 GHz in
both states.
* AMD P-State remains active, CPU boost remains enabled, and the power and
platform profiles remain balanced.
* The recovery event is detected normally as `POWER_SUPPLY_ONLINE=1`; after
disconnecting AC again, the system returns to `POWER_SUPPLY_ONLINE=0` and
battery discharging, while normal CPU performance remains restored.
--
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:[~2026-07-30 9:49 UTC|newest]
Thread overview: 166+ 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
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
2024-08-12 18:55 ` bugzilla-daemon
2024-08-12 22:19 ` bugzilla-daemon
2024-08-12 22:20 ` bugzilla-daemon
2024-09-19 7:57 ` bugzilla-daemon
2024-09-19 12:05 ` bugzilla-daemon
2024-12-22 2:59 ` bugzilla-daemon
2024-12-22 3:00 ` bugzilla-daemon
2024-12-22 7:19 ` bugzilla-daemon
2024-12-22 15:52 ` bugzilla-daemon
2024-12-22 19:55 ` bugzilla-daemon
2024-12-22 20:15 ` bugzilla-daemon
2025-01-06 3:47 ` bugzilla-daemon
2025-01-06 3:52 ` bugzilla-daemon
2025-04-10 18:01 ` bugzilla-daemon
2025-04-10 18:05 ` bugzilla-daemon
2025-04-10 18:15 ` bugzilla-daemon
2025-04-10 18:30 ` bugzilla-daemon
2025-04-10 18:59 ` bugzilla-daemon
2025-04-10 18:59 ` bugzilla-daemon
2025-04-10 19:06 ` bugzilla-daemon
2025-04-14 18:27 ` bugzilla-daemon
2025-04-14 18:45 ` bugzilla-daemon
2025-04-24 8:12 ` bugzilla-daemon
2025-05-05 21:27 ` bugzilla-daemon
2025-07-16 10:46 ` bugzilla-daemon
2025-07-16 15:32 ` bugzilla-daemon
2025-07-18 8:22 ` bugzilla-daemon
2025-07-23 11:29 ` bugzilla-daemon
2025-08-28 5:10 ` bugzilla-daemon
2025-09-08 19:58 ` bugzilla-daemon
2025-09-08 20:09 ` bugzilla-daemon
2025-09-09 4:27 ` bugzilla-daemon
2025-09-09 10:38 ` bugzilla-daemon
2025-09-10 4:27 ` bugzilla-daemon
2025-09-10 4:28 ` bugzilla-daemon
2025-09-10 4:33 ` bugzilla-daemon
2025-09-11 4:32 ` bugzilla-daemon
2025-09-11 4:34 ` bugzilla-daemon
2025-09-11 14:18 ` bugzilla-daemon
2025-09-12 6:06 ` bugzilla-daemon
2025-09-13 16:59 ` bugzilla-daemon
2025-09-13 17:37 ` bugzilla-daemon
2025-09-13 18:30 ` bugzilla-daemon
2025-09-13 18:34 ` bugzilla-daemon
2025-09-13 18:44 ` bugzilla-daemon
2025-09-13 18:48 ` bugzilla-daemon
2025-09-14 0:45 ` bugzilla-daemon
2025-09-14 2:03 ` bugzilla-daemon
2025-09-14 2:04 ` bugzilla-daemon
2025-09-14 12:01 ` bugzilla-daemon
2025-09-15 5:49 ` bugzilla-daemon
2025-09-15 16:11 ` bugzilla-daemon
2025-09-15 16:16 ` bugzilla-daemon
2025-09-15 16:24 ` bugzilla-daemon
2025-09-15 16:33 ` bugzilla-daemon
2025-09-15 16:38 ` bugzilla-daemon
2025-09-15 17:12 ` bugzilla-daemon
2025-09-15 17:26 ` bugzilla-daemon
2025-09-16 0:58 ` bugzilla-daemon
2025-09-16 21:20 ` bugzilla-daemon
2025-09-16 22:14 ` bugzilla-daemon
2025-09-17 15:47 ` bugzilla-daemon
2025-09-17 21:49 ` bugzilla-daemon
2025-09-29 15:04 ` bugzilla-daemon
2025-10-06 14:02 ` bugzilla-daemon
2025-10-06 14:25 ` bugzilla-daemon
2025-10-06 21:01 ` bugzilla-daemon
2025-10-12 16:31 ` bugzilla-daemon
2025-10-18 7:37 ` bugzilla-daemon
2025-11-09 3:56 ` bugzilla-daemon
2025-11-09 6:55 ` bugzilla-daemon
2025-11-09 16:11 ` bugzilla-daemon
2025-11-09 19:21 ` bugzilla-daemon
2025-11-13 18:13 ` bugzilla-daemon
2025-11-20 17:34 ` bugzilla-daemon
2026-01-07 14:03 ` bugzilla-daemon
2026-01-08 6:50 ` bugzilla-daemon
2026-01-08 7:26 ` bugzilla-daemon
2026-01-08 13:06 ` bugzilla-daemon
2026-01-08 20:53 ` bugzilla-daemon
2026-04-23 15:03 ` bugzilla-daemon
2026-04-27 17:54 ` bugzilla-daemon
2026-06-21 11:23 ` bugzilla-daemon
2026-07-12 17:52 ` bugzilla-daemon
2026-07-13 9:32 ` bugzilla-daemon
2026-07-13 13:21 ` bugzilla-daemon
2026-07-13 13:53 ` bugzilla-daemon
2026-07-13 14:00 ` bugzilla-daemon
2026-07-13 20:56 ` bugzilla-daemon
2026-07-30 9:49 ` bugzilla-daemon [this message]
2026-07-30 10:08 ` bugzilla-daemon
2026-07-30 10:13 ` 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-8AYCriCWcA@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.