Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	Randy MacLeod <randy.macleod@windriver.com>,
	<openembedded-core@lists.openembedded.org>,
	Armin Kuster <akuster808@gmail.com>,
	"Huang, Jie (Jackie)" <Jackie.Huang@windriver.com>,
	"Xu, Chi" <Chi.Xu@windriver.com>,
	"WOLD, SAUL" <saul.wold@intel.com>
Subject: Re: Yocto Project Status WW47’17
Date: Tue, 28 Nov 2017 15:49:10 +0800	[thread overview]
Message-ID: <90368c50-316e-b03e-252f-33110c059737@windriver.com> (raw)
In-Reply-To: <1511432407.862.111.camel@linuxfoundation.org>


On 11/23/2017 06:20 PM, Richard Purdie wrote:
> On Mon, 2017-11-20 at 20:22 -0500, Randy MacLeod wrote:
>>> o   Issues with 4.13.10 host kernels booting kvm x86 guests on
>>> Tumbleweed (Suse) and Fedora 26 (attempting to see if 4.13.12
>>> helps)
>>   
>> Robert, can you test Fedora 26. It would help to have a defect open
>> with steps to reproduce or
>> something about the typical workflow/ build time/ day of the week/
>> phase of the moon.
> 
> We have some further data:
> 
> a) The issue occurs on 4.13.12
> 
> rpurdie@tumbleweed:/tmp> cat /proc/version
> Linux version 4.13.12-1-vanilla (geeko@buildhost) (gcc version 7.2.1 20171020 [gcc-7-branch revision 253932] (SUSE Linux)) #1 SMP PREEMPT Wed Nov 8 11:21:09 UTC 2017 (9151c66)
> 
> b) The hang usually occurs at the TIMER line in the kernel logs but can
> occur after booting into userspace around the udevd line, or
> occasionally later in the boot process.
> 
> c) The similarity between this and the ppc bug I worked on make me
> strongly suspect qemu's timers are stopping firing and the guest is
> sitting in the idle loop.
> 
> d) I do now have a way to brute force the hangs at will. The attached
> "runqemu-parallel.py" script runs 50 qemus in parallel. In around 45s I
> had 10 hung on the autobuilder. I can provide more info on using that
> script if its not obvious. It does assume my recent master changes to
> the qemuconf files so we don't need to run bitbake -e to run runqemu.
> 
> This could well be the same kind of locking issue we saw on ppc. I'll
> continue to look into that.
> 
> Hopefully this extra information will put us on a good track to
> resolving it now. It is continuing to break builds and stop patch
> merging.

I modified the script to run on my host (I used qemux86, not qemux86-64,
the later one is still in building) (Up to date Fedora 26, the kernel
is 4.13.13):

$ cat /proc/version
Linux version 4.13.13-200.fc26.x86_64 
(mockbuild@bkernel01.phx2.fedoraproject.org) (gcc version 7.2.1 20170915 (Red 
Hat 7.2.1-2) (GCC)) #1 SMP Wed Nov 15 15:46:36 UTC 2017

But didn't see any hangs after 10 minutes, all the qemus reached login. So maybe
it had been fixed on 4.13.13 ?

// Robert

> 
> Cheers,
> 
> Richard
> 


  reply	other threads:[~2017-11-28  7:50 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 [this message]
2017-11-28 10:47       ` Robert Yang
2017-11-28 12:48         ` Good news " Robert Yang
2017-11-28 13:15           ` Richard Purdie
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=90368c50-316e-b03e-252f-33110c059737@windriver.com \
    --to=liezhi.yang@windriver.com \
    --cc=Chi.Xu@windriver.com \
    --cc=Jackie.Huang@windriver.com \
    --cc=akuster808@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=randy.macleod@windriver.com \
    --cc=richard.purdie@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox