[OE-core] Yocto-2.2 build failures on Ubuntu 14.04.5 & 16.04.x hosts due to crash of unity-settings-daemon followed by restart of lightdm

Richard Purdie richard.purdie at linuxfoundation.org
Tue Dec 27 16:49:11 UTC 2016


On Tue, 2016-12-27 at 15:18 +0530, srikanth krishnakar wrote:
> Hello Richard,
> 
> I was under impression that installing Ubuntu-14.04.4 (+lastest
> updates) would give me stable build environment, unfortunately that
> is not the case ! I could see the logout issue on this installation
> too. So I believe that issue should be reproducible on any 14.04.x
> installation including 16.04.x with all latest updates installed. The
> second attempt of build on "Ubuntu-14.04.4" shows the status of
> bitbake as halted at libvorbis when logout happened:
> 
> ---------------------------------------------------------
> NOTE: Running task 2460 of 4212 (/home/poky/meta/recipes-
> core/ncurses/ncurses_6.0+20160625.bb:do_packagedata)
> NOTE: recipe ncurses-6.0+20160625-r0: task do_packagedata: Started
> NOTE: recipe ncurses-6.0+20160625-r0: task do_packagedata: Succeeded
> NOTE: Running task 2461 of 4212 (/home/poky/meta/recipes-
> core/readline/readline_6.3.bb:do_package)
> NOTE: recipe libjpeg-turbo-1_1.5.0-r0: task do_package: Succeeded
> NOTE: Running task 2462 of 4212 (/home/poky/meta/recipes-
> graphics/jpeg/libjpeg-turbo_1.5.0.bb:do_packagedata)
> NOTE: recipe libjpeg-turbo-1_1.5.0-r0: task do_packagedata: Started
> NOTE: recipe libjpeg-turbo-1_1.5.0-r0: task do_packagedata: Succeeded
> NOTE: Running task 2463 of 4212 (/home/poky/meta/recipes-
> multimedia/libvorbis/libvorbis_1.3.5.bb:do_package)
> NOTE: recipe readline-6.3-r0: task do_package: Started
> NOTE: recipe libvorbis-1.3.5-r0: task do_package: Started


None of these look particularly suspicios for causing your X session to
die.

Some further questions:

a) Is anything showing in the dmesg logs? Is the OOM killer the thing
which is killing processes?
b) How are you measuring free memory? You mentioned it was low, it
would depend on the disk cache size and swap status too.
c) Have you tried a lower BB_NUMBER_THREADS and lower PARALLEL_MAKE
values to rule out resource problems and perhaps identify more
specifically which task is causing your problem?

As I mentioned previously, this problem should reduce to a specific
recipe+task causing the problem, unless its a general resource issue in
which case the threads/parallel make will stop the problem occurring.

We have autobuilders running various versions of Ubuntu and we don't
notice problems with processes dying, admittedly we don't run X
desktops on them in general though.

Cheers,

Richard





More information about the Openembedded-core mailing list