linux-kernel - Re: Bug: Microblaze stopped booting after 0fa1c579349fdd90173381712ad78aa99c09d38b

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20180312075252.GA15895@salem.gmr.ssr.upm.es>
Date:   Mon, 12 Mar 2018 08:52:53 +0100
From:   "Alvaro G. M." <alvaro.gamez@...ent.com>
To:     Rob Herring <robh@...nel.org>
Cc:     Michal Simek <monstr@...str.eu>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: Bug: Microblaze stopped booting after
 0fa1c579349fdd90173381712ad78aa99c09d38b

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. <alvaro.gamez@...ent.com> 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 <alvaro.gamez@...ent.com>


-- 
Alvaro G. M.