Yep, if it boots fine, i usually retry 2/3 times, and it has happened that it failed only the second or the third time i tried.
Anyhow, now i'm down to this delta .config (the initial one had ~2k entries), so the bug appears to be ACPI related: ------------------------------------------------------------------------------- CONFIG_ACPI=y CONFIG_ACPI_APEI=y CONFIG_ACPI_APEI_GHES=y CONFIG_ACPI_APEI_MEMORY_FAILURE=y CONFIG_ACPI_APEI_PCIEAER=y CONFIG_ACPI_APEI_SEA=y CONFIG_ACPI_BGRT=y CONFIG_ACPI_BUTTON=y CONFIG_ACPI_CCA_REQUIRED=y CONFIG_ACPI_CONTAINER=y CONFIG_ACPI_CPPC_LIB=y CONFIG_ACPI_DOCK=y CONFIG_ACPI_FAN=y CONFIG_ACPI_GENERIC_GSI=y CONFIG_ACPI_GTDT=y CONFIG_ACPI_HED=y CONFIG_ACPI_HOTPLUG_CPU=y CONFIG_ACPI_I2C_OPREGION=y CONFIG_ACPI_IORT=y CONFIG_ACPI_MCFG=y CONFIG_ACPI_NUMA=y CONFIG_ACPI_PCI_SLOT=y ------------------------------------------------------------------------------- How to reproduce it from d05-6 - 192.168.122.14 is my kvm instance: $ make defconfig $ cat $abovedelta >> .config $ make olddefconfig $ make -j65 $ scp arch/arm64/boot/Image ubuntu@192.168.122.14:. $ ssh ubuntu@192.168.122.14 and inside the kvm instance: $ sudo cp Image /boot/ and when rebooting, presc Esc at the grub menu, select the "Image" entry previously created[*] *: in /boot/grub/grub.cfg create a copy of the default Ubuntu instance, but use /boot/Image instead of /boot/vmlinuz-x.y.z, remove "quiet splash" from the default argument and rename it 'Image' -- 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/1749040 Title: KPTI support for arm64 systems Status in linux package in Ubuntu: Incomplete Status in linux source package in Artful: In Progress Status in linux source package in Bionic: Incomplete Bug description: While regression testing the current linux-hwe proposed kernel (4.13.0-33.36~16.04.1), I found that it fails to boot on a Cavium ThunderX CRB. I've rebooted twice since upgrading from the current -updates kernel, and it's failed to boot both times, with different failure modes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749040/+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
