For quite a long time, I've been unable to recover my computer after suspending with `sudo systemctl suspend` or hibernate. This has been a very big problem for and its really affecting my productivity.
My machine successfully suspends but an attempt to recover it only brings up the keyboard light, motherboard fans, and WiFi indicator. But the screen doesn't come back on.
I've tried out possible solutions from the resources I've come across on the internet all to no avail.
On running `journalctl` I see that the system reached the sleep target but the sleep is a deep one.
The error log succeeding (bears the word Reboot) it is escaped and I don't know why that is that.
Code:
Jul 12 22:00:35 hp wpa_supplicant[1379]: ^[[0;1;39m^[[0;1;39mnl80211: deinit ifname=wlo1 disabled_11b_rates=0
Jul 12 22:00:36 hp systemd[1]: Starting Suspend...
Jul 12 22:00:36 hp systemd-sleep[5399]: Suspending system...
Jul 12 22:00:36 hp kernel: PM: suspend entry (deep)
^[[0;1;39m-- Reboot --
Jul 12 22:02:00 hp kernel: microcode: microcode updated early to revision 0x7, date = 2018-04-23
Jul 12 22:02:00 hp kernel: ^[[0;1;39m^[[0;1;39mLinux version 5.3.0-62-generic (buildd@lcy01-amd64-004) (gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)) #56~18.04.1-Ubuntu SMP Wed Jun 2Jul 12 22:02:00 hp kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=122abf7e-c4ab-4d19-9759-14a69b0ed4d5 ro nouveau.modeset=0 quiet splash vt.handoff=1
Jul 12 22:02:00 hp kernel: KERNEL supported cpus:
The only way I'm able to recover is by pressing the power button down for a complete shutdown. Then I boot back up.
I'm thinking the problem of recovering from suspend has to do with the inability of systemd to execute the graphical target.
I run an Ubuntu 18.04 LTS on a HP 8440p, Intel core i5 vPro (dual core).
On executing `dmesg | grep -i acpi`, I noticed that there's a conflict between to acpi drivers. Does this give pointers towards the root cause of my problem?
Code:
[ 1.546863] battery: ACPI: Battery Slot [BAT0] (battery present)
[ 1.546980] battery: ACPI: Battery Slot [BAT1] (battery absent)
[ 3.437500] acpi PNP0C14:01: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
[ 23.485642] parport_pc 00:04: reported by Plug and Play ACPI
[ 35.542208] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20190703/utaddress-213)
[ 35.542214] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 35.542217] ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20190703/utaddress-213)
[ 35.542219] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 35.542220] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20190703/utaddress-213)
[ 35.542223] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 35.542223] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20190703/utaddress-213)
[ 35.542226] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 38.114067] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no)
[ 38.119524] acpi device:0d: registered as cooling_device4
I will please like to be shown on how to go about debugging this problem.
Thank you.
Edit 1:
So far, nothing has seemed to work. I'm considering downgrading the Linux kernel to a 4.x as suggested by some people but I'm kind of skeptical on that being a solution.
I also noticed that after a long while of not using the PC, it automatically suspends on its own. Then click a key or hovering over the mouse brings back the screen up but in a frozen state.
A hard shutdown (pressing the power button for a few seconds) is the only remedy out of this state.
One thing I'm also surprised about is some characters in Journalctl getting escaped. This is a problem as the logs don't provide enough information about the system state when the PC suspends. All log entries after suspend are escaped and the next entry following it describes the Kernel initialization during the booting phase.
So a siginificant portion of logs detailing what occurs after
systemctl suspendand the failed wake is missing.
