linux-kernel - RE: [Oops][next-20170614][] powerpc boot fails with WARNING: CPU: 12 PID: 0 at mm/memblock.c

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]

Date:   Fri, 16 Jun 2017 10:57:22 +1000
From:   Michael Ellerman <mpe@...erman.id.au>
To:     "Rowand\, Frank" <Frank.Rowand@...y.com>,
        Abdul Haleem <abdhalee@...ux.vnet.ibm.com>
Cc:     sachinp <sachinp@...ux.vnet.ibm.com>,
        linux-next <linux-next@...r.kernel.org>,
        linux-kernel <linux-kernel@...r.kernel.org>,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        linuxppc-dev <linuxppc-dev@...ts.ozlabs.org>,
        Rob Herring <robh@...nel.org>
Subject: RE: [Oops][next-20170614][] powerpc boot fails with WARNING: CPU: 12 PID: 0 at mm/memblock.c

"Rowand, Frank" <Frank.Rowand@...y.com> writes:

> On Thursday, June 15, 2017 2:25 AM, Abdul Haleem [mailto:abdhalee@...ux.vnet.ibm.com]  wrote:
>>
>> On Thu, 2017-06-15 at 11:30 +0530, Abdul Haleem wrote:
>>> Hi,
>>>
>>> linux-next fails to boot on powerpc Bare-metal with these warnings.
>>>
>>> machine booted fine on next-20170613
>>
>> Thanks Michael, Yes it is (75fe04e59 of: remove *phandle properties from
>> expanded device tree)
>>
>> Frank, would you please take a look at the trace.
>>
>> Thanks
>
> < snip >
>
> My patch series 'of: remove *phandle properties from expanded device tree'
> in -next seems to have broken boot for a significant number of powerpc
> systems.  I am actively working on understanding and fixing the problem.

Thanks.

At least for me reverting that patch on top of linux-next gets things
booting again.

Stephen can you revert that patch in linux-next today?

cheers