Halt doesn't power system down

[Jeff Lane ]

I have a Skylake Core i7 system running up-to-date 16.04.1 (4.4 kernel).

Whenever I issue a halt (either shutdown -h now, or halt) the shutdown process gets as far as showing the "Target shutdown reached" on the console, but instead of actually powering the system down, it just sits there idling.

I have to manually power the system off by holding the power button down.

What should happen, is that 'shutdown -h now' should actually shut the OS down and power the computer off without any further intervention.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-83-generic 4.4.0-83.106
ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
Uname: Linux 4.4.0-83-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.1-0ubuntu2.9
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: bladernr 28322 F.... pulseaudio
 /dev/snd/pcmC0D0p: bladernr 28322 F...m pulseaudio
 /dev/snd/controlC0: bladernr 28322 F.... pulseaudio
CurrentDesktop: Unity
Date: Thu Jul 13 17:42:14 2017
HibernationDevice: RESUME=UUID=0ca350ae-0a5d-4d84-9ac5-f0f83959aa62
InstallationDate: Installed on 2016-02-11 (518 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
MachineType: Gigabyte Technology Co., Ltd. Z170MX-Gaming 5
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic.efi.signed root=UUID=fa272e99-2333-4360-a2f3-edbde23a1fed ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-83-generic N/A
 linux-backports-modules-4.4.0-83-generic N/A
 linux-firmware 1.157.11
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/16/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F3
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z170MX-Gaming 5
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
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.:bvrF3:bd10/16/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170MX-Gaming5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170MX-Gaming5:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: Z170MX-Gaming 5
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

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

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.12

[Jeff Lane  (bladernr)]

On Fri, Jul 14, 2017 at 9:25 AM, Joseph Salisbury
<email address hidden> wrote:
> Did this issue start happening after an update/upgrade?

No, it's done this as long as I've had the machine (It's home-built,
not an OEM designed system). 16.04 GA was the first OS on it and the
soft-power-off stuff has never worked on it. I just finally got
around to filing the bug.

> Was there a prior kernel version where you were not having this particular problem?

No, see above

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

Sure, but can't do that until this weekend.

>
> 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'.
>
> Once testing of the upstream kernel is complete, please mark this bug as
> "Confirmed".

Got it.

[Jeff Lane  (bladernr)]

So tested it, it works in 4.12, and 4.10 and 4.8. something else is going on though, I think I was just not patient enough, but IMO the power off shouldn't take 5 minutes to accomplish.

So where I thought the power off just wasn't happening, I was incorrect, it does happen, it just took several minutes to get there.

However, I also found that period to be fairly random in that on some attempts it would power off within a few seconds, in some it would take a few minutes. Not sure why, but that seems to be the key.

In a couple instances it looked like it was hung on an unmount operation, then after something like a 180 second timeout (IIRC) it went ahead and completed.

[Jeff Lane  (bladernr)]

Going to mark this as invalid for now, as the bug doesn't capture the root cause. I'll try to dig into this at a later date and raise a more appropriate bug.