I am a newbie and am having trouble with the SUSPEND option in the shut down area. The computer acts like the "suspend" function is working, but when I try to start back up, the computer hangs and requires a hard reboot.

I am using Linux Mint 18.2 on a 64 bit computer. I dual boot to win 10.

Thanks for any help. The "suspend" works in windows 10.

jessund

Hi jesseund and welcome to LQ.

Suggest you post your system specifications because this may have to do with how the system can suspend and what inputs will allow it to be signaled for waking up.

I would also recommend you obtaining the version and supplier of your BIOS from your startup screen.

1 members found this post helpful.

rtmisler....thanks for your reply. Below is data about my system:
--------------------------------------------------------
jesse@jesse-desktop ~ $ inxi -Fxzd
System: Host: jesse-desktop Kernel: 4.9.3-040903-generic x86_64 (64 bit gcc: 6.2.0)
Desktop: Cinnamon 3.4.4 (Gtk 3.18.9-1ubuntu3.3) Distro: Linux Mint 18.2 Sonya
Machine: Mobo: ASRock model: Z68 Pro3-M Bios: American Megatrends v: P1.50 date: 09/09/2011
CPU: Dual core Intel Core i3-2120 (-HT-MCP-) cache: 3072 KB
flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 13168
clock speeds: max: 3300 MHz 1: 1623 MHz 2: 1736 MHz 3: 1808 MHz 4: 1681 MHz
Graphics: Card: Intel 2nd Generation Core Processor Family Integrated Graphics Controller bus-ID: 00:02.0
Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa) Resolution: 1680x1050@59.95hz
GLX Renderer: Mesa DRI Intel Sandybridge Desktop GLX Version: 3.0 Mesa 12.0.6 Direct Rendering: Yes
Audio: Card Intel 6 Series/C200 Series Family High Definition Audio Controller
driver: snd_hda_intel bus-ID: 00:1b.0
Sound: Advanced Linux Sound Architecture v: k4.9.3-040903-generic
Network: Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
driver: r8169 v: 2.3LK-NAPI port: e000 bus-ID: 05:00.0
IF: enp5s0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives: HDD Total Size: 498.1GB (26.5% used) ID-1: /dev/sda model: OCZ size: 128.0GB
ID-2: /dev/sdb model: ST3250312AS size: 250.1GB ID-3: /dev/sdc model: SanDisk_SDSSDA12 size: 120.0GB
Optical: /dev/sr0 model: ATAPI iHAS224 B rev: GL0A dev-links: cdrom,cdrw,dvd,dvdrw
Features: speed: 48x multisession: yes
audio: yes dvd: yes rw: cd-r,cd-rw,dvd-r,dvd-ram state: running
Partition: ID-1: / size: 107G used: 39G (38%) fs: ext4 dev: /dev/sdc5
ID-2: swap-1 size: 4.10GB used: 0.00GB (0%) fs: swap dev: /dev/sdc1
RAID: No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors: System Temperatures: cpu: 42.0C mobo: N/A
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 239 Uptime: 2:41 Memory: 2373.8/7704.3MB Init: systemd runlevel: 5 Gcc sys: 5.4.0
Client: Shell (bash 4.3.481) inxi: 2.2.35
jesse@jesse-desktop ~ $
----------------------------------------------------
Getting SMBIOS data from sysfs.
SMBIOS 2.6 present.

Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
Vendor: American Megatrends Inc.
Version: P1.50
Release Date: 09/09/2011
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 8192 kB
Characteristics:
PCI is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
BIOS ROM is socketed
EDD is supported
5.25"/1.2 MB floppy services are supported (int 13h)
3.5"/720 kB floppy services are supported (int 13h)
3.5"/2.88 MB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
ACPI is supported
USB legacy is supported
BIOS boot specification is supported
Targeted content distribution is supported
BIOS Revision: 4.6

jesse@jesse-desktop ~ $
-------------------------------------------------
Hope this helps...jesseund

Try viewing the dmesg file where it falls asleep and fails to wake up: /var/log/dmesg.0 and/or dmesg.1.gz. That should tell you what is at work, and you can make adjustments in the usswsusp.conf. You can also try the pm-utils package of suspend and hibernate scripts. This link might get you started: https://wiki.archlinux.org/index.php..._and_hibernate

Your machine appears to be very capable of contending with suspend and resume, plus the fact that Windows can obviously do this. Therefore the BIOS is likely not in the way of this behavior.

I agree with AwesomeMachine that you should view your system log to understand what it is saying, however I fear that you'll see that it goes to one of the 'S' states for suspend to RAM, or suspend to disk, and then you may see no more information because that is sort of your problem, Linux is not recognizing the BIOS event which should wake the system back up.

It would be worth seeing if you can suspend to RAM and awake from that, versus suspend to disk (S3-hibernate).

Other things to check are the ACPI settings or the power management functions. The link offered by AwesomeMachine is a good read on those even if it is not a matching Linux distribution.

Here's a Debian article on that https://wiki.debian.org/Suspend.

I've actually done the opposite, which was to disable ACPI for a kiosk computer for make it so that it would never go to sleep and to test I had to do things like write to the correct file to put the system to sleep, to see that it did not go to sleep ... only to find that it did until I got my config correct. Meanwhile waking up for me in that case was a problem because it was a "no keyboard" system, also with no mouse and no touch screen - we had special buttons which were not interfaced normally like a keyboard, so the re-wake was "similar" but also not really supported.

My point there is that you can write the values to the correct PM or ACPI files and get the system to suspend to RAM and see if you can wake it from there.

And I would experiment with the various interfaces. Such as the power button (and check the power settings in your distribution to determine what it interprets the power button to be doing), but also mouse clicks, and keyboard presses. Not sure if this is a laptop computer, but if so, also check what the lid button does or doesn't do. There should be settings in the power settings for Debian.

I had identical issues with resuming with these kernel versions (well the 4.8 series)
Going back to 4.40-83 fixed this. You can try going to 4.10