Kernel 4.15.0-13.14 reboots instead of powering off (when on battery) on HP Spectre x360 ae-000x

Bug #1760110 reported by Dmitry Malykhanov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

This might be a duplicate of #1756455

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-13 the system does not power off but instead reboots. Both halt -p from the command line and menu action leads to reboot instead of turning hardware off. 4.15.0-12 has the same problem (see #1756455). Booting with kernel 4.15.0-10 resolves the issue, system turns off power and stays powered off.

* 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-13 correctly powers off system only when running on AC

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

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-13-generic 4.15.0-13.14
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: dmitry 1648 F.... pulseaudio
CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
Date: Fri Mar 30 14:39:28 2018
HibernationDevice: RESUME=UUID=7b592f97-cd3d-46d3-8183-1685fd2441b4
InstallationDate: Installed on 2018-03-10 (20 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
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-13-generic N/A
 linux-backports-modules-4.15.0-13-generic N/A
 linux-firmware 1.173
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
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

Revision history for this message
Dmitry Malykhanov (dmalykhanov) wrote :
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) 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 :

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

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

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Dmitry Malykhanov (dmalykhanov) wrote :

The system was originally installed using a snapshot ISO which had kernel 4.15.0-10. And everything was working great, system was powering off as expected. I still keep this kernel installed and actually use it daily. So everything was working fine with 4.15.0-10.11.

I have not tried the 4.16 release yet (will do soon), but 4.16.0-041600rc7 was sort of similar. The 4.15.0-12 and 4.15.0-13 just do not power off (and instead reboot the machine) 100% of the time. With 4.16rc7 it was more like 50/50 (could not figure out the pattern yet). Will try the 4.16 release and report back.

tags: added: kernel-bug-exists-upstream
Revision history for this message
Dmitry Malykhanov (dmalykhanov) wrote :

Generally 4.16.0-041600.201804012230 seems to have the same problem. "Generally" means that 4.16 behaviour seems to be even more random - sometimes it powers off correctly, and sometimes it does not power off even on AC (and reboots). Unfortunately, I could not figure out the exact rules and conditions. However, most of the time 4.16 fails to cut the power and reboots the box instead.

And 4.15.0-10.11 is rock solid, always powers off as expected.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Can you do a kernel bisect between 4.15.0-10.11 and 4.15.0-12?

Revision history for this message
Dmitry Malykhanov (dmalykhanov) wrote :

4.15.0-12 had the same problem, please see #1756455 [1] (which is absolutely the same as this one).

I have also tried all mainline kernels from 4.15.3 up to 4.17rc1, and here are the results:

* all mainline kernels in branch 4.15 do NOT have any issues
* starting with mainline 4.16.0 it is impossible to shut down (reboots instead)
* Ubuntu kernel 4.15.0-12 HAS this problem

So this regression was introduced in Ubuntu kernel 4.15.0-12, and in mainline kernel 4.16

1. https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1756455

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.