Re: issues with suspend on Dell XPS 13 2-in-1
Hi Dennis,
On Fri, 2018-10-12 at 08:38 -0500, Dennis Gilmore wrote:
> El jue, 26-04-2018 a las 15:09 +, Pandruvada, Srinivas escribió:
> > On Thu, 2018-04-26 at 07:42 -0500, Dennis Gilmore wrote:
> > > Hi Srinivas,
> > >
> > > El jue, 26-04-2018 a las 05:34 +, Pandruvada, Srinivas
> > > escribió:
> > > > Hi Dennis,
> > > >
> > > > On Wed, 2018-04-25 at 22:06 -0500, Dennis Gilmore wrote:
> > > > > Hi Srinivas,
> > > > >
> > > > > Yes I have latest bios, I have version 1.3.1 that was
> > > > > released
> > > > > on
> > > > > 18th
> > > > > of Feb.
> > > >
> > > > Can you try these commands and repeat the test?
> > > >
> > > > # cd /sys/kernel/debug/pmc_core/
> > > > # for i in {0..32}; do echo $i > ltr_ignore; done
> > >
> > > # for i in {0..32}; do echo $i > ltr_ignore; done
> > > -bash: ltr_ignore: Operación no permitida
>
> After some digging i figured out that the patches fedora has for
> secureboot caused the access to ltr_ignore to not work.
When you say access, you mean we don't see these debugfs attributes?
Do you know which patches caused this issue?
Do you see some non zero values here?
#cat /sys/devices/system/cpu/cpuidle/low_power_*
From the turbostat, looks like you has PC10 residency. The display is
garbled. Looks like you has 40+% residency, which is low, but may not
be across suspend/resume cycle.
You can only get the output of
sudo ./turbostat --show Package,Core,CPU,Pkg%pc2,Pkg%pc3,Pkg%pc6
Pkg%pc7,Pkg%pc8,Pkg%pc9,Pk%pc10
Thanks,
Srinivas
>
> # turbostat
> turbostat version 18.07.27 - Len Brown
> CPUID(0): GenuineIntel 22 CPUID levels; family:model:stepping
> 0x6:8e:9
> (6:142:9)
> CPUID(1): SSE3 MONITOR SMX EIST TM2 TSC MSR ACPI-TM HT TM
> CPUID(6): APERF, TURBO, DTS, PTM, HWP, HWPnotify, HWPwindow, HWPepp,
> No-HWPpkg, EPB
> cpu1: MSR_IA32_MISC_ENABLE: 0x00850089 (TCC EIST MWAIT PREFETCH
> TURBO)
> CPUID(7): SGX
> cpu1: MSR_IA32_FEATURE_CONTROL: 0xff07 (Locked )
> CPUID(0x15): eax_crystal: 2 ebx_tsc: 134 ecx_crystal_hz: 0
> TSC: 1608 MHz (2400 Hz * 134 / 2 / 100)
> CPUID(0x16): base_mhz: 1600 max_mhz: 3600 bus_mhz: 100
> cpu1: MSR_MISC_PWR_MGMT: 0x00401cc0 (ENable-EIST_Coordination
> DISable-
> EPB DISable-OOB)
> RAPL: 58254 sec. Joule Counter Range, at 4 Watts
> cpu1: MSR_PLATFORM_INFO: 0x804043df1011000
> 4 * 100.0 = 400.0 MHz max efficiency frequency
> 16 * 100.0 = 1600.0 MHz base frequency
> cpu1: MSR_IA32_POWER_CTL: 0x0024005d (C1E auto-promotion: DISabled)
> cpu1: MSR_TURBO_RATIO_LIMIT: 0x2224
> 34 * 100.0 = 3400.0 MHz max turbo 4 active cores
> 34 * 100.0 = 3400.0 MHz max turbo 3 active cores
> 34 * 100.0 = 3400.0 MHz max turbo 2 active cores
> 36 * 100.0 = 3600.0 MHz max turbo 1 active cores
> cpu1: MSR_CONFIG_TDP_NOMINAL: 0x000d (base_ratio=13)
> cpu1: MSR_CONFIG_TDP_LEVEL_1: 0x0006001c (PKG_MIN_PWR_LVL1=0
> PKG_MAX_PWR_LVL1=0 LVL1_RATIO=6 PKG_TDP_LVL1=28)
> cpu1: MSR_CONFIG_TDP_LEVEL_2: 0x00100038 (PKG_MIN_PWR_LVL2=0
> PKG_MAX_PWR_LVL2=0 LVL2_RATIO=16 PKG_TDP_LVL2=56)
> cpu1: MSR_CONFIG_TDP_CONTROL: 0x ( lock=0)
> cpu1: MSR_TURBO_ACTIVATION_RATIO: 0x000c (MAX_NON_TURBO_RATIO=12
> lock=0)
> cpu1: MSR_PKG_CST_CONFIG_CONTROL: 0x1e008008 (UNdemote-C3, UNdemote-
> C1,
> demote-C3, demote-C1, locked, pkg-cstate-limit=8 (unlimited))
> cpu1: POLL: CPUIDLE CORE POLL IDLE
> cpu1: C1: MWAIT 0x00
> cpu1: C1E: MWAIT 0x01
> cpu1: C3: MWAIT 0x10
> cpu1: C6: MWAIT 0x20
> cpu1: C7s: MWAIT 0x33
> cpu1: C8: MWAIT 0x40
> cpu1: C9: MWAIT 0x50
> cpu1: C10: MWAIT 0x60
> cpu1: cpufreq driver: intel_pstate
> cpu1: cpufreq governor: powersave
> cpufreq intel_pstate no_turbo: 0
> cpu1: MSR_MISC_FEATURE_CONTROL: 0x (L2-Prefetch L2-Prefetch-
> pair L1-Prefetch L1-IP-Prefetch)
> cpu0: MSR_PM_ENABLE: 0x0001 (HWP)
> cpu0: MSR_HWP_CAPABILITIES: 0x01070d24 (high 36 guar 13 eff 7 low 1)
> cpu0: MSR_HWP_REQUEST: 0x80002404 (min 4 max 36 des 0 epp 0x80 window
> 0x0 pkg 0x0)
> cpu0: MSR_HWP_INTERRUPT: 0x (Dis_Guaranteed_Perf_Change,
> Dis_Excursion_Min)
> cpu0: MSR_HWP_STATUS: 0x (No-Guaranteed_Perf_Change, No-
> Excursion_Min)
> cpu0: MSR_IA32_ENERGY_PERF_BIAS: 0x0006 (balanced)
> cpu0: MSR_RAPL_POWER_UNIT: 0x000a0e03 (0.125000 Watts, 0.61
> Joules,
> 0.000977 sec.)
> cpu0: MSR_PKG_POWER_INFO: 0x0024 (4 W TDP, RAPL 0 - 0 W, 0.00
> sec.)
> cpu0: MSR_PKG_POWER_LIMIT: 0x420078009c8048 (UNlocked)
> cpu0: PKG Limit #1: ENabled (9.00 Watts, 24.00 sec, clamp
> DISabled)
> cpu0: PKG Limit #2: DISabled (15.00 Watts, 0.002441* sec, clamp
> DISabled)
> cpu0: MSR_DRAM_POWER_LIMIT: 0x5400de (UNlocked)
> cpu0: DRAM Limit: DISabled (0.00 Watts, 0.000977 sec, clamp
> DISabled)
> cpu0: MSR_PP0_POLICY: 0
> cpu0: MSR_PP0_POWER_LIMIT: 0x (UNlocked)
> cpu0: Cores Limit: DISabled (0.00 Watts, 0.000977 sec, clamp
> DISabled)
> cpu0: MSR_PP1_POLICY: 0
> cpu0: MSR_PP1_POWER_LIMIT: 0x (UNlocked)
> cpu0: GFX Limit: DISabled (0.00 Watts, 0.000977 sec, clamp
> DISabled)
> cpu0: MSR_IA
RE: issues with suspend on Dell XPS 13 2-in-1
> El vie, 12-10-2018 a las 17:46 +, mario.limoncie...@dell.com
> escribió:
> > > -Original Message-
> > > From: Dennis Gilmore
> > > Sent: Friday, October 12, 2018 8:39 AM
> > > To: Pandruvada, Srinivas
> > > Cc: linux-kernel@vger.kernel.org; linux-a...@vger.kernel.org;
> > > Limonciello, Mario
> > > Subject: Re: issues with suspend on Dell XPS 13 2-in-1
> > >
> >
> > It appears I'm being added to this thread late. Can you give me some
> > more context?
> > Which XPS 2-in-1 is this (model number)? And what are the issues?
> >
> > I'm "guessing" high power consumption over S2I?
>
> Sorry we had a discussion back in April about high power consumption
> when suspending. The conversation stopped when the debugging steps did
> not work. Which turns out to be due to secure boot. I have just dealt
> with it by shutting down, but as I am currently travelling it annoyed
> me enough to try and figure out what is happening again. I have a 9635
> and esentially I get the same battery use regardless of if I suspend or
> not.
>
> Dennis
>
I see.
Can you remove those patches for now and perform those debugging steps?
>
> > >
> > > El jue, 26-04-2018 a las 15:09 +, Pandruvada, Srinivas
> > > escribió:
> > > > On Thu, 2018-04-26 at 07:42 -0500, Dennis Gilmore wrote:
> > > > > Hi Srinivas,
> > > > >
> > > > > El jue, 26-04-2018 a las 05:34 +, Pandruvada, Srinivas
> > > > > escribió:
> > > > > > Hi Dennis,
> > > > > >
> > > > > > On Wed, 2018-04-25 at 22:06 -0500, Dennis Gilmore wrote:
> > > > > > > Hi Srinivas,
> > > > > > >
> > > > > > > Yes I have latest bios, I have version 1.3.1 that was
> > > > > > > released
> > > > > > > on
> > > > > > > 18th
> > > > > > > of Feb.
> > > > > >
> > > > > > Can you try these commands and repeat the test?
> > > > > >
> > > > > > # cd /sys/kernel/debug/pmc_core/
> > > > > > # for i in {0..32}; do echo $i > ltr_ignore; done
> > > > >
> > > > > # for i in {0..32}; do echo $i > ltr_ignore; done
> > > > > -bash: ltr_ignore: Operación no permitida
> > >
> > > After some digging i figured out that the patches fedora has for
> > > secureboot caused the access to ltr_ignore to not work.
> > >
> >
> > If you are trying to debug high power consumption and those patches
> > are causing
> > problems, can you please remove those patches?
> >
> > LTR ignoring is an important debugging tactic to find problems with
> > S2I consuming
> > too much power.
> >
> > Additionally if you can read
> > /sys/kernel/debug/pmc_core/pch_ip_power_gating_status
> > That may help to point out what is wrong.
> >
> > > # turbostat
> > > turbostat version 18.07.27 - Len Brown
> > > CPUID(0): GenuineIntel 22 CPUID levels; family:model:stepping
> > > 0x6:8e:9
> > > (6:142:9)
> > > CPUID(1): SSE3 MONITOR SMX EIST TM2 TSC MSR ACPI-TM HT TM
> > > CPUID(6): APERF, TURBO, DTS, PTM, HWP, HWPnotify, HWPwindow,
> > > HWPepp,
> > > No-HWPpkg, EPB
> > > cpu1: MSR_IA32_MISC_ENABLE: 0x00850089 (TCC EIST MWAIT PREFETCH
> > > TURBO)
> > > CPUID(7): SGX
> > > cpu1: MSR_IA32_FEATURE_CONTROL: 0xff07 (Locked )
> > > CPUID(0x15): eax_crystal: 2 ebx_tsc: 134 ecx_crystal_hz: 0
> > > TSC: 1608 MHz (2400 Hz * 134 / 2 / 100)
> > > CPUID(0x16): base_mhz: 1600 max_mhz: 3600 bus_mhz: 100
> > > cpu1: MSR_MISC_PWR_MGMT: 0x00401cc0 (ENable-EIST_Coordination
> > > DISable-
> > > EPB DISable-OOB)
> > > RAPL: 58254 sec. Joule Counter Range, at 4 Watts
> > > cpu1: MSR_PLATFORM_INFO: 0x804043df1011000
> > > 4 * 100.0 = 400.0 MHz max efficiency frequency
> > > 16 * 100.0 = 1600.0 MHz base frequency
> > > cpu1: MSR_IA32_POWER_CTL: 0x0024005d (C1E auto-promotion: DISabled)
> > > cpu1: MSR_TURBO_RATIO_LIMIT: 0x2224
> > > 34 * 100.0 = 3400.0 MHz max turbo 4 active cores
> > > 34 * 100.0 = 3400.0 MHz max turbo 3 active cores
> > > 34 * 100.0 = 3400.0 MHz max turbo 2 active cores
> > > 36 * 100.0 = 3600.0 MHz max turbo 1 active cores
> > > cpu1: MSR_CONFIG_TDP_NOMINAL: 0x000d (base_ratio=13)
> > > cpu1: MSR_CONFIG_TDP_LEVEL_1: 0x0
Re: issues with suspend on Dell XPS 13 2-in-1
El vie, 12-10-2018 a las 17:46 +, mario.limoncie...@dell.com
escribió:
> > -Original Message-
> > From: Dennis Gilmore
> > Sent: Friday, October 12, 2018 8:39 AM
> > To: Pandruvada, Srinivas
> > Cc: linux-kernel@vger.kernel.org; linux-a...@vger.kernel.org;
> > Limonciello, Mario
> > Subject: Re: issues with suspend on Dell XPS 13 2-in-1
> >
>
> It appears I'm being added to this thread late. Can you give me some
> more context?
> Which XPS 2-in-1 is this (model number)? And what are the issues?
>
> I'm "guessing" high power consumption over S2I?
Sorry we had a discussion back in April about high power consumption
when suspending. The conversation stopped when the debugging steps did
not work. Which turns out to be due to secure boot. I have just dealt
with it by shutting down, but as I am currently travelling it annoyed
me enough to try and figure out what is happening again. I have a 9635
and esentially I get the same battery use regardless of if I suspend or
not.
Dennis
> >
> > El jue, 26-04-2018 a las 15:09 +, Pandruvada, Srinivas
> > escribió:
> > > On Thu, 2018-04-26 at 07:42 -0500, Dennis Gilmore wrote:
> > > > Hi Srinivas,
> > > >
> > > > El jue, 26-04-2018 a las 05:34 +, Pandruvada, Srinivas
> > > > escribió:
> > > > > Hi Dennis,
> > > > >
> > > > > On Wed, 2018-04-25 at 22:06 -0500, Dennis Gilmore wrote:
> > > > > > Hi Srinivas,
> > > > > >
> > > > > > Yes I have latest bios, I have version 1.3.1 that was
> > > > > > released
> > > > > > on
> > > > > > 18th
> > > > > > of Feb.
> > > > >
> > > > > Can you try these commands and repeat the test?
> > > > >
> > > > > # cd /sys/kernel/debug/pmc_core/
> > > > > # for i in {0..32}; do echo $i > ltr_ignore; done
> > > >
> > > > # for i in {0..32}; do echo $i > ltr_ignore; done
> > > > -bash: ltr_ignore: Operación no permitida
> >
> > After some digging i figured out that the patches fedora has for
> > secureboot caused the access to ltr_ignore to not work.
> >
>
> If you are trying to debug high power consumption and those patches
> are causing
> problems, can you please remove those patches?
>
> LTR ignoring is an important debugging tactic to find problems with
> S2I consuming
> too much power.
>
> Additionally if you can read
> /sys/kernel/debug/pmc_core/pch_ip_power_gating_status
> That may help to point out what is wrong.
>
> > # turbostat
> > turbostat version 18.07.27 - Len Brown
> > CPUID(0): GenuineIntel 22 CPUID levels; family:model:stepping
> > 0x6:8e:9
> > (6:142:9)
> > CPUID(1): SSE3 MONITOR SMX EIST TM2 TSC MSR ACPI-TM HT TM
> > CPUID(6): APERF, TURBO, DTS, PTM, HWP, HWPnotify, HWPwindow,
> > HWPepp,
> > No-HWPpkg, EPB
> > cpu1: MSR_IA32_MISC_ENABLE: 0x00850089 (TCC EIST MWAIT PREFETCH
> > TURBO)
> > CPUID(7): SGX
> > cpu1: MSR_IA32_FEATURE_CONTROL: 0xff07 (Locked )
> > CPUID(0x15): eax_crystal: 2 ebx_tsc: 134 ecx_crystal_hz: 0
> > TSC: 1608 MHz (2400 Hz * 134 / 2 / 100)
> > CPUID(0x16): base_mhz: 1600 max_mhz: 3600 bus_mhz: 100
> > cpu1: MSR_MISC_PWR_MGMT: 0x00401cc0 (ENable-EIST_Coordination
> > DISable-
> > EPB DISable-OOB)
> > RAPL: 58254 sec. Joule Counter Range, at 4 Watts
> > cpu1: MSR_PLATFORM_INFO: 0x804043df1011000
> > 4 * 100.0 = 400.0 MHz max efficiency frequency
> > 16 * 100.0 = 1600.0 MHz base frequency
> > cpu1: MSR_IA32_POWER_CTL: 0x0024005d (C1E auto-promotion: DISabled)
> > cpu1: MSR_TURBO_RATIO_LIMIT: 0x2224
> > 34 * 100.0 = 3400.0 MHz max turbo 4 active cores
> > 34 * 100.0 = 3400.0 MHz max turbo 3 active cores
> > 34 * 100.0 = 3400.0 MHz max turbo 2 active cores
> > 36 * 100.0 = 3600.0 MHz max turbo 1 active cores
> > cpu1: MSR_CONFIG_TDP_NOMINAL: 0x000d (base_ratio=13)
> > cpu1: MSR_CONFIG_TDP_LEVEL_1: 0x0006001c (PKG_MIN_PWR_LVL1=0
> > PKG_MAX_PWR_LVL1=0 LVL1_RATIO=6 PKG_TDP_LVL1=28)
> > cpu1: MSR_CONFIG_TDP_LEVEL_2: 0x00100038 (PKG_MIN_PWR_LVL2=0
> > PKG_MAX_PWR_LVL2=0 LVL2_RATIO=16 PKG_TDP_LVL2=56)
> > cpu1: MSR_CONFIG_TDP_CONTROL: 0x ( lock=0)
> > cpu1: MSR_TURBO_ACTIVATION_RATIO: 0x000c
> > (MAX_NON_TURBO_RATIO=12
> > lock=0)
> > cpu1: MSR_PKG_CST_CONFIG_CONTROL: 0x1e008008 (UNdemote-C3,
> > UNdemote-
> > C1,
> > demote-C3, demote-C1, locked, pkg-cstate-limit=8 (unlimited))
> > c
RE: issues with suspend on Dell XPS 13 2-in-1
> -Original Message-
> From: Dennis Gilmore
> Sent: Friday, October 12, 2018 8:39 AM
> To: Pandruvada, Srinivas
> Cc: linux-kernel@vger.kernel.org; linux-a...@vger.kernel.org; Limonciello,
> Mario
> Subject: Re: issues with suspend on Dell XPS 13 2-in-1
>
It appears I'm being added to this thread late. Can you give me some more
context?
Which XPS 2-in-1 is this (model number)? And what are the issues?
I'm "guessing" high power consumption over S2I?
>
>
> El jue, 26-04-2018 a las 15:09 +, Pandruvada, Srinivas escribió:
> > On Thu, 2018-04-26 at 07:42 -0500, Dennis Gilmore wrote:
> > > Hi Srinivas,
> > >
> > > El jue, 26-04-2018 a las 05:34 +, Pandruvada, Srinivas
> > > escribió:
> > > > Hi Dennis,
> > > >
> > > > On Wed, 2018-04-25 at 22:06 -0500, Dennis Gilmore wrote:
> > > > > Hi Srinivas,
> > > > >
> > > > > Yes I have latest bios, I have version 1.3.1 that was released
> > > > > on
> > > > > 18th
> > > > > of Feb.
> > > >
> > > > Can you try these commands and repeat the test?
> > > >
> > > > # cd /sys/kernel/debug/pmc_core/
> > > > # for i in {0..32}; do echo $i > ltr_ignore; done
> > >
> > > # for i in {0..32}; do echo $i > ltr_ignore; done
> > > -bash: ltr_ignore: Operación no permitida
>
> After some digging i figured out that the patches fedora has for
> secureboot caused the access to ltr_ignore to not work.
>
If you are trying to debug high power consumption and those patches are causing
problems, can you please remove those patches?
LTR ignoring is an important debugging tactic to find problems with S2I
consuming
too much power.
Additionally if you can read
/sys/kernel/debug/pmc_core/pch_ip_power_gating_status
That may help to point out what is wrong.
> # turbostat
> turbostat version 18.07.27 - Len Brown
> CPUID(0): GenuineIntel 22 CPUID levels; family:model:stepping 0x6:8e:9
> (6:142:9)
> CPUID(1): SSE3 MONITOR SMX EIST TM2 TSC MSR ACPI-TM HT TM
> CPUID(6): APERF, TURBO, DTS, PTM, HWP, HWPnotify, HWPwindow, HWPepp,
> No-HWPpkg, EPB
> cpu1: MSR_IA32_MISC_ENABLE: 0x00850089 (TCC EIST MWAIT PREFETCH TURBO)
> CPUID(7): SGX
> cpu1: MSR_IA32_FEATURE_CONTROL: 0xff07 (Locked )
> CPUID(0x15): eax_crystal: 2 ebx_tsc: 134 ecx_crystal_hz: 0
> TSC: 1608 MHz (2400 Hz * 134 / 2 / 100)
> CPUID(0x16): base_mhz: 1600 max_mhz: 3600 bus_mhz: 100
> cpu1: MSR_MISC_PWR_MGMT: 0x00401cc0 (ENable-EIST_Coordination DISable-
> EPB DISable-OOB)
> RAPL: 58254 sec. Joule Counter Range, at 4 Watts
> cpu1: MSR_PLATFORM_INFO: 0x804043df1011000
> 4 * 100.0 = 400.0 MHz max efficiency frequency
> 16 * 100.0 = 1600.0 MHz base frequency
> cpu1: MSR_IA32_POWER_CTL: 0x0024005d (C1E auto-promotion: DISabled)
> cpu1: MSR_TURBO_RATIO_LIMIT: 0x2224
> 34 * 100.0 = 3400.0 MHz max turbo 4 active cores
> 34 * 100.0 = 3400.0 MHz max turbo 3 active cores
> 34 * 100.0 = 3400.0 MHz max turbo 2 active cores
> 36 * 100.0 = 3600.0 MHz max turbo 1 active cores
> cpu1: MSR_CONFIG_TDP_NOMINAL: 0x000d (base_ratio=13)
> cpu1: MSR_CONFIG_TDP_LEVEL_1: 0x0006001c (PKG_MIN_PWR_LVL1=0
> PKG_MAX_PWR_LVL1=0 LVL1_RATIO=6 PKG_TDP_LVL1=28)
> cpu1: MSR_CONFIG_TDP_LEVEL_2: 0x00100038 (PKG_MIN_PWR_LVL2=0
> PKG_MAX_PWR_LVL2=0 LVL2_RATIO=16 PKG_TDP_LVL2=56)
> cpu1: MSR_CONFIG_TDP_CONTROL: 0x ( lock=0)
> cpu1: MSR_TURBO_ACTIVATION_RATIO: 0x000c
> (MAX_NON_TURBO_RATIO=12
> lock=0)
> cpu1: MSR_PKG_CST_CONFIG_CONTROL: 0x1e008008 (UNdemote-C3, UNdemote-
> C1,
> demote-C3, demote-C1, locked, pkg-cstate-limit=8 (unlimited))
> cpu1: POLL: CPUIDLE CORE POLL IDLE
> cpu1: C1: MWAIT 0x00
> cpu1: C1E: MWAIT 0x01
> cpu1: C3: MWAIT 0x10
> cpu1: C6: MWAIT 0x20
> cpu1: C7s: MWAIT 0x33
> cpu1: C8: MWAIT 0x40
> cpu1: C9: MWAIT 0x50
> cpu1: C10: MWAIT 0x60
> cpu1: cpufreq driver: intel_pstate
> cpu1: cpufreq governor: powersave
> cpufreq intel_pstate no_turbo: 0
> cpu1: MSR_MISC_FEATURE_CONTROL: 0x (L2-Prefetch L2-Prefetch-
> pair L1-Prefetch L1-IP-Prefetch)
> cpu0: MSR_PM_ENABLE: 0x0001 (HWP)
> cpu0: MSR_HWP_CAPABILITIES: 0x01070d24 (high 36 guar 13 eff 7 low 1)
> cpu0: MSR_HWP_REQUEST: 0x80002404 (min 4 max 36 des 0 epp 0x80 window
> 0x0 pkg 0x0)
> cpu0: MSR_HWP_INTERRUPT: 0x (Dis_Guaranteed_Perf_Change,
> Dis_Excursion_Min)
> cpu0: MSR_HWP_STATUS: 0x (No-Guaranteed_Perf_Change, No-
> Excursion_Min)
> cpu0: MSR_IA32_ENERGY_PERF_BIAS: 0x0006 (balanced)
> cpu0: MSR_RAPL_POWER_UNIT: 0x000a0e03 (0.125000 Watts, 0.61 Joules,
> 0.000977 sec.)
> cpu0: MSR_PKG_POWER_INFO: 0x00
Re: issues with suspend on Dell XPS 13 2-in-1
El jue, 26-04-2018 a las 15:09 +, Pandruvada, Srinivas escribió:
> On Thu, 2018-04-26 at 07:42 -0500, Dennis Gilmore wrote:
> > Hi Srinivas,
> >
> > El jue, 26-04-2018 a las 05:34 +, Pandruvada, Srinivas
> > escribió:
> > > Hi Dennis,
> > >
> > > On Wed, 2018-04-25 at 22:06 -0500, Dennis Gilmore wrote:
> > > > Hi Srinivas,
> > > >
> > > > Yes I have latest bios, I have version 1.3.1 that was released
> > > > on
> > > > 18th
> > > > of Feb.
> > >
> > > Can you try these commands and repeat the test?
> > >
> > > # cd /sys/kernel/debug/pmc_core/
> > > # for i in {0..32}; do echo $i > ltr_ignore; done
> >
> > # for i in {0..32}; do echo $i > ltr_ignore; done
> > -bash: ltr_ignore: Operación no permitida
After some digging i figured out that the patches fedora has for
secureboot caused the access to ltr_ignore to not work.
# turbostat
turbostat version 18.07.27 - Len Brown
CPUID(0): GenuineIntel 22 CPUID levels; family:model:stepping 0x6:8e:9
(6:142:9)
CPUID(1): SSE3 MONITOR SMX EIST TM2 TSC MSR ACPI-TM HT TM
CPUID(6): APERF, TURBO, DTS, PTM, HWP, HWPnotify, HWPwindow, HWPepp,
No-HWPpkg, EPB
cpu1: MSR_IA32_MISC_ENABLE: 0x00850089 (TCC EIST MWAIT PREFETCH TURBO)
CPUID(7): SGX
cpu1: MSR_IA32_FEATURE_CONTROL: 0xff07 (Locked )
CPUID(0x15): eax_crystal: 2 ebx_tsc: 134 ecx_crystal_hz: 0
TSC: 1608 MHz (2400 Hz * 134 / 2 / 100)
CPUID(0x16): base_mhz: 1600 max_mhz: 3600 bus_mhz: 100
cpu1: MSR_MISC_PWR_MGMT: 0x00401cc0 (ENable-EIST_Coordination DISable-
EPB DISable-OOB)
RAPL: 58254 sec. Joule Counter Range, at 4 Watts
cpu1: MSR_PLATFORM_INFO: 0x804043df1011000
4 * 100.0 = 400.0 MHz max efficiency frequency
16 * 100.0 = 1600.0 MHz base frequency
cpu1: MSR_IA32_POWER_CTL: 0x0024005d (C1E auto-promotion: DISabled)
cpu1: MSR_TURBO_RATIO_LIMIT: 0x2224
34 * 100.0 = 3400.0 MHz max turbo 4 active cores
34 * 100.0 = 3400.0 MHz max turbo 3 active cores
34 * 100.0 = 3400.0 MHz max turbo 2 active cores
36 * 100.0 = 3600.0 MHz max turbo 1 active cores
cpu1: MSR_CONFIG_TDP_NOMINAL: 0x000d (base_ratio=13)
cpu1: MSR_CONFIG_TDP_LEVEL_1: 0x0006001c (PKG_MIN_PWR_LVL1=0
PKG_MAX_PWR_LVL1=0 LVL1_RATIO=6 PKG_TDP_LVL1=28)
cpu1: MSR_CONFIG_TDP_LEVEL_2: 0x00100038 (PKG_MIN_PWR_LVL2=0
PKG_MAX_PWR_LVL2=0 LVL2_RATIO=16 PKG_TDP_LVL2=56)
cpu1: MSR_CONFIG_TDP_CONTROL: 0x ( lock=0)
cpu1: MSR_TURBO_ACTIVATION_RATIO: 0x000c (MAX_NON_TURBO_RATIO=12
lock=0)
cpu1: MSR_PKG_CST_CONFIG_CONTROL: 0x1e008008 (UNdemote-C3, UNdemote-C1,
demote-C3, demote-C1, locked, pkg-cstate-limit=8 (unlimited))
cpu1: POLL: CPUIDLE CORE POLL IDLE
cpu1: C1: MWAIT 0x00
cpu1: C1E: MWAIT 0x01
cpu1: C3: MWAIT 0x10
cpu1: C6: MWAIT 0x20
cpu1: C7s: MWAIT 0x33
cpu1: C8: MWAIT 0x40
cpu1: C9: MWAIT 0x50
cpu1: C10: MWAIT 0x60
cpu1: cpufreq driver: intel_pstate
cpu1: cpufreq governor: powersave
cpufreq intel_pstate no_turbo: 0
cpu1: MSR_MISC_FEATURE_CONTROL: 0x (L2-Prefetch L2-Prefetch-
pair L1-Prefetch L1-IP-Prefetch)
cpu0: MSR_PM_ENABLE: 0x0001 (HWP)
cpu0: MSR_HWP_CAPABILITIES: 0x01070d24 (high 36 guar 13 eff 7 low 1)
cpu0: MSR_HWP_REQUEST: 0x80002404 (min 4 max 36 des 0 epp 0x80 window
0x0 pkg 0x0)
cpu0: MSR_HWP_INTERRUPT: 0x (Dis_Guaranteed_Perf_Change,
Dis_Excursion_Min)
cpu0: MSR_HWP_STATUS: 0x (No-Guaranteed_Perf_Change, No-
Excursion_Min)
cpu0: MSR_IA32_ENERGY_PERF_BIAS: 0x0006 (balanced)
cpu0: MSR_RAPL_POWER_UNIT: 0x000a0e03 (0.125000 Watts, 0.61 Joules,
0.000977 sec.)
cpu0: MSR_PKG_POWER_INFO: 0x0024 (4 W TDP, RAPL 0 - 0 W, 0.00
sec.)
cpu0: MSR_PKG_POWER_LIMIT: 0x420078009c8048 (UNlocked)
cpu0: PKG Limit #1: ENabled (9.00 Watts, 24.00 sec, clamp
DISabled)
cpu0: PKG Limit #2: DISabled (15.00 Watts, 0.002441* sec, clamp
DISabled)
cpu0: MSR_DRAM_POWER_LIMIT: 0x5400de (UNlocked)
cpu0: DRAM Limit: DISabled (0.00 Watts, 0.000977 sec, clamp
DISabled)
cpu0: MSR_PP0_POLICY: 0
cpu0: MSR_PP0_POWER_LIMIT: 0x (UNlocked)
cpu0: Cores Limit: DISabled (0.00 Watts, 0.000977 sec, clamp
DISabled)
cpu0: MSR_PP1_POLICY: 0
cpu0: MSR_PP1_POWER_LIMIT: 0x (UNlocked)
cpu0: GFX Limit: DISabled (0.00 Watts, 0.000977 sec, clamp
DISabled)
cpu0: MSR_IA32_TEMPERATURE_TARGET: 0x0a640080 (100 C)
cpu0: MSR_IA32_PACKAGE_THERM_STATUS: 0x882e0808 (54 C)
cpu0: MSR_IA32_PACKAGE_THERM_INTERRUPT: 0x0003 (100 C, 100 C)
cpu1: MSR_PKGC3_IRTL: 0x884e (valid, 79872 ns)
cpu1: MSR_PKGC6_IRTL: 0x8876 (valid, 120832 ns)
cpu1: MSR_PKGC7_IRTL: 0x8894 (valid, 151552 ns)
cpu1: MSR_PKGC8_IRTL: 0x88fa (valid, 256000 ns)
cpu1: MSR_PKGC9_IRTL: 0x894c (valid, 339968 ns)
cpu1: MSR_PKGC10_IRTL: 0x8bf2 (valid, 1034240 ns)
CoreCPU Avg_MHz Busy% Bzy_MHz TSC_MHz IRQ SMI POLL
C1 C1E C3 C6 C7s C8 C9 C10 POLL%
C1% C1E%C3% C6% C7s%C8% C9% C10%CPU%c1
CPU%c3 CPU%c6 CPU%c7 CoreTmp PkgTmp GFX%rc6 GFXMHz Totl%C0 Any%C0
GFX%C0 CPUGFX% Pkg%pc2 Pkg%pc3 Pkg%pc6 Pkg%pc7 Pkg%pc8 Pkg%pc9 Pk%pc
Re: issues with suspend on Dell XPS 13 2-in-1
El jue, 26-04-2018 a las 15:09 +, Pandruvada, Srinivas escribió:
> On Thu, 2018-04-26 at 07:42 -0500, Dennis Gilmore wrote:
> > Hi Srinivas,
> >
> > El jue, 26-04-2018 a las 05:34 +, Pandruvada, Srinivas
> > escribió:
> > > Hi Dennis,
> > >
> > > On Wed, 2018-04-25 at 22:06 -0500, Dennis Gilmore wrote:
> > > > Hi Srinivas,
> > > >
> > > > Yes I have latest bios, I have version 1.3.1 that was released
> > > > on
> > > > 18th
> > > > of Feb.
> > >
> > > Can you try these commands and repeat the test?
> > >
> > > # cd /sys/kernel/debug/pmc_core/
> > > # for i in {0..32}; do echo $i > ltr_ignore; done
> >
> > # for i in {0..32}; do echo $i > ltr_ignore; done
> > -bash: ltr_ignore: Operación no permitida
> > -bash: ltr_ignore: Operación no permitida
> > -bash: ltr_ignore: Operación no permitida
> > -bash: ltr_ignore: Operación no permitida
> > -bash: ltr_ignore: Operación no permitida
> > -bash: ltr_ignore: Operación no permitida
> > -bash: ltr_ignore: Operación no permitida
> > -bash: ltr_ignore: Operación no permitida
> > -bash: ltr_ignore: Operación no permitida
> > -bash: ltr_ignore: Operación no permitida
> > -bash: ltr_ignore: Operación no permitida
> > -bash: ltr_ignore: Operación no permitida
> > -bash: ltr_ignore: Operación no permitida
> > -bash: ltr_ignore: Operación no permitida
> > -bash: ltr_ignore: Operación no permitida
> > -bash: ltr_ignore: Operación no permitida
> > -bash: ltr_ignore: Operación no permitida
> > -bash: ltr_ignore: Operación no permitida
> > -bash: ltr_ignore: Operación no permitida
> > -bash: ltr_ignore: Operación no permitida
> > -bash: ltr_ignore: Operación no permitida
> > -bash: ltr_ignore: Operación no permitida
> > -bash: ltr_ignore: Operación no permitida
> > -bash: ltr_ignore: Operación no permitida
> > -bash: ltr_ignore: Operación no permitida
> > -bash: ltr_ignore: Operación no permitida
> > -bash: ltr_ignore: Operación no permitida
> > -bash: ltr_ignore: Operación no permitida
> > -bash: ltr_ignore: Operación no permitida
> > -bash: ltr_ignore: Operación no permitida
> > -bash: ltr_ignore: Operación no permitida
> > -bash: ltr_ignore: Operación no permitida
> > -bash: ltr_ignore: Operación no permitida
> >
> > should I go ahead and run the test even though writing to
> > ltr_ignore
> > failed?
>
> Strange. Do you have any issue with the permissions?
> # cd /sys/kernel/debug/pmc_core/
> # ls -l
# ls -l
total 0
-rw-r--r--. 1 root root 0 abr 24 17:27 ltr_ignore
-r--r--r--. 1 root root 0 abr 24 17:27
mphy_core_lanes_power_gating_status
-r--r--r--. 1 root root 0 abr 24 17:27 pch_ip_power_gating_status
-r--r--r--. 1 root root 0 abr 24 17:27 pll_status
-r--r--r--. 1 root root 0 abr 24 17:27 slp_s0_residency_usec
I have rw permissions selinux is in permissive mode currently
Thanks
Dennis
> Do you have rw permissions?
>
> Thanks,
> Srinivas
>
> >
> > Dennis
> >
> > > Thanks,
> > > Srinivas
> > >
> > > >
> > > > Dennis
> > > >
> > > > El jue, 26-04-2018 a las 02:13 +, Pandruvada, Srinivas
> > > > escribió:
> > > > >
> > > > > I see around 43% PC10 residency with power drop of 0.7W.
> > > > > Do you have the latest BIOS of Dell 9365?
> > > > >
> > > > >
> > > > > Thanks,
> > > > > Srinivas
> > > > >
> > > > > On Fri, 2018-04-20 at 08:36 -0500, Dennis Gilmore wrote:
> > > > > > Here is the full output
> > > > > >
> > > > > > # turbostat
> > > > > > turbostat version 17.06.23 - Len Brown
> > > > > > CPUID(0): GenuineIntel 22 CPUID levels;
> > > > > > family:model:stepping
> > > > > > 0x6:8e:9 (6:142:9)
> > > > > > CPUID(1): SSE3 MONITOR SMX EIST TM2 TSC MSR ACPI-TM TM
> > > > > > CPUID(6): APERF, TURBO, DTS, PTM, HWP, HWPnotify,
> > > > > > HWPwindow,
> > > > > > HWPepp, No-HWPpkg, EPB
> > > > > > cpu0: MSR_IA32_MISC_ENABLE: 0x00850089 (TCC EIST No-MWAIT
> > > > > > PREFETCH
> > > > > > TURBO)
> > > > > > CPUID(7): SGX
> > > > > > cpu0: MSR_IA32_FEATURE_CONTROL: 0xff07 (Locked )
> > > > > > CPUID(0x15): eax_crystal: 2 ebx_tsc: 134 ecx_crystal_hz: 0
> > > > > > TSC: 1608 MHz (2400 Hz * 134 / 2 / 100)
> > > > > > CPUID(0x16): base_mhz: 1600 max_mhz: 3600 bus_mhz: 100
> > > > > > cpu0: MSR_MISC_PWR_MGMT: 0x00401cc0 (ENable-
> > > > > > EIST_Coordination
> > > > > > DISable-EPB DISable-OOB)
> > > > > > RAPL: 58254 sec. Joule Counter Range, at 4 Watts
> > > > > > cpu0: MSR_PLATFORM_INFO: 0x804043df1011000
> > > > > > 4 * 100.0 = 400.0 MHz max efficiency frequency
> > > > > > 16 * 100.0 = 1600.0 MHz base frequency
> > > > > > cpu0: MSR_IA32_POWER_CTL: 0x0024005d (C1E auto-promotion:
> > > > > > DISabled)
> > > > > > cpu0: MSR_TURBO_RATIO_LIMIT: 0x2224
> > > > > > 34 * 100.0 = 3400.0 MHz max turbo 4 active cores
> > > > > > 34 * 100.0 = 3400.0 MHz max turbo 3 active cores
> > > > > > 34 * 100.0 = 3400.0 MHz max turbo 2 active cores
> > > > > > 36 * 100.0 = 3600.0 MHz max turbo 1 active cores
> > > > > > cpu0: MSR_CONFIG_TDP_NOMINAL: 0x000d (base_ratio=13)
> > > > > > cpu0: MSR_CONFIG_TDP_LEVEL_1: 0x0006001c
> > > > > > (PKG_M
Re: issues with suspend on Dell XPS 13 2-in-1
On Thu, 2018-04-26 at 07:42 -0500, Dennis Gilmore wrote:
> Hi Srinivas,
>
> El jue, 26-04-2018 a las 05:34 +, Pandruvada, Srinivas escribió:
> > Hi Dennis,
> >
> > On Wed, 2018-04-25 at 22:06 -0500, Dennis Gilmore wrote:
> > > Hi Srinivas,
> > >
> > > Yes I have latest bios, I have version 1.3.1 that was released on
> > > 18th
> > > of Feb.
> >
> > Can you try these commands and repeat the test?
> >
> > # cd /sys/kernel/debug/pmc_core/
> > # for i in {0..32}; do echo $i > ltr_ignore; done
>
> # for i in {0..32}; do echo $i > ltr_ignore; done
> -bash: ltr_ignore: Operación no permitida
> -bash: ltr_ignore: Operación no permitida
> -bash: ltr_ignore: Operación no permitida
> -bash: ltr_ignore: Operación no permitida
> -bash: ltr_ignore: Operación no permitida
> -bash: ltr_ignore: Operación no permitida
> -bash: ltr_ignore: Operación no permitida
> -bash: ltr_ignore: Operación no permitida
> -bash: ltr_ignore: Operación no permitida
> -bash: ltr_ignore: Operación no permitida
> -bash: ltr_ignore: Operación no permitida
> -bash: ltr_ignore: Operación no permitida
> -bash: ltr_ignore: Operación no permitida
> -bash: ltr_ignore: Operación no permitida
> -bash: ltr_ignore: Operación no permitida
> -bash: ltr_ignore: Operación no permitida
> -bash: ltr_ignore: Operación no permitida
> -bash: ltr_ignore: Operación no permitida
> -bash: ltr_ignore: Operación no permitida
> -bash: ltr_ignore: Operación no permitida
> -bash: ltr_ignore: Operación no permitida
> -bash: ltr_ignore: Operación no permitida
> -bash: ltr_ignore: Operación no permitida
> -bash: ltr_ignore: Operación no permitida
> -bash: ltr_ignore: Operación no permitida
> -bash: ltr_ignore: Operación no permitida
> -bash: ltr_ignore: Operación no permitida
> -bash: ltr_ignore: Operación no permitida
> -bash: ltr_ignore: Operación no permitida
> -bash: ltr_ignore: Operación no permitida
> -bash: ltr_ignore: Operación no permitida
> -bash: ltr_ignore: Operación no permitida
> -bash: ltr_ignore: Operación no permitida
>
> should I go ahead and run the test even though writing to ltr_ignore
> failed?
Strange. Do you have any issue with the permissions?
# cd /sys/kernel/debug/pmc_core/
# ls -l
Do you have rw permissions?
Thanks,
Srinivas
>
> Dennis
>
> > Thanks,
> > Srinivas
> >
> > >
> > > Dennis
> > >
> > > El jue, 26-04-2018 a las 02:13 +, Pandruvada, Srinivas
> > > escribió:
> > > >
> > > > I see around 43% PC10 residency with power drop of 0.7W.
> > > > Do you have the latest BIOS of Dell 9365?
> > > >
> > > >
> > > > Thanks,
> > > > Srinivas
> > > >
> > > > On Fri, 2018-04-20 at 08:36 -0500, Dennis Gilmore wrote:
> > > > > Here is the full output
> > > > >
> > > > > # turbostat
> > > > > turbostat version 17.06.23 - Len Brown
> > > > > CPUID(0): GenuineIntel 22 CPUID levels; family:model:stepping
> > > > > 0x6:8e:9 (6:142:9)
> > > > > CPUID(1): SSE3 MONITOR SMX EIST TM2 TSC MSR ACPI-TM TM
> > > > > CPUID(6): APERF, TURBO, DTS, PTM, HWP, HWPnotify, HWPwindow,
> > > > > HWPepp, No-HWPpkg, EPB
> > > > > cpu0: MSR_IA32_MISC_ENABLE: 0x00850089 (TCC EIST No-MWAIT
> > > > > PREFETCH
> > > > > TURBO)
> > > > > CPUID(7): SGX
> > > > > cpu0: MSR_IA32_FEATURE_CONTROL: 0xff07 (Locked )
> > > > > CPUID(0x15): eax_crystal: 2 ebx_tsc: 134 ecx_crystal_hz: 0
> > > > > TSC: 1608 MHz (2400 Hz * 134 / 2 / 100)
> > > > > CPUID(0x16): base_mhz: 1600 max_mhz: 3600 bus_mhz: 100
> > > > > cpu0: MSR_MISC_PWR_MGMT: 0x00401cc0 (ENable-EIST_Coordination
> > > > > DISable-EPB DISable-OOB)
> > > > > RAPL: 58254 sec. Joule Counter Range, at 4 Watts
> > > > > cpu0: MSR_PLATFORM_INFO: 0x804043df1011000
> > > > > 4 * 100.0 = 400.0 MHz max efficiency frequency
> > > > > 16 * 100.0 = 1600.0 MHz base frequency
> > > > > cpu0: MSR_IA32_POWER_CTL: 0x0024005d (C1E auto-promotion:
> > > > > DISabled)
> > > > > cpu0: MSR_TURBO_RATIO_LIMIT: 0x2224
> > > > > 34 * 100.0 = 3400.0 MHz max turbo 4 active cores
> > > > > 34 * 100.0 = 3400.0 MHz max turbo 3 active cores
> > > > > 34 * 100.0 = 3400.0 MHz max turbo 2 active cores
> > > > > 36 * 100.0 = 3600.0 MHz max turbo 1 active cores
> > > > > cpu0: MSR_CONFIG_TDP_NOMINAL: 0x000d (base_ratio=13)
> > > > > cpu0: MSR_CONFIG_TDP_LEVEL_1: 0x0006001c (PKG_MIN_PWR_LVL1=0
> > > > > PKG_MAX_PWR_LVL1=0 LVL1_RATIO=6 PKG_TDP_LVL1=28)
> > > > > cpu0: MSR_CONFIG_TDP_LEVEL_2: 0x00100038 (PKG_MIN_PWR_LVL2=0
> > > > > PKG_MAX_PWR_LVL2=0 LVL2_RATIO=16 PKG_TDP_LVL2=56)
> > > > > cpu0: MSR_CONFIG_TDP_CONTROL: 0x ( lock=0)
> > > > > cpu0: MSR_TURBO_ACTIVATION_RATIO: 0x000c
> > > > > (MAX_NON_TURBO_RATIO=12 lock=0)
> > > > > cpu0: MSR_PKG_CST_CONFIG_CONTROL: 0x1e008008 (UNdemote-C3,
> > > > > UNdemote-C1, demote-C3, demote-C1, locked: pkg-cstate-
> > > > > limit=8:
> > > > > unlimited)
> > > > > cpu0: POLL: CPUIDLE CORE POLL IDLE
> > > > > cpu0: C1: MWAIT 0x00
> > > > > cpu0: C1E: MWAIT 0x01
> > > > > cpu0: C3: MWAIT 0x10
> > > > > cpu0: C6: MWAIT 0x20
> > > > > cpu0: C7s: MWAIT 0x33
> > > > > cpu0: C8: MWAIT 0x
Re: issues with suspend on Dell XPS 13 2-in-1
Hi Srinivas,
El jue, 26-04-2018 a las 05:34 +, Pandruvada, Srinivas escribió:
> Hi Dennis,
>
> On Wed, 2018-04-25 at 22:06 -0500, Dennis Gilmore wrote:
> > Hi Srinivas,
> >
> > Yes I have latest bios, I have version 1.3.1 that was released on
> > 18th
> > of Feb.
>
> Can you try these commands and repeat the test?
>
> # cd /sys/kernel/debug/pmc_core/
> # for i in {0..32}; do echo $i > ltr_ignore; done
# for i in {0..32}; do echo $i > ltr_ignore; done
-bash: ltr_ignore: Operación no permitida
-bash: ltr_ignore: Operación no permitida
-bash: ltr_ignore: Operación no permitida
-bash: ltr_ignore: Operación no permitida
-bash: ltr_ignore: Operación no permitida
-bash: ltr_ignore: Operación no permitida
-bash: ltr_ignore: Operación no permitida
-bash: ltr_ignore: Operación no permitida
-bash: ltr_ignore: Operación no permitida
-bash: ltr_ignore: Operación no permitida
-bash: ltr_ignore: Operación no permitida
-bash: ltr_ignore: Operación no permitida
-bash: ltr_ignore: Operación no permitida
-bash: ltr_ignore: Operación no permitida
-bash: ltr_ignore: Operación no permitida
-bash: ltr_ignore: Operación no permitida
-bash: ltr_ignore: Operación no permitida
-bash: ltr_ignore: Operación no permitida
-bash: ltr_ignore: Operación no permitida
-bash: ltr_ignore: Operación no permitida
-bash: ltr_ignore: Operación no permitida
-bash: ltr_ignore: Operación no permitida
-bash: ltr_ignore: Operación no permitida
-bash: ltr_ignore: Operación no permitida
-bash: ltr_ignore: Operación no permitida
-bash: ltr_ignore: Operación no permitida
-bash: ltr_ignore: Operación no permitida
-bash: ltr_ignore: Operación no permitida
-bash: ltr_ignore: Operación no permitida
-bash: ltr_ignore: Operación no permitida
-bash: ltr_ignore: Operación no permitida
-bash: ltr_ignore: Operación no permitida
-bash: ltr_ignore: Operación no permitida
should I go ahead and run the test even though writing to ltr_ignore
failed?
Dennis
> Thanks,
> Srinivas
>
> >
> > Dennis
> >
> > El jue, 26-04-2018 a las 02:13 +, Pandruvada, Srinivas
> > escribió:
> > >
> > > I see around 43% PC10 residency with power drop of 0.7W.
> > > Do you have the latest BIOS of Dell 9365?
> > >
> > >
> > > Thanks,
> > > Srinivas
> > >
> > > On Fri, 2018-04-20 at 08:36 -0500, Dennis Gilmore wrote:
> > > > Here is the full output
> > > >
> > > > # turbostat
> > > > turbostat version 17.06.23 - Len Brown
> > > > CPUID(0): GenuineIntel 22 CPUID levels; family:model:stepping
> > > > 0x6:8e:9 (6:142:9)
> > > > CPUID(1): SSE3 MONITOR SMX EIST TM2 TSC MSR ACPI-TM TM
> > > > CPUID(6): APERF, TURBO, DTS, PTM, HWP, HWPnotify, HWPwindow,
> > > > HWPepp, No-HWPpkg, EPB
> > > > cpu0: MSR_IA32_MISC_ENABLE: 0x00850089 (TCC EIST No-MWAIT
> > > > PREFETCH
> > > > TURBO)
> > > > CPUID(7): SGX
> > > > cpu0: MSR_IA32_FEATURE_CONTROL: 0xff07 (Locked )
> > > > CPUID(0x15): eax_crystal: 2 ebx_tsc: 134 ecx_crystal_hz: 0
> > > > TSC: 1608 MHz (2400 Hz * 134 / 2 / 100)
> > > > CPUID(0x16): base_mhz: 1600 max_mhz: 3600 bus_mhz: 100
> > > > cpu0: MSR_MISC_PWR_MGMT: 0x00401cc0 (ENable-EIST_Coordination
> > > > DISable-EPB DISable-OOB)
> > > > RAPL: 58254 sec. Joule Counter Range, at 4 Watts
> > > > cpu0: MSR_PLATFORM_INFO: 0x804043df1011000
> > > > 4 * 100.0 = 400.0 MHz max efficiency frequency
> > > > 16 * 100.0 = 1600.0 MHz base frequency
> > > > cpu0: MSR_IA32_POWER_CTL: 0x0024005d (C1E auto-promotion:
> > > > DISabled)
> > > > cpu0: MSR_TURBO_RATIO_LIMIT: 0x2224
> > > > 34 * 100.0 = 3400.0 MHz max turbo 4 active cores
> > > > 34 * 100.0 = 3400.0 MHz max turbo 3 active cores
> > > > 34 * 100.0 = 3400.0 MHz max turbo 2 active cores
> > > > 36 * 100.0 = 3600.0 MHz max turbo 1 active cores
> > > > cpu0: MSR_CONFIG_TDP_NOMINAL: 0x000d (base_ratio=13)
> > > > cpu0: MSR_CONFIG_TDP_LEVEL_1: 0x0006001c (PKG_MIN_PWR_LVL1=0
> > > > PKG_MAX_PWR_LVL1=0 LVL1_RATIO=6 PKG_TDP_LVL1=28)
> > > > cpu0: MSR_CONFIG_TDP_LEVEL_2: 0x00100038 (PKG_MIN_PWR_LVL2=0
> > > > PKG_MAX_PWR_LVL2=0 LVL2_RATIO=16 PKG_TDP_LVL2=56)
> > > > cpu0: MSR_CONFIG_TDP_CONTROL: 0x ( lock=0)
> > > > cpu0: MSR_TURBO_ACTIVATION_RATIO: 0x000c
> > > > (MAX_NON_TURBO_RATIO=12 lock=0)
> > > > cpu0: MSR_PKG_CST_CONFIG_CONTROL: 0x1e008008 (UNdemote-C3,
> > > > UNdemote-C1, demote-C3, demote-C1, locked: pkg-cstate-limit=8:
> > > > unlimited)
> > > > cpu0: POLL: CPUIDLE CORE POLL IDLE
> > > > cpu0: C1: MWAIT 0x00
> > > > cpu0: C1E: MWAIT 0x01
> > > > cpu0: C3: MWAIT 0x10
> > > > cpu0: C6: MWAIT 0x20
> > > > cpu0: C7s: MWAIT 0x33
> > > > cpu0: C8: MWAIT 0x40
> > > > cpu0: C9: MWAIT 0x50
> > > > cpu0: C10: MWAIT 0x60
> > > > cpu0: cpufreq driver: intel_pstate
> > > > cpu0: cpufreq governor: powersave
> > > > cpufreq intel_pstate no_turbo: 0
> > > > cpu0: MSR_MISC_FEATURE_CONTROL: 0x (L2-Prefetch L2-
> > > > Prefetch-pair L1-Prefetch L1-IP-Prefetch)
> > > > cpu0: MSR_PM_ENABLE: 0x0001 (HWP)
> > > > cpu0: MSR_HWP_CAPABILITIES: 0x01060d24 (high 36 guar 13 eff 6
> > > > low
> > > > 1)
> > > > c
Re: issues with suspend on Dell XPS 13 2-in-1
Hi Dennis,
On Wed, 2018-04-25 at 22:06 -0500, Dennis Gilmore wrote:
> Hi Srinivas,
>
> Yes I have latest bios, I have version 1.3.1 that was released on
> 18th
> of Feb.
Can you try these commands and repeat the test?
# cd /sys/kernel/debug/pmc_core/
# for i in {0..32}; do echo $i > ltr_ignore; done
Thanks,
Srinivas
>
> Dennis
>
> El jue, 26-04-2018 a las 02:13 +, Pandruvada, Srinivas escribió:
> >
> > I see around 43% PC10 residency with power drop of 0.7W.
> > Do you have the latest BIOS of Dell 9365?
> >
> >
> > Thanks,
> > Srinivas
> >
> > On Fri, 2018-04-20 at 08:36 -0500, Dennis Gilmore wrote:
> > > Here is the full output
> > >
> > > # turbostat
> > > turbostat version 17.06.23 - Len Brown
> > > CPUID(0): GenuineIntel 22 CPUID levels; family:model:stepping
> > > 0x6:8e:9 (6:142:9)
> > > CPUID(1): SSE3 MONITOR SMX EIST TM2 TSC MSR ACPI-TM TM
> > > CPUID(6): APERF, TURBO, DTS, PTM, HWP, HWPnotify, HWPwindow,
> > > HWPepp, No-HWPpkg, EPB
> > > cpu0: MSR_IA32_MISC_ENABLE: 0x00850089 (TCC EIST No-MWAIT
> > > PREFETCH
> > > TURBO)
> > > CPUID(7): SGX
> > > cpu0: MSR_IA32_FEATURE_CONTROL: 0xff07 (Locked )
> > > CPUID(0x15): eax_crystal: 2 ebx_tsc: 134 ecx_crystal_hz: 0
> > > TSC: 1608 MHz (2400 Hz * 134 / 2 / 100)
> > > CPUID(0x16): base_mhz: 1600 max_mhz: 3600 bus_mhz: 100
> > > cpu0: MSR_MISC_PWR_MGMT: 0x00401cc0 (ENable-EIST_Coordination
> > > DISable-EPB DISable-OOB)
> > > RAPL: 58254 sec. Joule Counter Range, at 4 Watts
> > > cpu0: MSR_PLATFORM_INFO: 0x804043df1011000
> > > 4 * 100.0 = 400.0 MHz max efficiency frequency
> > > 16 * 100.0 = 1600.0 MHz base frequency
> > > cpu0: MSR_IA32_POWER_CTL: 0x0024005d (C1E auto-promotion:
> > > DISabled)
> > > cpu0: MSR_TURBO_RATIO_LIMIT: 0x2224
> > > 34 * 100.0 = 3400.0 MHz max turbo 4 active cores
> > > 34 * 100.0 = 3400.0 MHz max turbo 3 active cores
> > > 34 * 100.0 = 3400.0 MHz max turbo 2 active cores
> > > 36 * 100.0 = 3600.0 MHz max turbo 1 active cores
> > > cpu0: MSR_CONFIG_TDP_NOMINAL: 0x000d (base_ratio=13)
> > > cpu0: MSR_CONFIG_TDP_LEVEL_1: 0x0006001c (PKG_MIN_PWR_LVL1=0
> > > PKG_MAX_PWR_LVL1=0 LVL1_RATIO=6 PKG_TDP_LVL1=28)
> > > cpu0: MSR_CONFIG_TDP_LEVEL_2: 0x00100038 (PKG_MIN_PWR_LVL2=0
> > > PKG_MAX_PWR_LVL2=0 LVL2_RATIO=16 PKG_TDP_LVL2=56)
> > > cpu0: MSR_CONFIG_TDP_CONTROL: 0x ( lock=0)
> > > cpu0: MSR_TURBO_ACTIVATION_RATIO: 0x000c
> > > (MAX_NON_TURBO_RATIO=12 lock=0)
> > > cpu0: MSR_PKG_CST_CONFIG_CONTROL: 0x1e008008 (UNdemote-C3,
> > > UNdemote-C1, demote-C3, demote-C1, locked: pkg-cstate-limit=8:
> > > unlimited)
> > > cpu0: POLL: CPUIDLE CORE POLL IDLE
> > > cpu0: C1: MWAIT 0x00
> > > cpu0: C1E: MWAIT 0x01
> > > cpu0: C3: MWAIT 0x10
> > > cpu0: C6: MWAIT 0x20
> > > cpu0: C7s: MWAIT 0x33
> > > cpu0: C8: MWAIT 0x40
> > > cpu0: C9: MWAIT 0x50
> > > cpu0: C10: MWAIT 0x60
> > > cpu0: cpufreq driver: intel_pstate
> > > cpu0: cpufreq governor: powersave
> > > cpufreq intel_pstate no_turbo: 0
> > > cpu0: MSR_MISC_FEATURE_CONTROL: 0x (L2-Prefetch L2-
> > > Prefetch-pair L1-Prefetch L1-IP-Prefetch)
> > > cpu0: MSR_PM_ENABLE: 0x0001 (HWP)
> > > cpu0: MSR_HWP_CAPABILITIES: 0x01060d24 (high 36 guar 13 eff 6 low
> > > 1)
> > > cpu0: MSR_HWP_REQUEST: 0x80002404 (min 4 max 36 des 0 epp 0x80
> > > window 0x0 pkg 0x0)
> > > cpu0: MSR_HWP_INTERRUPT: 0x (Dis_Guaranteed_Perf_Change,
> > > Dis_Excursion_Min)
> > > cpu0: MSR_HWP_STATUS: 0x (No-Guaranteed_Perf_Change, No-
> > > Excursion_Min)
> > > cpu0: MSR_IA32_ENERGY_PERF_BIAS: 0x0006 (balanced)
> > > cpu0: MSR_RAPL_POWER_UNIT: 0x000a0e03 (0.125000 Watts, 0.61
> > > Joules, 0.000977 sec.)
> > > cpu0: MSR_PKG_POWER_INFO: 0x0024 (4 W TDP, RAPL 0 - 0 W,
> > > 0.00 sec.)
> > > cpu0: MSR_PKG_POWER_LIMIT: 0x420078009c8048 (UNlocked)
> > > cpu0: PKG Limit #1: ENabled (9.00 Watts, 24.00 sec, clamp
> > > DISabled)
> > > cpu0: PKG Limit #2: DISabled (15.00 Watts, 0.002441* sec,
> > > clamp
> > > DISabled)
> > > cpu0: MSR_DRAM_POWER_LIMIT: 0x5400de (UNlocked)
> > > cpu0: DRAM Limit: DISabled (0.00 Watts, 0.000977 sec, clamp
> > > DISabled)
> > > cpu0: MSR_PP0_POLICY: 0
> > > cpu0: MSR_PP0_POWER_LIMIT: 0x (UNlocked)
> > > cpu0: Cores Limit: DISabled (0.00 Watts, 0.000977 sec, clamp
> > > DISabled)
> > > cpu0: MSR_PP1_POLICY: 0
> > > cpu0: MSR_PP1_POWER_LIMIT: 0x (UNlocked)
> > > cpu0: GFX Limit: DISabled (0.00 Watts, 0.000977 sec, clamp
> > > DISabled)
> > > cpu0: MSR_IA32_TEMPERATURE_TARGET: 0x0a640080 (100 C)
> > > cpu0: MSR_IA32_PACKAGE_THERM_STATUS: 0x88380802 (44 C)
> > > cpu0: MSR_IA32_PACKAGE_THERM_INTERRUPT: 0x0003 (100 C, 100 C)
> > > cpu0: MSR_PKGC3_IRTL: 0x884e (valid, 79872 ns)
> > > cpu0: MSR_PKGC6_IRTL: 0x8876 (valid, 120832 ns)
> > > cpu0: MSR_PKGC7_IRTL: 0x8894 (valid, 151552 ns)
> > > cpu0: MSR_PKGC8_IRTL: 0x88fa (valid, 256000 ns)
> > > cpu0: MSR_PKGC9_IRTL: 0x894c (valid, 339968 ns)
> > > cpu0: MSR_PKGC10_IRTL: 0x8bf2 (valid, 103424
Re: issues with suspend on Dell XPS 13 2-in-1
Hi Srinivas, Yes I have latest bios, I have version 1.3.1 that was released on 18th of Feb. Dennis El jue, 26-04-2018 a las 02:13 +, Pandruvada, Srinivas escribió: > > I see around 43% PC10 residency with power drop of 0.7W. > Do you have the latest BIOS of Dell 9365? > > > Thanks, > Srinivas > > On Fri, 2018-04-20 at 08:36 -0500, Dennis Gilmore wrote: > > Here is the full output > > > > # turbostat > > turbostat version 17.06.23 - Len Brown > > CPUID(0): GenuineIntel 22 CPUID levels; family:model:stepping > > 0x6:8e:9 (6:142:9) > > CPUID(1): SSE3 MONITOR SMX EIST TM2 TSC MSR ACPI-TM TM > > CPUID(6): APERF, TURBO, DTS, PTM, HWP, HWPnotify, HWPwindow, > > HWPepp, No-HWPpkg, EPB > > cpu0: MSR_IA32_MISC_ENABLE: 0x00850089 (TCC EIST No-MWAIT PREFETCH > > TURBO) > > CPUID(7): SGX > > cpu0: MSR_IA32_FEATURE_CONTROL: 0xff07 (Locked ) > > CPUID(0x15): eax_crystal: 2 ebx_tsc: 134 ecx_crystal_hz: 0 > > TSC: 1608 MHz (2400 Hz * 134 / 2 / 100) > > CPUID(0x16): base_mhz: 1600 max_mhz: 3600 bus_mhz: 100 > > cpu0: MSR_MISC_PWR_MGMT: 0x00401cc0 (ENable-EIST_Coordination > > DISable-EPB DISable-OOB) > > RAPL: 58254 sec. Joule Counter Range, at 4 Watts > > cpu0: MSR_PLATFORM_INFO: 0x804043df1011000 > > 4 * 100.0 = 400.0 MHz max efficiency frequency > > 16 * 100.0 = 1600.0 MHz base frequency > > cpu0: MSR_IA32_POWER_CTL: 0x0024005d (C1E auto-promotion: DISabled) > > cpu0: MSR_TURBO_RATIO_LIMIT: 0x2224 > > 34 * 100.0 = 3400.0 MHz max turbo 4 active cores > > 34 * 100.0 = 3400.0 MHz max turbo 3 active cores > > 34 * 100.0 = 3400.0 MHz max turbo 2 active cores > > 36 * 100.0 = 3600.0 MHz max turbo 1 active cores > > cpu0: MSR_CONFIG_TDP_NOMINAL: 0x000d (base_ratio=13) > > cpu0: MSR_CONFIG_TDP_LEVEL_1: 0x0006001c (PKG_MIN_PWR_LVL1=0 > > PKG_MAX_PWR_LVL1=0 LVL1_RATIO=6 PKG_TDP_LVL1=28) > > cpu0: MSR_CONFIG_TDP_LEVEL_2: 0x00100038 (PKG_MIN_PWR_LVL2=0 > > PKG_MAX_PWR_LVL2=0 LVL2_RATIO=16 PKG_TDP_LVL2=56) > > cpu0: MSR_CONFIG_TDP_CONTROL: 0x ( lock=0) > > cpu0: MSR_TURBO_ACTIVATION_RATIO: 0x000c > > (MAX_NON_TURBO_RATIO=12 lock=0) > > cpu0: MSR_PKG_CST_CONFIG_CONTROL: 0x1e008008 (UNdemote-C3, > > UNdemote-C1, demote-C3, demote-C1, locked: pkg-cstate-limit=8: > > unlimited) > > cpu0: POLL: CPUIDLE CORE POLL IDLE > > cpu0: C1: MWAIT 0x00 > > cpu0: C1E: MWAIT 0x01 > > cpu0: C3: MWAIT 0x10 > > cpu0: C6: MWAIT 0x20 > > cpu0: C7s: MWAIT 0x33 > > cpu0: C8: MWAIT 0x40 > > cpu0: C9: MWAIT 0x50 > > cpu0: C10: MWAIT 0x60 > > cpu0: cpufreq driver: intel_pstate > > cpu0: cpufreq governor: powersave > > cpufreq intel_pstate no_turbo: 0 > > cpu0: MSR_MISC_FEATURE_CONTROL: 0x (L2-Prefetch L2- > > Prefetch-pair L1-Prefetch L1-IP-Prefetch) > > cpu0: MSR_PM_ENABLE: 0x0001 (HWP) > > cpu0: MSR_HWP_CAPABILITIES: 0x01060d24 (high 36 guar 13 eff 6 low > > 1) > > cpu0: MSR_HWP_REQUEST: 0x80002404 (min 4 max 36 des 0 epp 0x80 > > window 0x0 pkg 0x0) > > cpu0: MSR_HWP_INTERRUPT: 0x (Dis_Guaranteed_Perf_Change, > > Dis_Excursion_Min) > > cpu0: MSR_HWP_STATUS: 0x (No-Guaranteed_Perf_Change, No- > > Excursion_Min) > > cpu0: MSR_IA32_ENERGY_PERF_BIAS: 0x0006 (balanced) > > cpu0: MSR_RAPL_POWER_UNIT: 0x000a0e03 (0.125000 Watts, 0.61 > > Joules, 0.000977 sec.) > > cpu0: MSR_PKG_POWER_INFO: 0x0024 (4 W TDP, RAPL 0 - 0 W, > > 0.00 sec.) > > cpu0: MSR_PKG_POWER_LIMIT: 0x420078009c8048 (UNlocked) > > cpu0: PKG Limit #1: ENabled (9.00 Watts, 24.00 sec, clamp > > DISabled) > > cpu0: PKG Limit #2: DISabled (15.00 Watts, 0.002441* sec, clamp > > DISabled) > > cpu0: MSR_DRAM_POWER_LIMIT: 0x5400de (UNlocked) > > cpu0: DRAM Limit: DISabled (0.00 Watts, 0.000977 sec, clamp > > DISabled) > > cpu0: MSR_PP0_POLICY: 0 > > cpu0: MSR_PP0_POWER_LIMIT: 0x (UNlocked) > > cpu0: Cores Limit: DISabled (0.00 Watts, 0.000977 sec, clamp > > DISabled) > > cpu0: MSR_PP1_POLICY: 0 > > cpu0: MSR_PP1_POWER_LIMIT: 0x (UNlocked) > > cpu0: GFX Limit: DISabled (0.00 Watts, 0.000977 sec, clamp > > DISabled) > > cpu0: MSR_IA32_TEMPERATURE_TARGET: 0x0a640080 (100 C) > > cpu0: MSR_IA32_PACKAGE_THERM_STATUS: 0x88380802 (44 C) > > cpu0: MSR_IA32_PACKAGE_THERM_INTERRUPT: 0x0003 (100 C, 100 C) > > cpu0: MSR_PKGC3_IRTL: 0x884e (valid, 79872 ns) > > cpu0: MSR_PKGC6_IRTL: 0x8876 (valid, 120832 ns) > > cpu0: MSR_PKGC7_IRTL: 0x8894 (valid, 151552 ns) > > cpu0: MSR_PKGC8_IRTL: 0x88fa (valid, 256000 ns) > > cpu0: MSR_PKGC9_IRTL: 0x894c (valid, 339968 ns) > > cpu0: MSR_PKGC10_IRTL: 0x8bf2 (valid, 1034240 ns) > > CoreCPUAvg_MHzBusy%Bzy_MHzTSC_MHzIRQ > > SMIC1C1EC3C6C7sC8C9C10C1% > > C1E%C3%C6%C7s%C8%C9%C10%CPU%c1 > > CPU%c3CPU%c6CPU%c7CoreTmpPkgTmpGFX%rc6GFXMHz > > Totl%C0Any%C0GFX%C0CPUGFX%Pkg%pc2Pkg%pc3 > > Pkg%pc6Pkg%pc7Pkg%pc8Pkg%pc9Pk%pc10PkgWatt > > CorWattGFXWattRAMWattPK
RE: issues with suspend on Dell XPS 13 2-in-1
> -Original Message- > From: Pandruvada, Srinivas [mailto:srinivas.pandruv...@intel.com] > Sent: Thursday, April 19, 2018 2:46 PM > To: linux-a...@vger.kernel.org; linux-kernel@vger.kernel.org; > dgilm...@redhat.com; Limonciello, Mario > Subject: Re: issues with suspend on Dell XPS 13 2-in-1 > > On Thu, 2018-04-19 at 17:30 +, mario.limoncie...@dell.com wrote: > > [...] > > > > > Those should impact opportunistic idle since for S2I regular > > > suspend > > > callbacks are called. In my 9365, I can get PC10 during S2I path > > > without adjusting them. Only problematic is systems with SATA, > > > where we > > > need to enable devsleep. > > > > Hmm, Dennis did mention that he had an NVME disk, so it can't be a > > devsleep > > problem. > > > > Perhaps can you also share your kernel config used with 9365 so > > Dennis > > can compare? > I am using ubuntu kernel config as is. Nothing special. > We need to look at the turbostat data and see what PkgC states the > system can reach. May be the issues is with loading DMC firmware or > some LTR issues. It could be potentially needing to update to new DMC firmware than Fedora installs by default too then. Eg due to: https://github.com/torvalds/linux/commit/39ccc9852e2b46964c9c44eba52db57413ba6d27 https://github.com/torvalds/linux/commit/4f0aa1fa3e3849caee450ee5d14fcc289cf16703 > > Thanks, > Srinivas > > > > > I believe we'll need to see some more information from Dennis you > > asked > > in previous email before we can make more progress here though. > > > > > > > > > > > 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? > > > > > > > > Assuming you mean for Dan to run this after he adjusts all the PM > > > > settings > > > > for those options power top called out, right? > > > > > > It is better. > > > May be some device is not behaving correctly. So he can try with > > > powertop --auto-tune and check turbostat and see status of PkgC > > > states. > > > > > > Thanks, > > > Srinivas > > > > > > > > > > > > > > > > > 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
Re: issues with suspend on Dell XPS 13 2-in-1
On Thu, 2018-04-19 at 17:30 +, mario.limoncie...@dell.com wrote: [...] > > Those should impact opportunistic idle since for S2I regular > > suspend > > callbacks are called. In my 9365, I can get PC10 during S2I path > > without adjusting them. Only problematic is systems with SATA, > > where we > > need to enable devsleep. > > Hmm, Dennis did mention that he had an NVME disk, so it can't be a > devsleep > problem. > > Perhaps can you also share your kernel config used with 9365 so > Dennis > can compare? I am using ubuntu kernel config as is. Nothing special. We need to look at the turbostat data and see what PkgC states the system can reach. May be the issues is with loading DMC firmware or some LTR issues. Thanks, Srinivas > > I believe we'll need to see some more information from Dennis you > asked > in previous email before we can make more progress here though. > > > > > > > > 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? > > > > > > Assuming you mean for Dan to run this after he adjusts all the PM > > > settings > > > for those options power top called out, right? > > > > It is better. > > May be some device is not behaving correctly. So he can try with > > powertop --auto-tune and check turbostat and see status of PkgC > > states. > > > > Thanks, > > Srinivas > > > > > > > > > > > > > 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 smime.p7s Description: S/MIME cryptographic signature
RE: issues with suspend on Dell XPS 13 2-in-1
> -Original Message- > From: Pandruvada, Srinivas [mailto:srinivas.pandruv...@intel.com] > Sent: Wednesday, April 18, 2018 11:37 PM > To: dgilm...@redhat.com; linux-kernel@vger.kernel.org; linux- > a...@vger.kernel.org; Limonciello, Mario > Subject: Re: issues with suspend on Dell XPS 13 2-in-1 > > On Wed, 2018-04-18 at 21:01 +, mario.limoncie...@dell.com wrote: > > > > > > > > [...] > > > > > 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. > > > > Why is policy set this way by default in kernel? Could we discuss to > > change > > Default kernel policy so that users can get better power consumption > > by default > Good question. This was discussed before, the problem is that it can > cause some issues with legacy devices. If the concern is legacy devices, what about flipping default policy when it's say SKL or newer? > It should be better done in user > space by some policy in gnome power manager, which user can > enable/disable. Sure, I think letting userspace change the policy if a user wants to turn It off makes sense. What I'm hoping to accomplish however is a better default policy however since most users should prefer more battery life, and "power users" would be the ones to further tune for their preferred usage. > > > > > I think it will be especially important as more machines continue to > > adopt > > suspend-to-idle. > Those should impact opportunistic idle since for S2I regular suspend > callbacks are called. In my 9365, I can get PC10 during S2I path > without adjusting them. Only problematic is systems with SATA, where we > need to enable devsleep. Hmm, Dennis did mention that he had an NVME disk, so it can't be a devsleep problem. Perhaps can you also share your kernel config used with 9365 so Dennis can compare? I believe we'll need to see some more information from Dennis you asked in previous email before we can make more progress here though. > > > > > 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? > > > > Assuming you mean for Dan to run this after he adjusts all the PM > > settings > > for those options power top called out, right? > It is better. > May be some device is not behaving correctly. So he can try with > powertop --auto-tune and check turbostat and see status of PkgC states. > > Thanks, > Srinivas > > > > > > > > > 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
Re: issues with suspend on Dell XPS 13 2-in-1
On Wed, 2018-04-18 at 21:01 +, mario.limoncie...@dell.com wrote: > > > > > [...] > > > 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. > > Why is policy set this way by default in kernel? Could we discuss to > change > Default kernel policy so that users can get better power consumption > by default Good question. This was discussed before, the problem is that it can cause some issues with legacy devices. It should be better done in user space by some policy in gnome power manager, which user can enable/disable. > > I think it will be especially important as more machines continue to > adopt > suspend-to-idle. Those should impact opportunistic idle since for S2I regular suspend callbacks are called. In my 9365, I can get PC10 during S2I path without adjusting them. Only problematic is systems with SATA, where we need to enable devsleep. > > > 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? > > Assuming you mean for Dan to run this after he adjusts all the PM > settings > for those options power top called out, right? It is better. May be some device is not behaving correctly. So he can try with powertop --auto-tune and check turbostat and see status of PkgC states. Thanks, Srinivas > > > > > 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 smime.p7s Description: S/MIME cryptographic signature
RE: issues with suspend on Dell XPS 13 2-in-1
> -Original Message- > From: Pandruvada, Srinivas [mailto:srinivas.pandruv...@intel.com] > Sent: Tuesday, April 17, 2018 6:00 PM > To: linux-a...@vger.kernel.org; linux-kernel@vger.kernel.org; > dgilm...@redhat.com; Limonciello, Mario > Subject: Re: issues with suspend on Dell XPS 13 2-in-1 > > On Mon, 2018-04-16 at 16:07 +, mario.limoncie...@dell.com wrote: > > Hi Dennis, > > > > > -Original Message- > > > From: Dennis Gilmore [mailto:dgilm...@redhat.com] > > > Sent: Friday, April 13, 2018 9:03 PM > > > To: linux-kernel@vger.kernel.org; linux-a...@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. Why is policy set this way by default in kernel? Could we discuss to change Default kernel policy so that users can get better power
Re: issues with suspend on Dell XPS 13 2-in-1
On Mon, 2018-04-16 at 16:07 +, mario.limoncie...@dell.com wrote: > Hi Dennis, > > > -Original Message- > > From: Dennis Gilmore [mailto:dgilm...@redhat.com] > > Sent: Friday, April 13, 2018 9:03 PM > > To: linux-kernel@vger.kernel.org; linux-a...@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 PC
RE: issues with suspend on Dell XPS 13 2-in-1
Hi Dennis, > -Original Message- > From: Dennis Gilmore [mailto:dgilm...@redhat.com] > Sent: Friday, April 13, 2018 9:03 PM > To: linux-kernel@vger.kernel.org; linux-a...@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? >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
