All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Greg Wilson-Lindberg <GWilson@sakuraus.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Morty 2.2.1 build failure
Date: Fri, 24 Mar 2017 08:25:23 +1300	[thread overview]
Message-ID: <13191224.qIYrFqvWFr@peggleto-mobl.ger.corp.intel.com> (raw)
In-Reply-To: <6a6dd70f430b4a7c8f7c925d18814be8@SFA-EX01.SAKURAUS.LOCAL>

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


  reply	other threads:[~2017-03-23 19:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-21 23:29 Morty 2.2.1 build failure Greg Wilson-Lindberg
2017-03-22  2:06 ` akuster808
2017-03-22  9:14   ` Esponde, Joel
2017-03-22 20:23   ` Greg Wilson-Lindberg
2017-03-23  8:25     ` Jussi Kukkonen
2017-03-23  9:49     ` Paul Eggleton
2017-03-23 16:58       ` Greg Wilson-Lindberg
2017-03-23 19:25         ` Paul Eggleton [this message]
2017-03-23 19:33           ` akuster
2017-03-23 20:11             ` Greg Wilson-Lindberg
2017-03-24  8:17               ` Jussi Kukkonen
2017-03-24 13:08                 ` Dan Riegsecker

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=13191224.qIYrFqvWFr@peggleto-mobl.ger.corp.intel.com \
    --to=paul.eggleton@linux.intel.com \
    --cc=GWilson@sakuraus.com \
    --cc=yocto@yoctoproject.org \
    /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.