All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: akuster <akuster808@gmail.com>, openembedded-core@lists.openembedded.org
Cc: Armin Kuster <akuster808@gmail.comt>,
	Saul Wold <Saul.Wold@windriver.com>
Subject: Re: [OE-core] [PATCH] core-image-sato: qemumips use 512 mem
Date: Sun, 13 Sep 2020 10:29:23 +0100	[thread overview]
Message-ID: <3abd8ce10108bb679cd8623df05adc104ee76a98.camel@linuxfoundation.org> (raw)
In-Reply-To: <20200913035916.24165-1-akuster808@gmail.com>

On Sat, 2020-09-12 at 20:59 -0700, akuster wrote:
> From: Armin Kuster <akuster808@gmail.comt>
> 
> Fixes:
> 
> WARNING: core-image-sato-sdk-1.0-r0 do_testimage: Couldn't login into
> serial console as root using blank password
> WARNING: core-image-sato-sdk-1.0-r0 do_testimage: The output:
> root
> <<< run_serial(): command timed out after 60 seconds without output
> >>>

I must admit I was sceptical but I reran my timing tests and this does
appear to significantly reduce the amount of time the serial login
takes for sato-sdk so you are probably right in claiming that.

Its a pretty bad 'advert' for systemd though :(.

> In another run, this error was seen:
> 
> Failed to reload daemon: Refusing to reload, not enough space
> available on /run/systemd. Currently, 14.3M are free, but a safety
> buffer of 16.0M is enforced.
> 
> With updates to systemd and Qemu we should revert: 499a31cf06 core-
> image-sato: don't use 512MB in qemumips

The original hard qemu hangs for qemumips were a real pain to debug so
I remain worried we're going to swap one set of problems for another :(

Cheers,

Richard


  parent reply	other threads:[~2020-09-13  9:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-13  3:59 [PATCH] core-image-sato: qemumips use 512 mem akuster
2020-09-13  4:52 ` [OE-core] " Khem Raj
2020-09-13  9:29 ` Richard Purdie [this message]
2020-09-14  7:13 ` Richard Purdie
2020-09-14 17:27   ` Khem Raj
2020-09-14 21:02     ` Richard Purdie
     [not found]     ` <1634C23CFDB6D44F.7642@lists.openembedded.org>
2020-09-15  8:58       ` Richard Purdie

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=3abd8ce10108bb679cd8623df05adc104ee76a98.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=Saul.Wold@windriver.com \
    --cc=akuster808@gmail.com \
    --cc=akuster808@gmail.comt \
    --cc=openembedded-core@lists.openembedded.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.