Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: linux-pci@vger.kernel.org
Cc: Kuppuswamy Sathyanarayanan
	<sathyanarayanan.kuppuswamy@linux.intel.com>,
	"Artem S. Tashkinov" <aros@gmx.com>
Subject: Re: [Bug 219984] New: [BISECTED] High power usage since 'PCI/ASPM: Correct LTR_L1.2_THRESHOLD computation'
Date: Mon, 7 Apr 2025 10:57:42 -0500	[thread overview]
Message-ID: <20250407155742.GA178541@bhelgaas> (raw)
In-Reply-To: <bug-219984-41252@https.bugzilla.kernel.org/>

[bugzilla reporter bcc'd]

Bisected to https://git.kernel.org/linus/7afeb84d14ea

I'll take a look; including linux-pci for completeness and in case
others are interested.

On Sun, Apr 06, 2025 at 03:11:54PM +0000, bugzilla-daemon@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=219984
> 
>             Bug ID: 219984
>            Summary: [BISECTED] High power usage since 'PCI/ASPM: Correct
>                     LTR_L1.2_THRESHOLD computation'
>           Reporter: sergey.v.dolgov@gmail.com
>         Regression: No
> 
> Created attachment 307924
>   --> https://bugzilla.kernel.org/attachment.cgi?id=307924&action=edit
> Bisection log
> 
> I have been observing increased power consumption on my HP Spectre x360
> Convertible 15-df1xxx (CoffeeLake) since kernel 6.1. Bisection revealed a
> regression in commit 7afeb84d14eaaebb71f5c558ed57ca858e4304e7 (PCI/ASPM:
> Correct LTR_L1.2_THRESHOLD computation). This still affects the mainline. 
> 
> With the original kernel 6.14, turbostat shows that the CPU sticks to Pkg%pc3
> more than 50% of the time, resulting in a discharge rate of 3.52 W reported by
> powertop during an idle empty plasma6 session with screen off.
> 
> After reverting 7afeb84d14eaaebb71f5c558ed57ca858e4304e7 and recompiling the
> kernel with the same config, Pk%pc10, CPU%LPI and SYS%LPI residencies are all
> above 80% during the same session, and "The battery reports a discharge rate of
> 1.35 W."
> 
> The two kernels above had no nvidia drivers to avoid tainting. However,
> compiling also the proprietary nvidia modules reduces the idle power
> consumption further to 796 mW.
> 
> Could you please revert 7afeb84d14eaaebb71f5c558ed57ca858e4304e7 upstream? Or,
> at least, to switch between the two encode_l12_threshold algorithms selectively
> depending on the system.

       reply	other threads:[~2025-04-07 15:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-219984-41252@https.bugzilla.kernel.org/>
2025-04-07 15:57 ` Bjorn Helgaas [this message]
2025-04-07 16:10   ` [Bug 219984] New: [BISECTED] High power usage since 'PCI/ASPM: Correct LTR_L1.2_THRESHOLD computation' Bjorn Helgaas
2025-04-07 18:33     ` Sergey Dolgov
2025-04-08 16:36       ` Bjorn Helgaas
2025-04-08 20:02         ` Sergey Dolgov
2025-04-08 23:18           ` Bjorn Helgaas
2025-04-10 13:59             ` Sergey Dolgov
2025-04-10 22:09               ` Bjorn Helgaas
2025-04-13 11:59                 ` Sergey Dolgov
2025-04-18 22:55                   ` Bjorn Helgaas
2025-04-20 12:42                     ` Sergey Dolgov
2025-05-02 21:30                 ` David E. Box
2025-05-06 11:57                   ` Sergey Dolgov
2025-07-08 18:02                     ` Sergey Dolgov
2025-07-08 18:37                       ` Bjorn Helgaas

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=20250407155742.GA178541@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=aros@gmx.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=sathyanarayanan.kuppuswamy@linux.intel.com \
    /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