Ubuntu stuck at boot screen after latest kernel update

[Alexander Rechsteiner]

The last update performed by the "Software Updater" application has broken my system. When booting, the screen will be stuck at the Ubuntu logo seen here: http://i.imgur.com/nfVflMN.png

When I boot into Grub and choose to use the previous kernel (3.19.0-43-generic) then I can boot without a problem: http://i.imgur.com/uosNyE8.png

The kernel causing trouble is 3.19.0-51-generic

I'm using Ubuntu on VMWare Workstation 11.1.3 build-3206955.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ubuntu-release-upgrader-core 1:0.220.8
ProcVersionSignature: Ubuntu 3.19.0-49.55~14.04.1-generic 3.19.8-ckt12
Uname: Linux 3.19.0-49-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: Unity
Date: Fri Feb 26 13:07:55 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-09-01 (178 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: alex 2165 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.04
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-09-01 (182 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 004: ID 0e0f:0008 VMware, Inc.
 Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
 Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: VMware, Inc. VMware Virtual Platform
Package: linux (not installed)
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-49-generic root=UUID=b4bb6101-fffa-43e0-8f65-12ceb3dba3e6 ro quiet splash
ProcVersionSignature: Ubuntu 3.19.0-49.55~14.04.1-generic 3.19.8-ckt12
RelatedPackageVersions:
 linux-restricted-modules-3.19.0-49-generic N/A
 linux-backports-modules-3.19.0-49-generic N/A
 linux-firmware 1.127.20
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
Tags: trusty
Uname: Linux 3.19.0-49-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/20/2014
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/20/2014:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1550311

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Alexander Rechsteiner (ubuntu-hwbqs6tox1bv6csee9psn)]

apport information

[Alexander Rechsteiner (ubuntu-hwbqs6tox1bv6csee9psn)]

apport information

[Alexander Rechsteiner (ubuntu-hwbqs6tox1bv6csee9psn)]

apport information

[Alexander Rechsteiner (ubuntu-hwbqs6tox1bv6csee9psn)]

apport information

[Alexander Rechsteiner (ubuntu-hwbqs6tox1bv6csee9psn)]

apport information

[Alexander Rechsteiner (ubuntu-hwbqs6tox1bv6csee9psn)]

apport information

[Alexander Rechsteiner (ubuntu-hwbqs6tox1bv6csee9psn)]

apport information

[Alexander Rechsteiner (ubuntu-hwbqs6tox1bv6csee9psn)]

apport information

[Alexander Rechsteiner (ubuntu-hwbqs6tox1bv6csee9psn)]

apport information

[Alexander Rechsteiner (ubuntu-hwbqs6tox1bv6csee9psn)]

apport information

[Alexander Rechsteiner (ubuntu-hwbqs6tox1bv6csee9psn)]

apport information

[Alexander Rechsteiner (ubuntu-hwbqs6tox1bv6csee9psn)]

apport information

[Alexander Rechsteiner (ubuntu-hwbqs6tox1bv6csee9psn)]

apport information

[penalvch (penalvch)]

Alexander Rechsteiner, thank you for reporting this and helping make Ubuntu better.

In order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically requested to do so.

Once testing of the latest upstream kernel is complete, please mark this report Status Confirmed. Please let us know your results.

Thank you for your understanding.

[Alexander Rechsteiner (ubuntu-hwbqs6tox1bv6csee9psn)]

I'm not able to reproduce this issue anymore. I've been prompted by the Software Updater to install some updates again, and since then I'm able to boot using the latest kernel.

[penalvch (penalvch)]

Alexander Rechsteiner, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1550311/comments/18 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.