All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Robert Yang <liezhi.yang@windriver.com>
Cc: openembedded-core@lists.openembedded.org, "Xu,
	Chi" <Chi.Xu@windriver.com>, "WOLD, SAUL" <saul.wold@intel.com>
Subject: Re: Good news Re: Yocto Project Status WW47’17
Date: Tue, 28 Nov 2017 13:15:17 +0000	[thread overview]
Message-ID: <1511874917.862.134.camel@linuxfoundation.org> (raw)
In-Reply-To: <6a03b501-31d9-5e20-4c40-ce381bb4ad17@windriver.com>

On Tue, 2017-11-28 at 20:48 +0800, Robert Yang wrote:
> Hi RP,
> On 11/28/2017 06:47 PM, Robert Yang wrote:
> > # Works
> > $ runqemu tmp/deploy/images/qemux86-64/ nographic snapshot
> > 
> > # Doesn't work, like hang:
> > $ runqemu tmp/deploy/images/qemux86-64/ nographic snapshot kvm
> I upgraded qemu-native to qemu-2.11.0-rc2, then no hangs any more. I
> dropped
> the conflicted patches during upgrade. I will send a formal upgrade
> tomorrow
> it this is acceptable.
> 
> Here is the draft patch for testing:
> 
>    git://git.openembedded.org/openembedded-core-contrib rbt/qemu_test
>    http://cgit.openembedded.org/openembedded-core-contrib/log/?h=rbt/
> qemu_test

Thanks for the data point. I've been putting my data into:

https://bugzilla.yoctoproject.org/show_bug.cgi?id=12301

As you can see there, I think there are actually two issues:

a) A boot hang around the ..TIMER line where the guest isn't getting
timer interupts

b) Something which causes the APIC to see "version 0".

I applied the 2.11-rc2 upgrade and it seemed to stop the hangs I was
seeing with "-no-kvm-irqchip" but doesn't stop the ones I see without
that.

I am seeing hangs in guests where the version 0 message appears as well
as where we see 0x14. The 0x14 versions do boot further into userspace
usually.

It also seems host hardware specific as I cannot get my local build
machine to hang as yet. That could mean its timing or could be cpu
revision, I've removed many but not all OS differences :/.

Cheers,

Richard


  reply	other threads:[~2017-11-28 13:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-20 15:36 Yocto Project Status WW47’17 Jolley, Stephen K
2017-11-21  1:22 ` Randy MacLeod
2017-11-21  1:56   ` Huang, Jie (Jackie)
2017-11-21 11:09   ` Richard Purdie
2017-11-21 11:14     ` Burton, Ross
2017-11-21 15:32     ` Wold, Saul
2017-11-22  6:09     ` Robert Yang
2017-11-23 10:20   ` Richard Purdie
2017-11-28  7:49     ` Robert Yang
2017-11-28 10:47       ` Robert Yang
2017-11-28 12:48         ` Good news " Robert Yang
2017-11-28 13:15           ` Richard Purdie [this message]
2017-11-28 13:46             ` Robert Yang

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=1511874917.862.134.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=Chi.Xu@windriver.com \
    --cc=liezhi.yang@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=saul.wold@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.