linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Witt <thomas@witt.link>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: david.e.box@linux.intel.com, Thomas Witt <kernel@witt.link>,
	Bjorn Helgaas <helgaas@kernel.org>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Kuppuswamy Sathyanarayanan 
	<sathyanarayanan.kuppuswamy@linux.intel.com>,
	Vidya Sagar <vidyas@nvidia.com>,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	Kai-Heng Feng <kai.heng.feng@canonical.com>,
	Tasev Nikola <tasev.stefanoska@skynet.be>,
	Mark Enriquez <enriquezmark36@gmail.com>,
	Koba Ko <koba.ko@canonical.com>,
	linux-pci@vger.kernel.org
Subject: Re: [PATCH] PCI/ASPM: Add back L1 PM Substate save and restore
Date: Sat, 5 Aug 2023 09:57:47 +0200	[thread overview]
Message-ID: <5d5dc59d-0ce0-c98c-c6c8-f1d748a8d968@witt.link> (raw)
In-Reply-To: <20230731150128.GK14638@black.fi.intel.com>

On 31/07/2023 17:01, Mika Westerberg wrote:
> Hi Thomas,
> 
> Thanks for trying that. Did you manage to try out the S0ix script David
> suggested? That should show us hopefully what is draining the battery in
> s2idle.

Hi Mika,

I did, with -s it gives

Your system does not support low power S0 idle capability.
Isolation suggestion:
Please check BIOS low power S0 idle capability setting.

with -r on

Your system did not achieve the runtime PC10 state during screen ON

additionally, it encounters a syntax error:
./s0ix-selftest-tool.sh: line 1182: wc:: syntax error in expression 
(error token is ":")

with -r off, it tries xset which fails due to a lack of xserver.

Thomas

  reply	other threads:[~2023-08-05  7:58 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-27  6:24 [PATCH] PCI/ASPM: Add back L1 PM Substate save and restore Mika Westerberg
2023-06-27  9:53 ` Thomas Witt
2023-06-27 10:04   ` Mika Westerberg
2023-06-27 20:41     ` Bjorn Helgaas
2023-06-28  6:46       ` Mika Westerberg
2023-06-28 10:24         ` Thomas Witt
2023-06-28 10:59           ` Mika Westerberg
2023-06-28 12:30             ` Mika Westerberg
2023-06-29  9:47             ` Thomas Witt
2023-06-29 10:23               ` Mika Westerberg
2023-06-29 14:24               ` David E. Box
2023-06-30 10:41                 ` Mika Westerberg
2023-06-30 16:58                   ` Thomas Witt
2023-07-05 20:53                     ` David E. Box
2023-07-06 19:14                       ` Thomas Witt
2023-07-31 15:01                         ` Mika Westerberg
2023-08-05  7:57                           ` Thomas Witt [this message]
2023-08-07  7:58                             ` Mika Westerberg
2023-08-10 23:44                               ` David E. Box
2023-06-28 12:16         ` Mario Limonciello
2023-06-28 12:38           ` Mika Westerberg

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=5d5dc59d-0ce0-c98c-c6c8-f1d748a8d968@witt.link \
    --to=thomas@witt.link \
    --cc=bhelgaas@google.com \
    --cc=david.e.box@linux.intel.com \
    --cc=enriquezmark36@gmail.com \
    --cc=helgaas@kernel.org \
    --cc=kai.heng.feng@canonical.com \
    --cc=kernel@witt.link \
    --cc=koba.ko@canonical.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=sathyanarayanan.kuppuswamy@linux.intel.com \
    --cc=tasev.stefanoska@skynet.be \
    --cc=vidyas@nvidia.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;
as well as URLs for NNTP newsgroup(s).