Bug 205237
Summary: | acpi_osi= needed for system to boot with acpi=off - HP Pavillion x360 13 inch | ||
---|---|---|---|
Product: | ACPI | Reporter: | Ilgaz Öcal (ilgaz) |
Component: | Config-Other | Assignee: | acpi_config-other |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | ilgaz, kai.heng.feng, rui.zhang |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 5.9.1 | Subsystem: | |
Regression: | No | Bisected commit-id: |
Description
Ilgaz Öcal
2019-10-18 05:57:33 UTC
Apologies for typo: It isn't Ubuntu 16.10 which I tested, it is 19.10. 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=!. 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. 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. As of Kernel 5.8.12 this "bug" doesn't exist anymore. Actually, when you enable the workaround (ACPI_OSI=) in Fedora 33 beta 1 it will fail to boot stating the following: atkbd serio09: unknown key pressed (translated set 2, code 0xd7) It didn't boot after stating that several times so I removed the ACPI_OSI= which I passed to kernel, it booted fine afterwards. Whoever fixed it, thank you on behalf of HP Pavilion x360 users. As I don't know the kernel bugzilla, I am not closing the bug. Feel free to do so. update: With the current kernel, you need to put ACPI_OSI=! to boot the device. Older ACPI_OSI= will disable entire USB functionality. sorry for bugging the list. There is a strange issue now that when I pass ACPI_OSI=! (in uppercase) to kernel, it gets ignored but acpi_osi=! (in lowercase) works. As of current 5.9.1 kernel (opensuse tumbleweed), this argument is no longer needed for a proper boot. It still complains about firmware regions not being covered otherwise it boots fine with all ACPI functionality seeming to work fine. |