From: richard.purdie@linuxfoundation.org
To: kai.kang@windriver.com
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] core-image-sato-sdk: test image with 512M memory
Date: Fri, 26 Jul 2019 22:40:06 +0100 [thread overview]
Message-ID: <0c505fd8dd1e01a8ff06eea35144466d3662f67d.camel@linuxfoundation.org> (raw)
In-Reply-To: <20190726092342.37231-1-kai.kang@windriver.com>
On Fri, 2019-07-26 at 05:23 -0400, kai.kang@windriver.com wrote:
> From: Kai Kang <kai.kang@windriver.com>
>
> When run do_testimage for core-image-sato-sdk, it fails to pass test
> case:
>
> > RESULTS - systemd.SystemdBasicTests.test_systemd_failed: FAILED
> > (0.43s)
>
> It is OOM issue and daemon rpc.statd is killed:
>
> > [ 531.306146] Out of memory: Kill process 193 (rpc.statd) score
> > 200 or sacrifice child
>
> Increase the memory of qemu to 512M to avoid such OOM issue.
>
> Signed-off-by: Kai Kang <kai.kang@windriver.com>
> ---
> meta/recipes-sato/images/core-image-sato-sdk.bb | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/meta/recipes-sato/images/core-image-sato-sdk.bb
> b/meta/recipes-sato/images/core-image-sato-sdk.bb
> index d7cc52b52b..f7963d018e 100644
> --- a/meta/recipes-sato/images/core-image-sato-sdk.bb
> +++ b/meta/recipes-sato/images/core-image-sato-sdk.bb
> @@ -9,3 +9,4 @@ IMAGE_FEATURES += "dev-pkgs tools-sdk \
>
> IMAGE_INSTALL += "kernel-devsrc"
>
> +TEST_QEMUPARAMS = "-m 512"
Any idea what is using so much memory in the image when this happens?
Its rather sad that we can't have NFS+systemd with 256MB memory...
Cheers,
Richard
next prev parent reply other threads:[~2019-07-26 21:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 9:23 [PATCH] core-image-sato-sdk: test image with 512M memory kai.kang
2019-07-26 10:11 ` Alexander Kanavin
2019-07-27 1:35 ` Kang Kai
2019-07-27 8:35 ` Alexander Kanavin
2019-07-29 2:11 ` Kang Kai
2019-07-26 21:40 ` richard.purdie [this message]
2019-07-27 8:42 ` Kang Kai
2019-08-12 8:57 ` Kang Kai
2019-08-16 6:53 ` Kang Kai
2019-08-19 9:14 ` ChenQi
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=0c505fd8dd1e01a8ff06eea35144466d3662f67d.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=kai.kang@windriver.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox