04-09-2018 03:03 PM - edited 04-09-2018 03:09 PM
TLDR: My new E480 (Intel GPU) has trouble with sleep power consumption. I managed to narrow the problem down to an additional Stick of RAM I recently installed. With just the stock 4GB RAM installed, the system drains about 0.25W in sleep, with the 8GB stick installed it will drain 1.6W - resulting in a loss of about 40% of battery over night. Can a faulty RAM stick consume that much power? Or is this even normal?! Further diagnostic information below.
Below is an excerpt of the Linux Kernel Log of the sleep/wakeup process, confirming that ACPI S3 sleep is actually entered. Additionally, I have added the output of dmidecode -t memory to show you the stats Linux picks up about the RAM.
[ 1217.050622] PM: suspend entry (deep) [ 1217.050624] PM: Syncing filesystems ... done. [ 1217.059044] Freezing user space processes ... (elapsed 0.002 seconds) done. [ 1217.061422] OOM killer disabled. [ 1217.061423] Freezing remaining freezable tasks ... (elapsed 0.000 seconds) done. [ 1217.062450] Suspending console(s) (use no_console_suspend to debug) [ 1217.253042] wlp5s0: deauthenticating from xx:xx:xx:xx:xx:xx by local choice (Reason: 3=DEAUTH_LEAVING) [ 1217.260879] wlp5s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22) [ 1217.261257] pcieport 0000:00:1d.2: AER: Corrected error received: id=00ea [ 1217.261274] pcieport 0000:00:1d.2: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00ea(Receiver ID) [ 1217.261278] pcieport 0000:00:1d.2: device [8086:9d1a] error status/mask=00000001/00002000 [ 1217.261282] pcieport 0000:00:1d.2: [ 0] Receiver Error (First) [ 1218.723575] ACPI: Preparing to enter system sleep state S3 [ 1218.808616] ACPI: EC: event blocked [ 1218.808617] ACPI: EC: EC stopped [ 1218.808619] PM: Saving platform NVS memory [ 1218.808630] Disabling non-boot CPUs ... [ 1218.829383] smpboot: CPU 1 is now offline [ 1218.845370] smpboot: CPU 2 is now offline [ 1218.870042] smpboot: CPU 3 is now offline [ 1218.884945] smpboot: CPU 4 is now offline [ 1218.899255] smpboot: CPU 5 is now offline [ 1218.921009] smpboot: CPU 6 is now offline [ 1218.933111] smpboot: CPU 7 is now offline [ 1218.937446] ACPI: Low-level resume complete [ 1218.937566] ACPI: EC: EC started [ 1218.937567] PM: Restoring platform NVS memory [ 1218.938352] Enabling non-boot CPUs ... [ 1218.938414] x86: Booting SMP configuration: [ 1218.938415] smpboot: Booting Node 0 Processor 1 APIC 0x2 [ 1218.939780] cache: parent cpu1 should not be sleeping [ 1218.939954] CPU1 is up [ 1218.939976] smpboot: Booting Node 0 Processor 2 APIC 0x4 [ 1218.941327] cache: parent cpu2 should not be sleeping [ 1218.941505] CPU2 is up [ 1218.941528] smpboot: Booting Node 0 Processor 3 APIC 0x6 [ 1218.942890] cache: parent cpu3 should not be sleeping [ 1218.943083] CPU3 is up [ 1218.943113] smpboot: Booting Node 0 Processor 4 APIC 0x1 [ 1218.944557] cache: parent cpu4 should not be sleeping [ 1218.944760] CPU4 is up [ 1218.944824] smpboot: Booting Node 0 Processor 5 APIC 0x3 [ 1218.946161] cache: parent cpu5 should not be sleeping [ 1218.946372] CPU5 is up [ 1218.946401] smpboot: Booting Node 0 Processor 6 APIC 0x5 [ 1218.947743] cache: parent cpu6 should not be sleeping [ 1218.947968] CPU6 is up [ 1218.947989] smpboot: Booting Node 0 Processor 7 APIC 0x7 [ 1218.949337] cache: parent cpu7 should not be sleeping [ 1218.949572] CPU7 is up [ 1218.955265] ACPI: Waking up from system sleep state S3 [ 1219.113251] thinkpad_acpi: unknown possible thermal alarm or keyboard event received [ 1219.113253] thinkpad_acpi: unhandled HKEY event 0x6032 [ 1219.113254] thinkpad_acpi: please report the conditions when this event happened to email@example.com [ 1219.180760] ACPI: EC: event unblocked [ 1219.181147] iwlwifi 0000:05:00.0: RF_KILL bit toggled to enable radio. [ 1219.190389] r8169 0000:03:00.0 enp3s0: link down [ 1219.417109] usb 1-6: reset high-speed USB device number 2 using xhci_hcd [ 1220.120008] psmouse serio1: synaptics: queried max coordinates: x [..5676], y [..4690] [ 1220.169231] psmouse serio1: synaptics: queried min coordinates: x [1266..], y [1162..] [ 1220.352976] OOM killer enabled. [ 1220.352979] Restarting tasks ... done. [ 1220.380403] [drm] RC6 on [ 1220.629674] PM: suspend exit [ 1223.621727] EXT4-fs (dm-1): re-mounted. Opts: data=ordered,commit=600 [ 1223.643784] EXT4-fs (nvme0n1p2): re-mounted. Opts: data=ordered,commit=600 [ 1224.040677] wlp5s0: authenticate with xx:xx:xx:xx:xx:xx [ 1224.043344] wlp5s0: send auth to xx:xx:xx:xx:xx:xx (try 1/3) [ 1224.044692] wlp5s0: authenticated [ 1224.045815] wlp5s0: associate with xx:xx:xx:xx:xx:xx (try 1/3) [ 1224.047087] wlp5s0: RX AssocResp from xx:xx:xx:xx:xx:xx (capab=0x11 status=0 aid=2) [ 1224.048539] wlp5s0: associated [ 1224.056938] wlp5s0: Limiting TX power to 24 (30 - 6) dBm as advertised by xx:xx:xx:xx:xx:xx [ 1230.270729] EXT4-fs (dm-1): re-mounted. Opts: data=ordered,commit=600 [ 1230.276608] EXT4-fs (nvme0n1p2): re-mounted. Opts: data=ordered,commit=600 [ 1230.346535] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 1230.347486] ehci-pci: EHCI PCI platform driver [ 1230.352170] uhci_hcd: unknown parameter 'ehci_hcd' ignored [ 1230.352174] uhci_hcd: unknown parameter 'usbhid' ignored [ 1230.352368] uhci_hcd: USB Universal Host Controller Interface driver
Handle 0x0004, DMI type 17, 40 bytes Memory Device Array Handle: 0x0003 Error Information Handle: Not Provided Total Width: 64 bits Data Width: 64 bits Size: 8192 MB Form Factor: SODIMM Set: None Locator: ChannelA-DIMM0 Bank Locator: BANK 0 Type: DDR4 Type Detail: Synchronous Unbuffered (Unregistered) Speed: 2400 MT/s Manufacturer: 859B Serial Number: 1A1DF23B Asset Tag: None Part Number: CT8G4SFD824A.C16FHP Rank: 2 Configured Clock Speed: 2400 MT/s Minimum Voltage: Unknown Maximum Voltage: Unknown Configured Voltage: 1.2 V
Solved! Go to Solution.
04-13-2018 09:50 AM
I resolved the issue by returned the RAM stick and getting a new one, which is single rank. I don't know whether the issue was due to a faulty stick or a systematic issue with dual rank RAM. The device now consumes about 0.3W in standby, which seems much more normal.