Linux 4.4.0-113.136 (i386/x86_32): failed to boot when 'kaslr' option is in use.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
High
|
Unassigned | ||
Xenial |
Expired
|
High
|
Unassigned |
Bug Description
Hello.
On Thu Feb 8, Linux kernel for Ubuntu 16.04.3 LTS has been updated to the 4.4.0-113.136 version (xenial-proposed). However, after reboot, plymouth freezes during start, and keys on an USB keyboard were in-active. After several seconds, the BusyBox shell screen appeared. It looks this way:
,------
| BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
| Enter 'help' for a list of built-in commands.
|
| (initramfs) _
`------
Unfortunately, the USB keyboard does not work and does not respond. The only way to solve this issue is a "hard reset" and in GRUB menu choosing an earlier kernel, which is linux 4.4.0-112.135. Now, everything works okay.
Proposed update to the Linux 4.4.0-113.136 contains many new updates (please see 1.) It's an i386/x86_32 architecture, which does not contain PTI yet, right? I'm asking, because mentioned -proposed updates contains a couple of PTI-related patches and bugs in PTI can cause a few different signatures of crashes etc. For example:
→ Crashes in early boot, especially around CPU bringup. Bugs in the trampoline code or mappings cause these.
→ Userspace segfaults early in boot, sometimes manifesting as mount(8) failing to mount the rootfs. These have tended to be TLB invalidation issues. Usually invalidating the wrong PCID, or otherwise missing an invalidation.
NOTE: if it's about PCID, which is mentioned in a second point, there is one patch in -proposed update: "x86/mm/32: Move setup_clear_
● UPDATE/WARNING: It seems, that 'kaslr' option is responsible for this issue. After booting the latest v4.4.0-115.139 kernel, I've had the same problems as described above. However, after removing 'kaslr' option from a command line via GRUB menu, system started normally etc. The latest, working kernel with 'kaslr' option is v4.4.0-112.135. According to all of this I think, that 'kaslr' is not compatible with some "Spectre & Meltdown" mitigation patches and fixes etc.
✗ Release ('/proc/
✗ Architecture: i386/x86_32
✗ PCI ('lspci -vnvn'): 00:0a.0 PCI bridge [0604]: NVIDIA Corporation MCP73 PCI Express bridge [10de:056d] (rev a1) (prog-if 01 [Subtractive decode]) Capabilities: [b8] Subsystem: Gigabyte Technology Co., Ltd MCP73 PCI Express bridge [1458:026f]
Thanks, regards.
________________
1. https:/
description: | updated |
description: | updated |
tags: | added: xenial |
description: | updated |
summary: |
Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1 - built-in shell. + built-in shell (initramfs). |
description: | updated |
tags: | added: kaslr |
summary: |
- Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1 - built-in shell (initramfs). + Linux 4.4.0-113.136 (i386/x86_32): failed to boot when 'kaslr' option is + in use. |
Changed in linux (Ubuntu): | |
status: | Confirmed → Incomplete |
Changed in linux (Ubuntu Xenial): | |
status: | Confirmed → Incomplete |
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 1748710
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.