On Fri, Mar 09, 2018 at 01:05:11PM -0600, Rob Herring wrote: > On Fri, Mar 9, 2018 at 6:51 AM, Alvaro G. M. <[email protected]> wrote: > > Hi, > > > > I've found via git bisect that 0fa1c579349fdd90173381712ad78aa99c09d38b > > makes microblaze unbootable. > > > > I'm sorry I can't provide any console output, as nothing appears at all, > > even when setting earlyprintk (or at least I wasn't able to get anything > > back!). > > Ah, looks like microblaze doesn't set CONFIG_NO_BOOTMEM and so > memblock_virt_alloc() doesn't work for CONFIG_HAVE_MEMBLOCK && > !CONFIG_NO_BOOTMEM. AFAICT, microblaze doesn't really need bootmem and > it can be removed, but I'm still investigating. Can you try out this > branch[1]. > > Rob > > [1] git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git > microblaze-fixes
Hi, Rob! This branch does indeed solve the issue. My microblaze system is now booting as it did before, and everything seems normal now. Thanks! Tested-by: Alvaro Gamez Machado <[email protected]> -- Alvaro G. M.
