On Wed, Sep 18, 2019 at 3:41 PM Geert Uytterhoeven <[email protected]> wrote: > On Wed, Sep 18, 2019 at 3:36 PM John Paul Adrian Glaubitz > <[email protected]> wrote: > > On 9/12/19 11:34 PM, Michael Schmitz wrote: > > > try adding 'initcall_debug' to the kernel command line. > > Attached the dmesg log with initcall_debug enabled. The delay was still > > there > > but no kernel OOPS. > > > [ 0.590000] calling dh_init+0x0/0x10 @ 1 > > [ 1.280000] random: fast init done > > [ 66.880000] random: crng init done > > [ 456.910000] initcall dh_init+0x0/0x10 returned 0 after 445625000 usecs > > Diffie-Hellman doing some heavy crypto lifting on a poor m68k CPU? > > Disable CONFIG_CRYPTO_DH?
See also https://lists.debian.org/debian-68k/2019/04/msg00033.html CRYPTO_DH is selected by CRYPTO_DEV_QAT and KEY_DH_OPERATIONS. The latter is bool, forcing CRYPTO_DH builtin. If KEY_DH_OPERATIONS needs to be enabled in a Debian kernel, perhaps it can be made tristate? Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected] In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
