All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Huang Rui <ray.huang@amd.com>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	Michele Della Guardia <micheledellaguardia@yahoo.it>
Cc: Linux Power Management <linux-pm@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Regressions <regressions@lists.linux.dev>
Subject: Fwd: Abnormal battery drain with kernel 6.5 (Ryzen 5500u)
Date: Fri, 1 Sep 2023 16:42:22 +0700	[thread overview]
Message-ID: <bede02c1-ef90-8e30-aa8b-e6fae49a8ccf@gmail.com> (raw)

Hi,

I notice a regression report on Bugzilla [1] that have been already handled
there. Quoting from it:

> After switching from 6.4.x kernel to 6.5 I experienced an abnormal battery drain since my laptop is actually never idle.
> I accepted default CPUfreq to schedutil and AMD Processor P-State mode is 3 (active). 
> 
> I expected a different behaviour, but am I missing something?
> In my boot configuration I had "amd_pstate.shared_mem=1" and tried to remove this switch, but did not affect my power consuption.
> 
> Is there something changed from 6.4.x to 6.5 that requires a different configuration to get an optimal power consumption?
> 
> Thanks a lot for your attention

See Bugzilla for the full thread.

Anyway, I'm adding it to regzbot:

#regzbot introduced: v6.4..v6.5 https://bugzilla.kernel.org/show_bug.cgi?id=217853

Thanks.

-- 
An old man doll... just what I always wanted! - Clara

             reply	other threads:[~2023-09-01  9:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-01  9:42 Bagas Sanjaya [this message]
2023-09-08  4:41 ` Fwd: Abnormal battery drain with kernel 6.5 (Ryzen 5500u) Huang Rui
2023-09-08  7:04   ` Michele Della Guardia
2023-11-02  8:05   ` Fwd: " Bagas Sanjaya
2023-11-02  9:15     ` Mateusz Guzik

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=bede02c1-ef90-8e30-aa8b-e6fae49a8ccf@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=micheledellaguardia@yahoo.it \
    --cc=rafael@kernel.org \
    --cc=ray.huang@amd.com \
    --cc=regressions@lists.linux.dev \
    --cc=viresh.kumar@linaro.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.