[HP Spectre x360 - 13-ae004na] On battery kernel 4.15.0-12 reboots instead of turning off

[Dmitry Malykhanov]

Ubuntu 18.04, installed from beta 1 ISO + all updates to date

HP Spectre x360 13", model 13-ae004na, secure boot on, latest BIOS F.15A, Ubuntu is the only system on disk.

When using kernel 4.15.0-12 the system does not power off but instead reboots. Both halt -p from the command line and menu action leads to reboot. Booting with previous kernel 4.15.0-10 resolves the issue, system turns off power as expected.

I am not attaching any logs because I cannot see anything unusual there, kern.log entries from 4.15.0-10 and 4.15.0-12 seems to be identical (in fact, there is only one entry there "msr: Direct access to MSR 1b0"). Please let me know what additional information you may need.
---
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: dmitry 1568 F.... pulseaudio
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=UUID=7b592f97-cd3d-46d3-8183-1685fd2441b4
InstallationDate: Installed on 2018-03-10 (13 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180309)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 8087:0a2b Intel Corp.
 Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP Spectre x360 Convertible 13-ae0xx
Package: linux-signed
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-12-generic N/A
 linux-backports-modules-4.15.0-12-generic N/A
 linux-firmware 1.173
Tags: bionic
Uname: Linux 4.15.0-12-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 02/22/2018
dmi.bios.vendor: AMI
dmi.bios.version: F.15
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 83B9
dmi.board.vendor: HP
dmi.board.version: 56.37
dmi.chassis.type: 31
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAMI:bvrF.15:bd02/22/2018:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.37:cvnHP:ct31:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Spectre
dmi.product.name: HP Spectre x360 Convertible 13-ae0xx
dmi.sys.vendor: HP

[Dmitry Malykhanov (dmalykhanov)]

Recent linux-firmware update (1.172 -> 1.173) somehow resolved this issue, although I cannot spot anything relevant in the changelog.

[Dmitry Malykhanov (dmalykhanov)]

OK, as expected linux-firmware upgrade seems to be unrelated. After doing more than two dozen shutdowns with each kernel (4.15.0-10 and 4.15.0-12) I see the following pattern:

* secure boot enabled or disabled makes no difference

* kernel 4.15.0-10 correctly powers off system (halt -p) every time, power source makes no difference

* kernel 4.15.0-12 correctly powers off system only when running on AC

* kernel 4.15.0-12 does NOT power off system (reboots instead) when AC power is NOT connected (running on battery) every time

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

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1756455

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Dmitry Malykhanov (dmalykhanov)]

apport information

[Dmitry Malykhanov (dmalykhanov)]

apport information

[Dmitry Malykhanov (dmalykhanov)]

apport information

[Dmitry Malykhanov (dmalykhanov)]

apport information

[Dmitry Malykhanov (dmalykhanov)]

apport information

[Dmitry Malykhanov (dmalykhanov)]

apport information

[Dmitry Malykhanov (dmalykhanov)]

apport information

[Dmitry Malykhanov (dmalykhanov)]

apport information

[Dmitry Malykhanov (dmalykhanov)]

apport information

[Dmitry Malykhanov (dmalykhanov)]

apport information

[Dmitry Malykhanov (dmalykhanov)]

apport information

[Dmitry Malykhanov (dmalykhanov)]

apport information

[penalvch (penalvch)]

Dmitry Malykhanov, the next step is to fully commit bisect from Ubuntu kernel 4.15.0-10.11 to Ubuntu kernel 4.15.0-12.13, in order to identify the last good kernel commit, followed immediately by the first bad one. This will allow for a more expedited analysis of the root cause of your issue. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ? This article was written for folks who don't know anything about linux, so it's easy to follow.

Please note, finding adjacent kernel versions, or providing a commit without testing it and reverting it is not fully commit bisecting.

Also, the kernel release names are irrelevant for the purposes of bisecting.

It is most helpful that after the bad commit (not kernel version) has been confirmed via testing, you then mark this report Status Confirmed.

Thank you for your help.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]