Re: Debian initramfs/initrd, was Re: stack smashing detected
On Mon, 6 Feb 2023, Stan Johnson wrote:
> > Thanks, so the kernel does start, but hangs later.
> > Adding "initcall_debug" to the kernel command line may reveal more..
> > ...
>
> Please see attached.
>
> ...
>
> [ 34.440000] calling key_proc_init+0x0/0x5e @ 1
> [ 34.470000] initcall key_proc_init+0x0/0x5e returned 0 after 1307 usecs
> [ 34.500000] calling asymmetric_key_init+0x0/0x10 @ 1
> [ 34.520000] Key type asymmetric registered
> [ 34.540000] initcall asymmetric_key_init+0x0/0x10 returned 0 after 22481 usecs
> [ 34.570000] calling x509_key_init+0x0/0x16 @ 1
> [ 34.580000] Asymmetric key parser 'x509' registered
> [ 34.600000] initcall x509_key_init+0x0/0x16 returned 0 after 14116 usecs
> [ 34.620000] calling crypto_kdf108_init+0x0/0x13a @ 1
>
You could try 'initcall_blacklist=key_proc_init' or
initcall_blacklist=x509_key_init' etc.
This kind of thing has come up before.
https://lists.debian.org/debian-68k/2019/06/msg00020.html
https://lists.debian.org/debian-68k/2019/06/msg00066.html
These systems are too slow for needless key generation so a bug report
may be needed.
Reply to: