On 2016-09-14 04:46 PM, Bystricky, Juro wrote:
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.
Yes, it may be. Thanks for reporting it.
Two weeks ago, I was building a qemuarm64 image on my laptop
(i7, 16 GB, SSD running Ubuntu-16.04)
and I saw a similarity bizarre result from running a build
in that chrome and then the X server were both killed.
I wasn't in front of the system when this happened so
I can't say exactly what was going on.
I did collect some of the logs from my IRC client and chrome:
[423679.028437] konversation[23416]: segfault at 7f72d2c33ce0 ip
00007f72eca4e818 sp 00007ffc7f450ae0 error 4 in
libQt5Gui.so.5.5.1[7f72ec8da000+527000]
[423679.325315] chrome[28083]: segfault at 968 ip 00007f63f7615643 sp
00007ffd26c25af0 error 4 in libX11.so.6.3.0[7f63f75ed000+135000]
and then from the X server:
Aug 29 16:11:59 laptop org.a11y.atspi.Registry[4763]: XIO: fatal IO
error 11 (Resource temporarily unavailable) on X server ":0"
Aug 29 16:11:59 laptop org.a11y.atspi.Registry[4763]: after 67649
requests (67649 known processed) with 0 events remaining.
Aug 29 16:11:59 laptop gnome-session[4748]: (diodon:4925): Gdk-WARNING
**: diodon: Fatal IO error 11 (Resource temporarily unavailable) on X
server :0
.
...
Aug 29 16:11:59 laptop systemd[1]: Started Process Core Dump (PID
28084/UID 0).
Aug 29 16:11:59 laptop gnome-session[4748]: Failed to connect to Mir:
Failed to connect to server socket: No such file or directory
Aug 29 16:11:59 laptop kernel: [423679.325315] chrome[28083]: segfault
at 968 ip 00007f63f7615643 sp 00007ffd26c25af0 error 4 in
libX11.so.6.3.0[7f63f75ed000+135000]
In my case, I had added meta-oe to oe-core and was building:
MACHINE=qemuarm64 bitbake imagemagick
I reproduced it once in X then did NOT see it happen when
I built with an X session running but building on the console.
i.e. the build of imagemagick for qemuarm64 succeeded.
I've removed the build logs it seems but I'll see if I can reproduce
the failure overnight.
../Randy
Thanks
Juro
-----Original Message-----
From: openembedded-core-boun...@lists.openembedded.org
[mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of
Seebs
Sent: Tuesday, September 6, 2016 11:40 PM
To: Fan, Wenzong (Wind River) <wenzong....@windriver.com>
Cc: Patches and discussions about the oe-core layer <openembedded-
c...@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
--
# Randy MacLeod. SMTS, Linux, Wind River
Direct: 613.963.1350 | 350 Terry Fox Drive, Suite 200, Ottawa, ON,
Canada, K2K 2W5
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
