Re: Dell XPS 13 9360: `slp_s0_residency_usec` stays 0

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Dear David,


Thank you for your reply.

Am 30.05.24 um 23:24 schrieb David E. Box:

On Fri, 2024-05-24 at 06:53 +0200, Paul Menzel wrote:

Am 22.05.24 um 18:37 schrieb Mario Limonciello:
On 5/22/2024 10:52, Paul Menzel wrote:

On the Intel Kaby Lake laptop Dell XPS 13 9360,
`/sys/kernel/debug/pmc_core/slp_s0_residency_usec` does stay 0 even
after a s2idle suspend/resume cycle.

It won't change your numbers but FWIW you can also read from

$ cat /sys/power/suspend_stats/last_hw_sleep

which is also accessible under kernel lockdown.

      $ sudo dmesg
      […]
      [    0.000000] DMI: Dell Inc. XPS 13 9360/0596KF, BIOS 2.21.0 06/02/2022
      […]
      [10176.745124] PM: suspend entry (s2idle)
      [10176.757275] Filesystems sync: 0.012 seconds
      [10176.769118] Freezing user space processes
      [10176.771693] Freezing user space processes completed (elapsed 0.002 seconds)
      [10176.771710] OOM killer disabled.
      [10176.771714] Freezing remaining freezable tasks
      [10176.773487] Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
      [10176.773504] printk: Suspending console(s) (use no_console_suspend to debug)
      [10176.948337] ACPI: EC: interrupt blocked
      [10176.951016] intel_pch_thermal 0000:00:14.2: CPU-PCH is cool [48C]
      [10181.281827] ACPI: EC: interrupt unblocked
      $ sudo more /sys/kernel/debug/pmc_core/slp_s0_residency_usec
      0

Is that expected?

Is it a regression?  If so; probably it's worth bisecting.

Sorry, I do not know. It’s the first time [1] I heard about this file,
and that fwts [2] checks it. Do you remember, if Dell has any public
logs from testing, containing `slp_s0_residency_usec`?

If it's not a regression IIUC you should probably run
https://github.com/intel/S0ixSelftestTool for assistance in next steps
on debugging why this is happening.

Thank you for the pointer. Please find the log file from `sudo
./s0ix-selftest-tool.sh -s` attached. Some PCIe ports are flagged.

The report suggests checking the kernel log for any error loading drm firmware.

Did you conclude that from the lines below?

   GFX DC5 after S2idle: 59
   GFX DC6 after S2idle: 0

Your system CPU Model ID is: 142, and the graphics DC6 value is not expected to enter DC9,
   please check the latest display DMC FW load status:

   Your system Intel graphics DMC FW loaded status is:yes

If the firmware is loaded properly, you should see a message similar to the
following:

     [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4)

The firmware is loaded:

[ 124.536942] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4)


Kind regards,

Paul


[1]: https://review.coreboot.org/c/coreboot/+/81595/10/src/mainboard/cwwk/adl/Kconfig#9
[2]: https://wiki.ubuntu.com/FirmwareTestSuite/


PS: Some system details:

```
$ LANG= lspci -nn
00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5904] (rev 02)
00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 620 [8086:5916] (rev 02)
00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 02)
00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller [8086:9d2f] (rev 21)

[…]




[Index of Archives]     [Linux Kernel Development]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux