acpi problem: ubntu freezes when booting asus zenbook
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
I am using a Asus Zenbook UX360U with an Intel Core I7-7500U CPU and an Intel HD Graphics 620 chip set.
Now I wanted to install the latest Ubuntu 16.04.2 LTS in parallel to the chipped Windows 10. To make this possible, I already had to set the acpi=off boot option in the usb grub and disable the secure load in the bios to load from the usb live stick.
In this way, the system installed itself correctly, and I can see the new grub2 boot options. While Windows still boots perfectly, I am not able to boot to Ubuntu. Instead, Ubuntu freezes 4 out of 5 times after I selected the respective boot option. A similar problem has been described here http://
Following the acpi debugging instructions listed here https:/
unable to handle kernel paging request at ...
in kmem_cache_all or __kmalloc.
Since the problem starts already with the acpi=ht option enabled, the acpi debugging guide states that "the issue is in the ACPI table parsing code itself, or perhaps the SMP code."
Is there a way to fix this problem?
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-
ProcVersionSign
Uname: Linux 4.8.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Feb 28 09:54:44 2017
InstallationDate: Installed on 2017-02-26 (2 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
SourcePackage: linux-hwe
UpgradeStatus: No upgrade log present (probably fresh install)
affects: | linux-hwe (Ubuntu) → linux (Ubuntu) |
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 1668537
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.