[yocto] Morty 2.2.1 build failure

Paul Eggleton paul.eggleton at linux.intel.com
Thu Mar 23 12:25:23 PDT 2017


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 at linux.intel.com]
> > Sent: Thursday, March 23, 2017 2:49 AM
> > To: Greg Wilson-Lindberg <GWilson at sakuraus.com>
> > Cc: yocto at yoctoproject.org; akuster808 <akuster808 at 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



More information about the yocto mailing list