Failure to switch off when hibernating

[pm2]

I've recently updated my HP laptop from Linux Mint 17.3 Rosa (64-bit) KDE to Linux Mint 18.2 Sonya (64-bit) KDE. Previously hibernation worked fine. Now the hibernation still works except that the machine does not switch off. I have to forceably switch off at the power switch after I've left sufficient time for the archiving to have occurred. On resume, assuming I left enough time for the satisfactory archiving, the machine can successfully come back but it is slower than previously. I have to wait for the clock to change from the time at hibernation to the current time. Any ideas to the cause?

Details:

Code: Select all

PM1024 ~ # inxi -mP
Memory:    Array-1 capacity: 16 GB devices: 2 EC: None
           Device-1: Bottom-Slot 1(top) size: 4 GB speed: 1600 MHz type: DDR3
           Device-2: Bottom-Slot 2(under) size: 4 GB speed: 1600 MHz type: DDR3
Partition: ID-1: / size: 87G used: 13G (16%) fs: ext4 dev: /dev/sda6
           ID-2: swap-1 size: 9.86GB used: 0.99GB (10%) fs: swap dev: /dev/sda7
PM1024 ~ # inxi -Fxz
System:    Host: PM1024 Kernel: 4.10.0-38-generic x86_64 (64 bit gcc: 5.4.0) Desktop: KDE Plasma 5.8.7 (Qt 5.6.1)
           Distro: Linux Mint 18.2 Sonya
Machine:   System: Hewlett-Packard (portable) product: HP Pavilion g6 Notebook PC v: 087C110000345D10000620100
           Mobo: Hewlett-Packard model: 183F v: 56.32 Bios: Insyde v: F.25 date: 05/29/2013
CPU:       Dual core Intel Core i3-3110M (-HT-MCP-) cache: 3072 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 9577
           clock speeds: max: 2400 MHz 1: 1200 MHz 2: 1200 MHz 3: 1199 MHz 4: 1200 MHz
Graphics:  Card: Intel 3rd Gen Core processor Graphics Controller bus-ID: 00:02.0
           Display Server: X.org 1.18.4 drivers: intel (unloaded: fbdev,vesa)
           tty size: 192x45 Advanced Data: N/A for root
Audio:     Card Intel 7 Series/C210 Series Family High Definition Audio Controller
           driver: snd_hda_intel bus-ID: 00:1b.0
           Sound: Advanced Linux Sound Architecture v: k4.10.0-38-generic
Network:   Card-1: Ralink RT5390R 802.11bgn PCIe Wireless Network Adapter
           driver: rt2800pci v: 2.3.0 bus-ID: 01:00.0
           IF: wlo1 state: up mac: <filter>
           Card-2: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller
           driver: r8169 v: 2.3LK-NAPI port: 3000 bus-ID: 02:00.0
           IF: eno1 state: down mac: <filter>
Drives:    HDD Total Size: 1000.2GB (2.3% used) ID-1: /dev/sda model: ST1000LM024_HN size: 1000.2GB temp: 33C
Partition: ID-1: / size: 87G used: 13G (16%) fs: ext4 dev: /dev/sda6
           ID-2: swap-1 size: 9.86GB used: 0.99GB (10%) fs: swap dev: /dev/sda7
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 56.0C mobo: N/A
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 231 Uptime: 7 days Memory: 2842.7/7873.8MB Init: systemd runlevel: 5 Gcc sys: 5.4.0
           Client: Shell (bash 4.3.481) inxi: 2.2.35

[Petermint]

Something similar happened on my machine then went away after a few updates. I also switched to a later kernel to fix one problem. Look for startup errors and shutdown errors in the system log. Does your machine work differently connected to the network when compared to Wifi/Ethernet off?

[pm2]

I've looked through the logs but I haven't found anything that leads me to the route of the problem. I've tried using the machine connected to the internet via WiFi and via physical connection, and also with no connection. In all cases the response is the same in that the hibernate works expect for actually switching off the machine.

[pm2]

Since 'upgrading' to Kernel: 4.13.0-31-generic x86_64 (64 bit Gcc:5.4.0) it now appears that resume fails. It claims to be resuming but the screen goes blank. Rebooting appears to be the only option thereafter.

[BG405]

I'd suggest trying the latest kernel from the 4.4 series, that may work better with your hardware which is approx. 4 years old. Also, your hibernate issue may be exacerbated by having a swap not much bigger than the installed RAM ... and I see that about 1GB was in use leaving very little headroom. It could simply be running out of space when hibernating.

The clock not updating at first is in fact quite handy; you can see when the system state has been (almost?) restored and it's ready to use.

Does Sleep (suspend-to-RAM) work OK?

[pm2]

'Suspend' seems to still work fine.