after upgrade from 3.13.0-43 to -44, UEFI system will not boot past grub

[MattW (seattle)]

I upgaded to -44 from -43 and my UEFI system (Dell Optiplex 3020) wont boot - i see grub, it starts, then collapses
back to the initramfs prompt

I downgraded to -43 and it works again

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-44-generic (not installed)
ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
Uname: Linux 3.13.0-43-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC2: mbw 2829 F.... pulseaudio
 /dev/snd/controlC0: mbw 2829 F.... pulseaudio
 /dev/snd/controlC1: mbw 2829 F.... pulseaudio
CurrentDesktop: Unity
Date: Mon Jan 12 15:51:45 2015
HibernationDevice: RESUME=UUID=ad3d0446-a2b9-4af5-8e88-3cdf6e9fd23d
InstallationDate: Installed on 2015-01-07 (5 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
MachineType: Dell Inc. OptiPlex 3020
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-43-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding.
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-43-generic N/A
 linux-backports-modules-3.13.0-43-generic N/A
 linux-firmware 1.127.11
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/14/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A03
dmi.board.name: 04YP6J
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 15
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA03:bd04/14/2014:svnDellInc.:pnOptiPlex3020:pvr01:rvnDellInc.:rn04YP6J:rvrA01:cvnDellInc.:ct15:cvr:
dmi.product.name: OptiPlex 3020
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.19 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19-rc4-vivid/

[MattW (seattle) (mbw)]

I just installed this kernel:

linux-headers-3.19.0-031900rc4-generic_3.19.0-031900rc4.201501112135_amd64.deb
linux-image-3.19.0-031900rc4-generic_3.19.0-031900rc4.201501112135_amd64.deb

as a test, as requested, but it also would not boot

Just added this tag:

kernel-bug-exists-upstream

[MattW (seattle) (mbw)]

The machine is On BIOS A03 on Dell Optiplex 3020, UEFI boot (not secure boot)

I just Upgraded to BIOS A05, no change in problem

Grub starts, if I dont touch the keyboard and the new kernel boots by default, I sometimes see this error:

loading linux 3.19.0-03a902.rc4
loading initial ramdisk...

ignoring BGRT: invalid status 0 (expected 1)

gave up waiting for root-dev

Alert /dev/mapper/ubuntu--vg-root does not exist, dropping to shell

Busybox

(initramfs)

If I boot Recovery of the same kernel, I get a bunch of devices listed, then it locks up

[Joseph Salisbury (jsalisbury)]

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org.

Once this bug is reported upstream, please add the tag: 'kernel-bug-reported-upstream'.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel

[penalvch (penalvch)]

MattW, before filing this upstream, the next step is to fully commit bisect from kernel 3.13.0-43 to 3.13.0-44 in order to identify the last good kernel commit, followed immediately by the first bad one. This will allow for a more expedited analysis of the root cause of your issue. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

Please note, finding adjacent kernel versions is not fully commit bisecting.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]