On Wed, 19 Jun 2019, John Paul Adrian Glaubitz wrote: > On 6/10/19 10:28 AM, Finn Thain wrote: > > 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. > > If you have a suggestion for a configuration change, please file a bug > against src:linux with [email protected] CC'ed so that I am > notified about this. >
I would not want to become a Debian/m68k porter, even if there was room for another one. Besides that, on a modern host, the emulators run Debian/m68k quite well despite CONFIG_CRYPTO_DH (console bugs and kernel module bugs notwithstanding). > I don't claim that the kernel configuration in Debian for m68k is > perfect, but in order to be able to sort these issues out, people should > avoid building their own custom kernels and help improving the Debian > kernel instead. > I certainly would not assert that "people should" do anything. However, I do encourage all Linux/m68k users to learn to cross-compile small kernels and other packages. That's because real m68k hardware has limitations -- no FPU, limited RAM etc. -- which Debian doesn't cater to. -- > Adrian >
