From: "Khem Raj" <raj.khem@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
akuster <akuster808@gmail.com>,
openembedded-core@lists.openembedded.org
Cc: Armin Kuster <akuster808@gmail.comt>
Subject: Re: [OE-core] [PATCH] core-image-sato: qemumips use 512 mem
Date: Mon, 14 Sep 2020 10:27:22 -0700 [thread overview]
Message-ID: <3889316c-3fb2-e100-468d-9ba2b77e69ad@gmail.com> (raw)
In-Reply-To: <82df031010def40bb2f2f1bfe160cbbb8330353d.camel@linuxfoundation.org>
On 9/14/20 12:13 AM, Richard Purdie wrote:
> 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
>>>>>
>>
>> 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
>>
>> Signed-off-by: Armin Kuster <akuster808@gmail.com>
>> ---
>> meta/recipes-sato/images/core-image-sato.bb | 1 -
>> 1 file changed, 1 deletion(-)
>>
>> diff --git a/meta/recipes-sato/images/core-image-sato.bb
>> b/meta/recipes-sato/images/core-image-sato.bb
>> index 673106eb6d..878e0eaa8d 100644
>> --- a/meta/recipes-sato/images/core-image-sato.bb
>> +++ b/meta/recipes-sato/images/core-image-sato.bb
>> @@ -12,4 +12,3 @@ TOOLCHAIN_HOST_TASK_append = " nativesdk-intltool
>> nativesdk-glib-2.0"
>> TOOLCHAIN_HOST_TASK_remove_task-populate-sdk-ext = " nativesdk-
>> intltool nativesdk-glib-2.0"
>>
>> QB_MEM = '${@bb.utils.contains("DISTRO_FEATURES", "opengl", "-m
>> 512", "-m 256", d)}'
>> -QB_MEM_qemumips = "-m 256"
>
>
> We have now seen:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/60/builds/2452
>
> with this applied, not sure if its related. We have seen this kind of
> network dropout elsewhere but we don't seem to have good debug when it
> happens.
>
I wonder if ssh daemon is dead in this case. I also see its invoking
compilers on target( kernelmodule case), are they usign -jX during make
?, 512M might not be enough to run parallel compiles
> Cheers,
>
> Richard
>
>
>
>
next prev parent reply other threads:[~2020-09-14 17:27 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
2020-09-14 7:13 ` Richard Purdie
2020-09-14 17:27 ` Khem Raj [this message]
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=3889316c-3fb2-e100-468d-9ba2b77e69ad@gmail.com \
--to=raj.khem@gmail.com \
--cc=akuster808@gmail.com \
--cc=akuster808@gmail.comt \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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