[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170615021030.GA11000@roeck-us.net>
Date: Wed, 14 Jun 2017 19:10:30 -0700
From: Guenter Roeck <linux@...ck-us.net>
To: Frank Rowand <frowand.list@...il.com>
Cc: Frank Rowand <frank.rowand@...y.com>, linux-kernel@...r.kernel.org,
Rob Herring <robh@...nel.org>
Subject: Re: Qemu crashes in -next due to 'of: remove *phandle properties
from expanded device tree'
On Wed, Jun 14, 2017 at 05:45:52PM -0700, Frank Rowand wrote:
> 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?
>
See attached. I am on the road; I'll try to do some debugging later from home.
Guenter
View attachment "ppc64.log" of type "text/plain" (6408 bytes)
Powered by blists - more mailing lists