linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Pandruvada, Srinivas" <srinivas.pandruvada@intel.com>
To: "linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"dgilmore@redhat.com" <dgilmore@redhat.com>,
	"Mario.Limonciello@dell.com" <Mario.Limonciello@dell.com>
Subject: Re: issues with suspend on Dell XPS 13 2-in-1
Date: Tue, 17 Apr 2018 22:59:39 +0000	[thread overview]
Message-ID: <1524005977.31134.15.camel@intel.com> (raw)
In-Reply-To: <b7c4434319bf4ff8877f882d219a60ba@ausx13mpc120.AMER.DELL.COM>

[-- Attachment #1: Type: text/plain, Size: 6054 bytes --]

On Mon, 2018-04-16 at 16:07 +0000, Mario.Limonciello@dell.com wrote:
> Hi Dennis,
> 
> > -----Original Message-----
> > From: Dennis Gilmore [mailto:dgilmore@redhat.com]
> > Sent: Friday, April 13, 2018 9:03 PM
> > To: linux-kernel@vger.kernel.org; linux-acpi@vger.kernel.org
> > Cc: Limonciello, Mario
> > Subject: issues with suspend on Dell XPS 13 2-in-1
> > 
> > Hi All,
> > 
> > I have a Dell XPS 13 2-in-1 (9365) that when I supend gets warm and
> > has
> > much shorter than expected battery life, it is about the same as if
> > the
> > laptop just runs. I am currently running Fedora 28 with 4.16.2
> > kernel.
> > 
> 
> Since battery consumption is quite relative I think It would be good
> if
> you can make a comparable benchmark as this is further discussed.
> Eg fully charge your notebook, pull the plug, suspend it at 100% and
> check the power left after some repeatable amount of time.
> 
> > My laptop has NVMe for storage and is configured for AHCI mode in
> > the
> > bios.
> > 
> > powertop by default shows
> > > > Bad           VM writeback timeout
> > 
> >    Bad           NMI watchdog should be turned off
> >    Bad           Autosuspend for unknown USB device 1-7 (138a:0091)
> >    Bad           Runtime PM for I2C Adapter i2c-0 (i915 gmbus dpc)
> >    Bad           Runtime PM for I2C Adapter i2c-1 (i915 gmbus dpb)
> >    Bad           Runtime PM for I2C Adapter i2c-2 (i915 gmbus dpd)
> >    Bad           Runtime PM for PCI Device Intel Corporation
> > Wireless
> > 8265 / 8275
> >    Bad           Runtime PM for PCI Device Intel Corporation Device
> > 590c
> >    Bad           Runtime PM for PCI Device Realtek Semiconductor
> > Co.,
> > Ltd. RTS525A PCI Express Card Reader
> >    Bad           Runtime PM for PCI Device Intel Corporation Device
> > 9d3d
> >    Bad           Runtime PM for PCI Device Sandisk Corp WD Black
> > NVMe
> > SSD
> >    Bad           Runtime PM for PCI Device Intel Corporation
> > Sunrise
> > Point-LP PCI Express Root Port #9
> >    Bad           Runtime PM for PCI Device Intel Corporation
> > Sunrise
> > Point-LP Thermal subsystem
> >    Bad           Runtime PM for PCI Device Intel Corporation
> > Sunrise
> > Point-LP USB 3.0 xHCI Controller
> >    Bad           Runtime PM for PCI Device Intel Corporation
> > Sunrise
> > Point-LP PMC
> >    Bad           Runtime PM for PCI Device Intel Corporation
> > Sunrise
> > Point-LP HD Audio
> >    Bad           Runtime PM for PCI Device Intel Corporation
> > Sunrise
> > Point-LP PCI Express Root Port #1
> >    Bad           Runtime PM for PCI Device Intel Corporation Device
> > 9d4b
> >    Bad           Runtime PM for PCI Device Intel Corporation Xeon
> > E3-
> > 1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem
> >    Bad           Runtime PM for PCI Device Intel Corporation
> > Sunrise
> > Point-LP Integrated Sensor Hub
> >    Bad           Runtime PM for PCI Device Intel Corporation Device
> > 591e
> 
> After you've adjusted all of these in powertop, have you compared
> your performance of the battery over sleep (and actually over runtime
> usage really too)?
> 
> They should help to allow the CPU to get into deeper states.
> 
> After you've made that change you should also see on the "Idle Stats"
> page that your CPU is spending more time in the lower C states
> (hopefully
> more in C9/10).
> 
> Srinivas,
> 
> Do you know why Runtime PM is defaulting to disabled for all of these
> devices?  Is that a default kernel policy problem or a distro policy
> problem?
This is default kernel policy.
I suggest run
#turbostat
then suspend and wake
when wake up let the turbostat collect data for next sampling interval.
We have to see what are PkgC% residencies are?

Thanks,
Srinivas

> 
> 
> >    Good          Bluetooth device interface status
> >    Good          Enable Audio codec power management
> >    Good          Runtime PM for I2C Adapter i2c-8 (Synopsys
> > DesignWare
> > I2C adapter)
> >    Good          Autosuspend for USB device Integrated_Webcam_HD
> > [CNFGE16N092020028362]
> >    Good          Autosuspend for USB device xHCI Host Controller
> > [usb1]
> >    Good          Autosuspend for USB device xHCI Host Controller
> > [usb2]
> >    Good          Runtime PM for I2C Adapter i2c-7 (SMBus I801
> > adapter
> > at efa0)
> >    Good          Autosuspend for unknown USB device 1-2 (8087:0a2b)
> >    Good          Runtime PM for I2C Adapter i2c-6 (Synopsys
> > DesignWare
> > I2C adapter)
> >    Good          I2C Device i2c-DLL077A:01 has no runtime power
> > management
> >    Good          I2C Device i2c-WCOM482F:00 has no runtime power
> > management
> >    Good          Runtime PM for PCI Device Intel Corporation
> > Sunrise
> > Point-LP PCI Express Root Port #10
> >    Good          Runtime PM for PCI Device Intel Corporation
> > Sunrise
> > Point-LP CSME HECI #1
> >    Good          Runtime PM for PCI Device Intel Corporation
> > Sunrise
> > Point-LP Serial IO I2C Controller #1
> >    Good          Runtime PM for PCI Device Intel Corporation
> > Sunrise
> > Point-LP SMBus
> >    Good          Runtime PM for PCI Device Intel Corporation
> > Sunrise
> > Point-LP PCI Express Root Port #5
> >    Good          Runtime PM for PCI Device Intel Corporation
> > Sunrise
> > Point-LP Serial IO I2C Controller #0
> >    Good          Wake-on-lan status for device virbr0-nic
> >    Good          Wake-on-lan status for device virbr0
> >    Good          Wake-on-lan status for device wlp60s0
> > 
> > Regards
> > 
> > Dennis

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3290 bytes --]

  reply	other threads:[~2018-04-17 22:59 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-14  2:02 issues with suspend on Dell XPS 13 2-in-1 Dennis Gilmore
2018-04-16 16:07 ` Mario.Limonciello
2018-04-17 22:59   ` Pandruvada, Srinivas [this message]
2018-04-18 21:01     ` Mario.Limonciello
2018-04-19  4:36       ` Pandruvada, Srinivas
2018-04-19 17:30         ` Mario.Limonciello
2018-04-19 19:45           ` Pandruvada, Srinivas
2018-04-19 19:53             ` Mario.Limonciello
     [not found]     ` <CAJesf3MUUGo_MVpr9+8zy-Nm5OAuYu1uwo2z50T2KcN-G5B5ew@mail.gmail.com>
     [not found]       ` <1524708778.7505.1.camel@intel.com>
2018-04-26  3:06         ` Dennis Gilmore
2018-04-26  5:34           ` Pandruvada, Srinivas
2018-04-26 12:42             ` Dennis Gilmore
2018-04-26 15:09               ` Pandruvada, Srinivas
2018-04-26 15:40                 ` Dennis Gilmore
2018-10-12 13:38                 ` Dennis Gilmore
2018-10-12 17:46                   ` Mario.Limonciello
2018-10-14 18:48                     ` Dennis Gilmore
2018-10-15  4:29                       ` Mario.Limonciello
2018-10-16 17:33                   ` Pandruvada, Srinivas

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=1524005977.31134.15.camel@intel.com \
    --to=srinivas.pandruvada@intel.com \
    --cc=Mario.Limonciello@dell.com \
    --cc=dgilmore@redhat.com \
    --cc=linux-acpi@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;
as well as URLs for NNTP newsgroup(s).