core-image-sato: qemumips use 512 mem
PATCH 1/1 core-image-sato: qemumips use 512 mem
From: Armin Kuster <[email protected]>
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
--- meta/recipes-sato/images/core-image-sato.bb | 1 - 1 file changed, 1 deletion(-)
meta/recipes-sato/images/core-image-sato.bb +0 -1
@@ -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"
Signature · 1 line
2.17.1
Quoted 25 lines · akuster
From: Armin Kuster <[email protected]>
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-r0do_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:
499a31cf06core-image-sato: don't use 512MB in qemumipsSigned-off-by Armin Kuster <[email protected]>--- meta/recipes-sato/images/core-image-sato.bb | 1 - 1 file changed, 1 deletion(-)meta/recipes-sato/images/core-image-sato.bb +0
-0
meta/recipes-sato/images/core-image-sato.bb TOOLCHAIN_HOST_TASK_append = " nativesdk-intltool nativesdk-glib-2.0" · line 15
Quoted 4 lines
meta/recipes-sato/images/core-image-sato.bb +0
-1@@ -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"
Incidently, I was testing similar patch, which essentially is a revert of [1], I think we have to ensure that these issues seen by Ross a year ago are hopefully gone with time
[1] https://git.openembedded.org/openembedded-core/commit/?id=499a31cf06c934b40b5866d5eb77c9ad20c9a15f
Quoted 4 lines
Quoted 10 lines · akuster
From: Armin Kuster <[email protected]>
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-r0do_testimage: The output:
root
<<<run_serial(): command timed out after 60 seconds without outputQuoted 1 line
Quoted 1 line
Quoted 1 line
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 :(.
Quoted 8 lines
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:
499a31cf06core-
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
Quoted 35 lines · akuster
From: Armin Kuster <[email protected]>
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-r0do_testimage: The output:
root
<<<run_serial(): command timed out after 60 seconds without outputQuoted 1 line
Quoted 1 line
Quoted 1 line
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:
499a31cf06core-
image-sato: don't use 512MB in qemumipsSigned-off-by Armin Kuster <[email protected]>--- meta/recipes-sato/images/core-image-sato.bb | 1 - 1 file changed, 1 deletion(-)meta/recipes-sato/images/core-image-sato.bb +0
-0@@ -12,4 +12,3 @@ TOOLCHAIN_HOST_TASK_append = " nativesdk-intltoolnativesdk-glib-2.0"
TOOLCHAIN_HOST_TASK_remove_task-populate-sdk-ext = " nativesdk-
intltool nativesdk-glib-2.0"
Quoted 3 lines
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.
Cheers,
Richard
Quoted 43 lines · Richard Purdie
Quoted 35 lines · akuster
From: Armin Kuster <[email protected]>
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-r0do_testimage: The output:
root
<<<run_serial(): command timed out after 60 seconds without outputQuoted 1 line
Quoted 1 line
Quoted 1 line
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:
499a31cf06core-
image-sato: don't use 512MB in qemumipsSigned-off-by Armin Kuster <[email protected]>--- meta/recipes-sato/images/core-image-sato.bb | 1 - 1 file changed, 1 deletion(-)meta/recipes-sato/images/core-image-sato.bb +0
-0@@ -12,4 +12,3 @@ TOOLCHAIN_HOST_TASK_append = " nativesdk-intltoolnativesdk-glib-2.0"
TOOLCHAIN_HOST_TASK_remove_task-populate-sdk-ext = " nativesdk-
intltool nativesdk-glib-2.0"Quoted 3 lines
QB_MEM= '${@bb.utils.contains("DISTRO_FEATURES", "opengl", "-m
512", "-m 256", d)}'
-QB_MEM_qemumips = "-m 256"We have now seen:
Quoted 6 lines
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
Quoted 7 lines
Cheers,
Richard
Quoted 57 lines · Khem Raj
Quoted 46 lines · Richard Purdie
Quoted 39 lines · akuster
From: Armin Kuster <[email protected]>
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-r0do_testimage: The output:
root
<<<run_serial(): command timed out after 60 seconds without outputIn 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:
499a31cf06core-
image-sato: don't use 512MB in qemumipsSigned-off-by Armin Kuster <[email protected]>--- meta/recipes-sato/images/core-image-sato.bb | 1 - 1 file changed, 1 deletion(-)meta/recipes-sato/images/core-image-sato.bb +0
-0@@ -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"Quoted 3 lines
QB_MEM= '${@bb.utils.contains("DISTRO_FEATURES", "opengl", "-m
512", "-m 256", d)}'
-QB_MEM_qemumips = "-m 256"We have now seen:
Quoted 8 lines
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.
Quoted 4 lines
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
Shouldn't be using -j for these tests. I think we need better debugging using the serial console when these failures occur...
Cheers,
Richard
Quoted 29 lines · Richard Purdie via lists.openembedded.org
Quoted 28 lines · Khem Raj
Quoted 26 lines · Richard Purdie
Quoted 11 lines · akuster
meta/recipes-sato/images/core-image-sato.bb +0
-0@@ -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"Quoted 3 lines
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.
Quoted 7 lines
Quoted 4 lines
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 compilesShouldn't be using -j for these tests. I think we need better debugging using the serial console when these failures occur...
We now also have:
https://autobuilder.yoctoproject.org/typhoon/#/builders/60/builds/2460
which is hanging in a dnf command.
From the autobuilder, I couldn't ssh into the image, it hangs but tantalisingly, it would show me the time of the last login. I was therefore able to run dmesg and confirm there is nothing in the logs relating to this hang. I can't get a shell (bash or ash), top won't run. Not sure what else to try but I am pretty sure this is our 512MB memory bug, its still there. I'll leave it running for now in case anyone has better ideas about debugging.
Cheers,
Richard