This bug was fixed in the package linux - 4.8.0-19.21
---------------
linux (4.8.0-19.21) yakkety; urgency=low
[ Tim Gardner ]
* Release Tracking Bug
- LP: #1629057
* 4.8.0 kernels do not complete boot process on VM (LP: #1627198)
- [Config] CONFIG_HARDENED_USERCOPY_PAGESPAN=n
* mount-image-callback cannot mount partitioned disk image (LP: #1628336)
- SAUCE: nbd: Only delay uevent until connected
* Support snaps inside of lxd containers (LP: #1611078)
- apparmor: add interface to be able to grab loaded policy
- securityfs: update interface to allow inode_ops, and setup from vfs fns
- apparmor: refactor aa_prepare_ns into prepare_ns and create_ns routines
- apparmor: add __aa_find_ns fn
- apparmor: add mkdir/rmdir interface to manage policy namespaces
- apparmor: fix oops in pivot_root mediation
- apparmor: fix warning that fn build_pivotroot discards const
- apparmor: add interface to advertise status of current task stacking
- apparmor: update policy permissions to consider ns being viewed/managed
- apparmor: add per ns policy management interface
- apparmor: bump domain stacking version to 1.2
* linux-image-extra-4.8.0-17-generic does not provide many sound card modules
(LP: #1628523)
- [Config] CONFIG_ZONE_DMA=y for generic
* Yakkety - disable ARCH_ZX (LP: #1628503)
- [Config] armhf: disable ARCH_ZX
* Enable switchdev config parameter for Yakkety (LP: #1628241)
- [Config] CONFIG_NET_SWITCHDEV=y for amd64/arm64
* Ubuntu 16.10 kernel v4.8: Installation failing on Habanero with Shiner card
(LP: #1628009)
- firmware: Update bnx2x to 7.13.1.0
* vNIC driver missing in 4.8 kernel package (LP: #1628187)
- [Config] Enable CONFIG_IBMVNIC=m
* Yakkety - armhf: MFD_TPS65217 and REGULATOR_TPS65217 are boot essential
(LP: #1628112)
- [Config] armhf: MFD_TPS65217=y && REGULATOR_TPS65217=y
* Miscellaneous Ubuntu changes
- Rebase to v4.8-rc8
- [Config] skip Ubuntu-4.8.0-18.20
- [Config] missing modules in armhf/s390x
* Miscellaneous Ubuntu changes
- rebase to v4.8-rc8
-- Leann Ogasawara <leann.ogasaw...@canonical.com> Sun, 25 Sep 2016
12:13:35 -0700
** Changed in: linux (Ubuntu Yakkety)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1627198
Title:
4.8.0 kernels do not complete boot process on VM
Status in Linux:
Unknown
Status in linux package in Ubuntu:
Fix Released
Status in linux-raspi2 package in Ubuntu:
Fix Committed
Status in linux source package in Yakkety:
Fix Released
Status in linux-raspi2 source package in Yakkety:
Fix Committed
Bug description:
On my native amd64 box, 4.8.0-15 works just fine, but on my VMWare
Fusion 8.5 system, none of the 4.8.0 kernels complete the boot
process. I tried 4.8.0-15 from yakkety and 4.8.0-16 from yakkety-
proposed.
Currently I am seeing the last message in my console at boot up as:
[ OK ] Started Bluetooth service
and then... it just sits there.
Through the use of snapshots, restores, and package bisects, I've
definitively narrowed it to linux-generic linux-image-generic and
linux-headers-generic.
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1627198/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
