[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1497571456.2897.86.camel@kernel.crashing.org>
Date: Fri, 16 Jun 2017 10:04:16 +1000
From: Benjamin Herrenschmidt <benh@...nel.crashing.org>
To: "Rowand, Frank" <Frank.Rowand@...y.com>,
Abdul Haleem <abdhalee@...ux.vnet.ibm.com>
Cc: sachinp <sachinp@...ux.vnet.ibm.com>,
Stephen Rothwell <sfr@...b.auug.org.au>,
linux-kernel <linux-kernel@...r.kernel.org>,
linux-next <linux-next@...r.kernel.org>,
linuxppc-dev <linuxppc-dev@...ts.ozlabs.org>
Subject: Re: [Oops][next-20170614][] powerpc boot fails with WARNING: CPU:
12 PID: 0 at mm/memblock.c
On Thu, 2017-06-15 at 17:06 +0000, Rowand, Frank wrote:
> 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.
I think kexec needs them in sysfs (or /proc) when building the fdt
for the target kernel.
Cheers,
Ben.
Powered by blists - more mailing lists