Re: Summary of M3 status

[richard.purdie@linuxfoundation.org]

On Tue, 2019-09-03 at 19:59 -0700, akuster808 wrote:
> 
> On 9/3/19 5:39 AM, Bruce Ashfield wrote:
> > On Tue, Sep 3, 2019 at 4:10 AM Richard Purdie
> > <richard.purdie@linuxfoundation.org> wrote:
> > > I'm going to summarise the current state as it will help people
> > > see the
> > > set of issues we have. We have three issues blocking the current
> > > patch
> > > queue and kernel uprev, spread over four machines and five
> > > autobuilder
> > > targets:
> > > 
> > > qemumips64:
> > > 
> > >   
> > > https://autobuilder.yoctoproject.org/typhoon/#/builders/74/builds/987
> > > 
> > >   RESULTS - parselogs.ParseLogsTest.test_parselogs: FAILED
> > > (1.97s)
> > > 
> > >   Central error: [    1.689184] kprobes: failed to populate
> > > blacklist: -22
> > >   [happens 5.2 kernel only]
> > I'll have a look at the kprobes log. Could just be something we
> > need
> > to whitelist, but I'll root cause it.
> > 
> > > qemumips:
> > > 
> > >   qemu machine locks up:
> > > 
> > >   
> > > https://autobuilder.yoctoproject.org/typhoon/#/builders/60/builds/982
> > > 
> > >   (happens with 5.0 and 5.2 kernels and qemu 4.0 and 4.1 and is
> > > in
> > >    master. Not sure of the original cause)
> > > 
> > > qemuarm64:
> > > 
> > >   Central error: [    1.816386] kprobes: failed to populate
> > > blacklist: -22
> > > 
> > >   RESULTS - parselogs.ParseLogsTest.test_parselogs: FAILED
> > > (1.11s)
> > > 
> > >   
> > > https://autobuilder.yoctoproject.org/typhoon/#/builders/97/builds/329
> > >   
> > > https://autobuilder.yoctoproject.org/typhoon/#/builders/42/builds/985
> > >   [happens 5.2 kernel only]
> > > 
> > > qemuarm:
> > > 
> > >   
> > > https://autobuilder.yoctoproject.org/typhoon/#/builders/38/builds/990
> > >   
> > > https://autobuilder.yoctoproject.org/typhoon/#/builders/53/builds/989
> > > 
> > >   See compile failure for stap.StapTest.test_stap below.
> > >   [happens 5.2 kernel only]
> > And I can look at this one as well.
> > 
> > If anyone gets to them first, let me know!
> 
> There is a patch under test in master-next. I just noticed it. Guess
> it
> means some got to it before either of us.

It means we had autobuilder time so I tried the obvious fix. It didn't
help and the problem remains, help very much appreciated.

Cheers,

Richard