From: Michael Ellerman <mpe@ellerman.id.au>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Rowand\, Frank" <Frank.Rowand@sony.com>,
Abdul Haleem <abdhalee@linux.vnet.ibm.com>,
sachinp <sachinp@linux.vnet.ibm.com>,
linux-next <linux-next@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Rob Herring <robh@kernel.org>
Subject: Re: [Oops][next-20170614][] powerpc boot fails with WARNING: CPU: 12 PID: 0 at mm/memblock.c
Date: Fri, 16 Jun 2017 20:35:49 +1000 [thread overview]
Message-ID: <8737b0w77e.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <20170616133258.74900bc3@canb.auug.org.au>
Stephen Rothwell <sfr@canb.auug.org.au> writes:
> On Fri, 16 Jun 2017 11:13:35 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>> On Fri, 16 Jun 2017 10:57:22 +1000 Michael Ellerman <mpe@ellerman.id.au> wrote:
>> > "Rowand, Frank" <Frank.Rowand@sony.com> writes:
>> > > On Thursday, June 15, 2017 2:25 AM, Abdul Haleem [mailto:abdhalee@linux.vnet.ibm.com] wrote:
>> > >> On Thu, 2017-06-15 at 11:30 +0530, Abdul Haleem wrote:
>> > >>>
>> > >>> 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?
>>
>> OK.
>
> Actually, Rob removed it from his tree before I merged it.
Yep, just noticed that.
Thanks all.
cheers
prev parent reply other threads:[~2017-06-16 10:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-15 6:00 [Oops][next-20170614] powerpc boot fails with WARNING: CPU: 12 PID: 0 at mm/memblock.c Abdul Haleem
2017-06-15 9:24 ` [Oops][next-20170614][] " Abdul Haleem
2017-06-15 17:06 ` Rowand, Frank
2017-06-16 0:04 ` Benjamin Herrenschmidt
2017-06-16 0:57 ` Michael Ellerman
2017-06-16 1:13 ` Stephen Rothwell
2017-06-16 3:32 ` Stephen Rothwell
2017-06-16 10:35 ` Michael Ellerman [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8737b0w77e.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=Frank.Rowand@sony.com \
--cc=abdhalee@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=robh@kernel.org \
--cc=sachinp@linux.vnet.ibm.com \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).