Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

[SOLVED]suspend fails

Linux Kernel, Network, and Services configuration.
Post Reply
Message
Author
boopw
Posts: 3
Joined: 2019-06-03 23:39

[SOLVED]suspend fails

#1 Post by boopw »

Hi,
I'm running Debian Stretch recently installed, I cannot get my laptop resume after suspending, it seems like the suspend ends up shutting down the system.
Here's what I could get from the logs but I don't know where to look next, any help would be appreciated...

Before suspend:

Code: Select all

systemd[1]: Reached target Sleep.
systemd[1]: Starting Suspend...
systemd-sleep[5704]: Suspending system...
(that's the last thing I found, then resume process)

When trying to resume (it end up rebooting):

Code: Select all

kernel: PM: Checking hibernation image partition /dev/disk/by-uuid/92f30772-c8c5-4272-ad92-a5f6b32846d3
kernel: PM: Hibernation image not present or could not be loaded.
kernel: PM: Starting manual resume from disk
kernel: PM: Hibernation image partition 8:12 present
kernel: PM: Looking for hibernation image.
kernel: PM: Image not found (code -22)
kernel: PM: Hibernation image not present or could not be loaded.
System infos:

Code: Select all

Linux version 4.9.0-9-amd64 (debian-kernel@lists.debian.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1) ) #1 SMP Debian 4.9.168-1+deb9u2 (2019-05-13)
Hardware:

Code: Select all

H/W path       Device      Class          Description
=====================================================
                           system         N501JW (ASUS-NotebookSKU)
/0                         bus            N501JW
/0/0                       memory         64KiB BIOS
/0/7                       processor      Intel(R) Core(TM) i7-4720HQ CPU @ 2.60GHz
/0/7/8                     memory         1MiB L2 cache
/0/7/9                     memory         256KiB L1 cache
/0/7/a                     memory         6MiB L3 cache
/0/b                       memory         8GiB System Memory
/0/b/0                     memory         4GiB SODIMM DDR3 Synchronous 1600 MHz (0.6 ns)
/0/b/1                     memory         DIMM [empty]
/0/b/2                     memory         4GiB SODIMM DDR3 Synchronous 1600 MHz (0.6 ns)
/0/b/3                     memory         DIMM [empty]
/0/100                     bridge         Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller
/0/100/1                   bridge         Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller
/0/100/1/0                 display        GM107M [GeForce GTX 960M]
/0/100/2                   display        4th Gen Core Processor Integrated Graphics Controller
/0/100/3                   multimedia     Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller
/0/100/14                  bus            8 Series/C220 Series Chipset Family USB xHCI
/0/100/14/0    usb3        bus            xHCI Host Controller
/0/100/14/0/1              input          USB Receiver
/0/100/14/0/5              communication  Bluetooth wireless interface
/0/100/14/0/7              multimedia     USB2.0 HD UVC WebCam
/0/100/14/0/a              input          SiS HID Touch Controller
/0/100/14/1    usb4        bus            xHCI Host Controller
/0/100/16                  communication  8 Series/C220 Series Chipset Family MEI Controller #1
/0/100/1a                  bus            8 Series/C220 Series Chipset Family USB EHCI #2
/0/100/1a/1    usb1        bus            EHCI Host Controller
/0/100/1a/1/1              bus            USB hub
/0/100/1b                  multimedia     8 Series/C220 Series Chipset High Definition Audio Controller
/0/100/1c                  bridge         8 Series/C220 Series Chipset Family PCI Express Root Port #1
/0/100/1c.2                bridge         8 Series/C220 Series Chipset Family PCI Express Root Port #3
/0/100/1c.2/0  wlp59s0     network        Wireless 7260
/0/100/1c.3                bridge         8 Series/C220 Series Chipset Family PCI Express Root Port #4
/0/100/1c.3/0              generic        RTS5227 PCI Express Card Reader
/0/100/1d                  bus            8 Series/C220 Series Chipset Family USB EHCI #1
/0/100/1d/1    usb2        bus            EHCI Host Controller
/0/100/1d/1/1              bus            USB hub
/0/100/1f                  bridge         HM87 Express LPC Controller
/0/100/1f.2                storage        8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode]
/0/100/1f.3                bus            8 Series/C220 Series Chipset Family SMBus Controller
/0/1           scsi4       storage        
[...]
/0/1/0.0.0/7   /dev/sda7   volume         9537MiB EXT4 volume
[...]
/0/1/0.0.0/c   /dev/sda12  volume         9536MiB Linux swap volume
[...]
/0/2           scsi5       storage        
[...]
note: I added the swap uuid (and nokaslr because I found this in some previous posts...) in grub configuration:

Code: Select all

$ cat /etc/default/grub 
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
#   info -f grub -n 'Simple configuration'

GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet nokaslr resume=/dev/disk/by-uuid/92f30772-c8c5-4272-ad92-a5f6b32846d3"
GRUB_CMDLINE_LINUX=""

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"
Thanks
Last edited by boopw on 2019-06-09 19:25, edited 1 time in total.

User avatar
Head_on_a_Stick
Posts: 14114
Joined: 2014-06-01 17:46
Location: London, England
Has thanked: 81 times
Been thanked: 133 times

Re: suspend fails

#2 Post by Head_on_a_Stick »

How are you attempting to suspend?

Why do the logs refer to hibernation instead?

You should use /etc/initramfs-tools/conf.d/resume to set the resume device (and regenerate the initramfs afterwards) but that is for hibernation rather than suspend.

Try the acpi_sleep= kernel parameter:

https://askubuntu.com/questions/713805/ ... -power-off
deadbang

boopw
Posts: 3
Joined: 2019-06-03 23:39

Re: suspend fails

#3 Post by boopw »

Hi,

the device is already set in /etc/initramfs-tools/conf.d/resume (to the swap partition uuid)

no chance with "acpi_sleep=nonvs" but it seems to be a very peculiar case

I tried different things to suspend:

- using gnome buttons
- systemctl suspend
- power button (which does the same)

I got the same result. I think the suspend process fails for some reason, and then the system try to find a hibernation partition because it really powered off (I suppose...), it looks like the suspend process doesn't complete and the power switches off before it ends. I didn't see anything I could really change in the BIOS regarding power management.

User avatar
Head_on_a_Stick
Posts: 14114
Joined: 2014-06-01 17:46
Location: London, England
Has thanked: 81 times
Been thanked: 133 times

Re: suspend fails

#4 Post by Head_on_a_Stick »

Perhaps try a live version of Debian buster and see if that works any better.

Or update the motherboard firmware ("BIOS") but that can be risky.
deadbang

boopw
Posts: 3
Joined: 2019-06-03 23:39

Re: suspend fails

#5 Post by boopw »

Well indeed the BIOS was outdated, I upgraded from 209 to 211 and things work just fine,
I didn't think a slightly outdated BIOS could prevent this to work, the last version is only a few months younger than the one I had and it's from 2015.
Thanks for your help !

Post Reply