Morty 2.2.1 build failure

Morty 2.2.1 build failure

[Greg Wilson-Lindberg]

Hello List,

I got a copy of the book "Embedded Linux Systems with the Yocto Project" at the SCALE 15x conference and this prompted me to try building the Yocto Poky build before getting the Boot to Qt Yocto build environment.

I tried building on 2 x86 systems, a 64 bit system at work and a 32 bit system at my home, both failed in the same way:

gwilson 11:06:54:~/yocto/poky-morty-16.0.1$ source ./oe-init-build-env
You had no conf/local.conf file. This configuration file has therefore been
created for you with some default values. You may wish to edit it to, for
example, select a different MACHINE (target hardware). See conf/local.conf
for more information as common configuration options are commented.

You had no conf/bblayers.conf file. This configuration file has therefore been
created for you with some default values. To add additional metadata layers
into your configuration please add entries to conf/bblayers.conf.

The Yocto Project has extensive documentation about OE including a reference
manual which can be found at:
    http://yoctoproject.org/documentation

For more information about OpenEmbedded see their website:
    http://www.openembedded.org/


### Shell environment set up for builds. ###

You can now run 'bitbake <target>'

Common targets are:
    core-image-minimal
    core-image-sato
    meta-toolchain
    meta-ide-support

You can also run generated qemu images with a command like 'runqemu qemux86'
gwilson 11:07:08:~/yocto/poky-morty-16.0.1/build$
gwilson 11:07:10:~/yocto/poky-morty-16.0.1/build$
gwilson 11:07:11:~/yocto/poky-morty-16.0.1/build$ bitbake core-image-sato
Parsing recipes: 100% |############################################################################################| Time: 0:00:29
Parsing of 864 .bb files complete (0 cached, 864 parsed). 1318 targets, 50 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION        = "1.32.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "Ubuntu-14.04"
TARGET_SYS        = "i586-poky-linux"
MACHINE           = "qemux86"
DISTRO            = "poky"
DISTRO_VERSION    = "2.2.1"
TUNE_FEATURES     = "m32 i586"
TARGET_FPU        = ""
meta
meta-poky
meta-yocto-bsp    = "<unknown>:<unknown>"

NOTE: Fetching uninative binary shim from http://downloads.yoctoproject.org/releases/uninative/1.4/x86_64-nativesdk-libc.tar.bz2;sha256sum=101ff8f2580c193488db9e76f9646fb6ed38b65fb76f403acb0e2178ce7127ca
--2017-03-20 11:07:57--  http://downloads.yoctoproject.org/releases/uninative/1.4/x86_64-nativesdk-libc.tar.bz2
Resolving downloads.yoctoproject.org (downloads.yoctoproject.org)... 198.145.20.127
Connecting to downloads.yoctoproject.org (downloads.yoctoproject.org)|198.145.20.127|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2473216 (2.4M) [application/octet-stream]
Saving to: '/home/gwilson/yocto/poky-morty-16.0.1/build/downloads/uninative/101ff8f2580c193488db9e76f9646fb6ed38b65fb76f403acb0e2178ce7127ca/x86_64-nativesdk-libc.tar.bz2'


2017-03-20 11:07:58 (6.62 MB/s) - '/home/gwilson/yocto/poky-morty-16.0.1/build/downloads/uninative/101ff8f2580c193488db9e76f9646fb6ed38b65fb76f403acb0e2178ce7127ca/x86_64-nativesdk-libc.tar.bz2' saved [2473216/2473216]

Initialising tasks: 100% |#########################################################################################| Time: 0:00:15
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
WARNING: flex-native-2.6.0-r0 do_fetch: Failed to fetch URL http://downloads.sourceforge.net/flex/flex-2.6.0.tar.bz2, attempting MIRRORS if available
WARNING: file-native-5.28-r0 do_fetch: Failed to fetch URL git://github.com/file/file.git, attempting MIRRORS if available
ERROR: file-native-5.28-r0 do_fetch: Fetcher failure: Unable to find revision 3c521817322a6bf5160cfeb09b9145ccde587b2a in branch master even from upstream
ERROR: file-native-5.28-r0 do_fetch: Fetcher failure for URL: 'git://github.com/file/file.git'. Unable to fetch URL from any source.
ERROR: file-native-5.28-r0 do_fetch: Function failed: base_do_fetch
ERROR: Logfile of failure stored in: /home/gwilson/yocto/poky-morty-16.0.1/build/tmp/work/x86_64-linux/file-native/5.28-r0/temp/log.do_fetch.23747
ERROR: Task (virtual:native:/home/gwilson/yocto/poky-morty-16.0.1/meta/recipes-devtools/file/file_5.28.bb:do_fetch) failed with exit code '1'
NOTE: Tasks Summary: Attempted 203 tasks of which 0 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
  virtual:native:/home/gwilson/yocto/poky-morty-16.0.1/meta/recipes-devtools/file/file_5.28.bb:do_fetch
Summary: There were 2 WARNING messages shown.
Summary: There were 3 ERROR messages shown, returning a non-zero exit code.
gwilson 11:13:14:~/yocto/poky-morty-16.0.1/build$

I get 1 file that needs to go to a mirror and a second file that can't be found at all.

Are these known bugs? Do I need to just back up and use Morty 2.2?

Regards,

Greg Wilson-Lindberg
Sakura Finetek
310-783-5075

Re: Morty 2.2.1 build failure

[akuster808]

Greg,

On 03/21/2017 04:29 PM, Greg Wilson-Lindberg wrote:
> Hello List,
>
> I got a copy of the book "Embedded Linux Systems with the Yocto Project" at the SCALE 15x conference and this prompted me to try building the Yocto Poky build before getting the Boot to Qt Yocto build environment.
>
> I tried building on 2 x86 systems, a 64 bit system at work and a 32 bit system at my home, both failed in the same way:
>
> gwilson 11:06:54:~/yocto/poky-morty-16.0.1$ source ./oe-init-build-env
> You had no conf/local.conf file. This configuration file has therefore been
> created for you with some default values. You may wish to edit it to, for
> example, select a different MACHINE (target hardware). See conf/local.conf
> for more information as common configuration options are commented.
>
> You had no conf/bblayers.conf file. This configuration file has therefore been
> created for you with some default values. To add additional metadata layers
> into your configuration please add entries to conf/bblayers.conf.
>
> The Yocto Project has extensive documentation about OE including a reference
> manual which can be found at:
>      http://yoctoproject.org/documentation
>
> For more information about OpenEmbedded see their website:
>      http://www.openembedded.org/
>
>
> ### Shell environment set up for builds. ###
>
> You can now run 'bitbake <target>'
>
> Common targets are:
>      core-image-minimal
>      core-image-sato
>      meta-toolchain
>      meta-ide-support
>
> You can also run generated qemu images with a command like 'runqemu qemux86'
> gwilson 11:07:08:~/yocto/poky-morty-16.0.1/build$
> gwilson 11:07:10:~/yocto/poky-morty-16.0.1/build$
> gwilson 11:07:11:~/yocto/poky-morty-16.0.1/build$ bitbake core-image-sato
> Parsing recipes: 100% |############################################################################################| Time: 0:00:29
> Parsing of 864 .bb files complete (0 cached, 864 parsed). 1318 targets, 50 skipped, 0 masked, 0 errors.
> NOTE: Resolving any missing task queue dependencies
>
> Build Configuration:
> BB_VERSION        = "1.32.0"
> BUILD_SYS         = "x86_64-linux"
> NATIVELSBSTRING   = "Ubuntu-14.04"
> TARGET_SYS        = "i586-poky-linux"
> MACHINE           = "qemux86"
> DISTRO            = "poky"
> DISTRO_VERSION    = "2.2.1"
> TUNE_FEATURES     = "m32 i586"
> TARGET_FPU        = ""
> meta
> meta-poky
> meta-yocto-bsp    = "<unknown>:<unknown>"
>
> NOTE: Fetching uninative binary shim from http://downloads.yoctoproject.org/releases/uninative/1.4/x86_64-nativesdk-libc.tar.bz2;sha256sum=101ff8f2580c193488db9e76f9646fb6ed38b65fb76f403acb0e2178ce7127ca
> --2017-03-20 11:07:57--  http://downloads.yoctoproject.org/releases/uninative/1.4/x86_64-nativesdk-libc.tar.bz2
> Resolving downloads.yoctoproject.org (downloads.yoctoproject.org)... 198.145.20.127
> Connecting to downloads.yoctoproject.org (downloads.yoctoproject.org)|198.145.20.127|:80... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 2473216 (2.4M) [application/octet-stream]
> Saving to: '/home/gwilson/yocto/poky-morty-16.0.1/build/downloads/uninative/101ff8f2580c193488db9e76f9646fb6ed38b65fb76f403acb0e2178ce7127ca/x86_64-nativesdk-libc.tar.bz2'
>
>
> 2017-03-20 11:07:58 (6.62 MB/s) - '/home/gwilson/yocto/poky-morty-16.0.1/build/downloads/uninative/101ff8f2580c193488db9e76f9646fb6ed38b65fb76f403acb0e2178ce7127ca/x86_64-nativesdk-libc.tar.bz2' saved [2473216/2473216]
>
> Initialising tasks: 100% |#########################################################################################| Time: 0:00:15
> NOTE: Executing SetScene Tasks
> NOTE: Executing RunQueue Tasks
> WARNING: flex-native-2.6.0-r0 do_fetch: Failed to fetch URL http://downloads.sourceforge.net/flex/flex-2.6.0.tar.bz2, attempting MIRRORS if available
> WARNING: file-native-5.28-r0 do_fetch: Failed to fetch URL git://github.com/file/file.git, attempting MIRRORS if available
> ERROR: file-native-5.28-r0 do_fetch: Fetcher failure: Unable to find revision 3c521817322a6bf5160cfeb09b9145ccde587b2a in branch master even from upstream
> ERROR: file-native-5.28-r0 do_fetch: Fetcher failure for URL: 'git://github.com/file/file.git'. Unable to fetch URL from any source.

this is a known issue and should be fixed now (again). The upstream repo 
had issues which caused the hashes to not match. I heard the repo got 
corrected.

> ERROR: file-native-5.28-r0 do_fetch: Function failed: base_do_fetch
> ERROR: Logfile of failure stored in: /home/gwilson/yocto/poky-morty-16.0.1/build/tmp/work/x86_64-linux/file-native/5.28-r0/temp/log.do_fetch.23747
> ERROR: Task (virtual:native:/home/gwilson/yocto/poky-morty-16.0.1/meta/recipes-devtools/file/file_5.28.bb:do_fetch) failed with exit code '1'
> NOTE: Tasks Summary: Attempted 203 tasks of which 0 didn't need to be rerun and 1 failed.
>
> Summary: 1 task failed:
>    virtual:native:/home/gwilson/yocto/poky-morty-16.0.1/meta/recipes-devtools/file/file_5.28.bb:do_fetch
> Summary: There were 2 WARNING messages shown.
> Summary: There were 3 ERROR messages shown, returning a non-zero exit code.
> gwilson 11:13:14:~/yocto/poky-morty-16.0.1/build$
>
> I get 1 file that needs to go to a mirror and a second file that can't be found at all.
Please try again.
>
> Are these known bugs? Do I need to just back up and use Morty 2.2?
This affected 2.1, 2.2 and master.

regards,
Armin
>
> Regards,
>
> Greg Wilson-Lindberg
> Sakura Finetek
> 310-783-5075

Re: Morty 2.2.1 build failure

[Esponde, Joel]

Hi,

You are right Armin and here is the revert commit for the morty branch:
http://git.yoctoproject.org/cgit.cgi/poky/commit/?h=morty&id=e292e935b077a95ae093d4b425c7e95b177b030b

Joël Esponde

> -----Message d'origine-----
> De : yocto-bounces@yoctoproject.org [mailto:yocto-
> bounces@yoctoproject.org] De la part de akuster808
> Envoyé : mercredi 22 mars 2017 03:07
> À : yocto@yoctoproject.org
> Objet : Re: [yocto] Morty 2.2.1 build failure
> 
> 
> Greg,
> 
> On 03/21/2017 04:29 PM, Greg Wilson-Lindberg wrote:
> > Hello List,
> >
> > I got a copy of the book "Embedded Linux Systems with the Yocto Project"
> at the SCALE 15x conference and this prompted me to try building the Yocto
> Poky build before getting the Boot to Qt Yocto build environment.
> >
> > I tried building on 2 x86 systems, a 64 bit system at work and a 32 bit system
> at my home, both failed in the same way:
> >
> > gwilson 11:06:54:~/yocto/poky-morty-16.0.1$ source ./oe-init-build-env
> > You had no conf/local.conf file. This configuration file has therefore
> > been created for you with some default values. You may wish to edit it
> > to, for example, select a different MACHINE (target hardware). See
> > conf/local.conf for more information as common configuration options are
> commented.
> >
> > You had no conf/bblayers.conf file. This configuration file has
> > therefore been created for you with some default values. To add
> > additional metadata layers into your configuration please add entries to
> conf/bblayers.conf.
> >
> > The Yocto Project has extensive documentation about OE including a
> > reference manual which can be found at:
> >      http://yoctoproject.org/documentation
> >
> > For more information about OpenEmbedded see their website:
> >      http://www.openembedded.org/
> >
> >
> > ### Shell environment set up for builds. ###
> >
> > You can now run 'bitbake <target>'
> >
> > Common targets are:
> >      core-image-minimal
> >      core-image-sato
> >      meta-toolchain
> >      meta-ide-support
> >
> > You can also run generated qemu images with a command like 'runqemu
> qemux86'
> > gwilson 11:07:08:~/yocto/poky-morty-16.0.1/build$
> > gwilson 11:07:10:~/yocto/poky-morty-16.0.1/build$
> > gwilson 11:07:11:~/yocto/poky-morty-16.0.1/build$ bitbake
> > core-image-sato Parsing recipes: 100%
> >
> |#########################################################
> ###################################| Time: 0:00:29 Parsing of 864
> .bb files complete (0 cached, 864 parsed). 1318 targets, 50 skipped, 0 masked,
> 0 errors.
> > NOTE: Resolving any missing task queue dependencies
> >
> > Build Configuration:
> > BB_VERSION        = "1.32.0"
> > BUILD_SYS         = "x86_64-linux"
> > NATIVELSBSTRING   = "Ubuntu-14.04"
> > TARGET_SYS        = "i586-poky-linux"
> > MACHINE           = "qemux86"
> > DISTRO            = "poky"
> > DISTRO_VERSION    = "2.2.1"
> > TUNE_FEATURES     = "m32 i586"
> > TARGET_FPU        = ""
> > meta
> > meta-poky
> > meta-yocto-bsp    = "<unknown>:<unknown>"
> >
> > NOTE: Fetching uninative binary shim from
> > http://downloads.yoctoproject.org/releases/uninative/1.4/x86_64-native
> > sdk-
> libc.tar.bz2;sha256sum=101ff8f2580c193488db9e76f9646fb6ed38b65fb76
> > f403acb0e2178ce7127ca
> > --2017-03-20 11:07:57--
> > http://downloads.yoctoproject.org/releases/uninative/1.4/x86_64-native
> > sdk-libc.tar.bz2 Resolving downloads.yoctoproject.org
> > (downloads.yoctoproject.org)... 198.145.20.127 Connecting to
> > downloads.yoctoproject.org
> (downloads.yoctoproject.org)|198.145.20.127|:80... connected.
> > HTTP request sent, awaiting response... 200 OK
> > Length: 2473216 (2.4M) [application/octet-stream] Saving to:
> > '/home/gwilson/yocto/poky-morty-
> 16.0.1/build/downloads/uninative/101ff8f2580c193488db9e76f9646fb6ed38b
> 65fb76f403acb0e2178ce7127ca/x86_64-nativesdk-libc.tar.bz2'
> >
> >
> > 2017-03-20 11:07:58 (6.62 MB/s) -
> > '/home/gwilson/yocto/poky-morty-
> 16.0.1/build/downloads/uninative/101ff
> >
> 8f2580c193488db9e76f9646fb6ed38b65fb76f403acb0e2178ce7127ca/x86_64-
> nat
> > ivesdk-libc.tar.bz2' saved [2473216/2473216]
> >
> > Initialising tasks: 100%
> >
> |#########################################################
> ############
> > ####################| Time: 0:00:15
> > NOTE: Executing SetScene Tasks
> > NOTE: Executing RunQueue Tasks
> > WARNING: flex-native-2.6.0-r0 do_fetch: Failed to fetch URL
> > http://downloads.sourceforge.net/flex/flex-2.6.0.tar.bz2, attempting
> > MIRRORS if available
> > WARNING: file-native-5.28-r0 do_fetch: Failed to fetch URL
> > git://github.com/file/file.git, attempting MIRRORS if available
> > ERROR: file-native-5.28-r0 do_fetch: Fetcher failure: Unable to find
> > revision 3c521817322a6bf5160cfeb09b9145ccde587b2a in branch master
> > even from upstream
> > ERROR: file-native-5.28-r0 do_fetch: Fetcher failure for URL:
> 'git://github.com/file/file.git'. Unable to fetch URL from any source.
> 
> this is a known issue and should be fixed now (again). The upstream repo
> had issues which caused the hashes to not match. I heard the repo got
> corrected.
> 
> > ERROR: file-native-5.28-r0 do_fetch: Function failed: base_do_fetch
> > ERROR: Logfile of failure stored in:
> > /home/gwilson/yocto/poky-morty-16.0.1/build/tmp/work/x86_64-
> linux/file
> > -native/5.28-r0/temp/log.do_fetch.23747
> > ERROR: Task (virtual:native:/home/gwilson/yocto/poky-morty-
> 16.0.1/meta/recipes-devtools/file/file_5.28.bb:do_fetch) failed with exit
> code '1'
> > NOTE: Tasks Summary: Attempted 203 tasks of which 0 didn't need to be
> rerun and 1 failed.
> >
> > Summary: 1 task failed:
> >
> > virtual:native:/home/gwilson/yocto/poky-morty-16.0.1/meta/recipes-devt
> > ools/file/file_5.28.bb:do_fetch
> > Summary: There were 2 WARNING messages shown.
> > Summary: There were 3 ERROR messages shown, returning a non-zero exit
> code.
> > gwilson 11:13:14:~/yocto/poky-morty-16.0.1/build$
> >
> > I get 1 file that needs to go to a mirror and a second file that can't be found
> at all.
> Please try again.
> >
> > Are these known bugs? Do I need to just back up and use Morty 2.2?
> This affected 2.1, 2.2 and master.
> 
> regards,
> Armin
> >
> > Regards,
> >
> > Greg Wilson-Lindberg
> > Sakura Finetek
> > 310-783-5075
> 
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Re: Morty 2.2.1 build failure

[Greg Wilson-Lindberg]

Hi Armin, et al,

I tried it again this morning and it did get past the file not found error. But when it gets above step 4000 somewhere it gets an error that kills not just the yocto build but the full login session. I'm left staring at the Linux Login screen. I originally saw this problem with a git clone of 16.0.0, and figured it was a git problem, tried building from a download of the 16.0.1 bz2 file when I ran into the file not found error.

At this point I'm not sure what I can pass on to the list to help find the bug, if there are some switches that I can set to get more debug info, or maybe something is already saved that I can send that will help?

Regards,
Greg

> -----Original Message-----
> From: yocto-bounces@yoctoproject.org [mailto:yocto-
> bounces@yoctoproject.org] On Behalf Of akuster808
> Sent: Tuesday, March 21, 2017 7:07 PM
> To: yocto@yoctoproject.org
> Subject: Re: [yocto] Morty 2.2.1 build failure
> 
> 
> Greg,
> 
> On 03/21/2017 04:29 PM, Greg Wilson-Lindberg wrote:
> > Hello List,
> >
> > I got a copy of the book "Embedded Linux Systems with the Yocto Project"
> at the SCALE 15x conference and this prompted me to try building the Yocto
> Poky build before getting the Boot to Qt Yocto build environment.
> >
> > I tried building on 2 x86 systems, a 64 bit system at work and a 32 bit system
> at my home, both failed in the same way:
> >
> > gwilson 11:06:54:~/yocto/poky-morty-16.0.1$ source ./oe-init-build-env
> > You had no conf/local.conf file. This configuration file has therefore
> > been created for you with some default values. You may wish to edit it
> > to, for example, select a different MACHINE (target hardware). See
> > conf/local.conf for more information as common configuration options are
> commented.
> >
> > You had no conf/bblayers.conf file. This configuration file has
> > therefore been created for you with some default values. To add
> > additional metadata layers into your configuration please add entries to
> conf/bblayers.conf.
> >
> > The Yocto Project has extensive documentation about OE including a
> > reference manual which can be found at:
> >      http://yoctoproject.org/documentation
> >
> > For more information about OpenEmbedded see their website:
> >      http://www.openembedded.org/
> >
> >
> > ### Shell environment set up for builds. ###
> >
> > You can now run 'bitbake <target>'
> >
> > Common targets are:
> >      core-image-minimal
> >      core-image-sato
> >      meta-toolchain
> >      meta-ide-support
> >
> > You can also run generated qemu images with a command like 'runqemu
> qemux86'
> > gwilson 11:07:08:~/yocto/poky-morty-16.0.1/build$
> > gwilson 11:07:10:~/yocto/poky-morty-16.0.1/build$
> > gwilson 11:07:11:~/yocto/poky-morty-16.0.1/build$ bitbake
> > core-image-sato Parsing recipes: 100%
> >
> |#########################################################
> ###################################| Time: 0:00:29 Parsing of 864
> .bb files complete (0 cached, 864 parsed). 1318 targets, 50 skipped, 0 masked,
> 0 errors.
> > NOTE: Resolving any missing task queue dependencies
> >
> > Build Configuration:
> > BB_VERSION        = "1.32.0"
> > BUILD_SYS         = "x86_64-linux"
> > NATIVELSBSTRING   = "Ubuntu-14.04"
> > TARGET_SYS        = "i586-poky-linux"
> > MACHINE           = "qemux86"
> > DISTRO            = "poky"
> > DISTRO_VERSION    = "2.2.1"
> > TUNE_FEATURES     = "m32 i586"
> > TARGET_FPU        = ""
> > meta
> > meta-poky
> > meta-yocto-bsp    = "<unknown>:<unknown>"
> >
> > NOTE: Fetching uninative binary shim from
> > http://downloads.yoctoproject.org/releases/uninative/1.4/x86_64-native
> > sdk-
> libc.tar.bz2;sha256sum=101ff8f2580c193488db9e76f9646fb6ed38b65fb76
> > f403acb0e2178ce7127ca
> > --2017-03-20 11:07:57--
> > http://downloads.yoctoproject.org/releases/uninative/1.4/x86_64-native
> > sdk-libc.tar.bz2 Resolving downloads.yoctoproject.org
> > (downloads.yoctoproject.org)... 198.145.20.127 Connecting to
> > downloads.yoctoproject.org
> (downloads.yoctoproject.org)|198.145.20.127|:80... connected.
> > HTTP request sent, awaiting response... 200 OK
> > Length: 2473216 (2.4M) [application/octet-stream] Saving to:
> > '/home/gwilson/yocto/poky-morty-
> 16.0.1/build/downloads/uninative/101ff8f2580c193488db9e76f9646fb6ed38b
> 65fb76f403acb0e2178ce7127ca/x86_64-nativesdk-libc.tar.bz2'
> >
> >
> > 2017-03-20 11:07:58 (6.62 MB/s) -
> > '/home/gwilson/yocto/poky-morty-
> 16.0.1/build/downloads/uninative/101ff
> >
> 8f2580c193488db9e76f9646fb6ed38b65fb76f403acb0e2178ce7127ca/x86_64-
> nat
> > ivesdk-libc.tar.bz2' saved [2473216/2473216]
> >
> > Initialising tasks: 100%
> >
> |#########################################################
> ############
> > ####################| Time: 0:00:15
> > NOTE: Executing SetScene Tasks
> > NOTE: Executing RunQueue Tasks
> > WARNING: flex-native-2.6.0-r0 do_fetch: Failed to fetch URL
> > http://downloads.sourceforge.net/flex/flex-2.6.0.tar.bz2, attempting
> > MIRRORS if available
> > WARNING: file-native-5.28-r0 do_fetch: Failed to fetch URL
> > git://github.com/file/file.git, attempting MIRRORS if available
> > ERROR: file-native-5.28-r0 do_fetch: Fetcher failure: Unable to find
> > revision 3c521817322a6bf5160cfeb09b9145ccde587b2a in branch master
> > even from upstream
> > ERROR: file-native-5.28-r0 do_fetch: Fetcher failure for URL:
> 'git://github.com/file/file.git'. Unable to fetch URL from any source.
> 
> this is a known issue and should be fixed now (again). The upstream repo
> had issues which caused the hashes to not match. I heard the repo got
> corrected.
> 
> > ERROR: file-native-5.28-r0 do_fetch: Function failed: base_do_fetch
> > ERROR: Logfile of failure stored in:
> > /home/gwilson/yocto/poky-morty-16.0.1/build/tmp/work/x86_64-
> linux/file
> > -native/5.28-r0/temp/log.do_fetch.23747
> > ERROR: Task (virtual:native:/home/gwilson/yocto/poky-morty-
> 16.0.1/meta/recipes-devtools/file/file_5.28.bb:do_fetch) failed with exit
> code '1'
> > NOTE: Tasks Summary: Attempted 203 tasks of which 0 didn't need to be
> rerun and 1 failed.
> >
> > Summary: 1 task failed:
> >
> > virtual:native:/home/gwilson/yocto/poky-morty-16.0.1/meta/recipes-devt
> > ools/file/file_5.28.bb:do_fetch
> > Summary: There were 2 WARNING messages shown.
> > Summary: There were 3 ERROR messages shown, returning a non-zero exit
> code.
> > gwilson 11:13:14:~/yocto/poky-morty-16.0.1/build$
> >
> > I get 1 file that needs to go to a mirror and a second file that can't be found
> at all.
> Please try again.
> >
> > Are these known bugs? Do I need to just back up and use Morty 2.2?
> This affected 2.1, 2.2 and master.
> 
> regards,
> Armin
> >
> > Regards,
> >
> > Greg Wilson-Lindberg
> > Sakura Finetek
> > 310-783-5075
> 
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Re: Morty 2.2.1 build failure

[Jussi Kukkonen]

[-- Attachment #1: Type: text/plain, Size: 8095 bytes --]

On 22 March 2017 at 22:23, Greg Wilson-Lindberg <GWilson@sakuraus.com>
wrote:

> Hi Armin, et al,
>
> I tried it again this morning and it did get past the file not found
> error. But when it gets above step 4000 somewhere it gets an error that
> kills not just the yocto build but the full login session. I'm left staring
> at the Linux Login screen. I originally saw this problem with a git clone
> of 16.0.0, and figured it was a git problem, tried building from a download
> of the 16.0.1 bz2 file when I ran into the file not found error.
>

The "file" git repo was broken twice in the past week but current poky
master branch (current commit 49c2df5652d2) and morty branch (current
commit e292e935b077) do fetch it correctly at the time of writing.

Personally I recommend not using the tarball releases: stick to git
branches (and remember to pull once in a while) as they are likely to get
fixes to issues like these faster.

HTH,
  Jussi


>
> At this point I'm not sure what I can pass on to the list to help find the
> bug, if there are some switches that I can set to get more debug info, or
> maybe something is already saved that I can send that will help?
>
> Regards,
> Greg
>
> > -----Original Message-----
> > From: yocto-bounces@yoctoproject.org [mailto:yocto-
> > bounces@yoctoproject.org] On Behalf Of akuster808
> > Sent: Tuesday, March 21, 2017 7:07 PM
> > To: yocto@yoctoproject.org
> > Subject: Re: [yocto] Morty 2.2.1 build failure
> >
> >
> > Greg,
> >
> > On 03/21/2017 04:29 PM, Greg Wilson-Lindberg wrote:
> > > Hello List,
> > >
> > > I got a copy of the book "Embedded Linux Systems with the Yocto
> Project"
> > at the SCALE 15x conference and this prompted me to try building the
> Yocto
> > Poky build before getting the Boot to Qt Yocto build environment.
> > >
> > > I tried building on 2 x86 systems, a 64 bit system at work and a 32
> bit system
> > at my home, both failed in the same way:
> > >
> > > gwilson 11:06:54:~/yocto/poky-morty-16.0.1$ source ./oe-init-build-env
> > > You had no conf/local.conf file. This configuration file has therefore
> > > been created for you with some default values. You may wish to edit it
> > > to, for example, select a different MACHINE (target hardware). See
> > > conf/local.conf for more information as common configuration options
> are
> > commented.
> > >
> > > You had no conf/bblayers.conf file. This configuration file has
> > > therefore been created for you with some default values. To add
> > > additional metadata layers into your configuration please add entries
> to
> > conf/bblayers.conf.
> > >
> > > The Yocto Project has extensive documentation about OE including a
> > > reference manual which can be found at:
> > >      http://yoctoproject.org/documentation
> > >
> > > For more information about OpenEmbedded see their website:
> > >      http://www.openembedded.org/
> > >
> > >
> > > ### Shell environment set up for builds. ###
> > >
> > > You can now run 'bitbake <target>'
> > >
> > > Common targets are:
> > >      core-image-minimal
> > >      core-image-sato
> > >      meta-toolchain
> > >      meta-ide-support
> > >
> > > You can also run generated qemu images with a command like 'runqemu
> > qemux86'
> > > gwilson 11:07:08:~/yocto/poky-morty-16.0.1/build$
> > > gwilson 11:07:10:~/yocto/poky-morty-16.0.1/build$
> > > gwilson 11:07:11:~/yocto/poky-morty-16.0.1/build$ bitbake
> > > core-image-sato Parsing recipes: 100%
> > >
> > |#########################################################
> > ###################################| Time: 0:00:29 Parsing of 864
> > .bb files complete (0 cached, 864 parsed). 1318 targets, 50 skipped, 0
> masked,
> > 0 errors.
> > > NOTE: Resolving any missing task queue dependencies
> > >
> > > Build Configuration:
> > > BB_VERSION        = "1.32.0"
> > > BUILD_SYS         = "x86_64-linux"
> > > NATIVELSBSTRING   = "Ubuntu-14.04"
> > > TARGET_SYS        = "i586-poky-linux"
> > > MACHINE           = "qemux86"
> > > DISTRO            = "poky"
> > > DISTRO_VERSION    = "2.2.1"
> > > TUNE_FEATURES     = "m32 i586"
> > > TARGET_FPU        = ""
> > > meta
> > > meta-poky
> > > meta-yocto-bsp    = "<unknown>:<unknown>"
> > >
> > > NOTE: Fetching uninative binary shim from
> > > http://downloads.yoctoproject.org/releases/uninative/1.4/x86_64-native
> > > sdk-
> > libc.tar.bz2;sha256sum=101ff8f2580c193488db9e76f9646fb6ed38b65fb76
> > > f403acb0e2178ce7127ca
> > > --2017-03-20 11:07:57--
> > > http://downloads.yoctoproject.org/releases/uninative/1.4/x86_64-native
> > > sdk-libc.tar.bz2 Resolving downloads.yoctoproject.org
> > > (downloads.yoctoproject.org)... 198.145.20.127 Connecting to
> > > downloads.yoctoproject.org
> > (downloads.yoctoproject.org)|198.145.20.127|:80... connected.
> > > HTTP request sent, awaiting response... 200 OK
> > > Length: 2473216 (2.4M) [application/octet-stream] Saving to:
> > > '/home/gwilson/yocto/poky-morty-
> > 16.0.1/build/downloads/uninative/101ff8f2580c193488db9e76f9646fb6ed38b
> > 65fb76f403acb0e2178ce7127ca/x86_64-nativesdk-libc.tar.bz2'
> > >
> > >
> > > 2017-03-20 11:07:58 (6.62 MB/s) -
> > > '/home/gwilson/yocto/poky-morty-
> > 16.0.1/build/downloads/uninative/101ff
> > >
> > 8f2580c193488db9e76f9646fb6ed38b65fb76f403acb0e2178ce7127ca/x86_64-
> > nat
> > > ivesdk-libc.tar.bz2' saved [2473216/2473216]
> > >
> > > Initialising tasks: 100%
> > >
> > |#########################################################
> > ############
> > > ####################| Time: 0:00:15
> > > NOTE: Executing SetScene Tasks
> > > NOTE: Executing RunQueue Tasks
> > > WARNING: flex-native-2.6.0-r0 do_fetch: Failed to fetch URL
> > > http://downloads.sourceforge.net/flex/flex-2.6.0.tar.bz2, attempting
> > > MIRRORS if available
> > > WARNING: file-native-5.28-r0 do_fetch: Failed to fetch URL
> > > git://github.com/file/file.git, attempting MIRRORS if available
> > > ERROR: file-native-5.28-r0 do_fetch: Fetcher failure: Unable to find
> > > revision 3c521817322a6bf5160cfeb09b9145ccde587b2a in branch master
> > > even from upstream
> > > ERROR: file-native-5.28-r0 do_fetch: Fetcher failure for URL:
> > 'git://github.com/file/file.git'. Unable to fetch URL from any source.
> >
> > this is a known issue and should be fixed now (again). The upstream repo
> > had issues which caused the hashes to not match. I heard the repo got
> > corrected.
> >
> > > ERROR: file-native-5.28-r0 do_fetch: Function failed: base_do_fetch
> > > ERROR: Logfile of failure stored in:
> > > /home/gwilson/yocto/poky-morty-16.0.1/build/tmp/work/x86_64-
> > linux/file
> > > -native/5.28-r0/temp/log.do_fetch.23747
> > > ERROR: Task (virtual:native:/home/gwilson/yocto/poky-morty-
> > 16.0.1/meta/recipes-devtools/file/file_5.28.bb:do_fetch) failed with
> exit
> > code '1'
> > > NOTE: Tasks Summary: Attempted 203 tasks of which 0 didn't need to be
> > rerun and 1 failed.
> > >
> > > Summary: 1 task failed:
> > >
> > > virtual:native:/home/gwilson/yocto/poky-morty-16.0.1/meta/recipes-devt
> > > ools/file/file_5.28.bb:do_fetch
> > > Summary: There were 2 WARNING messages shown.
> > > Summary: There were 3 ERROR messages shown, returning a non-zero exit
> > code.
> > > gwilson 11:13:14:~/yocto/poky-morty-16.0.1/build$
> > >
> > > I get 1 file that needs to go to a mirror and a second file that can't
> be found
> > at all.
> > Please try again.
> > >
> > > Are these known bugs? Do I need to just back up and use Morty 2.2?
> > This affected 2.1, 2.2 and master.
> >
> > regards,
> > Armin
> > >
> > > Regards,
> > >
> > > Greg Wilson-Lindberg
> > > Sakura Finetek
> > > 310-783-5075
> >
> > --
> > _______________________________________________
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>

[-- Attachment #2: Type: text/html, Size: 11934 bytes --]

Re: Morty 2.2.1 build failure

[Paul Eggleton]

On Thursday, 23 March 2017 9:23:24 AM NZDT Greg Wilson-Lindberg wrote:
> I tried it again this morning and it did get past the file not found error.
> But when it gets above step 4000 somewhere it gets an error that kills not
> just the yocto build but the full login session. I'm left staring at the
> Linux Login screen.

Your machine isn't running out of RAM by any chance, triggering the OOM 
killer? Anything indicative in your system logs?

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: Morty 2.2.1 build failure

[Greg Wilson-Lindberg]

Hi Paul,

I looked in the logs from the failure yesterday and couldn't find anything, so I restarted the build and it ran for about another 1000 steps before crashing again. I still can't find anything in any of the logs, syslog, kern.log, auth.log, etc.

Cheers,
Greg

> -----Original Message-----
> From: Paul Eggleton [mailto:paul.eggleton@linux.intel.com]
> Sent: Thursday, March 23, 2017 2:49 AM
> To: Greg Wilson-Lindberg <GWilson@sakuraus.com>
> Cc: yocto@yoctoproject.org; akuster808 <akuster808@gmail.com>
> Subject: Re: [yocto] Morty 2.2.1 build failure
> 
> On Thursday, 23 March 2017 9:23:24 AM NZDT Greg Wilson-Lindberg wrote:
> > I tried it again this morning and it did get past the file not found error.
> > But when it gets above step 4000 somewhere it gets an error that kills
> > not just the yocto build but the full login session. I'm left staring
> > at the Linux Login screen.
> 
> Your machine isn't running out of RAM by any chance, triggering the OOM
> killer? Anything indicative in your system logs?
> 
> Cheers,
> Paul
> 
> --
> 
> Paul Eggleton
> Intel Open Source Technology Centre

Re: Morty 2.2.1 build failure

[Paul Eggleton]

That's really bizarre. There shouldn't be anything in a bitbake build that 
could cause anything like this (other than possibly how intensive it is, which 
might trigger out-of-memory or an underlying hardware/software failure).

Assuming the X session is ending is there anything in your ~/.xsession-errors 
or /var/log/Xorg.*.log?

Cheers,
Paul

On Friday, 24 March 2017 5:58:24 AM NZDT Greg Wilson-Lindberg wrote:
> Hi Paul,
> 
> I looked in the logs from the failure yesterday and couldn't find anything,
> so I restarted the build and it ran for about another 1000 steps before
> crashing again. I still can't find anything in any of the logs, syslog,
> kern.log, auth.log, etc.
> 
> Cheers,
> Greg
> 
> > -----Original Message-----
> > From: Paul Eggleton [mailto:paul.eggleton@linux.intel.com]
> > Sent: Thursday, March 23, 2017 2:49 AM
> > To: Greg Wilson-Lindberg <GWilson@sakuraus.com>
> > Cc: yocto@yoctoproject.org; akuster808 <akuster808@gmail.com>
> > Subject: Re: [yocto] Morty 2.2.1 build failure
> > 
> > On Thursday, 23 March 2017 9:23:24 AM NZDT Greg Wilson-Lindberg wrote:
> > > I tried it again this morning and it did get past the file not found
> > > error.
> > > But when it gets above step 4000 somewhere it gets an error that kills
> > > not just the yocto build but the full login session. I'm left staring
> > > at the Linux Login screen.
> > 
> > Your machine isn't running out of RAM by any chance, triggering the OOM
> > killer? Anything indicative in your system logs?
> > 
> > Cheers,
> > Paul
> > 
> > --
> > 
> > Paul Eggleton
> > Intel Open Source Technology Centre


-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: Morty 2.2.1 build failure

[akuster]

On 03/23/2017 12:25 PM, Paul Eggleton wrote:
> That's really bizarre. There shouldn't be anything in a bitbake build that
> could cause anything like this (other than possibly how intensive it is, which
> might trigger out-of-memory or an underlying hardware/software failure).

I usually get my builds to reboot my system when I build on a loptop. I 
have not seen this on a tower style work station. You may want to play 
with the BB_NUMBER_THREADS=# and PARALLEL_MAKE = "-j #" settings in your 
local.conf.

- armin
>
> Assuming the X session is ending is there anything in your ~/.xsession-errors
> or /var/log/Xorg.*.log?
>
> Cheers,
> Paul
>
> On Friday, 24 March 2017 5:58:24 AM NZDT Greg Wilson-Lindberg wrote:
>> Hi Paul,
>>
>> I looked in the logs from the failure yesterday and couldn't find anything,
>> so I restarted the build and it ran for about another 1000 steps before
>> crashing again. I still can't find anything in any of the logs, syslog,
>> kern.log, auth.log, etc.
>>
>> Cheers,
>> Greg
>>
>>> -----Original Message-----
>>> From: Paul Eggleton [mailto:paul.eggleton@linux.intel.com]
>>> Sent: Thursday, March 23, 2017 2:49 AM
>>> To: Greg Wilson-Lindberg <GWilson@sakuraus.com>
>>> Cc: yocto@yoctoproject.org; akuster808 <akuster808@gmail.com>
>>> Subject: Re: [yocto] Morty 2.2.1 build failure
>>>
>>> On Thursday, 23 March 2017 9:23:24 AM NZDT Greg Wilson-Lindberg wrote:
>>>> I tried it again this morning and it did get past the file not found
>>>> error.
>>>> But when it gets above step 4000 somewhere it gets an error that kills
>>>> not just the yocto build but the full login session. I'm left staring
>>>> at the Linux Login screen.
>>> Your machine isn't running out of RAM by any chance, triggering the OOM
>>> killer? Anything indicative in your system logs?
>>>
>>> Cheers,
>>> Paul
>>>
>>> --
>>>
>>> Paul Eggleton
>>> Intel Open Source Technology Centre
>

Re: Morty 2.2.1 build failure

[Greg Wilson-Lindberg]

Hi Armin & Paul,

First there is nothing in the X log files.
I'm building on a desktop machine with 12GB of memory and an 8 core processor running Kubuntu 14.04.
I added the PARALLEL_MAKE parameter set to 4, no effect, still built with 8 threads, crashed.
Set BB_NUMBER_THREADS to 4, built with 4 threads, still crashed.

Regards,
Greg

> -----Original Message-----
> From: akuster [mailto:akuster@mvista.com]
> Sent: Thursday, March 23, 2017 12:33 PM
> To: Greg Wilson-Lindberg <GWilson@sakuraus.com>
> Cc: Paul Eggleton <paul.eggleton@linux.intel.com>; yocto@yoctoproject.org
> Subject: Re: [yocto] Morty 2.2.1 build failure
> 
> 
> 
> On 03/23/2017 12:25 PM, Paul Eggleton wrote:
> > That's really bizarre. There shouldn't be anything in a bitbake build
> > that could cause anything like this (other than possibly how intensive
> > it is, which might trigger out-of-memory or an underlying
> hardware/software failure).
> 
> I usually get my builds to reboot my system when I build on a loptop. I have
> not seen this on a tower style work station. You may want to play with the
> BB_NUMBER_THREADS=# and PARALLEL_MAKE = "-j #" settings in your
> local.conf.
> 
> - armin
> >
> > Assuming the X session is ending is there anything in your
> > ~/.xsession-errors or /var/log/Xorg.*.log?
> >
> > Cheers,
> > Paul
> >
> > On Friday, 24 March 2017 5:58:24 AM NZDT Greg Wilson-Lindberg wrote:
> >> Hi Paul,
> >>
> >> I looked in the logs from the failure yesterday and couldn't find
> >> anything, so I restarted the build and it ran for about another 1000
> >> steps before crashing again. I still can't find anything in any of
> >> the logs, syslog, kern.log, auth.log, etc.
> >>
> >> Cheers,
> >> Greg
> >>
> >>> -----Original Message-----
> >>> From: Paul Eggleton [mailto:paul.eggleton@linux.intel.com]
> >>> Sent: Thursday, March 23, 2017 2:49 AM
> >>> To: Greg Wilson-Lindberg <GWilson@sakuraus.com>
> >>> Cc: yocto@yoctoproject.org; akuster808 <akuster808@gmail.com>
> >>> Subject: Re: [yocto] Morty 2.2.1 build failure
> >>>
> >>> On Thursday, 23 March 2017 9:23:24 AM NZDT Greg Wilson-Lindberg
> wrote:
> >>>> I tried it again this morning and it did get past the file not
> >>>> found error.
> >>>> But when it gets above step 4000 somewhere it gets an error that
> >>>> kills not just the yocto build but the full login session. I'm left
> >>>> staring at the Linux Login screen.
> >>> Your machine isn't running out of RAM by any chance, triggering the
> >>> OOM killer? Anything indicative in your system logs?
> >>>
> >>> Cheers,
> >>> Paul
> >>>
> >>> --
> >>>
> >>> Paul Eggleton
> >>> Intel Open Source Technology Centre
> >

Re: Morty 2.2.1 build failure

[Jussi Kukkonen]

[-- Attachment #1: Type: text/plain, Size: 3734 bytes --]

On 23 March 2017 at 22:11, Greg Wilson-Lindberg <GWilson@sakuraus.com>
wrote:

> Hi Armin & Paul,
>
> First there is nothing in the X log files.
> I'm building on a desktop machine with 12GB of memory and an 8 core
> processor running Kubuntu 14.04.
> I added the PARALLEL_MAKE parameter set to 4, no effect, still built with
> 8 threads, crashed.
> Set BB_NUMBER_THREADS to 4, built with 4 threads, still crashed.
>

Getting thrown out of your desktop environment probably indicates the core
problem is outside of Yocto -- this is still a fine place to discuss the
issue, just pointing it out. You could keep an eye on 'top' sorted by %MEM
while doing a build: my theory here is that something (like the monstrous
amount of IO) that the build does could trigger a desktop component to do
something stupid that cascades into your desktop shell exiting/crashing.
This could show up as something using more and more memory at some point
during the build.

Hope this helps, sorry for lack of definitive answers,
  Jussi



>
> Regards,
> Greg
>
> > -----Original Message-----
> > From: akuster [mailto:akuster@mvista.com]
> > Sent: Thursday, March 23, 2017 12:33 PM
> > To: Greg Wilson-Lindberg <GWilson@sakuraus.com>
> > Cc: Paul Eggleton <paul.eggleton@linux.intel.com>;
> yocto@yoctoproject.org
> > Subject: Re: [yocto] Morty 2.2.1 build failure
> >
> >
> >
> > On 03/23/2017 12:25 PM, Paul Eggleton wrote:
> > > That's really bizarre. There shouldn't be anything in a bitbake build
> > > that could cause anything like this (other than possibly how intensive
> > > it is, which might trigger out-of-memory or an underlying
> > hardware/software failure).
> >
> > I usually get my builds to reboot my system when I build on a loptop. I
> have
> > not seen this on a tower style work station. You may want to play with
> the
> > BB_NUMBER_THREADS=# and PARALLEL_MAKE = "-j #" settings in your
> > local.conf.
> >
> > - armin
> > >
> > > Assuming the X session is ending is there anything in your
> > > ~/.xsession-errors or /var/log/Xorg.*.log?
> > >
> > > Cheers,
> > > Paul
> > >
> > > On Friday, 24 March 2017 5:58:24 AM NZDT Greg Wilson-Lindberg wrote:
> > >> Hi Paul,
> > >>
> > >> I looked in the logs from the failure yesterday and couldn't find
> > >> anything, so I restarted the build and it ran for about another 1000
> > >> steps before crashing again. I still can't find anything in any of
> > >> the logs, syslog, kern.log, auth.log, etc.
> > >>
> > >> Cheers,
> > >> Greg
> > >>
> > >>> -----Original Message-----
> > >>> From: Paul Eggleton [mailto:paul.eggleton@linux.intel.com]
> > >>> Sent: Thursday, March 23, 2017 2:49 AM
> > >>> To: Greg Wilson-Lindberg <GWilson@sakuraus.com>
> > >>> Cc: yocto@yoctoproject.org; akuster808 <akuster808@gmail.com>
> > >>> Subject: Re: [yocto] Morty 2.2.1 build failure
> > >>>
> > >>> On Thursday, 23 March 2017 9:23:24 AM NZDT Greg Wilson-Lindberg
> > wrote:
> > >>>> I tried it again this morning and it did get past the file not
> > >>>> found error.
> > >>>> But when it gets above step 4000 somewhere it gets an error that
> > >>>> kills not just the yocto build but the full login session. I'm left
> > >>>> staring at the Linux Login screen.
> > >>> Your machine isn't running out of RAM by any chance, triggering the
> > >>> OOM killer? Anything indicative in your system logs?
> > >>>
> > >>> Cheers,
> > >>> Paul
> > >>>
> > >>> --
> > >>>
> > >>> Paul Eggleton
> > >>> Intel Open Source Technology Centre
> > >
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>

[-- Attachment #2: Type: text/html, Size: 5527 bytes --]

Re: Morty 2.2.1 build failure

[Dan Riegsecker]

[-- Attachment #1: Type: text/plain, Size: 4799 bytes --]

For whatever it is worth, I am experiencing the same issue. I’m running a Lenovo ThinkStation P910 with two Intel Xeon E5-2630 v4 CPUs and 64 GB of RAM. I’m running Ubuntu 16.04. I also have been unable to find much useful information in the logs, but when running bitbake, lightdm just restarts and I end up at a log in screen with all running programs halted.

Thanks,
Dan
> On Mar 24, 2017, at 4:17 AM, Jussi Kukkonen <jussi.kukkonen@intel.com> wrote:
> 
> On 23 March 2017 at 22:11, Greg Wilson-Lindberg <GWilson@sakuraus.com <mailto:GWilson@sakuraus.com>> wrote:
> Hi Armin & Paul,
> 
> First there is nothing in the X log files.
> I'm building on a desktop machine with 12GB of memory and an 8 core processor running Kubuntu 14.04.
> I added the PARALLEL_MAKE parameter set to 4, no effect, still built with 8 threads, crashed.
> Set BB_NUMBER_THREADS to 4, built with 4 threads, still crashed.
> 
> Getting thrown out of your desktop environment probably indicates the core problem is outside of Yocto -- this is still a fine place to discuss the issue, just pointing it out. You could keep an eye on 'top' sorted by %MEM while doing a build: my theory here is that something (like the monstrous amount of IO) that the build does could trigger a desktop component to do something stupid that cascades into your desktop shell exiting/crashing. This could show up as something using more and more memory at some point during the build.
> 
> Hope this helps, sorry for lack of definitive answers,
>   Jussi
> 
>  
> 
> Regards,
> Greg
> 
> > -----Original Message-----
> > From: akuster [mailto:akuster@mvista.com <mailto:akuster@mvista.com>]
> > Sent: Thursday, March 23, 2017 12:33 PM
> > To: Greg Wilson-Lindberg <GWilson@sakuraus.com <mailto:GWilson@sakuraus.com>>
> > Cc: Paul Eggleton <paul.eggleton@linux.intel.com <mailto:paul.eggleton@linux.intel.com>>; yocto@yoctoproject.org <mailto:yocto@yoctoproject.org>
> > Subject: Re: [yocto] Morty 2.2.1 build failure
> >
> >
> >
> > On 03/23/2017 12:25 PM, Paul Eggleton wrote:
> > > That's really bizarre. There shouldn't be anything in a bitbake build
> > > that could cause anything like this (other than possibly how intensive
> > > it is, which might trigger out-of-memory or an underlying
> > hardware/software failure).
> >
> > I usually get my builds to reboot my system when I build on a loptop. I have
> > not seen this on a tower style work station. You may want to play with the
> > BB_NUMBER_THREADS=# and PARALLEL_MAKE = "-j #" settings in your
> > local.conf.
> >
> > - armin
> > >
> > > Assuming the X session is ending is there anything in your
> > > ~/.xsession-errors or /var/log/Xorg.*.log?
> > >
> > > Cheers,
> > > Paul
> > >
> > > On Friday, 24 March 2017 5:58:24 AM NZDT Greg Wilson-Lindberg wrote:
> > >> Hi Paul,
> > >>
> > >> I looked in the logs from the failure yesterday and couldn't find
> > >> anything, so I restarted the build and it ran for about another 1000
> > >> steps before crashing again. I still can't find anything in any of
> > >> the logs, syslog, kern.log, auth.log, etc.
> > >>
> > >> Cheers,
> > >> Greg
> > >>
> > >>> -----Original Message-----
> > >>> From: Paul Eggleton [mailto:paul.eggleton@linux.intel.com <mailto:paul.eggleton@linux.intel.com>]
> > >>> Sent: Thursday, March 23, 2017 2:49 AM
> > >>> To: Greg Wilson-Lindberg <GWilson@sakuraus.com <mailto:GWilson@sakuraus.com>>
> > >>> Cc: yocto@yoctoproject.org <mailto:yocto@yoctoproject.org>; akuster808 <akuster808@gmail.com <mailto:akuster808@gmail.com>>
> > >>> Subject: Re: [yocto] Morty 2.2.1 build failure
> > >>>
> > >>> On Thursday, 23 March 2017 9:23:24 AM NZDT Greg Wilson-Lindberg
> > wrote:
> > >>>> I tried it again this morning and it did get past the file not
> > >>>> found error.
> > >>>> But when it gets above step 4000 somewhere it gets an error that
> > >>>> kills not just the yocto build but the full login session. I'm left
> > >>>> staring at the Linux Login screen.
> > >>> Your machine isn't running out of RAM by any chance, triggering the
> > >>> OOM killer? Anything indicative in your system logs?
> > >>>
> > >>> Cheers,
> > >>> Paul
> > >>>
> > >>> --
> > >>>
> > >>> Paul Eggleton
> > >>> Intel Open Source Technology Centre
> > >
> 
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org <mailto:yocto@yoctoproject.org>
> https://lists.yoctoproject.org/listinfo/yocto <https://lists.yoctoproject.org/listinfo/yocto>
> 
> -- 
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org <mailto:yocto@yoctoproject.org>
> https://lists.yoctoproject.org/listinfo/yocto <https://lists.yoctoproject.org/listinfo/yocto>

[-- Attachment #2: Type: text/html, Size: 11223 bytes --]