That's good news that 4.10-rc3 fixes the bug. I think it would be best
to perform a "Reverse" bisect to identify the fix that is already
upstream versus continuing a regular bisect to find the commit that
introduced the bug.
For a reverse bisect, we need to find the last bad kernel version and
first good one. We now know that v4.10-rc3 is good. Can you next text
4.10-rc1? It is available from:
If 4.10-rc1 is good, we would want to test 4.9 and it's release candidates,
then if needed, 4.8, etc.
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13
Status in linux package in Ubuntu:
Status in linux source package in Trusty:
The EFI stub loader produces consistent boot errors when booting
Trusty starting with version 3.13.0-101-generic. This bug can be
reproduced in many ways (using efibootmgr, an EFI shell, rEFInd,
etc.). One approach is:
1) Install an EFI shell on the computer and set it as the default boot
option using efibootmgr.
2) Copy the kernel and initrd files from /boot to /boot/efi.
3) Rename the kernel file to use a .efi filename extension.
4) Reboot into the EFI shell.
5) Try to launch the kernel with a command like:
fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2
The result will be a hung or crashed system. (In VirtualBox, in which
I've tested this, the VM produces a "guru meditation" and the session
I myself have tested only with the 3.13.0-104 kernel; however, reports
from others indicate that the problem began with the 3.13.0-101
kernel. See this Kubuntu forum thread for details:
Note that early on, this thread focuses on rEFInd; however, the bug
can be reproduced with other boot managers, including the EFI shell,
as described in the preceding procedure, so I do not believe this is a
rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux
kernel, and I believe it's this component that's failing. The problem
does NOT occur when using GRUB to launch the kernel. (GRUB does not
rely on the EFI stub loader.)
I have NOT encountered the problem with Xenial and its 4.4.0-series kernels
(last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last
tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from
series beyond 3.13.0.
USER PID ACCESS COMMAND
/dev/snd/controlC0: rodsmith 1675 F.... pulseaudio
DistroRelease: Ubuntu 14.04
InstallationDate: Installed on 2014-04-27 (960 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
eth0 no wireless extensions.
lo no wireless extensions.
Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
Package: linux (not installed)
ProcFB: 0 EFI VGA
root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39
Uname: Linux 3.13.0-106-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.vendor: innotek GmbH
dmi.board.vendor: Oracle Corporation
dmi.chassis.vendor: Oracle Corporation
dmi.sys.vendor: innotek GmbH
To manage notifications about this bug go to:
Mailing list: https://launchpad.net/~kernel-packages
Post to : firstname.lastname@example.org
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp