All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 218686] Fail to set energy_performance_preference of amd processor on asus ga403uv
Date: Wed, 31 Jul 2024 11:54:25 +0000	[thread overview]
Message-ID: <bug-218686-137361-Im57OMNkCg@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218686-137361@https.bugzilla.kernel.org/>

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

--- Comment #65 from Chema (chemasanchezgarabito@gmail.com) ---
(In reply to xiaojian.du from comment #62)
> (In reply to Chema from comment #61)
> > (In reply to Chema from comment #60)
> > > I have the same laptop and also the command outputs are the same.
> > > 
> > > I have updated last week to the last BIOS version, but no changes I have
> > > seen.
> > > 
> > > Is there any updates to this?
> > 
> > Also, if CPPC is working in windows why it cant in linux?
> 
> Not exactly.
> 
> How to check CPPC is used or not on *Windows OS*:
>     *check Windows Logs -> System, look for "Kernel-Processor-Power" or
> event ID 55.
>        ->>If you find ACPI Collaborative Processor Performance Control,
>            then Windows is using CPPC.
>        ->>If you find ACPI Performance (P) / Throttle (T) State,
>            then it is using legacy P-states, and CPPC is disabled.

I have created and attachment showing that CPPC is working on windows, so is
this a thing of linux that does not work or is it that windows have a
workaround for activating it without the bios having it enabled?

Thanks.

-- 
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-07-31 11:54 UTC|newest]

Thread overview: 102+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-06  2:56 [Bug 218686] New: Fail to set energy_performance_preference of amd processor on asus ga403uv bugzilla-daemon
2024-04-08  1:48 ` [Bug 218686] " bugzilla-daemon
2024-04-10  3:36 ` bugzilla-daemon
2024-04-10  5:28 ` bugzilla-daemon
2024-04-10  5:33 ` bugzilla-daemon
2024-04-10  5:39 ` bugzilla-daemon
2024-04-10  5:41 ` bugzilla-daemon
2024-04-10  5:46 ` bugzilla-daemon
2024-04-10  5:48 ` bugzilla-daemon
2024-04-10  6:17 ` bugzilla-daemon
2024-04-10  6:19 ` bugzilla-daemon
2024-04-10  6:26 ` bugzilla-daemon
2024-04-10  6:27 ` bugzilla-daemon
2024-04-10  6:29 ` bugzilla-daemon
2024-04-10  6:42 ` bugzilla-daemon
2024-04-10  6:43 ` bugzilla-daemon
2024-04-10  6:47 ` bugzilla-daemon
2024-04-10  6:49 ` bugzilla-daemon
2024-04-10  6:51 ` bugzilla-daemon
2024-04-10  6:55 ` bugzilla-daemon
2024-04-10  7:02 ` bugzilla-daemon
2024-04-10  7:12 ` bugzilla-daemon
2024-04-10  7:21 ` bugzilla-daemon
2024-04-10  7:26 ` bugzilla-daemon
2024-04-10  7:27 ` bugzilla-daemon
2024-04-10 16:08 ` bugzilla-daemon
2024-04-10 16:08 ` bugzilla-daemon
2024-04-11  4:18 ` bugzilla-daemon
2024-04-11  4:19 ` bugzilla-daemon
2024-04-11  4:20 ` bugzilla-daemon
2024-04-11  5:29 ` bugzilla-daemon
2024-04-11  5:30 ` bugzilla-daemon
2024-04-11  7:25 ` bugzilla-daemon
2024-04-11  9:02 ` bugzilla-daemon
2024-04-11  9:15 ` bugzilla-daemon
2024-04-11 10:09 ` bugzilla-daemon
2024-04-11 11:14 ` bugzilla-daemon
2024-04-11 12:56 ` bugzilla-daemon
2024-04-11 15:53 ` bugzilla-daemon
2024-04-11 15:54 ` bugzilla-daemon
2024-04-15  8:37 ` bugzilla-daemon
2024-04-18  7:36 ` bugzilla-daemon
2024-04-18  7:56 ` bugzilla-daemon
2024-04-18  8:41 ` bugzilla-daemon
2024-04-23  7:03 ` bugzilla-daemon
2024-04-23  7:25 ` bugzilla-daemon
2024-05-17  8:50 ` bugzilla-daemon
2024-05-17 11:53 ` bugzilla-daemon
2024-05-17 15:11 ` bugzilla-daemon
2024-05-20 15:26 ` bugzilla-daemon
2024-05-22 14:39 ` bugzilla-daemon
2024-05-22 14:53 ` bugzilla-daemon
2024-05-22 15:12 ` bugzilla-daemon
2024-05-27  8:12 ` bugzilla-daemon
2024-05-27  8:21 ` bugzilla-daemon
2024-05-27  9:48 ` bugzilla-daemon
2024-05-27 10:09 ` bugzilla-daemon
2024-07-15 23:08 ` bugzilla-daemon
2024-07-19  8:46 ` bugzilla-daemon
2024-07-30 10:32 ` bugzilla-daemon
2024-07-30 18:10 ` bugzilla-daemon
2024-07-30 23:34 ` bugzilla-daemon
2024-07-30 23:38 ` bugzilla-daemon
2024-07-31  5:41 ` bugzilla-daemon
2024-07-31  5:41 ` bugzilla-daemon
2024-07-31 11:50 ` bugzilla-daemon
2024-07-31 11:54 ` bugzilla-daemon [this message]
2024-07-31 12:12 ` bugzilla-daemon
2024-08-01  3:39 ` bugzilla-daemon
2024-08-01 12:02 ` bugzilla-daemon
2024-08-03 18:54 ` bugzilla-daemon
2024-08-03 18:56 ` bugzilla-daemon
2024-08-04 15:00 ` bugzilla-daemon
2024-08-04 23:50 ` bugzilla-daemon
2024-08-05 13:11 ` bugzilla-daemon
2024-08-05 14:32 ` bugzilla-daemon
2024-08-05 20:16 ` bugzilla-daemon
2024-08-06  8:29 ` bugzilla-daemon
2024-08-06  9:11 ` bugzilla-daemon
2024-08-06 14:27 ` bugzilla-daemon
2024-09-08 15:15 ` bugzilla-daemon
2024-09-08 15:33 ` bugzilla-daemon
2024-09-08 15:34 ` bugzilla-daemon
2024-09-09  2:54 ` bugzilla-daemon
2024-09-09 13:54 ` bugzilla-daemon
2024-09-09 14:43 ` bugzilla-daemon
2024-09-09 15:00 ` bugzilla-daemon
2024-09-09 15:02 ` bugzilla-daemon
2024-09-09 15:04 ` bugzilla-daemon
2024-09-09 21:16 ` bugzilla-daemon
2024-09-09 21:18 ` bugzilla-daemon
2024-09-09 21:31 ` bugzilla-daemon
2024-09-09 21:54 ` bugzilla-daemon
2024-09-09 22:06 ` bugzilla-daemon
2024-09-10  0:21 ` bugzilla-daemon
2024-09-10  0:49 ` bugzilla-daemon
2024-09-10  1:20 ` bugzilla-daemon
2024-09-10  1:22 ` bugzilla-daemon
2024-09-10 18:28 ` bugzilla-daemon
2024-09-11  4:32 ` bugzilla-daemon
2024-09-23 15:57 ` bugzilla-daemon
2024-09-23 15:58 ` 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-218686-137361-Im57OMNkCg@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.