During boot process, system goes to sleep

[flrtx]

After upgrading to 16.04, my computer goes to sleep during the boot process, shortly after I entered the passphrase to unlock my LVM. When I wake it up, I’m at the graphical login prompt. I type my user password, press enter and it goes to sleep again. When I wake it up, I’m in my working Lubuntu desktop. This happens every time I boot. And it’s quite annoying.
Please tell me which additional information I can provide to help fix this bug.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-38-generic 4.4.0-38.57
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic i686
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: steffi 2155 F.... lxpanel
CurrentDesktop: LXDE
Date: Thu Sep 22 20:24:31 2016
HibernationDevice: RESUME=UUID=9e305c00-cee8-4703-9352-abc5fb755282
InstallationDate: Installed on 2016-09-21 (1 days ago)
InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
MachineType: Acer Aspire one
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic root=/dev/mapper/lubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-38-generic N/A
 linux-backports-modules-4.4.0-38-generic N/A
 linux-firmware 1.157.3
SourcePackage: linux
UpgradeStatus: Upgraded to xenial on 2016-09-22 (0 days ago)
dmi.bios.date: 02/20/2009
dmi.bios.vendor: Acer
dmi.bios.version: V1.05
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Aspire one
dmi.board.vendor: Acer
dmi.board.version: V1.05
dmi.chassis.type: 1
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.05
dmi.modalias: dmi:bvnAcer:bvrV1.05:bd02/20/2009:svnAcer:pnAspireone:pvrV1.05:rvnAcer:rnAspireone:rvrV1.05:cvnAcer:ct1:cvrV1.05:
dmi.product.name: Aspire one
dmi.product.version: V1.05
dmi.sys.vendor: Acer

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.4 stable kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.23

[flrtx (fltrx)]

Thanks for your advice, Joseph.

I installed kernel v4.4.28 and booted using this kernel. Unfortunatelly, the bug is still there.

[flrtx (fltrx)]

I now upgraded my Ubtunu to 17.04 and the bug is still there. Could you, please, please look into this. It makes it really hard to use my computer.

[Kai-Heng Feng (kaihengfeng)]

Do you still have older kernel in machine? E.g. 3.13, 3.19. Boot from older kernel to see if the problem persists.

Furthermore, can you try latest live usb from [1]?

[1] http://cdimages.ubuntu.com/lubuntu/daily-live/current/artful-desktop-amd64.iso

[flrtx (fltrx)]

I only have 4.10.0-20 and 4.8.0-20. I tried them both. It’s the same.

I also tried booting in upstart mode (since I was in the Grub prompt). The boot process works better, the system doesn’t go to sleep during boot. However, the GUI doesn’t load and I only have a console, which I can’t even use to shut the computer down ('failed to talk to init service'). But still, is this an indication my problem has to do with systemd?

[Kai-Heng Feng (kaihengfeng)]

Try these kernel parameters:
button.lid_init_state=open
button.lid_init_state=method
button.lid_init_state=ignore

See which one works.

[flrtx (fltrx)]

I upgraded my machine to 17.10 and the bug is still there.

[Kai-Heng Feng (kaihengfeng)]

Did you try #8?

[flrtx (fltrx)]

I now tried the kernel parameters. 'button.lid_init_state' works around the bug when set to 'open' or 'ignore'. The system boots without going to sleep. When I set it to 'method', the system doesn't boot at all.
Does that help to track down the source of the bug?

[dino99 (9d9)]

Should be good to know about a possible damaged 'profile'. Please test via an other 'user' login (create one if needed).
If logging with that new user does not expose that problem, then that mean your 'profile' is borked.

[flrtx (fltrx)]

The system goes to sleep before even getting to the login prompt. So it can’t be a corrupted profile, can it?

[Kai-Heng Feng (kaihengfeng)]

When you set it to open/ignore, can you successfully suspend the laptop by closing the lid?

[flrtx (fltrx)]

No, suspending the laptop doesn’t work when set to open or ignore. The screen locks but the system doesn’t suspend.

[flrtx (fltrx)]

An upgrade to 18.04 LTS (kernel 4.15) didn’t fix this bug.

[Marty M. (technomooney)]

I am having the. Same issue (in the logs it even says suspend system) and the big problem with me is the sleep function is (or seems to be) broken and it can't get out of sleep mode... So this essentially makes my system a paperweight till this can be figured out or till the sleep function is working properly...

The issue though is it didn't do that right after install. It just randomly started doing that after I booted from a parted magic live CD.

I'm on 18.04 and I have a Lenovo yoga 11e 3rd gen winbox (i got rid of windows) type 20GA if needed can get other info if needed....

[Kai-Heng Feng (kaihengfeng)]

flrtx, can you try latest mainline kernel and attach full dmesg?

This new commit will be useful for debugging lid issues:
commit ae35d656d796fa203787455ce59874c6682dc0cf
Author: Hans de Goede <email address hidden>
Date: Wed Nov 22 16:06:11 2017 +0100

    ACPI: button: Add a debug message when we're sending a LID event

[Kai-Heng Feng (kaihengfeng)]

Marty M.,
Please file a separate bug, thanks!

[Jorge Minguet (jjminguet)]

Hi
I have the same problem in Lubuntu 18.04 with same laptop Acer Aspire One. Please see attached photo of booting screen with errors about "suspend / resume device". I hope it helps to solve problem.
Regards,
Geo.

[Michal Hagara (haagrid)]

Hi,

I've came across this bug report, when dealing with the same problem on Dell E7450 (pretty much always docked) on kernel 5.9.11.

For anyone who stumbles upon this:

button.lid_init_state=open itself wasn't satisfactory, because it left my laptop display ON of course, making it the main one. I've took the naive approach, as my laptop is pretty much docker all the time.

cat /etc/X11/xinit/xinitrc.d/10-lid-workaround.sh
#!/usr/bin/bash

display_cnt=$(xrandr | grep -c " connected")
if [ $display_cnt -eq 3 ]; then
  xrandr --output DP1-1 --auto --left-of DP1-2 --output eDP1 --off
fi

which turns the laptop display off after login, while maintaing monitor arrangemment I want ....display names might differ in your case.

[Rodger Cespedes (rodcespe)]

Hi Everyone,

Hope you're doing well!

wanted to share some feedback on what i have found!

I was struggling because I was facing the same symptoms mention in this bug. My Laptop would bootup just fine it would reach all the way up to the user login screen, I would then type my user and password and then a few seconds will go by and my pc will go into standby mode. what I have found to resolve my issue was adding the acpi=off in the GRUB_CMDLINE_LINUX_DEFAULT. I also added additional commands which didn't help to fix the problem but in the end i kept them in the GRUB_CMDLINE_LINUX_DEFAULT.

I was able to manage to resolve this bug by editing the GRUB and did the following:

Step 1 edit Grub
sudo nano /etc/default/grub

Step 2 Edit linke
I edited this line:
GRUB_CMDLINE_LINUX_DEFAULT="quiet"

And replace it with this line:
GRUB_CMDLINE_LINUX_DEFAULT="nomodeset noplymouth button.lid_init_state=ignore intel_idle.max_cstate=4 acpi=off"

Step 3 Save
then save the grub file.

Step 4 Then update grub
sudo update-grub

Step 5 Then reboot
then go ahead and reboot your PC and it should resolve this issue.

Would like to share this link as reference which helped me figure this out
https://ubuntuforums.org/showthread.php?t=2404968