This backport patchset is not successful. There are multiple platform regressions that appear intransigent. Therefore, I've reverted all patches related to Secure Boot and signed module enforcement. This should restore arm64 EFI functionality. Platforms wishing to use secure boot and signed module enforcement must install lts-xenial.
git://kernel.ubuntu.com/rtg/ubuntu-trusty.git arm64-efi-lp1608854-revert test kernel at http://people.canonical.com/~rtg/arm64-efi- lp1608854-revert/ -- 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/1608854 Title: [arm64] nova instances can't boot with 3.13.0-92 Status in debian-installer package in Ubuntu: New Status in linux package in Ubuntu: Fix Released Status in debian-installer source package in Trusty: New Status in linux source package in Trusty: In Progress Bug description: Hi, It would appear that arm64 nova instances can't boot on 3.13.0-92. The serial console displays : error: plain Image kernel not supported - rebuild with CONFIG_(U)EFI_STUB enabled. unaligned pointer 0xb90002e058000c57 Aborted. Press any key to exit. I suspect this is due to LP#1566221, more specifically : * [Config] CONFIG_EFI=n for arm64 This is pretty serious. I'm not 100% sure the above is the cause, but if so, it should be reverted asap. Thank you. --- AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [ 27.314355] random: nonblocking pool is initialized [ 43.711734] init: jenkins-slave main process (1169) terminated with status 143 DistroRelease: Ubuntu 14.04 Ec2AMI: ami-000008ce Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.medium Ec2Kernel: None Ec2Ramdisk: None IwConfig: lo no wireless extensions. eth0 no wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic root=UUID=88f61243-be05-46db-b772-d7ed13eb39de ro earlyprintk ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36 RelatedPackageVersions: linux-restricted-modules-3.13.0-85-generic N/A linux-backports-modules-3.13.0-85-generic N/A linux-firmware 1.127.22 RfKill: Error: [Errno 2] No such file or directory Tags: trusty ec2-images Uname: Linux 3.13.0-85-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1608854/+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
