All of lore.kernel.org
 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 12:03:37 +0100	[thread overview]
Message-ID: <Z2vmiUyIcvE8vV0b@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")
[...]
> Graphics:
>   Device-1: Intel TigerLake-H GT1 [UHD Graphics] driver: i915 v: kernel
>   Device-2: NVIDIA GA104M [GeForce RTX 3070 Mobile / Max-Q] driver: nvidia
>     v: 565.77

I note that you're using the out-of-tree nvidia driver on v6.12.

The driver may be using the portions of the akcipher API that were
removed by the commit you bisected to.  E.g. this source file calls
crypto_akcipher_verify():

https://github.com/NVIDIA/open-gpu-kernel-modules/blob/main/kernel-open/nvidia/libspdm_ecc.c

Are you seeing build or load errors for the nvidia module?

If the module is not loaded, no voltage / frequency scaling happens,
which would indeed result in the dGPU consuming an awful lot of power.

Thanks,

Lukas

  parent reply	other threads:[~2024-12-25 11:03 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
2024-12-25 11:03 ` Lukas Wunner [this message]
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=Z2vmiUyIcvE8vV0b@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 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.