Abnormal battery drain during suspend (s2idle) on Dell Latitude 7430

Ubuntu Version

Ubuntu 26.04 LTS

Desktop Environment (if applicable)

GNOME

Problem Description

Hi, I face an abnormal battery drain during suspend (s2idle), about 5W 3W (which is 5% battery in one hour).
There is no deep sleep (s3) available on the laptop.

I am pretty sure that some component on the PCI bus is still active whereas it should not during s2idle. But I did not manage to be sure of which one, nor to avoid it. Options are the SSD, the WiFi card or sensors. If the SSD is involved I am not even sure if it is a controller problem or a kernel/OS one.

Thank you for any help :slight_smile:

Relevant System Information

Here is the output of ĂŹnxi -b`:

System:
Host: ahonorat-Latitude-7430 Kernel: 7.0.0-38-generic arch: x86_64 bits: 64
Desktop: GNOME v: 50.1 Distro: Ubuntu 26.04.1 LTS (Resolute Raccoon)
Machine:
Type: Laptop System: Dell product: Latitude 7430 v: N/A
serial:
Mobo: Dell model: 0NMM73 v: A02 serial:
Firmware: UEFI vendor: Dell v: 1.42.0 date: 07/23/2026
Battery:
ID-1: BAT0 charge: 32.5 Wh (67.1%) condition: 48.4/58 Wh (83.4%)
volts: 15.25 min: 15.2
CPU:
Info: 10-core (2-mt/8-st) 12th Gen Intel Core i7-1265U [MST AMCP]
speed (MHz): avg: 400 min/max: 400/1800:1300
Graphics:
Device-1: Intel Alder Lake-UP3 GT2 [Iris Xe Graphics] driver: xe v: kernel
Device-2: Microdia Integrated_Webcam_FHD driver: uvcvideo type: USB
Display: wayland server: X.Org v: 24.1.10 with: Xwayland v: 24.1.10
compositor: gnome-shell driver: dri: iris gpu: xe resolution: 3072x1728~60Hz
API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 26.0.8-1ubuntu0.3
renderer: Mesa Intel Iris Xe Graphics (ADL GT2)
Info: Tools: api: eglinfo,glxinfo x11: xdriinfo, xdpyinfo, xprop, xrandr
Network:
Device-1: Intel Alder Lake-P PCH CNVi WiFi driver: iwlwifi
Drives:
Local Storage: total: 465.76 GiB used: 18.35 GiB (3.9%)
Info:
Memory: total: 32 GiB note: est. available: 30.03 GiB used: 2.87 GiB (9.6%)
Processes: 394 Uptime: 43m Shell: Bash inxi: 3.3.40

Here is the current Kernel configuration:
GRUB_CMDLINE_LINUX_DEFAULT=“iwlwifi.power_save=1 xe.force_probe=46a8 module_blacklist=i915 intel_pstate=passive quiet splash”

Error Messages / Logs

Error message got after modifying the Intel s0ix self test tool:

Checking PCI Devices D3 States:
[ 48.184056] snd_hda_intel 0000:00:1f.3: PCI PM: Suspend power state: D3hot
[ 48.184121] i915 0000:00:02.0: PCI PM: Suspend power state: D3hot
[ 48.187237] xhci_hcd 0000:00:0d.0: PCI PM: Suspend power state: D3cold
[ 48.200795] intel_ish_ipc 0000:00:12.0: PCI PM: Suspend power state: D0
[ 48.200802] intel_ish_ipc 0000:00:12.0: PCI PM: Skipped
[ 48.200950] i801_smbus 0000:00:1f.4: PCI PM: Suspend power state: D0
[ 48.200959] i801_smbus 0000:00:1f.4: PCI PM: Skipped
[ 48.213421] nvme 0000:01:00.0: PCI PM: Suspend power state: D3hot
[ 48.213830] pcieport 0000:00:06.0: PCI PM: Suspend power state: D0
[ 48.213849] pcieport 0000:00:06.0: PCI PM: Skipped
[ 48.215666] mei_me 0000:00:16.0: PCI PM: Suspend power state: D3hot
[ 48.216911] proc_thermal_pci 0000:00:04.0: PCI PM: Suspend power state: D3hot
[ 48.217893] intel-lpss 0000:00:15.1: PCI PM: Suspend power state: D3hot
[ 48.219578] xhci_hcd 0000:00:14.0: PCI PM: Suspend power state: D3hot
[ 48.219682] iwlwifi 0000:00:14.3: PCI PM: Suspend power state: D3hot
[ 48.223407] thunderbolt 0000:00:0d.2: PCI PM: Suspend power state: D3cold

Checking PCI Devices tree diagram:
-[0000:00]-±00.0 Intel Corporation Alder Lake-U15 Host and DRAM Controller
±02.0 Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics]
±04.0 Intel Corporation Alder Lake Innovation Platform Framework Processor Participant
±06.0-[01]----00.0 KIOXIA Corporation NVMe SSD
±07.0-[02-39]–
±07.1-[3a-71]–
±08.0 Intel Corporation 12th Gen Core Processor Gaussian & Neural Accelerator
±0d.0 Intel Corporation Alder Lake-P Thunderbolt 4 USB Controller
±0d.2 Intel Corporation Alder Lake-P Thunderbolt 4 NHI #0
±12.0 Intel Corporation Alder Lake-P Integrated Sensor Hub
±14.0 Intel Corporation Alder Lake PCH USB 3.2 xHCI Host Controller
±14.2 Intel Corporation Alder Lake PCH Shared SRAM
±14.3 Intel Corporation Alder Lake-P PCH CNVi WiFi
±15.0 Intel Corporation Alder Lake PCH Serial IO I2C Controller #0
±15.1 Intel Corporation Alder Lake PCH Serial IO I2C Controller #1
±16.0 Intel Corporation Alder Lake PCH HECI Controller
±1f.0 Intel Corporation Alder Lake PCH eSPI Controller
±1f.3 Intel Corporation Alder Lake PCH-P High Definition Audio Controller
±1f.4 Intel Corporation Alder Lake PCH-P SMBus Host Controller
-1f.5 Intel Corporation Alder Lake-P PCH SPI Controller

The pcieport 0000:00:06.0 ASPM enable status:
LnkCtl: ASPM L1 Enabled; RCB 64 bytes, Disabled- CommClk+

Pcieport is not in D3cold
0000:00:06.0

lspci excerpt of the devices not reachning D3cold:

00:12.0 Serial controller: Intel Corporation Alder Lake-P Integrated Sensor Hub (rev 01) (prog-if 00 [8250])
Subsystem: Dell Alder Lake-P Integrated Sensor Hub
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 26
IOMMU group: 8
Region 0: Memory at 6053170000 (64-bit, non-prefetchable) [size=64K]
Capabilities: [80] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold-)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [90] Vendor Specific Information: Len=14 <?>
Kernel driver in use: intel_ish_ipc
Kernel modules: intel_ish_ipc

00:1f.4 SMBus: Intel Corporation Alder Lake PCH-P SMBus Host Controller (rev 01)
Subsystem: Dell Alder Lake PCH-P SMBus Host Controller
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- SERR- <PERR- INTx-
Interrupt: pin A routed to IRQ 16
IOMMU group: 13
Region 0: Memory at 605319c000 (64-bit, non-prefetchable) [size=256]
Region 4: I/O ports at efa0 [size=32]
Kernel driver in use: i801_smbus
Kernel modules: i2c_i801

01:00.0 Non-Volatile memory controller: KIOXIA Corporation NVMe SSD (rev 01) (prog-if 02 [NVM Express])
Subsystem: KIOXIA Corporation NVMe SSD
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 16
IOMMU group: 14
Region 0: Memory at 9de00000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [80] Express (v2) Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited
ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset+ SlotPowerLimit 75W
DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ FLReset-
MaxPayload 256 bytes, MaxReadReq 512 bytes
DevSta: CorrErr+ NonFatalErr- FatalErr- UnsupReq+ AuxPwr- TransPend-
LnkCap: Port #0, Speed 8GT/s, Width x4, ASPM L1, Exit Latency L1 <64us
ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp+
LnkCtl: ASPM L1 Enabled; RCB 64 bytes, Disabled- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 8GT/s, Width x4
TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
DevCap2: Completion Timeout: Range ABCD, TimeoutDis+ NROPrPrP- LTR+
10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt+ EETLPPrefix-
EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
FRS- TPHComp- ExtTPHComp-
AtomicOpsCap: 32bit- 64bit- 128bitCAS-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR+ 10BitTagReq- OBFF Disabled,
AtomicOpsCtl: ReqEn-
LnkCap2: Supported Link Speeds: 2.5-8GT/s, Crosslink- Retimer- 2Retimers- DRS-
LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis-
Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
Compliance Preset/De-emphasis: -6dB de-emphasis, 0dB preshoot
LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete+ EqualizationPhase1+
EqualizationPhase2+ EqualizationPhase3+ LinkEqualizationRequest-
Retimer- 2Retimers- CrosslinkRes: unsupported
Capabilities: [d0] MSI-X: Enable+ Count=9 Masked-
Vector table: BAR=0 offset=00002000
PBA: BAR=0 offset=00003000
Capabilities: [e0] MSI: Enable- Count=1/8 Maskable- 64bit+
Address: 0000000000000000 Data: 0000
Capabilities: [f8] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [100 v1] Latency Tolerance Reporting
Max snoop latency: 15728640ns
Max no snoop latency: 15728640ns
Capabilities: [110 v1] L1 PM Substates
L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+
PortCommonModeRestoreTime=10us PortTPowerOnTime=60us
L1SubCtl1: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+
T_CommonMode=0us LTR1.2_Threshold=616448ns
L1SubCtl2: T_PwrOn=500us
Capabilities: [128 v1] Alternative Routing-ID Interpretation (ARI)
ARICap: MFVC- ACS-, Next Function: 0
ARICtl: MFVC- ACS-, Function Group: 0
Capabilities: [200 v2] Advanced Error Reporting
UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP+ ECRC- UnsupReq- ACSViol-
CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
AERCap: First Error Pointer: 00, ECRCGenCap- ECRCGenEn- ECRCChkCap+ ECRCChkEn-
MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
HeaderLog: 04000001 0000000f 01070000 c0c62330
Capabilities: [300 v1] Secondary PCI Express
LnkCtl3: LnkEquIntrruptEn- PerformEqu-
LaneErrStat: 0
Kernel driver in use: nvme
Kernel modules: nvme

What I’ve Tried

  1. I ran the official Intel s0ix self test tool and it says everything is fine, except when modifying the script to force assesment of PCI devices and not only rely on the residency level/duration.
  2. I have installed Powertop and set all its settings to GOOD.
  3. I have tried various kernel parameters, including nvme_core.default_ps_max_latency_us=0, including xe or i915, including intel specific parameters.
  4. I reached Dell’s engineers but since there is no battery drain with Windows (modern standby) they stopped to help (although the laptop is Ubuntu certified)
  5. I modified the BIOS dynamic tables (DSDT) to enforce deep sleep mode, but this caused other bugs after resuming from suspend

Well now I am bit stucked, and wondering if it is a bug from Dell’s BIOS, Intel components or the kernel.

Start by updating UEFI, troubleshoot from there.

Hello,
you mean using the lastest version of BIOS ? I am using the lastest version available (1.42).

I meant the firmware which since ~2012 is UEFI. The 1981 BIOS very rapidly disappeared from the consumer market having been replaced with the more modern and feature rich UEFI. Some manufacturers and users still use the term “BIOS” incorrectly.

2 Likes

To speed things along, I’m going to translate @celticwarrior’s accurate but slightly-confusing answer.

He was saying: “yes, try updating the ‘BIOS’ to the latest version. And be aware of the newer vocabulary too.”

3 Likes

@ahonorat to check first sudo dmidecode -s bios-version

And welcome to the community!

Hello, sure, I just ran the command, the output is “1.42.0“.

Thank you for your welcome!

1 Like

It seems to be up to date https://www.dell.com/support/product-details/en-us/product/latitude-14-7430-2-in-1-laptop/drivers

When you run this

cat /sys/power/mem_sleep

do you get this, please?

[s2idle] deep

If yes run this

sudo journalctl -b -1 | grep -iE ‘suspend|resume|sleep|wake’

sudo dmesg | grep -iE ‘s2idle|suspend|resume|wakeup’

And after

sudo apt install powerstat

Run it

powerstat

That should give the team in this thread plenty of information.

There is a BIOS out September this year. May help

@Actionparsnip while I was looking at it, surprisingly, 42 isn’t even properly referenced on their sites. Everywhere, 40 seemed to be the one. Which one are you referring to, please?

@ahonorat after all the above, can you also try one thing? Please suspend the laptop for one hour and record the battery percentage before and after. If you lose 10%, there is definitely an issue. Thanks

Hello again, here are the output of the multiple commands that you suggested:

$ cat /sys/power/mem_sleep
[s2idle]

$ sudo journalctl -b -1 | grep -iE ‘suspend|resume|sleep|wake’
oct. 04 18:09:56 ahonorat-Latitude-7430 kernel: Low-power S0 idle used by default for system suspend
oct. 04 18:09:56 ahonorat-Latitude-7430 kernel: input: Sleep Button as /devices/platform/PNP0C0E:00/input/input2
oct. 04 18:09:56 ahonorat-Latitude-7430 kernel: ACPI: button: Sleep Button [SBTN]
oct. 04 18:09:56 ahonorat-Latitude-7430 kernel: rtc_cmos 00:00: RTC can wake from S4
oct. 04 18:09:57 ahonorat-Latitude-7430 kernel: nvme 0000:01:00.0: platform quirk: setting simple suspend
oct. 04 18:10:04 ahonorat-Latitude-7430 systemd[1]: Starting user-pm-setup.service - Disable devices as wakeup and set good autosuspend

oct. 04 18:10:05 ahonorat-Latitude-7430 sudo[1616]: root : PWD=/ ; USER=root ; COMMAND=/usr/bin/sh -c echo PEG0 > /proc/acpi/wakeup
oct. 04 18:10:05 ahonorat-Latitude-7430 disable-devices-as-wakeup.sh[1681]: User disabled acpi wakeup from PEG0
oct. 04 18:10:05 ahonorat-Latitude-7430 unknown: User disabled acpi wakeup from PEG0
oct. 04 18:10:05 ahonorat-Latitude-7430 systemd-logind[1580]: Watching system buttons on /dev/input/event2 (Sleep Button)
oct. 04 18:10:05 ahonorat-Latitude-7430 sudo[1702]: root : PWD=/ ; USER=root ; COMMAND=/usr/bin/sh -c echo XHCI > /proc/acpi/wakeup
oct. 04 18:10:05 ahonorat-Latitude-7430 disable-devices-as-wakeup.sh[1734]: User disabled acpi wakeup from XHCI
oct. 04 18:10:05 ahonorat-Latitude-7430 unknown: User disabled acpi wakeup from XHCI
oct. 04 18:10:05 ahonorat-Latitude-7430 sudo[1753]: root : PWD=/ ; USER=root ; COMMAND=/usr/bin/sh -c echo TXHC > /proc/acpi/wakeup
oct. 04 18:10:05 ahonorat-Latitude-7430 disable-devices-as-wakeup.sh[1848]: User disabled acpi wakeup from TXHC
oct. 04 18:10:05 ahonorat-Latitude-7430 unknown: User disabled acpi wakeup from TXHC
oct. 04 18:10:05 ahonorat-Latitude-7430 sudo[1856]: root : PWD=/ ; USER=root ; COMMAND=/usr/bin/sh -c echo TDM0 > /proc/acpi/wakeup
oct. 04 18:10:05 ahonorat-Latitude-7430 disable-devices-as-wakeup.sh[1864]: User disabled acpi wakeup from TDM0
oct. 04 18:10:05 ahonorat-Latitude-7430 unknown: User disabled acpi wakeup from TDM0
oct. 04 18:10:05 ahonorat-Latitude-7430 sudo[1870]: root : PWD=/ ; USER=root ; COMMAND=/usr/bin/sh -c echo TRP0 > /proc/acpi/wakeup
oct. 04 18:10:05 ahonorat-Latitude-7430 disable-devices-as-wakeup.sh[1893]: User disabled acpi wakeup from TRP0
oct. 04 18:10:05 ahonorat-Latitude-7430 unknown: User disabled acpi wakeup from TRP0
oct. 04 18:10:05 ahonorat-Latitude-7430 sudo[1903]: root : PWD=/ ; USER=root ; COMMAND=/usr/bin/sh -c echo TRP1 > /proc/acpi/wakeup
oct. 04 18:10:05 ahonorat-Latitude-7430 disable-devices-as-wakeup.sh[1923]: User disabled acpi wakeup from TRP1
oct. 04 18:10:05 ahonorat-Latitude-7430 unknown: User disabled acpi wakeup from TRP1
oct. 04 18:10:05 ahonorat-Latitude-7430 sudo[1930]: root : PWD=/ ; USER=root ; COMMAND=/usr/bin/sh -c echo AWAC > /proc/acpi/wakeup
oct. 04 18:10:05 ahonorat-Latitude-7430 disable-devices-as-wakeup.sh[1948]: User disabled acpi wakeup from AWAC
oct. 04 18:10:05 ahonorat-Latitude-7430 unknown: User disabled acpi wakeup from AWAC
oct. 04 18:10:05 ahonorat-Latitude-7430 sudo[1953]: root : PWD=/ ; USER=root ; COMMAND=/usr/bin/sh -c echo disabled > /sys/devices/platform/USBC000:00/power_supply/ucsi-source-psy-USBC000:002/power/wakeup
oct. 04 18:10:05 ahonorat-Latitude-7430 disable-devices-as-wakeup.sh[1966]: User disabled sys wakeup from platform/USBC000:00/power_supply/ucsi-source-psy-USBC000:002
oct. 04 18:10:05 ahonorat-Latitude-7430 unknown: User disabled sys wakeup from platform/USBC000:00/power_supply/ucsi-source-psy-USBC000:002
oct. 04 18:10:05 ahonorat-Latitude-7430 sudo[1968]: root : PWD=/ ; USER=root ; COMMAND=/usr/bin/sh -c echo disabled > /sys/devices/platform/USBC000:00/power_supply/ucsi-source-psy-USBC000:001/power/wakeup
oct. 04 18:10:05 ahonorat-Latitude-7430 disable-devices-as-wakeup.sh[1975]: User disabled sys wakeup from platform/USBC000:00/power_supply/ucsi-source-psy-USBC000:001
oct. 04 18:10:05 ahonorat-Latitude-7430 unknown: User disabled sys wakeup from platform/USBC000:00/power_supply/ucsi-source-psy-USBC000:001
oct. 04 18:10:05 ahonorat-Latitude-7430 sudo[1977]: root : PWD=/ ; USER=root ; COMMAND=/usr/bin/sh -c echo disabled > /sys/devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-VEN_0488:00/power/wakeup
oct. 04 18:10:05 ahonorat-Latitude-7430 disable-devices-as-wakeup.sh[1983]: User disabled sys wakeup from pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-VEN_0488:00
oct. 04 18:10:05 ahonorat-Latitude-7430 unknown: User disabled sys wakeup from pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-VEN_0488:00
oct. 04 18:10:05 ahonorat-Latitude-7430 sudo[1987]: root : PWD=/ ; USER=root ; COMMAND=/usr/bin/sh -c echo disabled > /sys/devices/pci0000:00/0000:00:0d.2/domain0/power/wakeup
oct. 04 18:10:05 ahonorat-Latitude-7430 disable-devices-as-wakeup.sh[2028]: User disabled sys wakeup from pci0000:00/0000:00:0d.2/domain0
oct. 04 18:10:05 ahonorat-Latitude-7430 unknown: User disabled sys wakeup from pci0000:00/0000:00:0d.2/domain0
oct. 04 18:10:05 ahonorat-Latitude-7430 sudo[2032]: root : PWD=/ ; USER=root ; COMMAND=/usr/bin/sh -c echo disabled > /sys/devices/pci0000:00/0000:00:0d.2/domain0/0-0/power/wakeup
oct. 04 18:10:05 ahonorat-Latitude-7430 disable-devices-as-wakeup.sh[2039]: User disabled sys wakeup from pci0000:00/0000:00:0d.2/domain0/0-0
oct. 04 18:10:05 ahonorat-Latitude-7430 unknown: User disabled sys wakeup from pci0000:00/0000:00:0d.2/domain0/0-0
oct. 04 18:10:05 ahonorat-Latitude-7430 systemd[1]: Finished user-pm-setup.service - Disable devices as wakeup and set good autosuspend.
oct. 04 18:10:06 ahonorat-Latitude-7430 rtkit-daemon[2243]: Handling system-suspend using logind.
oct. 04 19:20:43 ahonorat-Latitude-7430 systemd-logind[1580]: Suspending

oct. 04 19:20:43 ahonorat-Latitude-7430 NetworkManager[1736]: [1791134443.2575] manager: sleep: sleep requested (sleeping: no enabled: yes)
oct. 04 19:20:43 ahonorat-Latitude-7430 ModemManager[1818]: [sleep-monitor-systemd] system is about to suspend
oct. 04 19:20:43 ahonorat-Latitude-7430 ModemManager[1818]: [sleep-monitor-systemd] ready to sleep; dropping inhibitor
oct. 04 19:20:43 ahonorat-Latitude-7430 NetworkManager[1736]: [1791134443.2600] manager: NetworkManager state is now DISABLED (ASLEEP)
oct. 04 19:20:43 ahonorat-Latitude-7430 NetworkManager[1736]: [1791134443.2602] device (wlp0s20f3): state change: activated → deactivating (reason ‘sleeping’, managed-type: ‘full’)
oct. 04 19:20:43 ahonorat-Latitude-7430 NetworkManager[1736]: [1791134443.3996] device (wlp0s20f3): state change: deactivating → disconnected (reason ‘sleeping’, managed-type: ‘full’)
oct. 04 19:20:44 ahonorat-Latitude-7430 systemd[1]: Reached target sleep.target - Sleep.
oct. 04 19:20:44 ahonorat-Latitude-7430 systemd[1]: Starting systemd-suspend.service - System Suspend

oct. 04 19:20:44 ahonorat-Latitude-7430 systemd-sleep[51151]: Successfully froze unit ‘user.slice’.
oct. 04 19:20:44 ahonorat-Latitude-7430 systemd-sleep[51151]: Performing sleep operation ‘suspend’

oct. 04 19:20:44 ahonorat-Latitude-7430 kernel: PM: suspend entry (s2idle)
oct. 04 20:30:52 ahonorat-Latitude-7430 kernel: printk: Suspending console(s) (use no_console_suspend to debug)
oct. 04 20:30:52 ahonorat-Latitude-7430 kernel: PM: suspend exit
oct. 04 20:30:52 ahonorat-Latitude-7430 systemd-sleep[51151]: System returned from sleep operation ‘suspend’.
oct. 04 20:30:52 ahonorat-Latitude-7430 systemd-sleep[51151]: Successfully thawed unit ‘user.slice’.
oct. 04 20:30:52 ahonorat-Latitude-7430 systemd[1]: systemd-suspend.service: Deactivated successfully.
oct. 04 20:30:52 ahonorat-Latitude-7430 systemd[1]: Finished systemd-suspend.service - System Suspend.
oct. 04 20:30:52 ahonorat-Latitude-7430 systemd[1]: Stopped target sleep.target - Sleep.
oct. 04 20:30:52 ahonorat-Latitude-7430 systemd[1]: Reached target suspend.target - Suspend.
oct. 04 20:30:52 ahonorat-Latitude-7430 systemd-logind[1580]: Operation ‘suspend’ finished.
oct. 04 20:30:52 ahonorat-Latitude-7430 NetworkManager[1736]: [1791138652.3875] manager: sleep: wake requested (sleeping: yes enabled: yes)
oct. 04 20:30:52 ahonorat-Latitude-7430 ModemManager[1818]: [sleep-monitor-systemd] system is resuming
oct. 04 20:30:52 ahonorat-Latitude-7430 rtkit-daemon[2243]: Resumed scheduling 8 threads.
oct. 04 20:30:52 ahonorat-Latitude-7430 systemd[1]: Stopped target suspend.target - Suspend.

$sudo dmesg | grep -iE ‘s2idle|suspend|resume|wakeup’
[ 2.319705] nvme 0000:01:00.0: platform quirk: setting simple suspend
[ 9.843360] User disabled acpi wakeup from PEG0
[ 9.917616] User disabled acpi wakeup from XHCI
[ 9.990657] User disabled acpi wakeup from TXHC
[ 10.056377] User disabled acpi wakeup from TDM0
[ 10.104016] User disabled acpi wakeup from TRP0
[ 10.142876] User disabled acpi wakeup from TRP1
[ 10.184980] User disabled acpi wakeup from AWAC
[ 10.238733] User disabled sys wakeup from platform/USBC000:00/power_supply/ucsi-source-psy-USBC000:002
[ 10.279112] User disabled sys wakeup from platform/USBC000:00/power_supply/ucsi-source-psy-USBC000:001
[ 10.330512] User disabled sys wakeup from pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-VEN_0488:00
[ 10.462937] User disabled sys wakeup from pci0000:00/0000:00:0d.2/domain0
[ 10.508816] User disabled sys wakeup from pci0000:00/0000:00:0d.2/domain0/0-0
[ 5540.164869] PM: suspend entry (s2idle)
[ 5540.182621] printk: Suspending console(s) (use no_console_suspend to debug)
[ 7784.560993] PM: suspend exit
[ 8168.686846] PM: suspend entry (s2idle)
[ 8168.705620] printk: Suspending console(s) (use no_console_suspend to debug)
[11631.476134] PM: suspend exit

About that last output, note that all the “User disabled acpi wakeup” lines comes from a service that I run at startup to disable waking up the laptop by the touchpad especially: I kept only the keyboard and power button. I had the same battery drain without all of this.

$powerstat
Running for 300.0 seconds (30 samples at 10.0 second intervals).
Power measurements will start in 180 seconds time.

Time User Nice Sys Idle IO Run Ctxt/s IRQ/s Watts
21:45:36 1.4 0.1 1.0 97.3 0.2 1 783 509 4.99
21:45:46 1.4 0.0 1.1 97.3 0.1 1 815 491 3.77
21:45:56 2.1 0.0 1.6 96.1 0.2 1 838 566 3.96
21:46:06 1.2 0.1 1.0 97.4 0.3 1 695 439 3.06
21:46:16 1.5 0.0 1.2 97.0 0.2 1 798 512 4.44
21:46:26 1.1 0.1 1.0 97.6 0.2 1 689 443 3.45
21:46:36 33.1 0.0 15.4 0.0 51.4 1 5148 3114 9.82
21:46:46 0.8 0.0 0.3 98.9 0.0 1 3836 2490 4.65
21:46:56 3.6 0.0 2.8 93.5 0.0 2 3816 3060 4.98
21:47:06 3.1 0.0 2.3 94.6 0.1 2 2699 1942 4.45
21:47:16 1.3 0.1 1.2 97.0 0.3 1 781 495 3.15
21:47:26 1.4 0.1 1.0 97.4 0.1 1 771 502 3.69
21:47:36 1.2 0.0 1.1 97.5 0.0 1 771 491 3.17
^C-------- ----- ----- ----- ----- ----- ---- ------ ------ ------
Average 4.1 0.0 2.4 89.4 4.1 1.2 1726.1 1158.0 4.43
GeoMean 1.9 0.0 1.4 0.0 0.0 1.1 1255.6 822.7 4.21
StdDev 8.4 0.0 3.8 25.8 13.7 0.4 1511.5 1030.7 1.69


Minimum 0.8 0.0 0.3 0.0 0.0 1.0 688.6 439.4 3.06
Maximum 33.1 0.1 15.4 98.9 51.4 2.0 5147.9 3113.6 9.82


Summary:
System: 4.43 Watts on average with standard deviation 1.69

(sorry for long post)

Thank you @dmxplx, I just suspended it for one hour and I lost 5% of battery.
It’s 58 Wh battery, so about 3W, sorry I miscalculated in the original post.
So suspend consumes 3W instead of 4.5 W for awake idle time according to powerstat.

To me it seems there is still a problem: I have multiple Dell laptops at work (not the same model, one older, one more recent) and I can keep them suspended a whole week-end 


https://www.dell.com/support/product-details/en-gb/product/latitude-14-7430-2-in-1-laptop/drivers

This? If its the wrong model then do not install the BIOS

I forgot to specify: my Latitude 7430 is the version without touchscreen (but they share the same UEFI as far as I understand).
Anyway I tried with many preceeding UEFI (updated regularly for over a year) and it behaved the same.

Ah. Gotcha. Worth checking though

@ahonorat

It is not that bad.
But, the logs confirm the machine is using s2idle (only).
When you run this

cat /sys/power/mem_sleep
cat /sys/power/state
sudo dmesg | grep -iE ‘acpi.*(s3|sleep)|s3|deep’

Do you onyl have this?

[s2idle]

Well it’s not that bad but I know it can be better :wink:
With Windows on the same laptop I have at least twice lower battery drain (only 1-2% battery per hour or so, using modern standby and without hibernation).

Here are the requested outputs:

$ cat /sys/power/mem_sleep
[s2idle]

$ cat /sys/power/state
freeze mem disk

$ sudo dmesg | grep -iE ‘acpi.*(s3|sleep)|s3|deep’
[ 0.200751] Performance Events: XSAVE Architectural LBR, PEBS fmt4±baseline, AnyThread deprecated, Alderlake Hybrid events, 32-deep LBR, full-width counters, Intel PMU driver.
[ 1.214427] ACPI: button: Sleep Button [SBTN]
[ 6.608737] xe 0000:00:02.0: [drm] Tile0: GT0: vcs3 fused off
[ 6.608748] xe 0000:00:02.0: [drm] Tile0: GT0: vecs3 fused off

Thank you again for your help!

1 Like