Re: [OE-core] [PATCH] core-image-sato: qemumips use 512 mem

From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>, 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: Tue, 15 Sep 2020 09:58:39 +0100	[thread overview]
Message-ID: <352127433a1b0fae6cc7b8edef1476c307655816.camel@linuxfoundation.org> (raw)
In-Reply-To: <1634C23CFDB6D44F.7642@lists.openembedded.org>

On Mon, 2020-09-14 at 22:02 +0100, Richard Purdie via lists.openembedded.org wrote:
> On Mon, 2020-09-14 at 10:27 -0700, Khem Raj wrote:
> > On 9/14/20 12:13 AM, Richard Purdie wrote:
> > > On Sat, 2020-09-12 at 20:59 -0700, akuster wrote:
> > > > 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
> 
> Shouldn'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