Poweroff or reboot hangs. Laptop won't shutdown. 16.04

Bug #1594023 reported by Elio
334
This bug affects 68 people
Affects Status Importance Assigned to Milestone
Ubuntu
Confirmed
Undecided
Unassigned
linux (Ubuntu)
Confirmed
High
Unassigned

Bug Description

This is about a fresh Ubuntu 16.04 install on a new laptop (asus x540sa). After pressing the shutdown button in the start menu; the shutdown procedure starts and in the final splash screen the system just hangs. Tried a second time by pressing Esc once the splash screen showed up and I saw that it reaches the line "Reached target shutdown" and just stops there, no matter how long I leave it there the machine won't turn off.

I also tried a Kubuntu 16.04 fresh install on the same machine and it hanged too at the final splash screen where the pulsating logo stopped. Then I tried with Esc only to see the exact same line in the end.

The issue seems to affect lately quite many users as shown by the google results of the past month / week or so.

I have also tried shutting down from the console with shutdown -and all the parameters after that suggested online- and sudo poweroff but unfortunately they didn't do the trick. The exact same situation occurred.

Unmounting the swap as suggested online doesn't work.

Also rebooting the system is not working either due to the same issue.

So right now the only way for me to poweroff the machine is to press the power button on the keyboard continuously.

Reproducible: Always

Steps to Reproduce:
1.Install OS
2.Do something, anything or nothing
3.Try to shutdown or reboot

Actual Results:
The computer is not shutting down: "Reached target shutdown" and hangs there.

Expected Results:
Powering off the machine.

For what it's worth, closing the lid won't suspend the system, but using the menu buttons for suspension will do it.

Tags: cscc xenial
Revision history for this message
Elio (eliodisegno) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in systemd (Ubuntu):
status: New → Confirmed
Revision history for this message
Willem Pieter Groeneveld (limsgroen) wrote :

exactly the same here on my compaq presario c500

Changed in systemd (Ubuntu):
importance: Undecided → High
importance: High → Critical
Revision history for this message
jtarin (jtarin) wrote :

Same here

Revision history for this message
Don Nadie (don.nadie) wrote :

Just want to say I have the same problem.

Revision history for this message
jtarin (jtarin) wrote :

I solved this in my situation by adding the term "acpi=force" to the "GRUB_CMDLINE_LINUX_DEFAULT".

Revision history for this message
jtarin (jtarin) wrote :

In my situation I solved the problem by editing my Grub configuration.

 GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=force"

Revision history for this message
damiano (damiano1996) wrote :

I have the same problem with a notebook asus f402sa and I couldn't resolve it neither editing the grub configuration as you said.

Changed in systemd (Ubuntu):
assignee: nobody → damiano (damiano1996)
Revision history for this message
sciasbat (fabio-forno) wrote :

Same bug with an asus x540s

Martin Pitt (pitti)
affects: systemd (Ubuntu) → linux (Ubuntu)
Revision history for this message
Elio (eliodisegno) wrote :

After the last update my asus x540sa notebook seems to shut down and restart properly. Closing the lid still doesn't suspend the system though.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Does this bug still exist for folks after applying the latest updates as Elio did in comment #10?

Changed in linux (Ubuntu):
importance: Critical → High
Revision history for this message
jtarin (jtarin) wrote :

I'm still having the problem even after all current updates.

Revision history for this message
sciasbat (fabio-forno) wrote :

Fot me it's fixed with the latest update. Still very slow, you need need to wait up to 1 minute for the shutdown, but it works

Revision history for this message
Tari (tari-sk) wrote :

After yesterday update still not working for me. System still stuck on poweroff.

Revision history for this message
Michael Yarv (mixa-poison) wrote :

Hello,

I have exact the same problem with ASUS notebook.
Is there any quick fix for it?
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=force" didn't help me.

Revision history for this message
francis (a-c-f) wrote :

Hi, same problem here. I have lenovo yoga 500....

Revision history for this message
Tari (tari-sk) wrote :

When can we expect the FIX???

Revision history for this message
Andrew Smith (z-andrew-4) wrote :

I run LTS releases and ran into this Shutdown failure about the time the upgrade notification came through from 14.04, so did not investigate closely as I suspected it would go when I upgraded to 16.04. It didn't. Mine is a pretty standard i7 desktop with an SSD. I have noticed the following:
*When it fails I can either Suspend it or pop up a terminal and do "shutdown -h now". Both work immediately but,
*If Suspend is used, the following time I can do a normal Shutdown and it works normally. The normal Shutdown after that fails.
*If the terminal command is used, the following time I do a normal Shutdown it fails.
So somehow Suspend circumvents the problem for one time. I am no command line guru so I don't know what logs or files I should be looking at. Any suggestions?

Revision history for this message
Jakub T. Jankiewicz (jcubic) wrote :

I have similar problem but only reboot is not working and it hangs after display is turn off, the keyboard is highlighted but it don't respond to keyboard brightness buttons.

Revision history for this message
Thomas Franke (t-aus-o) wrote :

Again: When can we expect a FIX???

Revision history for this message
VinDSL (perfect-pecker) wrote :

Ran into this problem on my Dell 7010 i5 desktop machine, after doing a fresh 16.10 install -- first time it's happened with any OS that I've run on it.

In my case, I'm getting DRDY ERRs on shutdown/restart. Hangs for several minutes with my SSD activity light lit up solid. Eventually the errors time out, and it shuts down, but it's a painfully long process.

I downgraded the kernel to 4.4.x for shiggles. The LTS enablement stack, graphic stack, and so forth were foobar, of course, but it otherwise booted and shutdown normally.

It smells like a kernel bug, to me, at this point. I'll investigate further and post back, if I can put a finger on it.

Revision history for this message
Blackbug (blackbug-nx) wrote :

I am also facing the issue since a week. I upgraded few libs and installed xcfe DE on kubuntu and started having this issue. I have tried to modify the grub as well by adding the acpi line but doesnt help.

Revision history for this message
VinDSL (perfect-pecker) wrote :

UPDATE: I'm more convinced than ever, that this is a kernel bug.

I multi-booted the following 64-bit distros on my Dell 7010 i5-3470:
Ubuntu 16.10 Yakkety Yak, Linux Kernel 4.8.x (as described above)
openSUSE Tumbleweed, Linux Kernel 4.8.x (same problem)
Peppermint 7, Linux Kernel 4.4.x (no problems)

As an aside:
Windows 10 Pro (no problems)

Revision history for this message
Blackbug (blackbug-nx) wrote :

If I switch to runlevel 2,3 or 4 and then shutdown it successfully shutsoff.

This bug is seriously annoying now. I damaged my filesystem because of frequent improper shutdown.

Revision history for this message
jtarin (jtarin) wrote : Re: [Bug 1594023] Re: Poweroff or reboot hangs. Laptop won't shutdown. 16.04

So is the only solution kernel regression?

On Nov 3, 2016 7:35 AM, "Blackbug" <email address hidden> wrote:

> If I switch to runlevel 2,3 or 4 and then shutdown it successfully
> shutsoff.
>
> This bug is seriously annoying now. I damaged my filesystem because of
> frequent improper shutdown.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1594023
>
> Title:
> Poweroff or reboot hangs. Laptop won't shutdown. 16.04
>
> Status in linux package in Ubuntu:
> Confirmed
>
> Bug description:
> This is about a fresh Ubuntu 16.04 install on a new laptop (asus
> x540sa). After pressing the shutdown button in the start menu; the
> shutdown procedure starts and in the final splash screen the system
> just hangs. Tried a second time by pressing Esc once the splash screen
> showed up and I saw that it reaches the line "Reached target shutdown"
> and just stops there, no matter how long I leave it there the machine
> won't turn off.
>
> I also tried a Kubuntu 16.04 fresh install on the same machine and it
> hanged too at the final splash screen where the pulsating logo
> stopped. Then I tried with Esc only to see the exact same line in the
> end.
>
> The issue seems to affect lately quite many users as shown by the
> google results of the past month / week or so.
>
> I have also tried shutting down from the console with shutdown -and
> all the parameters after that suggested online- and sudo poweroff but
> unfortunately they didn't do the trick. The exact same situation
> occurred.
>
> Unmounting the swap as suggested online doesn't work.
>
> Also rebooting the system is not working either due to the same issue.
>
> So right now the only way for me to poweroff the machine is to press
> the power button on the keyboard continuously.
>
> Reproducible: Always
>
> Steps to Reproduce:
> 1.Install OS
> 2.Do something, anything or nothing
> 3.Try to shutdown or reboot
>
> Actual Results:
> The computer is not shutting down: "Reached target shutdown" and hangs
> there.
>
> Expected Results:
> Powering off the machine.
>
> For what it's worth, closing the lid won't suspend the system, but
> using the menu buttons for suspension will do it.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1594023/+subscriptions
>

Revision history for this message
Aang (aang-aero) wrote :

I have a Dell 14z-5423 - same issue on Ubuntu 14.04.5 and 16.04.1 :-(

Revision history for this message
Blackbug (blackbug-nx) wrote :

Okay, I got it fixed for now on my machine by reinstalling the current kernel. After this I can restart/shutdown without getting hung.

Not sure if this is the generic workaround.

Revision history for this message
jtarin (jtarin) wrote :

Works for me too with kernel upgrade

On Nov 3, 2016 1:40 PM, "Blackbug" <email address hidden> wrote:

> Okay, I got it fixed for now on my machine by reinstalling the current
> kernel. After this I can restart/shutdown without getting hung.
>
> Not sure if this is the generic workaround.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1594023
>
> Title:
> Poweroff or reboot hangs. Laptop won't shutdown. 16.04
>
> Status in linux package in Ubuntu:
> Confirmed
>
> Bug description:
> This is about a fresh Ubuntu 16.04 install on a new laptop (asus
> x540sa). After pressing the shutdown button in the start menu; the
> shutdown procedure starts and in the final splash screen the system
> just hangs. Tried a second time by pressing Esc once the splash screen
> showed up and I saw that it reaches the line "Reached target shutdown"
> and just stops there, no matter how long I leave it there the machine
> won't turn off.
>
> I also tried a Kubuntu 16.04 fresh install on the same machine and it
> hanged too at the final splash screen where the pulsating logo
> stopped. Then I tried with Esc only to see the exact same line in the
> end.
>
> The issue seems to affect lately quite many users as shown by the
> google results of the past month / week or so.
>
> I have also tried shutting down from the console with shutdown -and
> all the parameters after that suggested online- and sudo poweroff but
> unfortunately they didn't do the trick. The exact same situation
> occurred.
>
> Unmounting the swap as suggested online doesn't work.
>
> Also rebooting the system is not working either due to the same issue.
>
> So right now the only way for me to poweroff the machine is to press
> the power button on the keyboard continuously.
>
> Reproducible: Always
>
> Steps to Reproduce:
> 1.Install OS
> 2.Do something, anything or nothing
> 3.Try to shutdown or reboot
>
> Actual Results:
> The computer is not shutting down: "Reached target shutdown" and hangs
> there.
>
> Expected Results:
> Powering off the machine.
>
> For what it's worth, closing the lid won't suspend the system, but
> using the menu buttons for suspension will do it.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1594023/+subscriptions
>

Revision history for this message
Blackbug (blackbug-nx) wrote :

I again have the same issue. Although not everytime. Its hard to reason why it hangs at times. If it happens frequently will reinstall the kernel once again.

Revision history for this message
Daniele Viganò (daniele-vigano) wrote :

Could be related to this bug?

https://bugzilla.kernel.org/show_bug.cgi?id=187061
https://bugzilla.kernel.org/show_bug.cgi?id=151631

It affects kernels >= 4.8 on (as far as I know) any distro.
I'm experiencing problems on both Fedora 24 and Ubuntu 16.10 running kernel 4.8 on a Dell Latitude E5450 with a Samsung 850 SSD.

Revision history for this message
VinDSL (perfect-pecker) wrote :

@ Daniele Viganò (daniele-vigano)

We're both experiencing the same shutdown problems -- same OEM -- same kernels -- same Samsung 850 SSDs.

The only obvious difference is you have a Dell Latitude E5450 laptop, and I have a Dell Optiplex 7010 SFF desktop.

Since neither of us are experiencing shutdown problems with kernels <= 4.7, yes, I would judge that it relates to the bug(s) you listed above.

Revision history for this message
b-ob (b-ob) wrote :

Same problem with a fresh install of Lubuntu 16.10. No problem at all with Lubuntu 16.04. I've tried a live Kubuntu 16.10: same problem. It seems to be a bug related to kernel 4.8, since live Fedora 24 (kernel 4.7) is fine but live beta Fedora 25 (kernel 4.8) doesn't shut down.

It seems that the computer (Dell Optiplex 9010 with SSD) is trying to access the disk after the line "Reached target shutdown", since it gives some errors like "ata1.00: exception Emask...", "ata1.00: failed command..." and the like. After a while, it prints "ata1: reset failed, giving up" and finally a "reboot: Power down" and then turn the power off (5 to 10 minutes after having printed the line "Reached target shutdown").

Revision history for this message
Daniele Viganò (daniele-vigano) wrote :

So, it seems we are all on Dell with a Samsung SSD 850 drive. Next week I'll have a chance to try a different SSD from Kingston. I'll see if the bug is still reproducible.

Revision history for this message
Blackbug (blackbug-nx) wrote :

I have HP envy ultrabook. However, I do have samsung 850 SSD..so i guess it all comes to SSD then

Revision history for this message
VinDSL (perfect-pecker) wrote :

My biggest fear is that during one of these 'freezing' episodes my Samsung 850 SSD will remount the root partition as read-only. I've had several HDDs go read-only, over the years, and it's a PITA to recover from it, especially in RAID configs.

Somebody will to need to handle this situation upstream. Two likely scenarios would be either a Linux kernel patch, and/or a firmware upgrade from Samsung. In the meantime, we're all sitting on ticking time bombs.

I suppose it goes without saying, but make sure you're fully backed-up !!!

Revision history for this message
Daniele Viganò (daniele-vigano) wrote :

It seems that the code causing the bug will be reverted in 4.9-rc7: https://bugzilla.kernel.org/show_bug.cgi?id=187061#c15

Revision history for this message
EWoldhek (3y9-elis-fkz) wrote :

Same here on Samsung Ultrabook core i5 after upgrading to 16.10.
Linux version 4.8.0-27-generic (buildd@lgw01-11) (gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12) ) #29-Ubuntu SMP Thu Oct 20 21:03:13 UTC 2016
SSD: Samsung MZNTE128
After "Reached target Shutdown" i get:
- ata1.00: exeption Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
- ata1.00: failed command: Flush CACHE
Some other lines with - ata1: comreset failed

Hope you guys can find it.....

Regards, Erik

Revision history for this message
VinDSL (perfect-pecker) wrote :

Kernel 4.9-rc7 fixed it !!!

I waited until the Ubu Mainline kernel was available, just to make sure.

LINK: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9-rc7/

@Daniele Viganò, thanks for all the effort(s) you went to, over in the mailing lists and bugzilla, to make this happen.

Good job !

Revision history for this message
Davidiam (hectorjerezano) wrote :

I can confirm On my dell laptop E7450 With kernel 4.8 BUG reported here. With 4.9 rc7 this BUG is FIX!

Revision history for this message
EWoldhek (3y9-elis-fkz) wrote :

Will it be fixed in 4.8 through standard udpates?

Konstantin (hi-angel-z)
Changed in linux (Ubuntu):
assignee: damiano (damiano1996) → nobody
38 comments hidden view all 118 comments
Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

I thinks it's LP: #1776616 for your issue.

Revision history for this message
Hey! (press-1p-start) wrote :

Hi.

On my computer the transition from 4.5.7 to 4.6.0 is the cause of this bug.

Can anyone try to install the following kernels to see if this bug happens?

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5.7-yakkety/

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-rc1-wily/

Revision history for this message
Dave (dbakerp) wrote :

Same bug appears on my Lenovo M58p desktop with Ubuntu 16.04.5 LTS kernel 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Revision history for this message
Liomar (liomarhora) wrote :

I was having the same problem on Debian 9, but my PC was old.
When I looked at linux-image and linux-header in synaptic, there were installations for old PCs and modern PCs, on my old PC was installed the version for modern Pcs. I installed the correct version and uninstalled the wrong one. Worked perfectly.

Ex:
linux-image-4.9.0.4-686 - Linux 4.9 for older PCs
linux-image-686 - Linux for older PCs (meta-package)

linux-image-4.9.0.4-686-pae - Linux 4.9 for modern PCs
linux-image-686-pae - Linux for modern PCs (meta-package)

Revision history for this message
Manan Solanki (manan2110) wrote :

The same issue is also reproducible for me on my HP Pavilion N004tx laptop. I'm using Ubuntu 18.10.

Revision history for this message
Vishal Dindalkop (vishald) wrote :

I had similar issues when i installed Ubuntu i tried to boot ubuntu but it got hang because of ACPI error
i made acpi off so it can boot in but when i tried to shut down it got hand this time

Reason is simple
Its related to your graphic card

step 1:
i went through these proceess
->booted into system with acpi off from grub command
since i was not able to without doing so

step 2:
later when i got into ubuntu
i did
(this step neccessary or not i'm not sure, included it since i had followed it) i think its very necessary
->sudo apt-get update
->sudo apt-get upgrade

step 3:

Install graphic card Driver

https://www.tecmint.com/things-you-mostly-need-to-do-after-installing-ubuntu-16-04/4/

after doing this once you might hang but on restart you wont need acpi off
you can run ubntu without any hang during start splash screen or shutdown splash screen

Revision history for this message
JohnDoe_71Rus (johndoe99) wrote :

option PowerNow Disabled in BIOS looks like fix the problem. But the CPU temp is grow up. And it work many years before with PowerNow Enable without problem.

Revision history for this message
Dariusz Deoniziak (darekdeoniziak) wrote :

I do have the same problem since Ubuntu 17.14, it doesn't matter if it is Ubuntu distribution or any of its flavours (e.g. Kubuntu which I am using currently). I do not remember if it worked fine on 16.04, all I can tell I was always doing distro upgrade and haven't installed fresh Ubuntu installation since 16.04.

Laptop is Dell Inspiron 7548.

There are various blog or forum posts about this issue, mostly suggesting to edit grub (some about editing defaulTimeout in system.conf), unfortunatelly editing acpi settings or editing anything similar doesn't work.

I do not use any custom ppa other than google/chrome. Means I am using stock/distro mesa drivers too.

The laptop freezes on splash logo only during shutdown (reboot works fine). I have noticed that laptop freezes on poweroff command (visible on nosplash). The laptop sometimes doesn't freeze when battery is not fully charged, the less battery is charged the lesser chances that laptop will freeze. On 15-30% of battery laptop does shutdown fine, never noticed freeze. But when battery is 90% or fully charged, or charging, the freeze almost always happens.

This laptop does have battery test in UEFI, test says battery is in fine condition. Anybody else noticed any connection with shutdown freezes and battery?

One more thing worth noting, once following some another forum posts I have edited reboot command behaviour to shutdown laptop, laptop did shutdown always after invoking reboot, even when battery was fully charged and charging. But I have reverted this change because I need reboot more than shutdown.

Revision history for this message
Keith (kballthingsliunx) wrote :

Sounds like broken record here, oh no broken shutdown here actually.
Bodhi Linux 4.2 on old hardare Aspire 5000 laptop, was wooring fine till a day or two ago.
Hangs at shutting down several things says all stopped down to hardware clock something or another.
can hit Esc a couple times and it progresses but still just stops.
Will boot fine with a Power Button Hold down and restart.

Revision history for this message
hardyn (arlenn) wrote :

Had same issue with MSI GP73 laptop. Problem was solved by installing the NVidia "blob" drivers.

Revision history for this message
Slawomir (slaw001) wrote :

Hi, I have a DELL Latitude E5520 (4.15.0-52-generic #56~16.04.1-Ubuntu)

Problem was solved:

/etc/default/grub
changed the entry bellow:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
on the following:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=force reboot=pci"
and
sudo update-grub

Revision history for this message
Max Argus (argus-max) wrote :

Same Problem Dell XPS 15z
Kernel: 4.18.0-22-generic
OS: 18.04.02
Window manager: KDE
Not using Nvidia blob drivers.

Editing grub with "acpi=force reboot=pci" didn't help.

Sometimes also partially freezes when using firefox (mouse dosen't move, ping command dosen't work, can't kill -9 firefox process)

Brad Figg (brad-figg)
tags: added: cscc
Revision history for this message
B. C. Schmerker (bcschmerker) wrote :

This hang on shutdown and/or reboot is NOT confined to portables. I encountered the issue installing xubuntu™ 18.04-LTS on an emachines®/acer® EL1210-09 (2.3 GHz Advanced Micro Devices® Athlon® LE-1620; nVIDIA® nFORCE® 720 chipset; 2 x 2 GiB DDR2 main memory) with a Shuttle® PSU upgrade (PC6300001 in for stock 220W LITEON®) and the planar C77 geForce® 64-bit GPU by-passed for the nVIDIA® GF-109 on an msi® N610GT-MD1GD3/LP half-height video display adapter. I normally use:

GRUB_CMDLINE_LINUX_DEFAULT="debug"

in /etc/default/grub, which is how I confirmed the issue: Depending on shutdown or reboot option, the system halts at "Starting reboot..." or "Starting power-off...", forcing a manual power-down. Will report back after testing:

GRUB_CMDLINE_LINUX_DEFAULT="debug acpi=off"

and:

GRUB_CMDLINE_LINUX_DEFAULT="debug acpi=force"

I'd rather save the C77 geForce® driver set (provided to Canonical Ltd. by nVidia Corporation) for the nFORCE® 720 as a last resort, as it affects Kernel behavior in both startup and shutdown.

Revision history for this message
B. C. Schmerker (bcschmerker) wrote :

Update: acpi=off only got me to a timestamped kernel message "reboot:System halted". acpi=force had no effect. Repeating report to Bug 1776616, which is specifically relevant to Kernel 4.15-n-generic on xubuntu™ 18.04-LTS.

Revision history for this message
B. C. Schmerker (bcschmerker) wrote :

Update: Issue worked around with nVIDIA® geForce® driver 340.107 for C77 GPU in MCP78 northbridge (package:nvidia-340). Repeating report to Bug 1776616.

Revision history for this message
Tushar (tushar321) wrote :

This issue still persists.Mine is an
Hp laptop with an Intel Bay Trail processor, Intel HD graphics(Not Nvidia), 8GB RAM with Dual boot Windows and Ubuntu 16.04.2. Bios version F.46 and kernel version 4.15.0-55-generic

Whenever I try to SHUTDOWN/RESTART/SLEEP the Screen goes off(Black) but the Hard Disk keeps spinning with power button light ON. sometimes while doing shutdown the screen hangs on Ubuntu logo with dots. when esc is pressed it's seen that after [OK] Reached Target Shutdown nothing happens cursor blinking or Freeze.

I tried to Re-install ubuntu with 16.04.6 while installing it displayed error related to APCI. somehow it got installed and when I checked dmesg it showed this error message
"ACPI Error: [\_PR_.CPU0._PPC] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364)" and this

"ACPI Error: Method parse/execution failed \_SB.PCI0.LPCB.EC0.IPCL, AE_NOT_FOUND (20170831/psparse-550)"

I tried almost everything I found on internet acpi=force, acpi=off and other stuff. It's discouraging from 2016 to 2019 there is still no permanent fix for this issue. some people on internet tried some or other fix for some it worked for some it didn't. Did anyone one of you found the fix for this ?

Revision history for this message
JohnDoe_71Rus (johndoe99) wrote :

try 5.2.8 from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2.8/

the same, last mesage in console

Started Show Plymouth Power Off Screen
Starting Power-Off
[... ] systemd-shutdown [1]: Failed to wait for process: Protocol error

Revision history for this message
Vadym Stupakov (red-eyed) wrote :

I have same problem and solved it.
workaround is: https://unix.stackexchange.com/a/544728/149135

Revision history for this message
Guy Mandor (guy-mandor) wrote :

@VadymStupakov: You're a saviour. I had been struggling with this issue for over a year. The solution worked perfectly. My power button Thanks you!

1 comments hidden view all 118 comments
Revision history for this message
Ashwin Biju (regenhalogen) wrote :

I had the same problem with elementary os i fixed it by disabling the usb 3.0 option in the bios of my hp laptop....

Revision history for this message
Marko T (tolima1) wrote :

Hi, I have the same problem with not being able to reboot or shutdown.
Error is displayed: "Failed to power off system via logind: There's already a shutdown or sleep operation in progress"

Ubuntu 20.04 on Dell Pavilion M6600.

I tried modifying the "quiet splash acpi=force" but without success.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Revision history for this message
tyler krueger (pumking10) wrote :

its effecting ubuntu 20.04 if there is a way to fix it please help me out.

Changed in ubuntu:
status: New → Confirmed
affects: linux → ubuntu
Revision history for this message
VinDSL (perfect-pecker) wrote :

Every machine is different. Here's the grub that I use on 'doorstop' machines:

# If you change this file, run 'update-grub' afterwards to update
GRUB_DEFAULT="0"
GRUB_TIMEOUT_STYLE="true"
GRUB_TIMEOUT="10"
GRUB_DISTRIBUTOR="`lsb_release -i -s 2> /dev/null || echo Debian`"
GRUB_CMDLINE_LINUX_DEFAULT="elevator=deadline quiet splash plymouth.enable=0 libahci.ignore_sss=1 noefi"
GRUB_CMDLINE_LINUX="libata.force=noncq"
GRUB_GFXMODE="1920x1200x24

It knocks a few seconds off of boot times, and shuts them down in a heartbeat.

Here's the 'systemd-analyze time' result on my Dell Dimension 3000 box, circa 2004:

Startup finished in 3.650s (kernel) + 7.044s (userspace) = 10.694s
graphical.target reached after 7.008s in userspace

No joke...

Revision history for this message
atefrihane (atfinho) wrote :

I'm using dell 3543 and ubuntu 20.04
reboot but works but power off hangs
is there a way to fix it please ??

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubuntu:
status: New → Confirmed
Revision history for this message
Stefano (cmarlowe) wrote :

I have the same issue, I'm using an ASUS k50in with graphic card Nvidea GT220M.
When I power off my laptop the procedure stops at the output line Reached target Power-Off.
This is the output of the command uname -a for my laptop

Linux stefano-K61IC 5.8.0-40-generic #45~20.04.1-Ubuntu SMP Fri Jan 15 11:35:04 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

I have tried in the grub configurations the GRUB_CMDLINE_LINUX_DEFAULT='acpi=force' then I tried using GRUB_CMDLINE_LINUX_DEFAULT='acpi=noirq' and then GRUB_CMDLINE_LINUX_DEFAULT='acpi=off' everytime without success.
Can you suggest a way to fix it? Or some debug steps that can be performed to better understand the issue?

Revision history for this message
Jan Johansson (insomniacno1) wrote :

Lenovo Thinkpad X300, 4GB Ram, INTEL SSDSA1MH160G1HP (045C8781)160GB SSD, Intel GMA X3100 i915, battery SANYO 42T4522 77% capacity though charges to 100%.

Peach OSI TW 16.04 LTS build on Xubuntu, Kernel 4.4.0-217-generic.

Problem with shutdown started with 4.4.0-216-generic and is still in 4.4.0-217-generic which is the newest kernel for my setup.

If the machine has been idle for a while, sometimes with Firefox 88.0 open, sometimes after using VLC player - then it hangs on shutdown, Screen is off but wifi and bluetooth light is on(its off when totally shutdown). At this point not even ESC work(as the screen is off and never comes on), only by holding the power button the laptop turns off.

Restarting sometimes work ok, but from time to time it can take up to 10 min to start up(where normal startup is 30seconds).

Editing grub and adding noefi after quiet splash, worked for a while and then last night it would not shut down again and I had to use power button. this morning it started up normal 30seconds.

I have had updates comming in, I have installed Intel graphic tool to update the driver but problem persist, so don't think its a graphic card driver issue.

Many here has reported it on other systems with totally different config, so I think this is a kernel issue that seem to pass through in newer kernel updates.

Also seem that it is not only 16.04 since it has been reported in newer versions too.

I'm still using 16.04 because there is no 20.04 Peach(now named Patriot) after the author died in september this year - I might move to 20.04 or newer when most of the bugs has been addressed.

Revision history for this message
Jan Johansson (insomniacno1) wrote :

So removing quiet splash and adding noefi to grub and editing

sudo xdg-open /etc/systemd/system.conf

removing the # infront of #DefaultTimeoutStopSec=90s and changing the timeout to 10s instead of 90s

Seem to have fixed my issue

I found the last bit here:

https://itsfoss.com/long-shutdown-linux/

Please comment and let me know if it solves it for you too.

1 comments hidden view all 118 comments
Revision history for this message
Jan Johansson (insomniacno1) wrote :

I have changed DefaultTimeoutStopSec=90s timeout to 20s as personal choice to make sure that anything running in the background has time to stop before shutting down, to avoid something braking,

Revision history for this message
Jan Johansson (insomniacno1) wrote :

I had the issue again. so my previous change didn't work.

I have changed DefaultTimeoutStopSec=90s timeout to 40s.

I tried turning off wifi byt rfkill block all from terminal prior to shutdown, that just ended up in black screen as usual but this time wifi was off, but laptop still on.

Revision history for this message
Jan Johansson (insomniacno1) wrote :

I have investigated further, it would seem that it is the shutdown function in ubuntu and flavors that is the problem, because sudo poweroff in terminal work just fine.

I suggest the ones still affected by this bug, try to open terminal and type:

sudo poweroff

your password

Just to see if it work for you, please let me know.

Could one of the experts here come up with a script that do the poweroff function without having to type password?

Revision history for this message
Jan Johansson (insomniacno1) wrote :

So sudo poweroff seems to fix the problem, somehow, because if I do that and then next time shutdown normally then the laptop shuts all the way down - meaning turn off.

Weird.

So sudo poweroff it is, should be put instead of shutdown, because it would seem that one is faulty, and in my case with 16.04 most likely is not getting solved.

for 18.04 and later there might be some solution.

I still call out for a script as temporary solution!

Thank you in advance

Jan

Revision history for this message
Jan Johansson (insomniacno1) wrote :

Hi again, so since october 28, I have been trying to install and run an old kernel from before this shutdown problem happened and I am now running 4.4.0-210-generic, for the last week(and I use my laptop every day most of the day), I have had no shutdown problems.

Since this problem occur in newer kernels too, than maybe developers can look to this kernel and see what is different, that might cause the problem.

To people who want to use this older kernel, just open synaptics and look first to what you have installed by searching for your kernel version number - do not add linux-image or linux-headers.

You should see what is installed and modules. Make a screenshot or write it down, then look for this old kernel the same way and install the items from your list.

Wait for it to finish.

Then either use Grub customizerI use this as there is a GUI and a lot of options, like having a list of kernels shown on start up) or you can just run

sudo update-grub

from terminal

Restart your machine

Edit these instructions to fit your own system, that might be different from mine.

Revision history for this message
Jan Johansson (insomniacno1) wrote :

I switched to Linux Mint 20.2 Uma Cinnamon and now I don't have shutdown problem anymore.

Revision history for this message
ranjit (ranjit3434) wrote :

I had dual OS installed on my old lenovo laptop

windows 7 & bodhi linux. but my linux system stuck at shutdown screen. i found a solution which worked for me,

#GRUB_CMDLINE_LINUX_DEFAULT='acpi=force acpi=nocrq reboot=pci'

 then grub update using

#sudo update-grub

1 comments hidden view all 118 comments
Revision history for this message
Jan Johansson (insomniacno1) wrote :

Just to add to this, it is definitely a kernel problem, and since it comes back once in a while it would suggest that its the same programmer/contributor that is the cause of this - it then get fixed in newer kernel and then comes back again(seem someone don't learn from their mistake).

I am on Linux mint 20.2
Kernel 5.4.0-162-generic

Displaying first 40 and last 40 comments. View all 118 comments or add a comment.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.