Re: Buster startup is blocked for minutes long

[Zach Marano <zmarano@google.com>]

There was a kernel regression introduced upstream however I thought it was already addressed in the Debian kernels. If Bastian is here, maybe he knows what the story is.

Some references:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897632

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897572#115

commit ff752d82d986d0f14406a707cc7cd3d121b179d5
Author: Ben Hutchings <ben@decadent.org.uk>
Date:   Wed Jun 13 04:31:00 2018 +0100

    random: Make getrandom() ready earlier

-----
Zach Marano
zmarano@google.com

On Thu, Aug 16, 2018 at 6:22 AM Gustavo Serra Scalet <gustavo.scalet@collabora.com> wrote:

Hi,

I was trying to build buster and run it on Google Cloud and I noticed
that it was taking a long time to boot (around 180 seconds, and not the
usual 15 seconds like stretch takes). In the end I noticed it was chrony
and its getrandom() call being blocked due to lack of system entropy.

I provided better details on a chrony bug report, but I just wanted to
report on this list to avoid other being caught up by surprise (and it
looks like I'm the first one noticing it for buster):

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906276

Is somebody else trying buster on other cloud providers? Please note
that chrony was not used on stretch, rather it was ntpd.
--
Gustavo Serra Scalet