failure to boot with linux-image-4.15.0-24-generic

And this morning was July 3th 7:00 AM CEST

I have this issue too.

The dpkg.log shows as bellow:

     upgrade linux-libc-dev:amd64 4.15.0-23.25 4.15.0-24.26
     upgrade gnome-control-center-data:all 1:3.28.1-0ubuntu1.18.04.1 1:3.28.1-0ubunt1.18.04.2
     upgrade gnome-control-center:amd64 1:3.28.1-0ubuntu1.18.04.1 1:3.28.1-0ubunt1.18.04.2
     upgrade gnome-control-center-faces:all 1:3.28.1-0ubuntu1.18.04.1 1:3.28.1-0ubunt1.18.04.2
     upgrade linux-generic:amd64 4.15.0.23.25 4.15.0.24.26
     upgrade linux-image-generic:amd64 4.15.0.23.25 4.15.0.24.26
     upgrade linux-headers-generic:amd64 4.15.0.23.25 4.15.0.24.26

Status changed to 'Confirmed' because the bug affects multiple users.

Here too on my Thinkpad T520.

Happens also on a complete fresh install after applying latest updates from today

Curiously my home-build computer (using also intel-graphics) works without any problem ...

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1779827/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

https://wiki.ubuntu.com/Bugs/FindRightPackage
I was reqested to follow above, and I would really like to be help that why I trues to emphaize that the title of My incident is the last OK in the bootlist and where it hangs
More over it is one of the packages release on My laptop When opened it eight hours ago. These info must narrow Down to be very few packages. I am still at work.

This is the result of less /var/log/apt/history.log

Start-Date: 2018-07-03 06:50:16
Commandline: /usr/bin/unattended-upgrade
Upgrade: linux-libc-dev:amd64 (4.15.0-23.25, 4.15.0-24.26)
End-Date: 2018-07-03 06:50:17

Start-Date: 2018-07-03 06:50:19
Commandline: /usr/bin/unattended-upgrade
Install: linux-headers-4.15.0-24:amd64 (4.15.0-24.26, automatic), linux-headers-4.15.0-24-generic:amd64 (4.15.0-24.26, automatic), linux-modules-extra-4.15.0-24-generic:amd64 (4.15.0-24.26, automatic), linux-modules-4.15.0-24-generic:amd64 (4.15.0-24.26, automatic), linux-image-4.15.0-24-generic:amd64 (4.15.0-24.26, automatic)
Upgrade: linux-headers-generic:amd64 (4.15.0.23.25, 4.15.0.24.26), linux-image-generic:amd64 (4.15.0.23.25, 4.15.0.24.26), linux-generic:amd64 (4.15.0.23.25, 4.15.0.24.26)
End-Date: 2018-07-03 06:51:04

Start-Date: 2018-07-03 07:47:59
Commandline: aptdaemon role='role-commit-packages' sender=':1.221'
Upgrade: bolt:amd64 (0.2-0ubuntu1, 0.3-0ubuntu0.1), gstreamer1.0-alsa:amd64 (1.14.0-2ubuntu1, 1.14.1-1ubuntu1~ubuntu18.04.1), networkd-dispatcher:amd64 (1.7-0ubuntu3, 1.7-0ubuntu3.2), fonts-beng-extra:amd64 (1.0-6, 1.0-6ubuntu0.1), gstreamer1.0-plugins-base-apps:amd64 (1.14.0-2ubuntu1, 1.14.1-1ubuntu1~ubuntu18.04.1), update-notifier-common:amd64 (3.192.1, 3.192.1.1), gstreamer1.0-tools:amd64 (1.14.0-1, 1.14.1-1~ubuntu18.04.1), fonts-deva-extra:amd64 (3.0-4, 3.0-4ubuntu0.1), gstreamer1.0-plugins-good:amd64 (1.14.0-1ubuntu1, 1.14.1-1ubuntu1~ubuntu18.04.1), virtualbox-dkms:amd64 (5.2.10-dfsg-6, 5.2.10-dfsg-6ubuntu18.04.1), gstreamer1.0-plugins-bad:amd64 (1.14.0-1ubuntu1, 1.14.1-1ubuntu1~ubuntu18.04.1), gstreamer1.0-plugins-base:amd64 (1.14.0-2ubuntu1, 1.14.1-1ubuntu1~ubuntu18.04.1), virtualbox:amd64 (5.2.10-dfsg-6, 5.2.10-dfsg-6ubuntu18.04.1), libgstreamer-plugins-good1.0-0:amd64 (1.14.0-1ubuntu1, 1.14.1-1ubuntu1~ubuntu18.04.1), gstreamer1.0-pulseaudio:amd64 (1.14.0-1ubuntu1, 1.14.1-1ubuntu1~ubuntu18.04.1), libgstreamer-gl1.0-0:amd64 (1.14.0-2ubuntu1, 1.14.1-1ubuntu1~ubuntu18.04.1), gstreamer1.0-x:amd64 (1.14.0-2ubuntu1, 1.14.1-1ubuntu1~ubuntu18.04.1), gir1.2-gst-plugins-base-1.0:amd64 (1.14.0-2ubuntu1, 1.14.1-1ubuntu1~ubuntu18.04.1), fonts-orya-extra:amd64 (2.0-5, 2.0-5ubuntu0.1), virtualbox-qt:amd64 (5.2.10-dfsg-6, 5.2.10-dfsg-6ubuntu18.04.1), fonts-gujr-extra:amd64 (1.0-6, 1.0-6ubuntu0.1), gir1.2-gstreamer-1.0:amd64 (1.14.0-1, 1.14.1-1~ubuntu18.04.1), libgstreamer-plugins-bad1.0-0:amd64 (1.14.0-1ubuntu1, 1.14.1-1ubuntu1~ubuntu18.04.1), update-notifier:amd64 (3.192.1, 3.192.1.1), gstreamer1.0-gl:amd64 (1.14.0-2ubuntu1, 1.14.1-1ubuntu1~ubuntu18.04.1), gstreamer1.0-plugins-ugly:amd64 (1.14.0-1, 1.14.1-1~ubuntu18.04.1)
Remove: linux-modules-extra-4.15.0-22-generic:amd64 (4.15.0-22.24), linux-headers-4.15.0-22:amd64 (4.15.0-22.24), linux-modules-4.15.0-22-generic:amd64 (4.15.0-22.24), linux-headers-4.15.0-22-generic:amd64 (4.15.0-22.24), linux-image-4.15.0-22-generic:amd64 (4.15.0-22.24)
End-Date: 2018-07-03 07:49:01
~

I faced this issue after performing an upgrade on my system at around 5 PM (IST). The symptoms were all the same as stated in the comments above.

I don't know if this is a good workaround. But, what I did is

sudo apt remove linux-image-4.15.0-24-generic linux-headers-4.15.0-24-generic

And, this helped me get the system back.

When I reinstall all these again they are all in and I get the notice "set to manually installed." for every single on of them.
To me this means that the main package that is dependent on all these "set to manually installed." is not installed.
If I uninstall VLC I get vlc-noc automatically. If I uninstall VLC the vlc-noc will uninstall, too.
If I then install vlc-noc it will notify me with "set to manually installed."
I am probably barking up the wrong tree, but it is just the way it comes to me right now.

Lenovo X230 - exactly the same issue :-(

Same issue here, HP EliteBook 8440p, SSD disk.

Are you able to boot if you select the prior kernel version(4.15.0-23) from the GRUB menu?

Status changed to 'Confirmed' because the bug affects multiple users.

Also, are there any error messages, such as a kernel panic when the system wont boot? If so, can you capture a screen shot or digital image?

Bug does not affect Lenovo X250 or P51.

I can perform a bisect to identify the commit that caused this? Is it possible for folks affected by this bug to test some kernels that I build?

@ #12

No booting to previous kernels (4.15.0-23 or -20) doesn't solve the problem, also removing 4.15.0-24 doesn't help here.

I'm in doubt it's a kernel problem.

If you do a little research you'll find that this issue (Started gnome display manager. dispatcher service ...... tem changes.pp link was shut down) also happened with previous Ubuntu versions. It seems related to GDM3.

I tried to disable wayland in GDM3 (by setting WaylandEnable=false in custom.conf) also of no help.

I started a kernel bisect between 4.15.0-23 and 4.15.0-24. The kernel bisect will require testing of about 7-10 test kernels.

I built the first test kernel, up to the following commit:
5a955cd22fdb93ad76312789ddee4d1e751e46e7

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1779827

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

Thanks in advance

Can anyone else confirm that booting into prior kernel versions does not prevent the bug? If so, it probably is not a kernel bug.

For me, booting into previous kernel versions did not fix it. (DELL)

Me either. The booting to prior kernel does not fix the issue. Glad to help test but need some instructions. Only have non-bootable system at this point.

This is interesting: I tried to boot linux-image-4.15.0-23-generic again and it did work now and after trying to boot linux-image-4.15.0-24-generic again, this did work as well and everything seems to be fine again...

Agreed, I see the same thing. Glad 0-23 boots, but 0-24 still hangs at the Ubuntu logo, five white dots, not animated.

Interesting thing happening... I tried booting 0-23 success, then did shutdown -r now, and tried booting 0-24, as noted above just hangs. Briefly hit power button tried to boot 0-23 again and now it doesn't boot...

Tried turning off power and then booting 0-23, still hangs, got "Started GNOME display manager. Dispatcher service......before the ppp link was shut down....

Initially when I had the issue this morning I just turned the power off and let the laptop sit for about three hours before trying to boot (successfully) the 0-23 kernel.

Ctrl-Alt-F1 repeatingly if the prompt dies.
Updated all third party apps to newest versions.
Took a look at the boot.log
Made me run these:
sudo apt-get install --reinstall apparmor
systemctl start nmbd.service
It boots on 24 kernel.
Very fast suspiciously fast. Boot.log looks good.
Until now it works.

The same issue on Lenovo M30-70.
I run Linux Mint 19 (cinnamon) parallelly on the same notebook. After upgrade to kernel 4.15.0-24 it hangs too. But here it boots with a prior kernel without problems and I turned off the upgrade to 4.15.0-24.

Same problem here with T440s. I found a quick workaround. I put the computer in standby when the 5 dots of ubuntu logo are stuck. Then resume and the login screen appears.

As no trick mentioned here worked ...

I made a fresh install and updated everything except the kernel (which remains at 4.15.0-20). And my Lenovo T 520 works again.

So indeed kernel 4.15.0-24 seems the culprit. No glue why booting to previous installed kernels doesn't work either as soon 4.15.0-24 is installed.

Here a screen dump of the packages, as required, that causes my incident, I guess!
It is from a T460 and was opened July 4th.
Please find dump attached.

Hi,

on my X230 I have run a fresh installation from USB and then update to the 4.10.0-24. Now the computer boots but it takes much more time. It hangs for cca 2 minutes on the Ubuntu dots screen with all 5 dots white and does not react at all.

CTRL-ALT-F1 and check the boot sequence for what it using 2 minutes for.
Might be what I experienced:

sudo apt-get install --reinstall apparmor
systemctl start nmbd.service

There might be several more services like that.

Have a look at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897631

it seems the kernel update breaks gdm

Same issue on the workstation, few hours spent to fix it by reinstalling gnome, gdm3, apparmor, loading previous kernel, switching to lightdm. Nothing helps, complete reinstall. Very frustrating, because need to return to configuration/installing apps for next the few weeks.
With Ubuntu you should get used to always have the drive with recent version near you in case of something go wrong. Because from my experience it is faster to reinstall than fix such issues.

I'm not sure if my issue is related:

I upgraded to 4.15.0-24 yesterday (no other updates) and this morning I get a blank screen on boot that sits there indefinitely (i.e. minutes).

To fix this, I CTRL-ALT-F6 to get another tty, which immediately show up. This however seems to trigger some event, as the graphical login appears (displaces) my tty6 terminal without my intervention. So I can reliably get the graphical login back by "playing" with tty6.

One thing I noticed during boot was the `nvidia-persistenced` (using Nvidia's proprietary 390 drivers) service doing a dozen start/stops in quick succession. This doesn't show up every time though, and the blank screen that follows prevents me from seeing more.

`snapd.service` and `unbound.service` appear as the main offenders, but I'm not sure what's cause and effect here.

Booting with the prior 4.15.0-23 kernel works fine, as before.

I confirm stopping the system loading on the "Ubuntu" board on the kernel 4.15.0-24,
the problem is probably related to the nvidia graphics card, my hardware:

00:00.0 RAM memory: NVIDIA Corporation MCP61 Memory Controller (rev a1)
00:01.0 ISA bridge: NVIDIA Corporation MCP61 LPC Bridge (rev a2)
00:01.1 SMBus: NVIDIA Corporation MCP61 SMBus (rev a2)
00:01.2 RAM memory: NVIDIA Corporation MCP61 Memory Controller (rev a2)
00:02.0 USB controller: NVIDIA Corporation MCP61 USB 1.1 Controller (rev a3)
00:02.1 USB controller: NVIDIA Corporation MCP61 USB 2.0 Controller (rev a3)
00:04.0 PCI bridge: NVIDIA Corporation MCP61 PCI bridge (rev a1)
00:05.0 Audio device: NVIDIA Corporation MCP61 High Definition Audio (rev a2)
00:06.0 IDE interface: NVIDIA Corporation MCP61 IDE (rev a2)
00:07.0 Bridge: NVIDIA Corporation MCP61 Ethernet (rev a2)
00:08.0 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
00:08.1 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
00:09.0 PCI bridge: NVIDIA Corporation MCP61 PCI Express bridge (rev a2)
00:0b.0 PCI bridge: NVIDIA Corporation MCP61 PCI Express bridge (rev a2)
00:0c.0 PCI bridge: NVIDIA Corporation MCP61 PCI Express bridge (rev a2)
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
---->>>
02:00.0 VGA compatible controller: NVIDIA Corporation GT218 [GeForce 210] (rev a2)
---->>>
02:00.1 Audio device: NVIDIA Corporation High Definition Audio Controller (rev a1)

several different configurations work correctly on this kernel, but not this one

According to this page

https://debianforum.de/forum/viewtopic.php?f=33&t=169585&hilit=entropie

This newly introduced fix in 4.15.0-24 is the cause

'random: fix crng_ready() test'

when it's reverted (like in debian 4.9.88-1+deb9u1) boot is fine again

'linux (4.9.88-1+deb9u1) stretch-security; urgency=high
[...]
  * Revert "random: fix crng_ready() test" (Closes: #897599), reopening
    CVE-2018-1108'

another solution could be to install 'haveged' as proposed and verified here

https://debianforum.de/forum/viewtopic.php?f=33&t=169585&hilit=entropie

and here

https://forum.ubuntuusers.de/topic/nix-geht-mehr-nach-installation-und-update/

I can confirm that installing the 'haveged' package solves the issue. If lack of entropy was the issue, it makes sense that tinkering with the the non-graphical terminal caused the boot to proceed where plain waiting didn't.

Happy confirmed as well! sudo apt install haveged fixes the issue.

Installing haveged didn't work for me (currently using lightdm as a workaround).

Can folks affected by this bug test the following kernel:

http://kernel.ubuntu.com/~jsalisbury/lp1779827/

Note about installing test kernels:
• If the test kernel is prior to 4.15(Bionic) you need to install the linux-image and linux-image-extra .deb packages.
• If the test kernel is 4.15(Bionic) or newer, you need to install the linux-modules, linux-modules-extra and linux-image-unsigned .deb packages.

Thanks in advance!

Gratulations to Joseph Salisbury

the test kernel works like a charm

My Lenovo T520 boots rather quick without having haveged installed.

Thanks for this quick fix.

Same problem with Dell Precision M3800 with Ubunto 18.04
Updated yesterday July 3, when I booted today, July 4, boot process gets stuck
Last few lines of /var/log/boot.log:

[^[[0;32m OK ^[[0m] Reached target Network.
         Starting Permit User Sessions...
[^[[0;32m OK ^[[0m] Started Unattended Upgrades Shutdown.
         Starting OpenBSD Secure Shell server...
         Starting Network Manager Wait Online...
[^[[0;32m OK ^[[0m] Started Permit User Sessions.
         Starting GNOME Display Manager...
         Starting Hold until boot process finishes up...
         Starting Network Manager Script Dispatcher Service...
[^[[0;32m OK ^[[0m] Started Network Manager Script Dispatcher Service.
[^[[0;32m OK ^[[0m] Started GNOME Display Manager.
[^[[0;32m OK ^[[0m] Started OpenBSD Secure Shell server.

How do you install test kernel?
I tried dpki -i linux-modules-4.15.0-24-generic_4.15.0-24.26+crng4_amd64.deb linux-modules-extra-4.15.0-24-generic_4.15.0-24.26+crng4_amd64.deb linux-image-unsigned-4.15.0-24-generic_4.15.0-24.26+crng4_amd64.deb

but I get error:

Preparing to unpack linux-modules-4.15.0-24-generic_4.15.0-24.26+crng4_amd64.deb ...
Unpacking linux-modules-4.15.0-24-generic (4.15.0-24.26+crng4) over (4.15.0-24.26+crng4) ...
Preparing to unpack linux-modules-extra-4.15.0-24-generic_4.15.0-24.26+crng4_amd64.deb ...
Unpacking linux-modules-extra-4.15.0-24-generic (4.15.0-24.26+crng4) over (4.15.0-24.26+crng4) ...
dpkg: regarding linux-image-unsigned-4.15.0-24-generic_4.15.0-24.26+crng4_amd64.deb containing linux-image-unsigned-4.15.0-24-generic:
 linux-image-unsigned-4.15.0-24-generic conflicts with linux-image-4.15.0-24-generic
  linux-image-4.15.0-24-generic (version 4.15.0-24.26) is present and installed.

dpkg: error processing archive linux-image-unsigned-4.15.0-24-generic_4.15.0-24.26+crng4_amd64.deb (--install):
 conflicting packages - not installing linux-image-unsigned-4.15.0-24-generic
Setting up linux-modules-4.15.0-24-generic (4.15.0-24.26+crng4) ...
Setting up linux-modules-extra-4.15.0-24-generic (4.15.0-24.26+crng4) ...
Processing triggers for linux-image-4.15.0-24-generic (4.15.0-24.26) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.15.0-24-generic
/etc/kernel/postinst.d/zz-update-grub:
Generating grub configuration file ...
Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported.
Found linux image: /boot/vmlinuz-4.15.0-24-generic
Found initrd image: /boot/initrd.img-4.15.0-24-generic
Found linux image: /boot/vmlinuz-4.15.0-23-generic
Found initrd image: /boot/initrd.img-4.15.0-23-generic
Found linux image: /boot/vmlinuz-4.15.0-22-generic
Found initrd image: /boot/initrd.img-4.15.0-22-generic
Found memtest86+ image: /boot/memtest86+.elf
Found memtest86+ image: /boot/memtest86+.bin
done
Errors were encountered while processing:
 linux-image-unsigned-4.15.0-24-generic_4.15.0-24.26+crng4_amd64.deb

Or how do I revert to previous working kernel (I don't have grub installed... long story).

My Ubuntu boots 8-11 minutes with 4.15.0-24. With 4.15.0-23 it boots quickly. Please, fix this damn regression!

Thanks for the quick response to this issue

How long will it take for that fix to reach the end users?

"haveged"

Is this a joke? I went to college dammit! ;D

The install of package haveged workaround also did not work for me - I was getting boot hangs in my KVM guest installation, waiting for 3 services to start.

After installing haveged, I only hang on something called "hold until start processes finish up" for about 15 seconds, then a permanent hang on "Stopping User Manager for UID 119".

I'm also interested to know how long it will take for the kernel fix to land in the repo so I can retry. Thanks!

Reverting the fix for CVE-2018-1108 to get this to work is not necessary and not a good idea. The root cause has been identified upstream in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897572 and fixes committed.

Turns out it was fontconfig generating a uuid that tripped over the CVE fix. One commited fix is to copy the necessary fonts to initramfs so genuuid is not needed. Another is a fix to randutils. Those are the changes that need to be pushed to Ubuntu users.

How did this regression ever get into an Ubuntu software update for the masses?

This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

Any workaround besides the haveged? haveged didn't work for me.

This appears to be a duplicate of bug #1779476.

I agree, if plymouth turns out to be the real problem then no kernel change is necessary. Changing the kernel would be only a workaround for the plymouth hang.

After turning on developer options for pre-release upgrades and installing a lot of stuff, I still have the same problem with the slow boot on the 2 machines I updated. uname-a shows same as before.Is that normal? I turned off developer stuff afterwards. Since 4.15.0-23 works fine, should I just delete the -24 til this gets straightened out?

I have tested 4.15.0-26-generic from the -proposed repository and it runs fine under kvm/qemu. The -24 version did not boot for me under kvm/kemu. Not sure if I am supposed to change the tag to verification-done-bionic or if that is supposed to be done by the person who originally filed the bug report. The one that I filed got marked as a duplicate. Thank you for your support in resolving this issue.

Tested linux-image-4.15.0-26-generic-4.15.0-26.28 from bionic-proposed, and with it system boots quickly again (without haveged-workaround in place). Dell E7440-laptop.

Don't know why the new kernel didn't install from the software updater, but after manually installing it, it works fine. Now to do the same on other machine. Funny it all installed fine with the software updater on my main machine.

You don't need to install all of the updates from the -proposed repository, only the kernel. When you check the proposed box in the software updater, you are effectively adding the following line to /etc/apt/sources.list (mirror is whatever mirror you have chosen):

deb http://mirrors.namecheap.com/ubuntu/ bionic-proposed universe restricted multiverse main

You can then either use the software updater or apt to install the kernel. I used the following apt command on the command line:

 apt-get install linux-generic

This command automatically pulled in the other dependencies such as the kernel headers and modules from the -proposed repository.

I updated the kernel through the bionic-proposed channel, but it still got stuck at startup:
"Started Dispatcher daemon for systemd-networkd.ce......before the ppp link was shut down...."
had to revert back to lighdm in order to reboot.

I had already installed everything from the proposed mirror using software updater, but it didn't install the new .26 kernel on the 2 affected machines. So I installed the image, headers, module-extra packages using apt-get install <package name>/bioic-proposed. that worked and everything worked fine afterwards afaik. I then removed the developer check from the software updater.

@alwaystired - Did you verify that you have installed the new .26 version?

Yes, the current output of uname -r is 4.15.0-26-generic, and this is the /var/log/dpkg.log output, is it the right one?

2018-07-06 17:44:45 startup archives unpack
2018-07-06 17:44:45 install linux-modules-4.15.0-26-generic:amd64 <none> 4.15.0-26.28
2018-07-06 17:44:45 status half-installed linux-modules-4.15.0-26-generic:amd64 4.15.0-26.28
2018-07-06 17:44:48 status unpacked linux-modules-4.15.0-26-generic:amd64 4.15.0-26.28
2018-07-06 17:44:48 status unpacked linux-modules-4.15.0-26-generic:amd64 4.15.0-26.28
2018-07-06 17:44:49 install linux-image-4.15.0-26-generic:amd64 <none> 4.15.0-26.28
2018-07-06 17:44:49 status half-installed linux-image-4.15.0-26-generic:amd64 4.15.0-26.28
2018-07-06 17:44:49 status unpacked linux-image-4.15.0-26-generic:amd64 4.15.0-26.28
2018-07-06 17:44:49 status unpacked linux-image-4.15.0-26-generic:amd64 4.15.0-26.28
2018-07-06 17:44:49 install linux-modules-extra-4.15.0-26-generic:amd64 <none> 4.15.0-26.28
2018-07-06 17:44:49 status half-installed linux-modules-extra-4.15.0-26-generic:amd64 4.15.0-26.28
2018-07-06 17:44:59 status unpacked linux-modules-extra-4.15.0-26-generic:amd64 4.15.0-26.28
2018-07-06 17:44:59 status unpacked linux-modules-extra-4.15.0-26-generic:amd64 4.15.0-26.28
2018-07-06 17:45:00 upgrade linux-generic:amd64 4.15.0.24.26 4.15.0.26.28
2018-07-06 17:45:00 status half-configured linux-generic:amd64 4.15.0.24.26
2018-07-06 17:45:00 status unpacked linux-generic:amd64 4.15.0.24.26
2018-07-06 17:45:00 status half-installed linux-generic:amd64 4.15.0.24.26
2018-07-06 17:45:00 status half-installed linux-generic:amd64 4.15.0.24.26
2018-07-06 17:45:00 status unpacked linux-generic:amd64 4.15.0.26.28
2018-07-06 17:45:00 status unpacked linux-generic:amd64 4.15.0.26.28
2018-07-06 17:45:00 upgrade linux-image-generic:amd64 4.15.0.24.26 4.15.0.26.28
2018-07-06 17:45:00 status half-configured linux-image-generic:amd64 4.15.0.24.26
2018-07-06 17:45:00 status unpacked linux-image-generic:amd64 4.15.0.24.26
2018-07-06 17:45:00 status half-installed linux-image-generic:amd64 4.15.0.24.26
2018-07-06 17:45:00 status half-installed linux-image-generic:amd64 4.15.0.24.26
2018-07-06 17:45:00 status unpacked linux-image-generic:amd64 4.15.0.26.28
2018-07-06 17:45:00 status unpacked linux-image-generic:amd64 4.15.0.26.28
2018-07-06 17:45:00 install linux-headers-4.15.0-26:all <none> 4.15.0-26.28
2018-07-06 17:45:00 status half-installed linux-headers-4.15.0-26:all 4.15.0-26.28
2018-07-06 17:45:25 status unpacked linux-headers-4.15.0-26:all 4.15.0-26.28
2018-07-06 17:45:25 status unpacked linux-headers-4.15.0-26:all 4.15.0-26.28
2018-07-06 17:45:25 install linux-headers-4.15.0-26-generic:amd64 <none> 4.15.0-26.28
2018-07-06 17:45:25 status half-installed linux-headers-4.15.0-26-generic:amd64 4.15.0-26.28
2018-07-06 17:45:38 status unpacked linux-headers-4.15.0-26-generic:amd64 4.15.0-26.28
2018-07-06 17:45:38 status unpacked linux-headers-4.15.0-26-generic:amd64 4.15.0-26.28
2018-07-06 17:45:38 upgrade linux-headers-generic:amd64 4.15.0.24.26 4.15.0.26.28
2018-07-06 17:45:38 status half-configured linux-headers-generic:amd64 4.15.0.24.26
2018-07-06 17:45:38 status unpacked linux-headers-generic:amd64 4.15.0....

Yep, that's the same version that is installed in my VM. So it looks like the new -26 kernel does not fix the problem for everybody. It worked for me, but doesn't seem to work for you.

Booting into the *-26 kernel gave a very quick handover to Gnome, but with some kind of
badly painted cursor and progress images apparently bleeding through from the plymouth screens.
However the deal breaker is that networking isn't enabled at all.

Report then is that *-26 kernel is not a workaround or a fix for this machine: Clevo bareboook W540 onboard graphics.
haveged is a workaround for getting into Gnome with *-24 kernel but networking is fairly retarded in its delivery to the desktop after Gnome starts - averaging 30s.
Booting into *-23 is the optimum boot speed and delivers networking in good time.

Installing *-26-th kernel from a proposed fixes the issue with very slow booting on my system.

I only had the slow boot problem on 2 out of 3 systems with the .24 kernel. Both systems that had problems had single ssd drives in them. One was an ECS GF8200A mb and the other was a jetway GF8200 based mb. The system that didn't have a problem was also an ECS GF8200A mb, but does not have a ssd drive in it. All work fine so far with the .26 kernel.

Sorry, but the bug also happens with 4.15.0-23

I upgraded a PC with a SSD replacing a HDD. So this laptop now only has a SSD which obviously has no spinning part to produce entropy to seed the random generator.

Here is what happens:
-1) not touching anything, there is a "30 seconds gap" (visible in dmesg) where nothing at all happens, then the boot sequence continues
-2) touching the trackpad randomly during the boot sequence makes the random generator initialize quicker (message in dmesg) but there is still the 30 sec gap in spite of the message in the log
-3) plugging an external spinning rust to USB fixes the issue! Now the system does not hang for 30 sec waiting anymore...

DMESG with 1)

[ 0.000000] microcode: microcode updated early to revision 0x44, date = 2010-10-04
[ 0.000000] Linux version 4.15.0-23-generic (buildd@lgw01-amd64-055) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 (Ubuntu 4.15.0-23.25-generic 4.15.18)
[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=e6b574d4-94de-420a-85e0-c6681bef57a1 ro quiet splash video=SVIDEO-1:d vt.handoff=1
[ 0.000000] KERNEL supported cpus:
[ 0.000000] Intel GenuineIntel
[ 0.000000] AMD AuthenticAMD
[ 0.000000] Centaur CentaurHauls
[ 0.000000] x86/fpu: x87 FPU will use FXSAVE

(...)

[ 2.742732] fbcon: inteldrmfb (fb0) is primary device
[ 2.743323] Console: switching to colour frame buffer device 160x50
[ 2.743365] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[ 2.816170] firewire_core 0000:02:09.0: created device fw0: GUID 474fc0001ac27070, S400
[ 3.421641] input: AlpsPS/2 ALPS GlidePoint as /devices/platform/i8042/serio2/input/input9
[ 34.943967] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[ 35.129322] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 35.142828] systemd[1]: systemd 237 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid)
[ 35.160097] systemd[1]: Detected architecture x86-64.

(...)

[ 46.267417] sky2 0000:09:00.0 enp9s0: Link is up at 100 Mbps, full duplex, flow control both
[ 46.267444] IPv6: ADDRCONF(NETDEV_CHANGE): enp9s0: link becomes ready

DMESG with 2)

[ 0.000000] microcode: microcode updated early to revision 0x44, date = 2010-10-04
[ 0.000000] Linux version 4.15.0-23-generic (buildd@lgw01-amd64-055) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 (Ubuntu 4.15.0-23.25-generic 4.15.18)
[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=e6b574d4-94de-420a-85e0-c6681bef57a1 ro quiet splash video=SVIDEO-1:d vt.handoff=1
[ 0.000000] KERNEL supported cpus:
[ 0.000000] Intel GenuineIntel
[ 0.000000] AMD AuthenticAMD
[ 0.000000] Centaur CentaurHauls
[ 0.000000] x86/fpu: x87 FPU will use FXSAVE

(...)

[ 2.749189] fbcon: inteldrmfb (fb0) is primary device
[ 2.749779] Console: switching to colour frame buffer device 160x50
[ 2.749822] i915 0000:00:02.0: fb...

I am also attaching the full 3 dmesg if some other differences I could not spot seem significant for you.

Mine is a Toshiba Satellite Z30-A-1E9 laptop with a single SSD. I tried booting with the 4.15.0-26-generic kernel now with an external HDD attached, and still couldn't boot - I waited for more than 3.5min and it was still stuck on the "before the ppp link was shut down" message, so I switched to lightdm then it booted within ~15s without the external drive.

Participating in bug https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1779476 for the last
couple of days.

Clevo barebook W540 pentium 3805U 1.90G onboard graphics BroadwellGT1 single ssd, intel Wless 3160, only hardware hanging off it is a usb wireless mouse.
Had indefinite hang begin with update to Ubuntu-offered *-24 kernel.
A fair amount of keyboarding and mouse wiggling (average 90s) is needed to wake the process up again.
Holding the SHIFT key speeds up the boot to an acceptable delay.
Once into Gnome, networking is also fairly retarded (average 45s) and sometimes needs UI operation for the Net Manager to do its usual auto connect to its secure network.
Installing haveged stopped the hang. Network also appears to be more responsive, but this can
be masked by the flaky operation of our el-cheapo wireless router. Using a usb dongle which emulates etho appears to deliver much more reliable network start.

Booting into *-23 stopped all symptoms - haveged not needed.
Booting into the dev channel *-26 returned the hang and added a few display artefacts to the plymouth/Gnome handover process. Zero networking delivered in Gnome, not even a UI for Net Manager.

Hanging a portable WD 1TB spinner off the laptop USB3 port returned a good boot time into Gnome with the *-24 kernel without haveged installed. Networking was however delayed variously between 60s and at one boot appeared to need UI input to wake the hardware up to the secure connection already in the Net Manager's list, even though Net Manager could immediately see other networks around the place.

Reverting now to *-23 kernel for the week's work.
Hope these naive reports were in any way useful.

The kernel provided in the proposed channel does not solve the issue for me. I also encounter the described boot issue in -23, -24 and -26 kernels. A workaround for me is using lightdm as display manager instead of gmd3.

What was proposed in this thread and didn't work for me:
* Installing havegd (verified for -23 and -24 kernels)
* Installing -26 form bionic-proposed
* Booting directly to -23 (without havegd)
* Adding a spinning disk during boot in -24, or -26 (not sure whether I also tested this one in -23)

I'm testing this on an HP ProBook 5320m (CPU: Intel Core i3 M350). This system does not have a dedicated GPU so I doubt it is caused by Nvidia cards directly as suggested before.

#50 : Another workaround besides the 'haveged' is 'rng-tools5'. I've booted through kernel version(4.15.0-23), installed the package 'rng-tools5' (because my processor supports it - intel 3rd generation or newest) and now i'm able to boot kernel 4.15.0-24 again.

Kurt,

If you have an i3-350M then please see bug 1727356 instead.

In fact, everyone using an Intel CPU from 2010 or earlier please see bug 1727356 instead.

This still looks like the getrandom() hang described in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897572. This was caused by the fix in the kernel for CVE-2018-1108. Two complementary fixes have been discussed in the Debian bug neither of which modify the kernel. The first is a change to the Plymouth package to avoid fontconfig generating uuids, which reportedly has the added bonus of speeding up boot compared to pre-CVE-fix times. The second is a change to randutils in the utils-linux package so they don't block on getrandom().

There's a link to the updated plymouth package which I tried:

https://packages.debian.org/sid/amd64/plymouth/download

Unfortunately all I got was a black screen, with or without haveged installed. This is not the getrandom hang. The screen remains black and no log is displayed. I suspect this is because some modification to the package or config files is needed for Ubuntu. Or maybe some other package needed reconfiguring due to the change plymouth. I'm no Ubuntu expert.

As I stated in comment #48, if these fixes indeed work, when properly incorporated into Ubuntu, they are preferable to backing out the CVE fix.

Also confirm this bug at my DELL E4310. System boots very slowly. Reverting to *23 kernel fixed this problem.

My bionic system has been fine until today, when I thought it wouldn't complete the boot at all. It did in fact start after about 10 minutes. I tried again with the same result. I am on the *24 kernel. I tried *23 (from the boot list) but it made no difference. Moving the mouse seemed to help.

Installing haveged fixed it - so thanks for the information.

On the log I was getting various service problems, snapd timeouts, very long 'resolve transaction' and 'search-file' delays.

But why the change all of a sudden? Since Monday 9th July am I have installed the following. I hope this may help someone pin it down further.

Start-Date: 2018-07-09 12:46:30
Commandline: /usr/sbin/synaptic
Upgrade: libegl1:amd64 (1.0.0-2ubuntu2, 1.0.0-2ubuntu2.1), libegl1-mesa-dev:amd64 (18.0.0~rc5-1ubuntu1, 18.0.5-0ubuntu0~18.04.1), libegl-mesa0:amd64 (18.0.0~rc5-1ubuntu1, 18.0.5-0ubuntu0~18.04.1), update-notifier-common:amd64 (3.192.1.1, 3.192.1.3), libgl1:amd64 (1.0.0-2ubuntu2, 1.0.0-2ubuntu2.1), libgl1:i386 (1.0.0-2ubuntu2, 1.0.0-2ubuntu2.1), libglapi-mesa:amd64 (18.0.0~rc5-1ubuntu1, 18.0.5-0ubuntu0~18.04.1), libglapi-mesa:i386 (18.0.0~rc5-1ubuntu1, 18.0.5-0ubuntu0~18.04.1), libopengl0:amd64 (1.0.0-2ubuntu2, 1.0.0-2ubuntu2.1), libxatracker2:amd64 (18.0.0~rc5-1ubuntu1, 18.0.5-0ubuntu0~18.04.1), libegl1-mesa:amd64 (18.0.0~rc5-1ubuntu1, 18.0.5-0ubuntu0~18.04.1), libgles2:amd64 (1.0.0-2ubuntu2, 1.0.0-2ubuntu2.1), libgbm1:amd64 (18.0.0~rc5-1ubuntu1, 18.0.5-0ubuntu0~18.04.1), libglvnd-dev:amd64 (1.0.0-2ubuntu2, 1.0.0-2ubuntu2.1), libwayland-egl1-mesa:amd64 (18.0.0~rc5-1ubuntu1, 18.0.5-0ubuntu0~18.04.1), libglx0:amd64 (1.0.0-2ubuntu2, 1.0.0-2ubuntu2.1), libglx0:i386 (1.0.0-2ubuntu2, 1.0.0-2ubuntu2.1), libglvnd-core-dev:amd64 (1.0.0-2ubuntu2, 1.0.0-2ubuntu2.1), libgl1-mesa-dri:amd64 (18.0.0~rc5-1ubuntu1, 18.0.5-0ubuntu0~18.04.1), libgl1-mesa-dri:i386 (18.0.0~rc5-1ubuntu1, 18.0.5-0ubuntu0~18.04.1), libosmesa6:amd64 (18.0.0~rc5-1ubuntu1, 18.0.5-0ubuntu0~18.04.1), libosmesa6:i386 (18.0.0~rc5-1ubuntu1, 18.0.5-0ubuntu0~18.04.1), libgl1-mesa-glx:amd64 (18.0.0~rc5-1ubuntu1, 18.0.5-0ubuntu0~18.04.1), libgl1-mesa-glx:i386 (18.0.0~rc5-1ubuntu1, 18.0.5-0ubuntu0~18.04.1), mesa-vdpau-drivers:amd64 (18.0.0~rc5-1ubuntu1, 18.0.5-0ubuntu0~18.04.1), update-notifier:amd64 (3.192.1.1, 3.192.1.3), mesa-va-drivers:amd64 (18.0.0~rc5-1ubuntu1, 18.0.5-0ubuntu0~18.04.1), libglx-mesa0:amd64 (18.0.0~rc5-1ubuntu1, 18.0.5-0ubuntu0~18.04.1), libglx-mesa0:i386 (18.0.0~rc5-1ubuntu1, 18.0.5-0ubuntu0~18.04.1), libglvnd0:amd64 (1.0.0-2ubuntu2, 1.0.0-2ubuntu2.1), libglvnd0:i386 (1.0.0-2ubuntu2, 1.0.0-2ubuntu2.1)
End-Date: 2018-07-09 12:46:44

Start-Date: 2018-07-09 20:40:50
Commandline: /usr/sbin/synaptic
Upgrade: libjpeg-turbo8-dev:amd64 (1.5.2-0ubuntu5, 1.5.2-0ubuntu5.18.04.1), libjpeg-turbo-progs:amd64 (1.5.2-0ubuntu5, 1.5.2-0ubuntu5.18.04.1), grub-common:amd64 (2.02-2ubuntu8, 2.02-2ubuntu8.1), grub2-common:amd64 (2.02-2ubuntu8, 2.02-2ubuntu8.1), kactivitymanagerd:amd64 (5.12.5-0ubuntu0.1, 5.12.6-0ubuntu0.1), grub-efi-amd64-bin:amd64 (2.02-2ubuntu8, 2.02-2ubuntu8.1), grub-efi-amd64:amd64 (2.02-2ubuntu8, 2.02-2ubuntu8.1), shim-signed:amd64 (1.34.9.1+13-0ubuntu2, 1.34.9.2+13-0ubuntu2), libjpeg-...

what helped me, when I was stuck on black boot screen, was to reinstall Gnome:

sudo apt purge gdm3
sudo apt install gdm3 ubuntu-desktop
systemctl restart gdm

after that everything works. - Running Ubuntu 18.04

@mocnak, re. comment #78. Thanks. I reinstalled gdm3 but didn't think about ubuntu-desktop. Anyway I've reverted to the existing Ubuntu version of plymouth and got my system working again (with haveged).

Did you try the fixed Plymouth?

before I wanted reply to your question, I rebooted my laptop, and now I'm
stuck on boot screen - so not the same as error described here. Anyway, it
helped me just to log-in once and now I'm on OS unable to boot properly
again. It took around 3 minutes to show me login screen.

On Tue, Jul 10, 2018, 17:57 Mark <email address hidden> wrote:

> @mocnak, re. comment #78. Thanks. I reinstalled gdm3 but didn't think
> about ubuntu-desktop. Anyway I've reverted to the existing Ubuntu
> version of plymouth and got my system working again (with haveged).
>
> Did you try the fixed Plymouth?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1779827
>
> Title:
> failure to boot with linux-image-4.15.0-24-generic
>
> Status in Ubuntu:
> Confirmed
> Status in linux package in Ubuntu:
> In Progress
> Status in The Bionic Beaver:
> Confirmed
> Status in linux source package in Bionic:
> Fix Committed
>
> Bug description:
> This was the last OK then my 18.04 hangs after an update this morning.
> 07:00 AM CEST
>
> Last Ok in boot was Started gnome display manager. dispatcher service
> ...... tem changes.pp link was shut down
>
> Tried install lightdm from command line and the response was lastest
> already installed.
>
> Probably it is what is coming after the lastest OK which is to be the
> error. And here I have lots of guesses......
>
> Any Ideas ? I need to do some work and I may not be waiting long.
>
> Search and browsed and now close to give up. Yeah it is a Lenovo.
>
> Guys: turn of auto update it is a machine killer.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+bug/1779827/+subscriptions
>

Tried mocnak's solution, no effect

Regular install 5 weeks old, update snappy breaks, update no more gui. Mocnak solution, zero effect, in syslog gdm complains about wrong parameters.

I am running a AMD a12 laptop, 16gbyte ram, 256gbyte ssd, 207gbyte free disk space. All filesystems 90% or more space available.

(I might not be there to test solution, migrating to the evil side because i need to get work done, VM's run on the evil-OS too.)

Sorry... my "bug" was PEBCAK!

It has nothing to do with entropy. I copied the system from an old HDD to a SDD, and in the process didn't change the resume UID that sits in: /etc/initramfs-tools/conf.d/resume

It was still pointing to a partition UID on the old disk. Hence when the old disk was attached via USB all was normal, but when the disk was not there, the system waited for 30 seconds to see that UID and try to resume.

I then replace the old UID with "none" (since I won't be hibernating that machine) did the initram command, and now all is fine.

So please, disregard posts #66 to #69, they are unrelated to the topic!

My apologies again.

I'm happy to report that I was able to boot normally with gdm now, and it didn't get stuck. Yesterday I removed and reinstalled gdm3 and ubuntu-desktop, as suggested here, rebooted, but it was still the same (i.e. stuck in reboot), so I switched back to lightdm. Today when I turned it on it started normally using gdm (although I don't remember switching it to gdm again!).

This is the dpkg log, in case it helps someone - the problem started after July 3rd, and was solved after July 10th:
2018-07-03 09:56:21 install linux-cloud-tools-4.15.0-24:amd64 <none> 4.15.0-24.26
2018-07-03 09:56:21 install linux-cloud-tools-4.15.0-24-generic:amd64 <none> 4.15.0-24.26
2018-07-03 09:56:21 install linux-modules-4.15.0-24-generic:amd64 <none> 4.15.0-24.26
2018-07-03 09:56:25 install linux-image-4.15.0-24-generic:amd64 <none> 4.15.0-24.26
2018-07-03 09:56:26 install linux-modules-extra-4.15.0-24-generic:amd64 <none> 4.15.0-24.26
2018-07-03 09:56:38 install linux-headers-4.15.0-24:all <none> 4.15.0-24.26
2018-07-03 09:57:03 install linux-headers-4.15.0-24-generic:amd64 <none> 4.15.0-24.26
2018-07-03 09:57:19 install linux-tools-4.15.0-24:amd64 <none> 4.15.0-24.26
2018-07-03 09:57:20 install linux-tools-4.15.0-24-generic:amd64 <none> 4.15.0-24.26
2018-07-04 11:58:33 install lightdm:amd64 1.26.0-0ubuntu1 1.26.0-0ubuntu1
2018-07-04 11:58:34 install libgeoclue0:amd64 <none> 0.12.99-4ubuntu2
2018-07-04 11:58:34 install libnm-util2:amd64 <none> 1.10.6-2ubuntu1
2018-07-04 11:58:35 install libnm-glib4:amd64 <none> 1.10.6-2ubuntu1
2018-07-04 11:58:35 install geoclue:amd64 <none> 0.12.99-4ubuntu2
2018-07-04 11:58:35 install geoclue-ubuntu-geoip:amd64 <none> 1.0.2+18.04.20180223-0ubuntu1
2018-07-04 11:58:35 install libpanel-applet3:amd64 <none> 1:3.26.0-1ubuntu5
2018-07-04 11:58:36 install indicator-applet:amd64 <none> 12.10.2+17.10.20170425-0ubuntu1
2018-07-04 11:58:36 install indicator-application:amd64 12.10.1+17.04.20161201-0ubuntu1 12.10.1+17.04.20161201-0ubuntu1
2018-07-04 11:58:36 install liburl-dispatcher1:amd64 <none> 0.1+17.04.20170328-0ubuntu4
2018-07-04 11:58:37 install indicator-datetime:amd64 15.10+17.10.20170829.2-0ubuntu4 15.10+17.10.20170829.2-0ubuntu4
2018-07-04 11:58:37 install liblightdm-gobject-1-0:amd64 <none> 1.26.0-0ubuntu1
2018-07-04 11:58:37 install indicator-keyboard:amd64 0.0.0+18.04.20180216-0ubuntu1 0.0.0+18.04.20180216-0ubuntu1
2018-07-04 11:58:37 install indicator-messages:amd64 13.10.1+17.04.20170120-0ubuntu2 13.10.1+17.04.20170120-0ubuntu2
2018-07-04 11:58:38 install indicator-power:amd64 12.10.6+17.10.20170829.1-0ubuntu4 12.10.6+17.10.20170829.1-0ubuntu4
2018-07-04 11:58:38 install indicator-session:amd64 17.3.20+17.10.20171006-0ubuntu1 17.3.20+17.10.20171006-0ubuntu1
2018-07-04 11:58:39 install ubuntu-touch-sounds:all <none> 15.08
2018-07-04 11:58:39 install unity-greeter:amd64 18.04.0+18.04.20180314.1-0ubuntu2 18.04.0+18.04.20180314.1-0ubuntu2
2018-07-04 11:58:40 install indicator-sound:amd64 12.10.2+18.04.20180420.3-0ubuntu1 12.10.2+18.04.20180420.3-0ubuntu1
2018-07-04 16:12:19 install libhavege1:amd64 <none> 1.9.1-6
2018-07-04 16:12:20 install haveged:amd64 <none> 1.9.1-6
2018-07-06 17:44:45 install linux-modules-4.15.0-26-generic:...

I am also affected by this, and it is most likely the issue with entropy for randomness, because if I mash some random keys, I get to boot.

@dimztimz - could you elaborate on what u did specifically? Other solutions above (not the patched kernel) don't work for me.

I have come to the conclusion that the problem with the #24 Linux Kernel is related
to the use of SSD hard drives.

I just took my SSD out of my computer and replaced it with an old manual / mechanical
hard drive and installed Linux Mint 19 on it including the #24 Kernel and it worked/booted
perfectly after the installation of #24, whereas previously when I was using my SSD in
the computer the #24 kernel broke the system and would not boot.

Hope someone addresses this issue fairly quickly because me thinks there are a lot
of people like me who have switched to SSD.

Thanks.

>I have come to the conclusion that the problem with the #24 Linux Kernel is related
to the use of SSD hard drives.
Really? Well, how smart! Just try to read a previous posts and you'll understand that you're completely wrong.

@m-tim-smith, comment #85, if none of the fixes/workarounds here are working for you, perhaps you have a different problem with very similar symptoms. For example bug #1779476.

@joverstreet1, comment #86, I have an SSD and my system's been running fine with kernel 24 since I installed haveged.

Did you install haveged "BEFORE" you attempted update to kernel #24 ?

Is you SSD a Western Digital, may I ask ?

Perhaps haveged is a solution but does not sound like a particularly
good one. How is one supposed to know that they have to do this ?

Sounds like to me that there is something in kernel #24 that needs to
be fixed so that will will work properly with SSD without having to
add this that and the other to get it to work.

Thanks for the info.

tim-smith:

I installed haveged and then install kernel #24 and unlike before
now seems to boot and run just fine.

Are the developers of the kernel aware of this problem ?

Sounds like adding haveged is a patchwork fix at best and that some
change to the kernel itself needs to be made - what that might
be, I have no idea because me certainly have EXTREMELY little
programming experience. Sort of thinking about going back to
Mint 18.3 for now.

Thanks.

@joverstreet1, kernel 24 was installed first, by Ubuntu Software Updater. I then installed haveged to work around a kernel change to getrandom(). My SSD is not Western Digital but the SSD has nothing to do with the problem, at least not the one that is the focus of this bug report.

The kernel change was done to fix CVE-2018-1108 as explained earlier in this bug. Some packages used during boot tripped over this change. According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897572 the offenders have been identified and fixed. However it seems Ubuntu has backed out the CVE fix instead.

The problem packages are plymouth & randutils (in utils_linux). The kernel change causes them to hang waiting for entropy. plymouth is involved in boot. It manages the handover from boot to the graphical login screen.

So yes the kernel, and other, developers are aware. I think Ubuntu release a new kernel with the CVE fix removed but I haven't used my Linux box for the last couple of days so don't know for sure.

Please could anyone share some detailed instructions on how to apply these quick fixes...

I am having these issues with my dell Inspiron 15 7000 series all of a sudden with ubuntu 18.04

I try to run ctrl+alt+f1 but it goes to bios.

Please some advice... I am having this issue just know while finishing my phd.

Easiest thing to do is just delete the .24 kernel. During boot, start tapping the esc key repeatedly. You should get the grub menu. Select the advanced option, and then load the last good kernel, which should be the .23 one if you've kept the system up to date. Once it boots and everything is working right, you can use your package manager to remove the offending .24 kernel or do it manually with sudo apt remove <kernel name>. Once you've removed it, grub will automatically be updated so it will boot to the .23 kernel. FWIW, the .24 kernel was removed from the repo as to not to infect people that do updates now.

Thank you Wes Newell for your reply.

I only installed ubuntu on this computer (big big big mistake) I do not have the grub menu at start.

After typing many commands which I did not understand ubuntu started. I have lost the sound however and now I am afraid to turn it off. If I run:

dpkg -l | grep linux-imagerc

linux-image-4.15.0-20-generic 4.15.0-20.21 amd64 Signed kernel image generic
rc linux-image-4.15.0-22-generic 4.15.0-22.24 amd64 Signed kernel image generic
ii linux-image-4.15.0-23-generic 4.15.0-23.25 amd64 Signed kernel image generic
ii linux-image-4.15.0-24-generic 4.15.0-24.26 amd64 Signed kernel image generic
ii linux-image-generic 4.15.0.23.25 amd64 Generic Linux kernel image

And currently:

uname -r:
4.15.0-24-generic

Which commands should I run to purge that kernel and run the previous one? Should I do it from tty? or from the current session? Should I wait for an update or will that make it worse...

@delosari https://forum.snapcraft.io/t/snapd-service-delays-startup-in-ubuntu-18-04-with-4-15-0-24/6205/10 says pressing shift key continuously during boot could be a workaround. It worked for me.

Has to be the right shift key on my 18.04lts system, but I've always just used tapping the Esc key immediately after post until the grub menu comes up. I explained earlier how to remove the .24 kernel. But don't try to remove the one you are running at the time. Not sure what would happen then.

Seeing this on Kubuntu 18.04 too. The haveged work around worked yesterday, but this morning I had to go back to 4.13 - the only previous kernel I have installed.

Installing the entropy daemon 'haveged' (sudo apt install haveged) worked on my notebook (Clevo, Tuxedo MS-1753, Kernel 4.15.0-24-generic). Boot time is as normal. Also manually adding entropy by moving the mouse like hell, reduced the boot time from 5 to 1.4 minutes.

This effected me after my first reboot in a couple weeks. I tried earlier kernels, still wouldn't boot.
Hangs on "[ OK ] Started GNOME Display Manager. Dispatcher Service......tem changes.pp link was shut down...."

 I was able to switch to lightdm to get in, but any time I try to update I get several pages of errors about python3 not being configured and py files being missing.

No apport report written because MaxReports is reached already
Errors were encountered while processing:
python3
update-notifier-common
python3-update-manager
gnome-shell
update-notifier
unattended-upgrades
update-manager
gnome-menus
update-manager-core
gdm3
E: Sub-process /usr/bin/dpkg returned an error code (1)

Any time I try to reboot with GDM, it hangs. will boot, ~mostly~ okay with lightdm.

My system is a System76 Sable Touch 3. 4th Generation Intel® Core™ i5-4440S ( 2.80GHz - 6MB cache - 4 Cores - HD Graphics 4600 )

Same here with Lenovo Yoga S1 laptop :(.

This bug was fixed in the package linux - 4.15.0-29.31

---------------
linux (4.15.0-29.31) bionic; urgency=medium

  * linux: 4.15.0-29.31 -proposed tracker (LP: #1782173)

  * [SRU Bionic][Cosmic] kernel panic in ipmi_ssif at msg_done_handler
    (LP: #1777716)
    - ipmi_ssif: Fix kernel panic at msg_done_handler

  * Update to ocxl driver for 18.04.1 (LP: #1775786)
    - misc: ocxl: use put_device() instead of device_unregister()
    - powerpc: Add TIDR CPU feature for POWER9
    - powerpc: Use TIDR CPU feature to control TIDR allocation
    - powerpc: use task_pid_nr() for TID allocation
    - ocxl: Rename pnv_ocxl_spa_remove_pe to clarify it's action
    - ocxl: Expose the thread_id needed for wait on POWER9
    - ocxl: Add an IOCTL so userspace knows what OCXL features are available
    - ocxl: Document new OCXL IOCTLs
    - ocxl: Fix missing unlock on error in afu_ioctl_enable_p9_wait()

  * Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after
    suspend (LP: #1776887)
    - ocxl: Document the OCXL_IOCTL_GET_METADATA IOCTL

  * Hard LOCKUP observed on stressing Ubuntu 18 04 (LP: #1777194)
    - powerpc: use NMI IPI for smp_send_stop
    - powerpc: Fix smp_send_stop NMI IPI handling

  * IPL: ppc64_cpu --frequency hang with INFO: rcu_sched detected stalls on
    CPUs/tasks on w34 and wsbmc016 with 920.1714.20170330n (LP: #1773964)
    - rtc: opal: Fix OPAL RTC driver OPAL_BUSY loops

  * [Regression] EXT4-fs error (device sda2): ext4_validate_block_bitmap:383:
    comm stress-ng: bg 4705: bad block bitmap checksum (LP: #1781709)
    - SAUCE: Revert "UBUNTU: SAUCE: ext4: fix ext4_validate_inode_bitmap: comm
      stress-ng: Corrupt inode bitmap"
    - SAUCE: ext4: check for allocation block validity with block group locked

linux (4.15.0-28.30) bionic; urgency=medium

  * linux: 4.15.0-28.30 -proposed tracker (LP: #1781433)

  * Cannot set MTU higher than 1500 in Xen instance (LP: #1781413)
    - xen-netfront: Fix mismatched rtnl_unlock
    - xen-netfront: Update features after registering netdev

linux (4.15.0-27.29) bionic; urgency=medium

  * linux: 4.15.0-27.29 -proposed tracker (LP: #1781062)

  * [Regression] EXT4-fs error (device sda1): ext4_validate_inode_bitmap:99:
    comm stress-ng: Corrupt inode bitmap (LP: #1780137)
    - SAUCE: ext4: fix ext4_validate_inode_bitmap: comm stress-ng: Corrupt inode
      bitmap

linux (4.15.0-26.28) bionic; urgency=medium

  * linux: 4.15.0-26.28 -proposed tracker (LP: #1780112)

  * failure to boot with linux-image-4.15.0-24-generic (LP: #1779827) // Cloud-
    init causes potentially huge boot delays with 4.15 kernels (LP: #1780062)
    - random: Make getrandom() ready earlier

linux (4.15.0-25.27) bionic; urgency=medium

  * linux: 4.15.0-25.27 -proposed tracker (LP: #1779354)

  * hisi_sas_v3_hw: internal task abort: timeout and not done. (LP: #1777736)
    - scsi: hisi_sas: Update a couple of register settings for v3 hw

  * hisi_sas: Add missing PHY spinlock init (LP: #1777734)
    - scsi: hisi_sas: Add missing PHY spinlock init

  * hisi_sas: improve read performance by pre-allocating slot DMA buffers
    (LP: #1777727)
    - scsi: hisi_sas: use dma_zalloc_cohe...

@Joseph Salisbury: I am confused. Looking at USN-3718-1 (https://usn.ubuntu.com/3718-1/) and USN-3718-2 (https://usn.ubuntu.com/3718-2/) it seems like CVE-1108 is fixed in Ubuntu 18.04 LTS for several linux kernel flavors (azure, gcp, hwe, kvm, oem and stock) and a subset for Ubuntu 16.04 LTS.

However the table at https://people.canonical.com/~kernel/cve/pkg/ALL-linux.html states 'pending applied'. The table https://people.canonical.com/~ubuntu-security/cve/2018/CVE-2018-1108.html states 'pending' and so on.

So my question is: is CVE-2018-1108 fixed in Ubuntu 18.04 LTS and 16.04 LTS? And if so since which kernel version? Did the new kernel that led to this bugreport fix the vulnerability. Did the fix you developed reintroduce the vulnerability?

Regards and thank you for your efforts!

I mean CVE-2018-1108 ...

This bug was fixed in the package linux - 4.15.0-29.31

---------------
linux (4.15.0-29.31) bionic; urgency=medium

  * linux: 4.15.0-29.31 -proposed tracker (LP: #1782173)

  * [SRU Bionic][Cosmic] kernel panic in ipmi_ssif at msg_done_handler
    (LP: #1777716)
    - ipmi_ssif: Fix kernel panic at msg_done_handler

  * Update to ocxl driver for 18.04.1 (LP: #1775786)
    - misc: ocxl: use put_device() instead of device_unregister()
    - powerpc: Add TIDR CPU feature for POWER9
    - powerpc: Use TIDR CPU feature to control TIDR allocation
    - powerpc: use task_pid_nr() for TID allocation
    - ocxl: Rename pnv_ocxl_spa_remove_pe to clarify it's action
    - ocxl: Expose the thread_id needed for wait on POWER9
    - ocxl: Add an IOCTL so userspace knows what OCXL features are available
    - ocxl: Document new OCXL IOCTLs
    - ocxl: Fix missing unlock on error in afu_ioctl_enable_p9_wait()

  * Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after
    suspend (LP: #1776887)
    - ocxl: Document the OCXL_IOCTL_GET_METADATA IOCTL

  * Hard LOCKUP observed on stressing Ubuntu 18 04 (LP: #1777194)
    - powerpc: use NMI IPI for smp_send_stop
    - powerpc: Fix smp_send_stop NMI IPI handling

  * IPL: ppc64_cpu --frequency hang with INFO: rcu_sched detected stalls on
    CPUs/tasks on w34 and wsbmc016 with 920.1714.20170330n (LP: #1773964)
    - rtc: opal: Fix OPAL RTC driver OPAL_BUSY loops

  * [Regression] EXT4-fs error (device sda2): ext4_validate_block_bitmap:383:
    comm stress-ng: bg 4705: bad block bitmap checksum (LP: #1781709)
    - SAUCE: Revert "UBUNTU: SAUCE: ext4: fix ext4_validate_inode_bitmap: comm
      stress-ng: Corrupt inode bitmap"
    - SAUCE: ext4: check for allocation block validity with block group locked

linux (4.15.0-28.30) bionic; urgency=medium

  * linux: 4.15.0-28.30 -proposed tracker (LP: #1781433)

  * Cannot set MTU higher than 1500 in Xen instance (LP: #1781413)
    - xen-netfront: Fix mismatched rtnl_unlock
    - xen-netfront: Update features after registering netdev

linux (4.15.0-27.29) bionic; urgency=medium

  * linux: 4.15.0-27.29 -proposed tracker (LP: #1781062)

  * [Regression] EXT4-fs error (device sda1): ext4_validate_inode_bitmap:99:
    comm stress-ng: Corrupt inode bitmap (LP: #1780137)
    - SAUCE: ext4: fix ext4_validate_inode_bitmap: comm stress-ng: Corrupt inode
      bitmap

linux (4.15.0-26.28) bionic; urgency=medium

  * linux: 4.15.0-26.28 -proposed tracker (LP: #1780112)

  * failure to boot with linux-image-4.15.0-24-generic (LP: #1779827) // Cloud-
    init causes potentially huge boot delays with 4.15 kernels (LP: #1780062)
    - random: Make getrandom() ready earlier

linux (4.15.0-25.27) bionic; urgency=medium

  * linux: 4.15.0-25.27 -proposed tracker (LP: #1779354)

  * hisi_sas_v3_hw: internal task abort: timeout and not done. (LP: #1777736)
    - scsi: hisi_sas: Update a couple of register settings for v3 hw

  * hisi_sas: Add missing PHY spinlock init (LP: #1777734)
    - scsi: hisi_sas: Add missing PHY spinlock init

  * hisi_sas: improve read performance by pre-allocating slot DMA buffers
    (LP: #1777727)
    - scsi: hisi_sas: use dma_zalloc_cohe...

I noticed similar effect with very recent (4.17) kernels. In 4.16.8 there were changes in random.c due to a security flaw. The function that detects "having enough entropy" is now strictly blocking. In the early boot phase this is bad on any machine without enough entropy sources. The kernel has 3 such sources: character devices, block devices and interrupts. On newer machines you can also have hardware random engines like in intel cores gen3+ (ivy bridge). This effect does not appear on computers with such a hw-rng. If you have one without hw-rng, and with a SSD only (they are not used for entropy gathering) and you don't mode your mouse, you are likely seeing this. The bad thing is, this kernel patch is actually necessary to prevent the system starting with insufficient safe random numbers. I applied a patch that reverts commit 43838a23a05fbd13e47d750d3dfd77001536dd33 in the kernel. After this change the startup worked like expected, but this is not a solution as it re-invents CVE-2018-1108. An idea would be to add a hw-rng like https://www.crowdsupply.com/13-37/infinite-noise-trng, but i did not test that so far. Check your cpu for the rdrand flag (lscpu). An entropy deamon like rngd helps only if you have entropy sources that it can use.

The updated kernel doesn't fix the issue for me. I still need to have 3 or 4 usb sticks connected to the computer so it can boot correctly and not get stuck on a blank screen. Probably still an entropy issue.

Hello.
With kernel -29 my VM boots fast as usual. But another strange thing I'm discovering is that plymouth image still blinking over desktop. It happens from time to time. Not always, but regularly.

I have this exact issue with ANY kernel above 4.15.0-20. I tried over a dozen different versions higher and ONLY 4.15.0-20 works straight away. So I seriously doubt its an issue with just 4.15.0-24, at least on my machine.

Linux 4.15.0-34 fails to boot in VirtualBox.
4.4.0-135 boots OK, same everything else.

stefan@stefan-lubuntu12:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
stefan@stefan-lubuntu12:~$ uname -a
Linux stefan-lubuntu12 4.4.0-135-generic #161-Ubuntu SMP Mon Aug 27 10:46:32 UTC 2018 i686 i686 i686 GNU/Linux

Also, cannot install 18.04 from ISO in new VM, probably also because of that.

Good thing I did not upgrade my physical machines to 18.04, like some poor souls in here did!

'Nuff said,
S.

Hi I am on Carbon X1 2015 and I was using ubuntu mate 16.04. The system suggested that I update to 18.04. I did that and went for run. I came back my screen was still there but the menu was gone. I forced a restart. I now get a screen for bios load then sda3_crypt. I put in my password and I get a blank screen with a blinking cursor that I cannot move and nothing else. I cannot recall what my kernel was. I just wanted tot ask if there has been any resolution on this issue...today is 2018-10-28.

I just read Stefan's comment and my heart sank...Any suggestions....anybody?

Adding my $0.02, whatever it is worth. I ran into this on a RamNode VPS. downgrading to 4.15.0-20-generic made it boot again. Attaching dmesg from that machine.
$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 58
model name : Intel(R) Xeon(R) CPU E3-1240 V2 @ 3.40GHz
stepping : 9
microcode : 0x1
cpu MHz : 3400.022
cache size : 4096 KB
physical id : 0
siblings : 1
core id : 0
cpu cores : 1
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss syscall nx lm constant_tsc arch_perfmon nopl cpuid pni pclmulqdq ssse3 cx16 pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm pti fsgsbase smep xsaveopt ibpb ibrs stibp
bugs : cpu_meltdown spectre_v1 spectre_v2
bogomips : 6800.04
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:

Wifi not working after upgrading to Disco Dingo development version

This bug was erroneously marked for verification in bionic; verification is not required and verification-needed-bionic is being removed.

Is there even anyone out there with disco dingo AND a functioning kernel with an nvidia driver? But of course if someone did, they wouldn't be here.

"I've tried nothing and I'm all out of ideas, man!"