<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Aug 24, 2016 at 7:25 AM, Richard Purdie <span dir="ltr"><<a href="mailto:richard.purdie@linuxfoundation.org" target="_blank">richard.purdie@linuxfoundation.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Fri, 2016-08-19 at 10:57 -0400, Bruce Ashfield wrote:<br>
> On 2016-08-18 11:20 AM, Richard Purdie wrote:<br>
> > On Thu, 2016-08-18 at 11:16 -0400, Bruce Ashfield wrote:<br>
> > > On 2016-08-18 11:15 AM, Richard Purdie wrote:<br>
> > > > On Mon, 2016-08-15 at 14:26 -0400, Bruce Ashfield wrote:<br>
> > > > > Integrating the korg 4.1.29 -stable release<br>
> > > > ><br>
> > > > > Signed-off-by: Bruce Ashfield <<a href="mailto:bruce@zedd.org">bruce@zedd.org</a>><br>
> > > > > ---<br>
> > > > > meta/recipes-kernel/linux/<a href="http://linux-yocto-rt_4.1.bb" rel="noreferrer" target="_blank">linu<wbr>x-yocto-rt_4.1.bb</a> | 6 +++--<br>
> > > > > -<br>
> > > > > meta/recipes-kernel/linux/<a href="http://linux-yocto-tiny_4.1.bb" rel="noreferrer" target="_blank">linu<wbr>x-yocto-tiny_4.1.bb</a> | 6 +++--<br>
> > > > > -<br>
> > > > > meta/recipes-kernel/linux/<a href="http://linux-yocto_4.1.bb" rel="noreferrer" target="_blank">linu<wbr>x-yocto_4.1.bb</a> | 20<br>
> > > > > ++++++++++---<br>
> > > > > -------<br>
> > > > > 3 files changed, 16 insertions(+), 16 deletions(-)<br>
> > > ><br>
> > > > FWIW since the update before this one, we've seen a lot of<br>
> > > > instability<br>
> > > > in ppc:<br>
> > > ><br>
> > > > <a href="https://autobuilder.yoctoproject.org/main/builders/nightly-ppc-" rel="noreferrer" target="_blank">https://autobuilder.<wbr>yoctoproject.org/main/<wbr>builders/nightly-ppc-</a><br>
> > > > lsb/<br>
> > > > builds/881/steps/Running%<wbr>20Sanity%20Tests/logs/stdio<br>
> > > ><br>
> > > > basically the network seems very flaky. Doesn't happen every<br>
> > > > time<br>
> > > > but<br>
> > > > we are seeing a rising number of these kinds of 'random'<br>
> > > > failures.<br>
> > > > Are<br>
> > > > there any ppc changes or fixes which look like they're<br>
> > > > responsible,<br>
> > > > I'm<br>
> > > > pretty sure its something 4.1 kernel related...<br>
> > > ><br>
> > > > The update also triggered a new 'error' for amd_nb in the error<br>
> > > > log<br>
> > > > parsing which I just whitelisted, probably from some change in<br>
> > > > the<br>
> > > > configuration options enabled.<br>
> > ><br>
> > > I have a 4.1.30 update queued locally, and I'll double check to<br>
> > > see<br>
> > > what may have changed in the configuration that could explain any<br>
> > > new warnings or instability.<br>
> ><br>
> > Just to be clear, the amb_nd change was on qemux86* on 4.1<br>
> ><br>
> > <a href="https://autobuilder.yoctoproject.org/main/builders/nightly-x86-64-l" rel="noreferrer" target="_blank">https://autobuilder.<wbr>yoctoproject.org/main/<wbr>builders/nightly-x86-64-l</a><br>
> > sb/builds/911/steps/Running%<wbr>20Sanity%20Tests/logs/stdio<br>
> ><br>
> > fixed with:<br>
> ><br>
> > <a href="http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=26b0657b2f7875" rel="noreferrer" target="_blank">http://git.yoctoproject.org/<wbr>cgit.cgi/poky/commit/?id=<wbr>26b0657b2f7875</a><br>
> > 1e60df6e695d5bc0dd703a5bc2<br>
><br>
> I had a look at this, and I don't have a root cause for why this is<br>
> just popping up now. I'm trying to track down an older build, so I<br>
> can<br>
> compare the .configs.<br>
><br>
> The kernel code, and Kconfig files themselves haven't changed in some<br>
> time, and the symbol in question AMD_NB is default 'y' if the<br>
> dependencies are met. We include cfg/amd.scc in all of the qemux86*<br>
> builds, so it gets enabled (as it should have before).<br>
><br>
> I could force that option off, but the whitelist is an appropriate<br>
> fix,<br>
> since this is an interaction between qemu and the kernel, whereas the<br>
> files that include amd.scc are targeted at a range of platforms.<br>
><br>
> ><br>
> > The ppc issue is a separate one.<br>
><br>
> I've been blasting away on my 4.1.30 qemuppc build, and I'm not<br>
> seeing<br>
> anything yet, but I will keep trying.<br>
<br>
</div></div>Its still going on even with the recent updates:<br>
<br>
<a href="https://autobuilder.yoctoproject.org/main/builders/nightly-ppc-lsb/builds/889/steps/Running%20Sanity%20Tests/logs/stdio" rel="noreferrer" target="_blank">https://autobuilder.<wbr>yoctoproject.org/main/<wbr>builders/nightly-ppc-lsb/<wbr>builds/889/steps/Running%<wbr>20Sanity%20Tests/logs/stdio</a><br>
<br>
Seems the network works intermittently, dropping connections...<br></blockquote><div><br></div><div>Hmm.<br><br></div><div>I've had a qemuppc up and running for 3 days now, doing transfers of files from my server, and yet my network hasn't dropped.<br></div><div>I'll continue trying to figure this out.<br><br></div><div>Bruce<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5"><br>
Cheers,<br>
<br>
Richard<br>
--<br>
______________________________<wbr>_________________<br>
Openembedded-core mailing list<br>
<a href="mailto:Openembedded-core@lists.openembedded.org">Openembedded-core@lists.<wbr>openembedded.org</a><br>
<a href="http://lists.openembedded.org/mailman/listinfo/openembedded-core" rel="noreferrer" target="_blank">http://lists.openembedded.org/<wbr>mailman/listinfo/openembedded-<wbr>core</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">"Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"</div>
</div></div>