[HP Pavilion 360 - 13-a200nt (ENERGY STAR)] Kernel parameter acpi_osi= required to boot

[Ilgaz]

When booting my HP Pavilion 360 - 13-a200nt (ENERGY STAR), it stops with just a non-blinking white cursor on screen in the top left, and the Caps Lock doesn't respond when pressed.

Previously on 4.x kernels, system would boot using acpi=off argument creating more problems.

WORKAROUND: Boot with kernel parameter:
acpi_osi=

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ilgaz 21270 F.... pulseaudio
 /dev/snd/controlC1: ilgaz 21270 F.... pulseaudio
 /dev/snd/pcmC1D0p: ilgaz 21270 F...m pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 17 10:02:44 2019
HibernationDevice: RESUME=UUID=f34af719-8757-473b-848b-7db85d6fefae
InstallationDate: Installed on 2019-10-13 (3 days ago)
InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227)
MachineType: Hewlett-Packard HP Pavilion 13 x360 PC
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic root=UUID=f6787f82-d072-410e-8058-2b7f14d012b9 ro verbose pci=biosirq acpi_osi=
RelatedPackageVersions:
 linux-restricted-modules-5.3.0-18-generic N/A
 linux-backports-modules-5.3.0-18-generic N/A
 linux-firmware 1.183
SourcePackage: linux
UpgradeStatus: Upgraded to eoan on 2019-10-16 (0 days ago)
dmi.bios.date: 06/21/2018
dmi.bios.vendor: Insyde
dmi.bios.version: F.41
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 2341
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 07.0A
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsyde:bvrF.41:bd06/21/2018:svnHewlett-Packard:pnHPPavilion13x360PC:pvr0977120000405F00000410180:rvnHewlett-Packard:rn2341:rvr07.0A:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
dmi.product.name: HP Pavilion 13 x360 PC
dmi.product.sku: L0B89EA#AB8
dmi.product.version: 0977120000405F00000410180
dmi.sys.vendor: Hewlett-Packard

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

This change was made by a bot.

[Kai-Heng Feng (kaihengfeng)]

Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4-rc3/

[Ilgaz (ilgaz)]

I just tested, without acpi_osi= , it freezes. I'd love to provide more details but as I said, it is just a blank screen with cursor, external HDD light is off, caps lock doesn't seem to work.

uname -ar
Linux ilgaz-HP-Pavilion-13-x360-PC 5.4.0-050400rc3-generic #201910132031 SMP Mon Oct 14 00:33:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

[Ilgaz (ilgaz)]

I tried once more with no dkms modules. It gets stuck in "loading ramdisk". Nothing happens and doesn't respond.

[ilgaz (ilgaz-linux-kernel-bugs)]

Kernel 4.x could boot with acpi=off with severely decreased functionality (battery, wifi, screenbacklight) however 5.x kernels, including the latest 5.4-rc3 freezes at "loading ramdisk" step unless you pass acpi_osi= (null, nothing after =) to kernel.

There is no visible log/feedback produced so users tend to give up and move on to other operating systems hence there isn't any tips regarding this workaround except couple of pages.

I can boot fine with acpi_osi= argument. I tested latest RC (using Ubuntu 16.10) however it effects every kernel out there, on this particular machine.

I can provide more details, even a root shell if it can help.

More possible machine details etc. are at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848445

[ilgaz (ilgaz-linux-kernel-bugs)]

Apologies for typo: It isn't Ubuntu 16.10 which I tested, it is 19.10.

[penalvch (penalvch)]

Ilgaz:

1) Could you please provide from the the sticker of the computer itself (not from the Bug Description, or the result of a terminal command) the full computer model? For example, HP Pavilion 13-u100 x360 Convertible PC.

2) Could you please undo all WORKAROUNDs and non-default kernel parameters and provide logs of a bad boot following https://wiki.ubuntu.com/DebuggingKernelBoot ?

3) Could you please advise to the purpose of the non-default kernel parameter pci=biosirq (i.e. is it required along with acpi_osi=, does it improve functionality with or without other parameters, etc.)?

[Ilgaz (ilgaz)]

Ilgaz:

1) Could you please provide from the the sticker of the computer itself (not from the Bug Description, or the result of a terminal command) the full computer model? For example, HP Pavilion 13-u100 x360 Convertible PC.

Model 13-a200nt PN: L0B69EA#AB8

2) Could you please undo all WORKAROUNDs and non-default kernel parameters and provide logs of a bad boot following https://wiki.ubuntu.com/DebuggingKernelBoot ?

Apologies since it is impossible. Just tried following the instructions on the referenced page. I just get a blank screen with no visible sign of anything happening. Caps lock led doesn't function either so I believe keyboard isn't functioning at all.

However, here is the dmesg |grep ACPI output from the "acpi_osi=" argument booted kernel. Perhaps it can help?
dmesg |grep ACPI
[ 0.000000] BIOS-e820: [mem 0x000000009cdbf000-0x000000009cfbefff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x000000009cfbf000-0x000000009cffefff] ACPI data
[ 0.000000] efi: SMBIOS=0x9cb30000 ESRT=0x9cb35718 ACPI 2.0=0x9cffe014
[ 0.016525] ACPI: Early table checksum verification disabled
[ 0.016530] ACPI: RSDP 0x000000009CFFE014 000024 (v02 HPQOEM)
[ 0.016535] ACPI: XSDT 0x000000009CFFE120 0000C4 (v01 HPQOEM SLIC-MPC 00000001 01000013)
[ 0.016544] ACPI: FACP 0x000000009CFEF000 00010C (v05 HPQOEM SLIC-MPC 00000001 HP 00040000)
[ 0.016554] ACPI: DSDT 0x000000009CFDC000 00E8EE (v02 HPQOEM SLIC-MPC 00000000 ACPI 00040000)
[ 0.016559] ACPI: FACS 0x000000009CFB9000 000040
[ 0.016563] ACPI: UEFI 0x000000009CFFD000 000236 (v01 HPQOEM 2341 00000001 HP 00040000)
[ 0.016568] ACPI: UEFI 0x000000009CFFC000 000042 (v01 HPQOEM 2341 00000000 HP 00040000)
[ 0.016573] ACPI: SSDT 0x000000009CFF5000 0069E4 (v01 HPQOEM 2341 00001000 ACPI 00040000)
[ 0.016577] ACPI: MSDM 0x000000009CFF4000 000055 (v03 HPQOEM SLIC-MPC 00000001 HP 00040000)
[ 0.016582] ACPI: ASF! 0x000000009CFF3000 0000A5 (v32 HPQOEM 2341 00000001 HP 00040000)
[ 0.016587] ACPI: ASPT 0x000000009CFF2000 000034 (v07 HPQOEM 2341 00000001 HP 00040000)
[ 0.016591] ACPI: BOOT 0x000000009CFF1000 000028 (v01 HPQOEM 2341 00000001 HP 00040000)
[ 0.016596] ACPI: DBGP 0x000000009CFF0000 000034 (v01 HPQOEM 2341 00000001 HP 00040000)
[ 0.016600] ACPI: HPET 0x000000009CFEE000 000038 (v01 HPQOEM 2341 00000001 HP 00040000)
[ 0.016605] ACPI: LPIT 0x000000009CFED000 000094 (v01 HPQOEM 2341 00000000 HP 00040000)
[ 0.016609] ACPI: APIC 0x000000009CFEC000 00008C (v03 HPQOEM SLIC-MPC 00000001 HP 00040000)
[ 0.016614] ACPI: MCFG 0x000000009CFEB000 00003C (v01 HPQOEM 2341 00000001 HP 00040000)
[ 0.016619] ACPI: SSDT 0x000000009CFDA000 00143D (v02 HPQOEM 2341 00001000 ACPI 00040000)
[ 0.016623] ACPI: SSDT 0x000000009CFD9000 000539 (v02 HPQOEM 2341 00003000 ACPI 00040000)
[ 0.016628] ACPI: SSDT 0x000000009CFD8000 000B74 (v02 HPQOEM 2341 00003000 ACPI 00040000)
[ 0.016633] ACPI: SSDT 0x000000009CFD2000 005D09 (v02 HPQOEM 2341 00003000 ACPI 00040000)
[ 0.016637] ACPI: DMAR 0x000000009CFD1000 0000B0 (v01 HPQOEM 2341 00000001 HP 00040000)
[ 0.016642] ACPI: FPDT 0x0000000...

[penalvch (penalvch)]

Ilgaz:

A) I'm afraid providing logs from a working boot does nothing to help.

B) To clarify, you removed all of the following kernel parameters:
quiet
splash
vt.handoff=7
acpi_osi=
pci=biosirq

then changed:
gfxmode $linux_gfx_mode

to:

gfxmode text

and then got the bad boot? If so, please provide video evidence starting from the computer being off all the way to it stopped booting (e.g. take a video of the computer screen via phone, get logs, etc.). Please note, stating it was a bad boot isn't helpful given this was already known.

C) To further clarify, does removing the external HDD device (USB?) impact your ability to boot?

[penalvch (penalvch)]

Ilgaz:

1) To keep this relevant to upstream, you will want to continue to test the latest mainline kernel as it is released (now 5.4-rc5). Instructions are available via https://wiki.ubuntu.com/Kernel/MainlineBuilds .

2) Please review https://help.ubuntu.com/community/DebuggingSystemCrash and attempt all suggestions to see if something useful may be obtained.

[Ilgaz (ilgaz)]

I have installed the recommended mainline kernel, removed all third party modules too. I changed the arguments as suggested. It doesn't boot, just a blank screen not even a cursor.

[penalvch (penalvch)]

Ilgaz:

To advise, you have missed steps in two different comments, which are vital to proceed. Please ensure you are responding to all items requested.

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848445/comments/10:
C) To further clarify, does removing the external HDD device (USB?) impact your ability to boot?

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848445/comments/13:
2) Please review https://help.ubuntu.com/community/DebuggingSystemCrash and attempt all suggestions to see if something useful may be obtained.

[Ilgaz (ilgaz)]

1) I removed the USB external disk while booting 5.4-rc5 it didn't change anything.

2) There is nothing to get debug logs, even the ethernet chip isn't powered on at the stage where system freezes. No output on screen either. As I said before, keyboard doesn't work either.

Right now I am keeping the 5.4.rc5 installed, if anything more needed don't hesitate to contact.

[penalvch (penalvch)]

Ilgaz, to clarify, did you actually try to gather logs as per all techniques noted in https://help.ubuntu.com/community/DebuggingSystemCrash or are you making assumptions of your not being able to?

[Ilgaz (ilgaz)]

Yes, I know it is strange but there is no output to screen nor any way to interact with the computer. I can't carry any of the steps described on the referenced page.

[penalvch (penalvch)]

Ilgaz, to help developers debug a potential ACPI/BIOS bug, could you please install the package acpidump and attach to this report uncompressed and untarred the following via a terminal:
sudo acpidump -o acpidump.txt

[penalvch (penalvch)]

Ilgaz, could you please report this problem following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate mailing list (TO: Rafael J. Wysocki and Len Brown CC: linux-acpi)?

Please provide a direct URL to your post to the mailing list (not Bugzilla) when it becomes available so that it may be tracked.

Thank you for your help.

[Ilgaz (ilgaz)]

Bug report to linux-acpi mailing list: https://www.spinics.net/lists/linux-acpi/msg90609.html

[rui.zhang (rui.zhang-linux-kernel-bugs)]

it is really rare to see a system running with acpi=off.
May I know why acpi=off is used in the first place?

for this particular issue, please confirm if problem still exists with acpi_osi=!.

[rui.zhang (rui.zhang-linux-kernel-bugs)]

Bug closed as there is no response from the bug reporter.
Please feel free to reopen it if the problem still exists in the latest upstream kernel.

[ilgaz (ilgaz-linux-kernel-bugs)]

Apologies for the delay, I have been instructed to use kernel mailing list to report the bug.
System boots fine once you use acpi_osi= argument with complete functionality. This has been true for all 5.x kernels to this date.