Bug#897632: Boot timeout after latest security update
Package: linux-image-4.9.0-6-amd64
Version: 4.9.88-1
Hi,
after the last security update of linux kernel, the boot on my Intel
Core i3-4330 hangs for about half a minute. I believe the culprint
might be waiting for the following line:
May 03 18:31:06 tux kernel: random: crng init done
as reported by journalctl -b:
May 03 18:30:09 tux kernel: clocksource: Switched to clocksource tsc
May 03 18:30:11 tux systemd-networkd[249]: eth0: Gained carrier
May 03 18:30:11 tux kernel: r8169 0000:02:00.0 eth0: link up
May 03 18:30:11 tux kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
May 03 18:30:12 tux avahi-daemon[380]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::76d4:35ff:fef4:9ab3.
May 03 18:30:12 tux avahi-daemon[380]: New relevant interface eth0.IPv6 for mDNS.
May 03 18:30:12 tux systemd-networkd[249]: eth0: Gained IPv6LL
May 03 18:30:12 tux avahi-daemon[380]: Registering new address record for fe80::76d4:35ff:fef4:9ab3 on eth0.*.
May 03 18:30:20 tux systemd-networkd[249]: eth0: DHCPv4 address 192.168.88.220/24 via 192.168.88.1
May 03 18:30:20 tux avahi-daemon[380]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.88.220.
May 03 18:30:20 tux avahi-daemon[380]: New relevant interface eth0.IPv4 for mDNS.
May 03 18:30:20 tux avahi-daemon[380]: Registering new address record for 192.168.88.220 on eth0.IPv4.
May 03 18:30:24 tux systemd-networkd[249]: eth0: Configured
May 03 18:31:06 tux kernel: random: crng init done
May 03 18:31:06 tux gnome-session[453]: gnome-session-binary[453]: WARNING: Could not parse desktop file orca-autostart.desktop or it references a not found TryExec binary
May 03 18:31:06 tux gnome-session-binary[453]: WARNING: Could not parse desktop file orca-autostart.desktop or it references a not found TryExec binary
May 03 18:31:06 tux dbus[367]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service'
May 03 18:31:06 tux systemd[1]: Starting Daemon for power management...
May 03 18:31:06 tux dbus[367]: [system] Successfully activated service 'org.freedesktop.UPower'
May 03 18:31:06 tux systemd[1]: Started Daemon for power management.
It could be related to this bit from the changelog:
CVE-2018-1108
Jann Horn reported that crng_ready() does not properly handle the
crng_init variable states and the RNG could be treated as
cryptographically safe too early after system boot.
--
Miroslav Kure
Reply to: