Re: NO_BOOTMEM breaks alpha pc164

2018-11-24 Thread Mike Rapoport
(adding linux-mm, the beginning of the thread is at https://lkml.org/lkml/2018/11/22/1032) On Fri, Nov 23, 2018 at 06:11:09PM +0200, Meelis Roos wrote: > >>The bad commit is swith to NO_BOOTMEM. > > > >[ ... ] > >>How do I debug it? > > > >Apparently, some of the early memory registration is not

Re: NO_BOOTMEM breaks alpha pc164

2018-11-23 Thread Meelis Roos
The bad commit is swith to NO_BOOTMEM. [ ... ] How do I debug it? Apparently, some of the early memory registration is not properly converted from bootmem to memblock + nobootmem for your system. You can try applying the below patch to enable debug printouts from memblock, maybe it'll

Re: NO_BOOTMEM breaks alpha pc164

2018-11-23 Thread Meelis Roos
When it hangs, it hangs right after starting init. "random: crng init done" is printed after starting init and nothing more appears on serial console. Can you please send the kernel log for the broken boot case? What happens if you try to boot with "init=/bin/sh" added to the kernel command

Re: NO_BOOTMEM breaks alpha pc164

2018-11-22 Thread Mike Rapoport
Hi, On Thu, Nov 22, 2018 at 03:27:44PM +0200, Meelis Roos wrote: > I have bisected 4.20-rc2 boot hang on a PC164 subarch alpha. > Other alphas in my collection are working fine. > > When it hangs, it hangs right after starting init. "random: crng init done" > is printed > after starting init

NO_BOOTMEM breaks alpha pc164

2018-11-22 Thread Meelis Roos
I have bisected 4.20-rc2 boot hang on a PC164 subarch alpha. Other alphas in my collection are working fine. When it hangs, it hangs right after starting init. "random: crng init done" is printed after starting init and nothing more appears on serial console. The bad commit is swith to