** Changed in: systemd (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1619844
Title:
[Xenial] shutdown/reboot hangs at
I no longer have this issue. I don't know whether it was updating mdadm
or another package, but I recently issued a shutdown command and walked
over to my box to hold the power button for a few seconds and finish
shutting it off, only to find it was already off. I've since confirmed
that a reboot
This bug disappeared for me when I did
apt-get install linux-generic-hwe-16.04
to upgrade to kernel version 4.10.0 instead of 4.4.0. (I also had
proposed-updates in /etc/apt/sources.list, but it was the linux-generic-
hwe-16.04 package that really fixed it.)
I suspected it was a kernel bug
Just a quick clarification, first boot/shutdown will still not be clean,
but subsequent ones (those that are booted with the updated mdadm
package) should be clean.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
It depends on what sort of raid modes are in place. If you are not using
raid (e.g. RAID1) as provided by your motherboard firmware, and only use
individual devices, it is best to disable raid settings in the bios and
use regular acpi setting. I have to do this for example on latest
generation of
Same issue here, on a Supermicro 6018R-WTR server. I've attached a
screenshot of the hung state. Note that the watchdog message is because
I've set up IPMI watchdog on this machine (as a workaround for this
issue). The hang on reboot is not happening every time for me -
something like 10%-20% of
Yes. I confirm that. After change in bios from raid to ahci computer is
rebooting and swithing off normally.
Wysłano z mojego smartfona Samsung Galaxy.
Oryginalna wiadomość Od: Tobias Alke
<1619...@bugs.launchpad.net> Data: 22.04.2017 08:53 (GMT+01:00) Do:
I think i have a specification to this issue.
First, my system with the same problem at shutdown/reboot, but only in a
very special case:
Fresh install of Ubuntu Server 16.04.2 LTS
CPU: Intel Xeon E3-1245v6 (Kabylake)
Mainboard: MSI C236A Workstation/Server Mainboard (model: 7998-012R; latest
Mine is an Intel NUC6i7KYK. As the model number suggests, it's an Intel
NUC with a Skull Canyon (6th generation) i7 processor. Intel ARK link:
http://ark.intel.com/products/89187/Intel-NUC-Kit-NUC6i7KYK.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Journal ends with:
Sep 02 23:59:22 nuc systemd-shutdown[1]: Sending SIGTERM to remaining
processes...
Sep 02 23:59:22 nuc systemd-journald[1455]: Journal stopped
which means that something is not dieing and we are not getting any more
logs recorded.
and it indicates that all/most attempts
Same problem here. Fresh install of 16.04.1 Ubuntu server. CPU intel
J1900. Kernel 4.4.0-59. I tried what suggested in the link above and any
other method I found around (force ahci in grub options, deactivate usb
3 legacy, using different commands for restarting..) but with no
success. Still
I can't quite figure out why, but the answer seems to be "occasionally".
I was able to reboot a few times (2 out of maybe 30?) using the complete
list of reboot= options. However, I suspect making the reboot= changes
is a red herring -- I rebooted the machine more in the past few hours
than I have
Does the following work-around work for you?
(http://michalorman.com/2013/10/fix-ubuntu-freeze-during-restart)
After answering, please set status back to "confirmed". Thank you.
** Changed in: systemd (Ubuntu)
Importance: Undecided => Critical
** Changed in: systemd (Ubuntu)
Status:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
14 matches
Mail list logo
