Hi. I can not enter mentioned command, because during system boot plymouth freezes and keyboard is unresponsive. After several seconds plymouth disappears and BusyBox v1.22.1 "console" appears (here, keyboard does not work and does not respond either). The only solution is to use hard reboot and choose an earlier v4.4.0-112.135 Linux kernel in GRUB menu etc.
Maybe I can execute 'apport-collect 1748710' command in v4.4.0-112.135 kernel? But this issue appeared after update to the "-proposed" kernel: v4.4.0-112.135. Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1748710 Title: Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1 built-in shell. Status in linux package in Ubuntu: Confirmed 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 a keyboard were in-active. After several seconds, the BusyBox 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 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_cpu_cap(X86_FEATURE_PCID) earlier". Maybe that's is the cause of a boot failure? There are no errors in log files, such as '/var/log/syslog' or '/var/log/kern.log'. Maybe only that one (but I have no idea if it's important)? ✗ PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug If I could provide some more informations, please let me know. Here are some technical informations: ● Release ('/proc/version_signature'): Ubuntu 4.4.0-112.135-generic 4.4.98 ● 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://lists.ubuntu.com/archives/xenial- changes/2018-February/020108.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748710/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
