On Mon, 10 Jun 2019, Finn Thain wrote: > On Mon, 10 Jun 2019, Finn Thain wrote: > > > > > The real mystery here is the two minute pause: > > > > [ 2.560000] random: fast init done > > [ 133.760000] random: crng init done > > [ 146.040000] Block layer SCSI generic (bsg) driver version 0.4 loaded > > (major 252) > > > > My first thought was that there isn't enough entropy before device drivers > > load. But I no longer think that this issue is related to the RNG at all, > > because when I boot that kernel in QEMU, I get a completely different > > result. (See attached log.) Weird. > > > > Aranym also stalls here (for about 20 seconds). Adding initcall_debug to > the kernel parameters reveals this: > > [ 0.620000] calling dh_init+0x0/0x10 @ 1 > [ 2.560000] random: fast init done > [ 24.030000] initcall dh_init+0x0/0x10 returned 0 after 22861089 usecs > > The reason why my kernel builds don't pause here is because they don't > call dh_init, because I have disabled CONFIG_CRYPTO_DH. > > I don't know why dh_init() is slow. Maybe it has to compute a public key. >
You can avoid loading the DH driver with the kernel parameter initcall_blacklist=dh_init --
