All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bystricky, Juro" <juro.bystricky@intel.com>
To: Seebs <seebs@seebs.net>,
	"Fan, Wenzong (Wind River)" <wenzong.fan@windriver.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: pseudo 1.8.1 doesn't work with docker & dumb-init
Date: Wed, 14 Sep 2016 20:46:38 +0000	[thread overview]
Message-ID: <6E51916E4A1F32428260031F4C7CD2B61188FFD1@ORSMSX112.amr.corp.intel.com> (raw)
In-Reply-To: <9478781A-C1DD-46F5-B447-04D324E9EBA6@seebs.net>

I am pretty sure I glimpsed the messages: 
	Child process timeout after 2 seconds.
    	Child process exit status 4: lock_held
on several occasions recently, just before my Xserver was restarted and I was kicked back to the login prompt.  
I typically ran several parallel bitbake builds. Ubuntu 16.04, not using container. The last message in the syslog (first error message) was always:
Fatal IO error 11 (Resource temporarily unavailable) on X server :0

Possibly not related to this problem, nevertheless worth mentioning.

Thanks

Juro


> -----Original Message-----
> From: openembedded-core-bounces@lists.openembedded.org
> [mailto:openembedded-core-bounces@lists.openembedded.org] On Behalf Of
> Seebs
> Sent: Tuesday, September 6, 2016 11:40 PM
> To: Fan, Wenzong (Wind River) <wenzong.fan@windriver.com>
> Cc: Patches and discussions about the oe-core layer <openembedded-
> core@lists.openembedded.org>
> Subject: Re: [OE-core] pseudo 1.8.1 doesn't work with docker & dumb-init
> 
> On 7 Sep 2016, at 1:32, wenzong fan wrote:
> 
> > Yes, I believe it's not a 100 reproducible issue. Maybe you could run
> > it with other builds in parallel and try it 3 times or more.
> 
> I can try, but that might need bigger hardware than I have to hand at
> the moment.
> 
> -s
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core


  reply	other threads:[~2016-09-14 20:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-31  9:21 pseudo 1.8.1 doesn't work with docker & dumb-init wenzong fan
2016-08-31 15:11 ` Joshua Lock
2016-09-02  1:24   ` wenzong fan
2016-08-31 15:48 ` Seebs
2016-09-02  1:33   ` wenzong fan
2016-09-02  2:10     ` Seebs
2016-09-07  6:32       ` wenzong fan
2016-09-07  6:40         ` Seebs
2016-09-14 20:46           ` Bystricky, Juro [this message]
2016-09-15  2:24             ` Randy MacLeod
2016-09-15 19:08               ` Randy MacLeod

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=6E51916E4A1F32428260031F4C7CD2B61188FFD1@ORSMSX112.amr.corp.intel.com \
    --to=juro.bystricky@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=seebs@seebs.net \
    --cc=wenzong.fan@windriver.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.