Ubuntu 14.04 won't shut down (reboots)

Bug #1346269 reported by Paul Bradley
96
This bug affects 19 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

I just installed a new 14.04 server install on the following hardware:

ASRock E3C224-4L Server/Workstation Board (Intel C224 chipset)
Intel Xeon E3-1245V3 Quad Core LGA1150 CPU
32GB of DDR3 ECC RAM
LSI 9201-16i SAS/SATA HBA

I am unable to power down the system without physically doing it with the button, or powering it off using the inbuild IPMI management.

All of the following result in a reboot:

sudo shutdown -h now
sudo shutdown -p now
sudo shutdown -P now
sudo halt now
sudo halt -fihp now
sudo init 0

I have tried acpi=force, acpi=off, acpi=noirq, noapic

I tried the script from http://askubuntu.com/questions/13288...-of-a-shutdown as follows:

#!/bin/bash

case "$1" in
stop) for i in /sys/bus/*/devices/*/power/control ; do echo on > $i ; done
;;
esac

exit 0

That didn't help.

I also set WOL off on the NIC that was plugged in (only one of the 4 onboard NICs is connected at present, for testing) with sudo ethtool -s eth0 wol d and it didn't help, I've looked in the BIOS, and can't find a WOL section in there. To try to eliminate WOL, I also tried with neither the NIC in use for testing, nor the dedicated IPMI NIC connected, and it didn't help.

I've updated my BIOS to the latest version.

I've probably tried more that I've forgotten to list here - I've exhausted my options!

I'm at a loose end now - no idea what to do next to further troubleshoot it, has anyone else had any similar problems on C224, or does anyone know what logs I should be inspecting, or how I can generate further debug logs?

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-32-generic 3.13.0-32.57
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
AlsaDevices:
 total 0
 crw-rw---- 1 root audio 116, 1 Jul 19 20:34 seq
 crw-rw---- 1 root audio 116, 33 Jul 19 20:34 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory: 'iw'
Date: Mon Jul 21 13:55:56 2014
InstallationDate: Installed on 2014-07-13 (7 days ago)
InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
PciMultimedia:

ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=screen
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcFB: 0 astdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/root/boot/vmlinuz-3.13.0-32-generic root=UUID=cebd6063-3e82-41e4-a8ac-22fa6a7d11a7 ro rootflags=subvol=root nomdmonddf nomdmonisw rootflags=degraded nomdmonddf nomdmonisw
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-32-generic N/A
 linux-backports-modules-3.13.0-32-generic N/A
 linux-firmware 1.127.4
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
WifiSyslog:

dmi.bios.date: 05/07/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.10
dmi.board.name: E3C224-4L
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd05/07/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnE3C224-4L:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

Revision history for this message
Paul Bradley (paul-bradley-webmail) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.16 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/v3.16-rc6-utopic/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
tags: added: kernel-bug-exists-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Jaap Woldringh (jjhwoldringh) wrote :

I can support this bug report. For my (very new) computer details see attachment (lshw.txt)
I currently use Linux xxxxx 3.13.0-35-generic #62-Ubuntu SMP Fri Aug 15 01:58:42 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

In /etc/default/grub I have the line:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=off"

Symptoms: without the "acpi=off" parameter the computer used to reboot repeatedly. With "acpi=off" it boots OK, but reboots spontaneously after shutdown, and the computer must be powered off using the power switch.

Trying the most recent upstream kernel ( 3.12.28, I guess compiled 9th of september) the computer boots OK, even without "acpi=off" and but during shutdown, after showing 2 red dots of the 5, first time. The computer has to be switched off using the power button. So another behaviour, but still it is not OK.

I also tried a LiveCD with Ubuntu 12.04.1 (Precise), this was quite OK (only no sound, on this very new hardware)
Same with LiveDVD with Ubuntu 12.4.5 (Precise, the latest), this behaved same as the 14.4.1 LiveDVD

So the bug entered somewher between Ubuntu 12.04.1 and 12.04.5

Hope this helps, adding 50% to the people affected ...

Greetings,

Jaap Woldringh

Revision history for this message
latimerio (fomember) wrote :

I can confirm this bug.

I just upgraded my home server from 12.04.5 LTS to 14.04.1 LTS and now the system always reboots after a poweroff / shutdown -h command.
The only way to shut the system off is to press the power button when it's in the POST phase.

If I issue a "poweroff" command the server shuts down and then instantly reboots.
I tried to set acpi=force in /etc/default/grub but this did not help.

With 12.04 I had no problem with poweroff and I used to use Wake On LAN to boot up my server whenever a client needs it.
Fortunately I had cloned my old system disk before the upgrade so I was able to revert to 12.04 without a fuss.
As expected the problem is not there with the 12.04 disk.
Thus it is not the hardware or BIOS which causes the problem but definetely something in 14.04.

Was there possibly some major change in 14.04 with respect to ACPI behaviour?
Ubuntu 14.04 is at its server release .1 but with not being able to put my home server to sleep it proves to be totally useless to me.

P.S. My Mobo is an MSI P9D-X with a Xeon CPU E3-1230L v3

Revision history for this message
Jaap Woldringh (jjhwoldringh) wrote :

Adding to my report in #4, I discovered that the shutdown behaviour of my computer changed by replacing the open source X.orgX graphics driver (xserver-xorg-video-ati) by the nonfree driver called "Video driver for the AMD graphics accelerator of fglrx-updates". The other non free driver (without the addition "updates" did not change things.
Now the system doesn't reboot after shutdown, but the shutdown halts halfway, I guess after the hard disk stops rotating (noise stops), but the cooling ventilators still run.

The graphics card is embedded in the AMD-processor, and is called AMD/ATI: Richland [ Radeon HD 8570D]

This is an improvement, but it is still not how things should be, of course, but might indicate where to seek.

Jaap Woldringh

Revision history for this message
latimerio (fomember) wrote :

I found that I needed a BIOS update to my ASUS (MSI was a typo in my 1st comment) P9D-X which fixed the hardware dependent issue.
Thus for me the reboot issue is no more now.

Revision history for this message
Jaap Woldringh (jjhwoldringh) wrote :

I want to report that after the latest update, containing a new kernel, 3.13.0-36-generic, this problem seems to be fixed for me.
Thanks to who have found and applied this solution to this problem. My new computer now works flawlessly with Ubuntu 14.04.1 LTS :), which is really great

Jaap Woldringh

Revision history for this message
tlue (tlueber) wrote :

I have exact same experience on a Lenovo Notebook (6 years old and always running Ubuntu) with Nvidia proprietary graphics driver. With 12.04 it was perfectly fine. Now since 14.04 I experience same as
Jaap Woldringh (jjhwoldringh) wrote on 2014-09-14:

the shutdown halts halfway, I guess after the hard disk stops rotating (noise stops), but the cooling ventilators still run.

I have to keep pressing the hardware off button for 10 seconds or so, to get it fully halted (vent stopping). Vent keeps going otherwise indefinitely (tested it for more than an hour leaving it be, but did not change anything)

Revision history for this message
tlue (tlueber) wrote :

actually wanted to add, the
a) sleep mode is working perfectly fine for me
b) after hardware-switch-off and switch on again, I often get message during startup that I should wait for disk being checked (not halted/unmounted properly even if not making any noise any more?)

Revision history for this message
tlue (tlueber) wrote :

what wonder! it worked first time today...
I got some security updates installed (must have been from within the last 4 days or so), and update of my JDK 1.7, skype and Launchpad-WebContainer-App (that crashed first). Not sure which of them had fixed it for me...

some excerpts from
cat /var/log/dpkg.log

2014-10-23 23:41:33 status unpacked libpciaccess0:i386 0.13.2-1
2014-10-23 23:41:34 status half-installed libdrm-nouveau2:i386 2.4.52-1
2014-10-23 23:42:14 status installed libgl1-mesa-dri:i386 10.1.3-0ubuntu0.1
2014-10-23 23:42:19 status installed mysql-common:all 5.5.40-0ubuntu0.14.04.1
2014-10-23 23:42:21 configure libqt4-opengl:i386 4:4.8.5+git192-g085f851+dfsg-2ubuntu4 <none>

Let me know if you need more details.

Revision history for this message
Christopher Barrington-Leigh (cpbl) wrote :

I cannot rely on "shutdown" on my laptop. The rebooting instead of shutting down happens to me some but not all of the time on a Lenovo X230T.
I have the latest updates to 14.04, and it just happened again today.

Revision history for this message
Sam Osborn (samosborn) wrote :

Can confirm.

I have had this issue on every *buntu distro I've tried, including elementary OS Luna which was based on 12.04.
I've tried the acpi=force etc in grub, updated grub, reinstalled grub, updated BIOS, tried the 'echo on' to usb devices. None have solved the issue. At first it was intermittent and less frequent if the power cord was plugged in. After a year it happens every time no matter which distro I'm using or method I use to shutdown.
To shutdown I go into the GRUB command line with 'c' when the grub menu comes up, and use the 'halt' command. I have to do this one more time and then the computer shuts off. If I then restart the computer with the power button, and then shutdown at the login screen, it shuts down.

I have a Lenovo Thinkpad, an Intel i5 chip and I dont know which graphics card but can provide any outputs of commands.

Revision history for this message
Björn Ramberg (bjoern-ramberg) wrote :

Also a confirmation here, tested with both HP Elitebook 840G1 and 850 (both Intel i7 with integrated graphics). Both behaving the same, rebooting instead of shutting down. Same results on both 3.13 and 3.16 kernels. Same results regardless of shutdown method.

Revision history for this message
Björn Ramberg (bjoern-ramberg) wrote :

The solution presented here: http://askubuntu.com/questions/452750/reboot-after-shutdown-ubuntu-14-04-also-12-04-dell-latitude-e7440 was found by an observant colleague and did the trick for me. After disabling wake-on-(Lan/USB) the error seems gone.

Tested on 3.16.0-50 Trusty on a HP EliteBook 840 Laptop.

Revision history for this message
Fakabbir amin (f4amin) wrote :

This solution seems to work on ubuntu 14.04 as well as later updates.
https://www.behnke.io/fedora-17-on-an-aspire-v5-571-reboot-on-shutdown/

Revision history for this message
rCX (rcx) wrote :

The solution suggested by f4amin also works for me on my lenovo x131e under Ubuntu 16.04

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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