There is an odd behaviour of this XPS 13 9370 machine, that is:
If the machine was running on battery, and being charged, putting it into standby and disconnecting the power cable after few hours will render resume from standy impossible. This affects either opening the screen lid or pressing the power button.
In the moment the power cable is plugged in again, both start to work as expected and the user session in memory is resumed successfully.
Additionally, there is no visible clue from the outside, if the machine is actually in standby. The front LED only lights up orange in case battery is low.
It would be nice to have some flashing orange LED in the front, to see the machine is standing by. Closing the lid always makes me think it does not work at all, and the battery drainage during standby times suggests the machine may be running in fact.
How can we debug this further?
I can send your request to the development team about having the led blink when in standby. If you put the system in standby with no ac adapter plugged into it then, the battery will drain. It is still running and if you have a program running in the background it will drain it faster. If you do not want the system to drain battery then, you will need to turn the system off.
Jesse, thanks for the reply. Yes, please do forward my request to let the front LED blink slowly (in orange/white?) during standby.
It is just remarkable for me that I put the system in stand by and within 13 h of "sleep" the battery went down from 53 % to 35 %. This behaviour is a little surprising.
It may also be that Fedora 28 and its systemd make wrong use of the ACPI modes and don't put the system in the desired state (upon closing the lid, pressing the power button or clicking stand by in GNOME).
I now recall that I could try pinging the machine from the outside during that state, to check if it keeps running.
/:-------------:\ yala@pons :-------------------:: OS: Fedora 28 TwentyEight :-----------/shhOHbmp---:\ Kernel: x86_64 Linux 4.17.2-200.fc28.x86_64 /-----------omMMMNNNMMD ---: Uptime: 18h 24m :-----------sMMMMNMNMP. ---: Packages: 2115 :-----------:MMMdP------- ---\ Shell: zsh 5.5.1 ,------------:MMMd-------- ---: Resolution: 3840x2160 :------------:MMMd------- .---: DE: GNOME :---- oNMMMMMMMMMNho .----: WM: GNOME Shell :-- .+shhhMMMmhhy++ .------/ WM Theme: :- -------:MMMd--------------: GTK Theme: Adwaita [GTK2/3] :- --------/MMMd-------------; Icon Theme: Adwaita :- ------/hMMMy------------: Font: Cantarell 11 :-- :dMNdhhdNMMNo------------; CPU: Intel Core i7-8550U @ 8x 4GHz [25.0°C] :---:sdNMMMMNds:------------: GPU: Mesa DRI Intel(R) UHD Graphics 620 (Kabylake GT2) :------:://:-------------:: RAM: 3947MiB / 15755MiB :---------------------://
I agree about the lack of a standby LED; very annoying.
For your battery drain, try adding mem_sleep_default=deep to your kernel parameters. It worked for me.
Thank you. I believe this sleep state is already default in Fedora, remembering having read about this somewhere. Will need to double check.
Today the machine did not resume from stand by after being closed for half a day, starting off at 53%.
Given the missing standby LED indicator whenof closed or "turned off", I cannot tell if the system was booted up or in a sleeping state.
Together with the resume issue that sometimes the screen stays black only until the moment an AC adaptor is plugged in, whicofh defeats the mobility of a portable device, it seems the overall power componets are not manufactured in the best possible way.
Given the cost associated with obtaining that kind of machine, I am wondering how we here and support can improve upon this situation.
Thank you for this useful reference.
With hints from https://ask.fedoraproject.org/en/question/122579/mem_sleep_default-ignored-adding-initrd-images-perm... this led me discover
# cat /sys/power/mem_sleep [s2idle] deep
deep mode is indeed not enabled.
The same link also has a link to https://forums.lenovo.com/t5/Linux-Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka-S... with instructions how to update GRUB for UEFI systems. There is more useful advice in https://docs.fedoraproject.org/en-US/fedora/f28/system-administrators-guide/kernel-module-driver-con... The final series of commands to activate this are:
cat /sys/power/mem_sleep ls /sys/firmware/efi # to check for EFI enable boot efibootmgr # to confirm EFI enabled boot grubby --info=ALL grubby --update-kernel=ALL --args="mem_sleep_default=deep" grubby --info=ALL less /boot/efi/EFI/fedora/grub.cfg # to confirm the changes reboot
Let's see if this works, and if it maybe also helps with the resume issue.
Then we're only waiting for a small microcode patch to have more meaningful LED status activity, and we are back on track with power management in Linux.
Since this story turned into an epic which is unlikely to be solved easily, I have broken it down into: