From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752098AbdFPBNj (ORCPT ); Thu, 15 Jun 2017 21:13:39 -0400 Received: from ozlabs.org ([103.22.144.67]:52971 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751641AbdFPBNi (ORCPT ); Thu, 15 Jun 2017 21:13:38 -0400 Date: Fri, 16 Jun 2017 11:13:35 +1000 From: Stephen Rothwell To: Michael Ellerman Cc: "Rowand, Frank" , Abdul Haleem , sachinp , linux-next , linux-kernel , linuxppc-dev , Rob Herring Subject: Re: [Oops][next-20170614][] powerpc boot fails with WARNING: CPU: 12 PID: 0 at mm/memblock.c Message-ID: <20170616111335.4e1a818a@canb.auug.org.au> In-Reply-To: <87injwwxzh.fsf@concordia.ellerman.id.au> References: <1497506437.15415.60.camel@abdul.in.ibm.com> <1497518696.15415.68.camel@abdul.in.ibm.com> <87injwwxzh.fsf@concordia.ellerman.id.au> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Michael, On Fri, 16 Jun 2017 10:57:22 +1000 Michael Ellerman wrote: > > "Rowand, Frank" 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. -- Cheers, Stephen Rothwell