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: Fri, 26 Apr 2024 08:18:38 +0000 [thread overview]
Message-ID: <bug-218759-137361-IV3F2xT49Y@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 #13 from The Linux kernel's regression tracker (Thorsten Leemhuis) (regressions@leemhuis.info) ---
FWIW, a more verbose bisection guide can be found here:
https://docs.kernel.org/admin-guide/verify-bugs-and-bisect-regressions.html
While at it, let me add this to the regression tracking:
#regzbot introduced: v6.8..v6.9-rc5
#regzbot summary: Ryzen 7840HS CPU single core never boosts to max frequency
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2024-04-26 8:18 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
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 [this message]
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-IV3F2xT49Y@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).