From: Kang Kai <Kai.Kang@windriver.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] core-image-sato-sdk: test image with 512M memory
Date: Sat, 27 Jul 2019 09:35:13 +0800 [thread overview]
Message-ID: <ee2018da-9448-97ba-b34e-c490164492bb@windriver.com> (raw)
In-Reply-To: <CANNYZj8Jm7q5NfUjHVuDJGaJHC51txQ-iMWZP7YC4-nWkRstdg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2272 bytes --]
On 2019/7/26 下午6:11, Alexander Kanavin wrote:
> I think you need to use QB_MEM here.
Used TEST_QEMUPARAMS because I found the following line in
testimage.bbclass:
# TEST_QEMUPARAMS can be used to pass extra parameters to qemu, e.g. "-m
1024" for setting the amount o f ram to 1 GB.
And it seems QB_MEM is not used when boot the qemu during testimage.
>
> Also, maybe we should just bump the 256M default?
I hope so.
Regards,
Kai
>
> Alex
>
> On Fri, 26 Jul 2019 at 12:24, <kai.kang@windriver.com
> <mailto:kai.kang@windriver.com>> wrote:
>
> From: Kai Kang <kai.kang@windriver.com
> <mailto: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
> <mailto:kai.kang@windriver.com>>
> ---
> meta/recipes-sato/images/core-image-sato-sdk.bb
> <http://core-image-sato-sdk.bb> | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/meta/recipes-sato/images/core-image-sato-sdk.bb
> <http://core-image-sato-sdk.bb>
> b/meta/recipes-sato/images/core-image-sato-sdk.bb
> <http://core-image-sato-sdk.bb>
> index d7cc52b52b..f7963d018e 100644
> --- a/meta/recipes-sato/images/core-image-sato-sdk.bb
> <http://core-image-sato-sdk.bb>
> +++ b/meta/recipes-sato/images/core-image-sato-sdk.bb
> <http://core-image-sato-sdk.bb>
> @@ -9,3 +9,4 @@ IMAGE_FEATURES += "dev-pkgs tools-sdk \
>
> IMAGE_INSTALL += "kernel-devsrc"
>
> +TEST_QEMUPARAMS = "-m 512"
> --
> 2.20.0
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> <mailto:Openembedded-core@lists.openembedded.org>
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
--
Kai Kang
[-- Attachment #2: Type: text/html, Size: 4921 bytes --]
next prev parent reply other threads:[~2019-07-27 1:36 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 [this message]
2019-07-27 8:35 ` Alexander Kanavin
2019-07-29 2:11 ` Kang Kai
2019-07-26 21:40 ` richard.purdie
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=ee2018da-9448-97ba-b34e-c490164492bb@windriver.com \
--to=kai.kang@windriver.com \
--cc=alex.kanavin@gmail.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;
as well as URLs for NNTP newsgroup(s).