Dell XPS 13 (9360) defaults to s2idle sleep/suspend instead of deep (suspend to ram)

Bug #1860390 reported by Esokrates
66
This bug affects 12 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

This is a reintroduction of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957 which I am experiencing with Ubuntu 20.04 fully upgraded on a Dell XPS 13 9360. This did not happen before in Ubuntu 19.04 nor in Ubuntu 19.10 (Eoan), so this issue is affecting Ubuntu kernels >= 5.4.

It seems that the Dell 9360 is set to go into s2idle mode rather than deep sleep, forgoing significant power savings.

I have confirmed this by suspending and then checking:
sudo journalctl | grep "PM: suspend" | tail -2. If the output is

PM: suspend entry (s2idle)
PM: suspend exit

cat /sys/power/mem_sleep showed

[s2idle] deep

As a temporary fix, I typed
echo deep > /sys/power/mem_sleep
as a root user (sudo -i).

Then the output of cat /sys/power/mem_sleep was
s2idle [deep]

After suspending now,
sudo journalctl | grep "PM: suspend" | tail -2 returns

PM: suspend entry (deep)
PM: suspend exit

I have made this permanent by editing
/etc/default/grub

and replacing
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
with
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep"

then regenerating my grub configuration (sudo update-grub).
---
ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-9-generic.
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: PCH [HDA Intel PCH], device 0: ALC3246 Analog [ALC3246 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: user 1570 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0xdc228000 irq 131'
   Mixer name : 'Realtek ALC3246'
   Components : 'HDA:10ec0256,1028075b,00100002 HDA:8086280b,80860101,00100000'
   Controls : 55
   Simple ctrls : 17
CurrentDesktop: GNOME
DistroRelease: Ubuntu 20.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 8087:0a2b Intel Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
 /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
 /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
     |__ Port 3: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M
     |__ Port 3: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M
MachineType: Dell Inc. XPS 13 9360
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-9-generic root=UUID=be0fafa9-2c93-4717-bc39-06d8bbf0a232 ro rootflags=subvol=@ resume=UUID=9b786c9e-5b9c-4651-bc7a-85faf191166c quiet splash i915.enable_psr=2 i915.enable_fbc=1 i915.enable_psr=2 i915.enable_fbc=1 mem_sleep_default=deep vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-9-generic N/A
 linux-backports-modules-5.4.0-9-generic N/A
 linux-firmware 1.184
Tags: focal
Uname: Linux 5.4.0-9-generic x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: cdrom lp lpadmin plugdev sudo
WifiSyslog:

_MarkForUpload: False
dmi.bios.date: 11/14/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.13.0
dmi.board.name: 04N87K
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr2.13.0:bd11/14/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn04N87K:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9360
dmi.product.sku: 075B
dmi.sys.vendor: Dell Inc.

Esokrates (esokrarkose)
tags: added: focal
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1860390

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Esokrates (esokrarkose) wrote : AlsaDevices.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Esokrates (esokrarkose) wrote : AplayDevices.txt

apport information

Revision history for this message
Esokrates (esokrarkose) wrote : CRDA.txt

apport information

Revision history for this message
Esokrates (esokrarkose) wrote : Card0.Amixer.values.txt

apport information

Revision history for this message
Esokrates (esokrarkose) wrote : Card0.Codecs.codec.0.txt

apport information

Revision history for this message
Esokrates (esokrarkose) wrote : Card0.Codecs.codec.2.txt

apport information

Revision history for this message
Esokrates (esokrarkose) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Esokrates (esokrarkose) wrote : Lspci.txt

apport information

Revision history for this message
Esokrates (esokrarkose) wrote : Lsusb-v.txt

apport information

Revision history for this message
Esokrates (esokrarkose) wrote : PciMultimedia.txt

apport information

Revision history for this message
Esokrates (esokrarkose) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Esokrates (esokrarkose) wrote : ProcEnviron.txt

apport information

Revision history for this message
Esokrates (esokrarkose) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Esokrates (esokrarkose) wrote : ProcModules.txt

apport information

Revision history for this message
Esokrates (esokrarkose) wrote : PulseList.txt

apport information

Revision history for this message
Esokrates (esokrarkose) wrote : RfKill.txt

apport information

Revision history for this message
Esokrates (esokrarkose) wrote : UdevDb.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Esokrates (esokrarkose)
description: updated
Revision history for this message
Jimisola Laursen (jimisola) wrote :

This bug affects me on Dell XPS 7390 with Ubuntu 19.10 (Linux turing2 5.3.0-26-generic #28-Ubuntu SMP Wed Dec 18 05:37:46 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux)

Revision history for this message
Marciano Siniscalchi (msiniscalchi) wrote :

I have the exact same device as the OP and followed the same upgrade path. Prior to upgrading to Focal, suspend used deep sleep. Now it uses s2idle, with considerable adverse effects on battery life.

Cutting and pasting from journalctl output:

...
Apr 01 12:20:47 XPS-13-linux kernel: PM: suspend entry (deep)
Apr 01 14:00:23 XPS-13-linux kernel: PM: suspend exit
Apr 01 17:40:10 XPS-13-linux kernel: PM: suspend entry (deep)
Apr 01 18:51:04 XPS-13-linux kernel: PM: suspend exit
Apr 04 19:37:39 XPS-13-linux kernel: PM: suspend entry (s2idle)
Apr 04 21:21:08 XPS-13-linux kernel: PM: suspend exit
Apr 04 22:15:33 XPS-13-linux kernel: PM: suspend entry (s2idle)
Apr 05 05:03:52 XPS-13-linux kernel: PM: suspend exit
Apr 05 11:35:00 XPS-13-linux kernel: PM: suspend entry (s2idle)
Apr 05 12:21:48 XPS-13-linux kernel: PM: suspend exit
Apr 05 12:40:56 XPS-13-linux kernel: PM: suspend entry (s2idle)
Apr 05 13:58:44 XPS-13-linux kernel: PM: suspend exit
Apr 05 14:44:53 XPS-13-linux kernel: PM: suspend entry (s2idle)
Apr 05 15:23:53 XPS-13-linux kernel: PM: suspend exit

Revision history for this message
stelian (stelian) wrote :

Same bug here, just upgraded from Eoan. Dell XPS 9360.

Revision history for this message
Robbob (rob-kirkbride) wrote :

Same here on a XPS 13 9370.

Revision history for this message
Stanislav German-Evtushenko (giner) wrote :

The same issue on Dell Latitude 5300 running both Ubuntu 18.04.5 and and Ubuntu 20.04.1

$ cat /sys/power/mem_sleep
[s2idle] deep

Revision history for this message
Steve Kroon (kroon) wrote :

I have the same issue on a Dell Latitude 5420 - and I can not use the workaround described in the question - writing to /sys/power/mem_sleep seems to be prohibited, even for a root user:

$ ls -als /sys/power/mem_sleep
0 -rw-r--r-- 1 root root 4096 Mar 3 17:16 /sys/power/mem_sleep
$ sudo echo deep > /sys/power/mem_sleep
bash: /sys/power/mem_sleep: Permission denied

Revision history for this message
Leonard Lausen (leezu) wrote :

Steve, you are executing echo as root but not writing to /sys/power/mem_sleep at root. Try switching to a root shell (sudo su) first. To make the workaround permanent, you can rely on systemd-tmpfiles to write the "deep" by creating a file /etc/tmpfiles.d/mem_sleep.conf containing:

# Path Mode UID GID Age Argument
w /sys/power/mem_sleep - - - - deep

Revision history for this message
Koen Roggemans (koen-roggemans) wrote :

Same problem on Dell 5540 clean install Ubuntu 24.04
I also can't change /sys/power/mem_sleep, also not with the method suggested by leezu. The systemd-tmpfiles method also doesn't change the file.

The method of the OP of replacing
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
with
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep"

doesn't help either. Still gives

koenr@koenr-Latitude-5540:~$ sudo journalctl | grep "PM: suspend" | tail -2
jul 10 20:06:16 koenr-Latitude-5540 kernel: PM: suspend entry (s2idle)
jul 10 20:06:25 koenr-Latitude-5540 kernel: PM: suspend exit

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.