public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frank Rowand <frowand.list@gmail.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Frank Rowand <frank.rowand@sony.com>,
	linux-kernel@vger.kernel.org, Rob Herring <robh@kernel.org>
Subject: Re: Qemu crashes in -next due to 'of: remove *phandle properties from expanded device tree'
Date: Wed, 14 Jun 2017 17:45:52 -0700	[thread overview]
Message-ID: <5941D8C0.1020100@gmail.com> (raw)
In-Reply-To: <20170614223559.GA19172@roeck-us.net>

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

  reply	other threads:[~2017-06-15  0:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-14 19:26 Qemu crashes in -next due to 'of: remove *phandle properties from expanded device tree' Guenter Roeck
2017-06-14 21:31 ` Frank Rowand
2017-06-14 22:35   ` Guenter Roeck
2017-06-15  0:45     ` Frank Rowand [this message]
2017-06-15  2:10       ` Guenter Roeck
2017-06-15  4:12       ` Guenter Roeck
2017-06-15  7:58         ` Frank Rowand
2017-06-15  9:53           ` Guenter Roeck
2017-06-15  6:48 ` 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=5941D8C0.1020100@gmail.com \
    --to=frowand.list@gmail.com \
    --cc=frank.rowand@sony.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=robh@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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