Comment 29 for bug 1548587

I have installed linux-headers-4.2.8-040208ckt4 and linux-image-4.2.8-040208ckt4 from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.2.8-ckt4-wily/ as requested; the new kernel behaved just like the ill-fated 4.2.0-30, that is, the VM booted but did not reach the login screen. The last entries in /var/log/syslog were:

Feb 24 05:05:42 fictissa whoopsie[856]: [05:05:42] online
Feb 24 05:05:42 fictissa dbus[827]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Feb 24 05:05:42 fictissa systemd[1]: Started Network Manager Script Dispatcher Service.
Feb 24 05:05:42 fictissa nm-dispatcher: Dispatching action 'up' for eno16780032
Feb 24 05:05:42 fictissa systemd[1]: Reloading OpenBSD Secure Shell server.
Feb 24 05:05:42 fictissa systemd[1]: Reloaded OpenBSD Secure Shell server.
Feb 24 05:05:42 fictissa avahi-daemon[820]: Invalid response packet from host 192.168.2.2.
Feb 24 05:05:42 fictissa systemd[1]: Reloading OpenBSD Secure Shell server.
Feb 24 05:05:42 fictissa systemd[1]: Reloaded OpenBSD Secure Shell server.
Feb 24 05:05:43 fictissa ntpd[951]: Listen normally on 4 eno16780032 192.168.2.136 UDP 123
Feb 24 05:05:43 fictissa ntpd[951]: Listen normally on 5 eno16780032 fe80::250:56ff:fe30:1caa UDP 123
Feb 24 05:05:43 fictissa ntpd[951]: peers refreshed
Feb 24 05:05:43 fictissa ntpd[951]: new interface(s) found: waking up resolver
Feb 24 05:05:43 fictissa gpu-manager[853]: update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf
Feb 24 05:05:43 fictissa systemd[1]: Started Detect the available GPUs and deal with any system changes.
Feb 24 05:05:43 fictissa systemd[1]: Starting Light Display Manager...
Feb 24 05:05:43 fictissa nmbd[917]: * Starting NetBIOS name server nmbd
Feb 24 05:05:43 fictissa nmbd[917]: ...done.
Feb 24 05:05:43 fictissa systemd[1]: Started LSB: start Samba NetBIOS nameserver (nmbd).
Feb 24 05:05:43 fictissa systemd[1]: Starting LSB: start Samba SMB/CIFS daemon (smbd)...
Feb 24 05:05:43 fictissa systemd[1]: Started Light Display Manager.
Feb 24 05:05:43 fictissa smbd[1241]: * Starting SMB/CIFS daemon smbd
Feb 24 05:05:43 fictissa smbd[1241]: ...done.
Feb 24 05:05:43 fictissa systemd[1]: Started LSB: start Samba SMB/CIFS daemon (smbd).
Feb 24 05:05:44 fictissa avahi-daemon[820]: Invalid response packet from host 192.168.2.2.
Feb 24 05:05:44 fictissa NetworkManager[849]: <info> startup complete
Feb 24 05:05:45 fictissa ntpd_intres[956]: DNS 0.ubuntu.pool.ntp.org -> 80.96.120.252
Feb 24 05:05:45 fictissa ntpd_intres[956]: DNS 1.ubuntu.pool.ntp.org -> 92.86.106.228
Feb 24 05:05:45 fictissa ntpd_intres[956]: DNS 2.ubuntu.pool.ntp.org -> 82.78.227.6
Feb 24 05:05:45 fictissa ntpd_intres[956]: DNS 3.ubuntu.pool.ntp.org -> 89.40.65.2
Feb 24 05:05:45 fictissa ntpd_intres[956]: DNS ntp.ubuntu.com -> 91.189.89.199
Feb 24 05:05:48 fictissa avahi-daemon[820]: Invalid response packet from host 192.168.2.2.
Feb 24 05:05:49 fictissa NetworkManager[849]: <info> WiFi hardware radio set enabled
Feb 24 05:05:49 fictissa NetworkManager[849]: <info> WWAN hardware radio set enabled
Feb 24 05:05:56 fictissa avahi-daemon[820]: Invalid response packet from host 192.168.2.2.
Feb 24 05:06:44 fictissa avahi-daemon[820]: message repeated 2 times: [ Invalid response packet from host 192.168.2.2.]
Feb 24 05:07:07 fictissa systemd[1]: Created slice user-1000.slice.
Feb 24 05:07:07 fictissa systemd[1]: Starting User Manager for UID 1000...
Feb 24 05:07:07 fictissa systemd[1]: Started Session 1 of user alexp.
Feb 24 05:07:07 fictissa systemd[1278]: Reached target Sockets.
Feb 24 05:07:07 fictissa systemd[1278]: Reached target Paths.
Feb 24 05:07:07 fictissa systemd[1278]: Reached target Timers.
Feb 24 05:07:07 fictissa systemd[1278]: Reached target Basic System.
Feb 24 05:07:07 fictissa systemd[1278]: Reached target Default.
Feb 24 05:07:07 fictissa systemd[1278]: Startup finished in 47ms.
Feb 24 05:07:07 fictissa systemd[1]: Started User Manager for UID 1000.

I notice that compared to a normal boot there are a whole bunch of log messages missing between NetworkManager<info> startup complete and Created slice user-1000.slice -- for example, there is no message from systemd saying that it reached target LoginPrompts, there is no message saying that session c1 of user lightdm has started etc.

As with 4.2.0-30 I was able to SSH into the VM and remove kernel 4.2.8 using apt-get and all is well.