Comment 65 for bug 1649326

The kernel in linux-image-3.13.0-101-generic_3.13.0-101.148~lp1649326Commit3f049ea_amd64.deb fails to boot, but in different ways that seem to be somewhat random:

* Sometimes the warnings "Failed to get file info size" and
  "Failed to alloc highmem for files" appear.
* Sometimes, when launching from rEFInd, the above messages
  appear along with ASSERT messages from the UDK2014 tool
  kit used to build rEFInd, as shown in boot-failure.png.
* Sometimes the message (shown in boot-failure.png) "ASSERT
  fsw_efi.c(674): CR has Bad Signature" scrolls across the
  screen and fills it entirely. (Note that fsw_efi.c is a
  rEFInd filesystem driver file; however, I've also tested
  booting the kernel from the FAT32 ESP, and even with the
  rEFInd filesystem driver never loaded, and the kernel still
  fails to boot, so this is not a filesystem driver problem
  per se.)
* Sometimes (usually when doing a cold boot), the kernel
  loads but then panics, as shown in boot-failure-2.png.

Note that I've tried to boot this kernel in many ways -- via rEFInd, via the VirtualBox EFI shell; from the ext4fs root (/) filesystem via the rEFInd ext4fs driver, and from the FAT32 ESP; cold booting and warm booting. None of these approaches has worked, but the failure symptoms vary and are somewhat inconsistent, even when booting in exactly the same way -- sometimes the screen hangs with errors, other times that scrolling message about "CR has Bad Signature" appears; and error messages can vary randomly from one attempt to another.