Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Lukas Wunner <lukas@wunner.de>
To: Kurt Borja <kuurtb@gmail.com>
Cc: linux-crypto@vger.kernel.org,
	Herbert Xu <herbert@gondor.apana.org.au>,
	"David S. Miller" <davem@davemloft.net>,
	linux-kernel@vger.kernel.org
Subject: Re: [REGRESSION][BISECTED] Double energy consumption on idle
Date: Wed, 25 Dec 2024 06:37:25 +0100	[thread overview]
Message-ID: <Z2uaFYEdPZL449_M@wunner.de> (raw)
In-Reply-To: <aqhq6okzqa56w3x6hb6xvhajs3ce6suxfrycjcmojpbrbosvzt@65sxbbnksphj>

On Tue, Dec 24, 2024 at 07:42:49PM -0500, Kurt Borja wrote:
> When I first booted into v6.13 I noticed my laptop got instantly hotter
> and battery started draining fast. Today I bisected the kernel an ran
> powerstat [1]. It comes down to
> 
> Upstream commit: 6b34562f0cfe ("crypto: akcipher - Drop sign/verify operations")
> 
> These results are reproducible on my system 100% of the time, and the
> regression is still present on the latest upstream commit.
> 
> Please tell me if there is more info or test I should provide. I can
> test any patch candidates too.

The commit removes dead code and doesn't touch anything power-related.
So it's quite odd that it should cause a power regression.

Could you try reverting only this single commit and verify that the
issue goes away?  Just to double-check that this commit is really
the root cause.


> Before commit 6b34562f0cfe
> CPU:  24.94 Watts on average with standard deviation 0.21  
[...]
> After commit 6b34562f0cfe
> CPU:  57.64 Watts on average with standard deviation 0.88

That's a huge amount of extra power draw.  I'd suspect the Nvidia
discrete graphics to consume such an amount, so maybe it's not
powered down?  Have you enabled relevant Kconfig options such as
CONFIG_VGA_SWITCHEROO and CONFIG_DRM_NOUVEAU on the v6.13-rc kernel?

Thanks,

Lukas

  reply	other threads:[~2024-12-25  5:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-25  0:42 [REGRESSION][BISECTED] Double energy consumption on idle Kurt Borja
2024-12-25  5:37 ` Lukas Wunner [this message]
2024-12-25 11:03 ` Lukas Wunner
2024-12-25 13:48   ` Kurt Borja
2024-12-27  9:37     ` Lukas Wunner

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=Z2uaFYEdPZL449_M@wunner.de \
    --to=lukas@wunner.de \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=kuurtb@gmail.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@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