Comment 4 for bug 1366546

This may be the bug that is affecting me.
I have a Lenovo Carbon 2. During about half the kernel updates in Utopic, the computer subsequently refused to boot. AT ALL.
I had the bios setting set to dual, with UEFI first and legacy second. But changing bios setting to "legacy" did not work.
My only solution was to re-install with a different kernel.
(I went back to Trusty, which worked.)
I have another Lenovo computer that did not have this problem at all, runs Utopic like a champ, with every update.
I have been unable to file a bug report because I seem to have no useful information.

I am worried because today, 10/29 Trusty installed kernel 39 during my morning updates. So I ran update-grub immediately to ascertain which kernel I was currently running, and which I would next boot into.
My currently working kernel is 37.
(You will note that I have lowlatency installed too. I have tested. There is no difference in boot behavior between low-latency and generic. )

Found linux image: /boot/vmlinuz-3.13.0-39-lowlatency
Found initrd image: /boot/initrd.img-3.13.0-39-lowlatency
Found linux image: /boot/vmlinuz-3.13.0-39-generic
Found initrd image: /boot/initrd.img-3.13.0-39-generic
Found linux image: /boot/vmlinuz-3.13.0-37-lowlatency
Found initrd image: /boot/initrd.img-3.13.0-37-lowlatency
Found linux image: /boot/vmlinuz-3.13.0-37-generic
Found initrd image: /boot/initrd.img-3.13.0-37-generic
Adding boot menu entry for EFI firmware configuration
done

If I shut my computer down and then re-boot and I cannot boot, which is what I expect will happen, I will update this comment.