From: bugzilla-daemon@kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 217589] Intel CPU maximum boost frequency reduced after resume from suspend to RAM
Date: Fri, 23 Jun 2023 17:58:04 +0000 [thread overview]
Message-ID: <bug-217589-137361-mkA7iGdGge@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217589-137361@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=217589
--- Comment #6 from Brad Jackson (bjackson0971@gmail.com) ---
Had to disable secure boot for debug output. First log:
intel_pstate: CPU 1 going offline
smpboot: CPU 1 is now offline
x86: Booting SMP configuration:
smpboot: Booting Node 0 Processor 1 APIC 0x1
intel_pstate: CPU 1 going online
intel_pstate: set_policy cpuinfo.max 5500000 policy->max 5500000
intel_pstate: cpu:1 min_policy_perf:11 max_policy_perf:70
intel_pstate: cpu:1 global_min:11 global_max:70
intel_pstate: cpu:1 max_perf_ratio:70 min_perf_ratio:11
Second log attached below.
--
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:[~2023-06-23 17:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 14:15 [Bug 217589] New: Intel CPU maximum boost frequency reduced after resume from suspend to RAM bugzilla-daemon
2023-06-23 14:43 ` [Bug 217589] " bugzilla-daemon
2023-06-23 14:53 ` bugzilla-daemon
2023-06-23 16:29 ` bugzilla-daemon
2023-06-23 16:41 ` bugzilla-daemon
2023-06-23 17:35 ` bugzilla-daemon
2023-06-23 17:58 ` bugzilla-daemon [this message]
2023-06-23 17:58 ` bugzilla-daemon
2023-06-26 17:05 ` bugzilla-daemon
2023-06-26 17:32 ` bugzilla-daemon
2023-06-26 18:53 ` bugzilla-daemon
2023-07-18 17:14 ` 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-217589-137361-mkA7iGdGge@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.