Subject: Re: Qemu crashes in -next due to 'of: remove *phandle properties from
 expanded device tree'
To: Guenter Roeck <linux@roeck-us.net>
References: <20170614192638.GA15210@roeck-us.net> <5941AB4E.3070804@gmail.com>
 <20170614223559.GA19172@roeck-us.net>
Cc: Frank Rowand <frank.rowand@sony.com>, linux-kernel@vger.kernel.org,
        Rob Herring <robh@kernel.org>
From: Frank Rowand <frowand.list@gmail.com>
Message-ID: <5941D8C0.1020100@gmail.com>
Date: Wed, 14 Jun 2017 17:45:52 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.4.0
MIME-Version: 1.0
In-Reply-To: <20170614223559.GA19172@roeck-us.net>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 885
Lines: 27

On 06/14/17 15:35, Guenter Roeck wrote:
> On Wed, Jun 14, 2017 at 02:31:58PM -0700, Frank Rowand wrote:
>> Hi Guenter,

< snip >

>> Can you also include the console messages before the "[ cut here ]" line?
>>
> http://kerneltests.org/builders
> 
> Check qemu test results in the 'next' column. ppc and ppc64 show related console
> messages.

Thanks for the pointer.  Unfortunately I did not see any additional clues (yet)
in the full log.

I tried to compare the failed boot to a good boot, but did not find a console
log for a good boot.  I started at the qemu-ppc-next builder page:

  http://kerneltests.org/builders/qemu-ppc64-next

and looked at recent tests that were successful (like #645).  But the log file
link from that test does not show the contents of the console for tests that
pass.  Is there some way to see what the console for a successful test looks
like?

-Frank