From: Michael Ellerman <mpe@ellerman•id.au>
To: "Rowand, Frank" <Frank.Rowand@sony•com>,
Abdul Haleem <abdhalee@linux•vnet.ibm.com>
Cc: sachinp <sachinp@linux•vnet.ibm.com>,
linux-next <linux-next@vger•kernel.org>,
linux-kernel <linux-kernel@vger•kernel.org>,
Stephen Rothwell <sfr@canb•auug.org.au>,
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 10:57:22 +1000 [thread overview]
Message-ID: <87injwwxzh.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <ED290C750E1B324E972B0017C9D4BAB02E5A7EAF@USCULXMSG03.am.sony.com>
"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:
>>> 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
next prev parent reply other threads:[~2017-06-16 0:57 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 [this message]
2017-06-16 1:13 ` Stephen Rothwell
2017-06-16 3:32 ` Stephen Rothwell
2017-06-16 10:35 ` Michael Ellerman
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=87injwwxzh.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman$(echo .)id.au \
--cc=Frank.Rowand@sony$(echo .)com \
--cc=abdhalee@linux$(echo .)vnet.ibm.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=robh@kernel$(echo .)org \
--cc=sachinp@linux$(echo .)vnet.ibm.com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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