[OE-core] [PATCH 2/6] linux-yocto/4.1: bump to v4.1.29

Richard Purdie richard.purdie at linuxfoundation.org
Thu Aug 18 15:20:45 UTC 2016


On Thu, 2016-08-18 at 11:16 -0400, Bruce Ashfield wrote:
> On 2016-08-18 11:15 AM, Richard Purdie wrote:
> > On Mon, 2016-08-15 at 14:26 -0400, Bruce Ashfield wrote:
> > > Integrating the korg 4.1.29 -stable release
> > > 
> > > Signed-off-by: Bruce Ashfield <bruce at zedd.org>
> > > ---
> > >  meta/recipes-kernel/linux/linux-yocto-rt_4.1.bb   |  6 +++---
> > >  meta/recipes-kernel/linux/linux-yocto-tiny_4.1.bb |  6 +++---
> > >  meta/recipes-kernel/linux/linux-yocto_4.1.bb      | 20
> > > ++++++++++---
> > > -------
> > >  3 files changed, 16 insertions(+), 16 deletions(-)
> > 
> > FWIW since the update before this one, we've seen a lot of
> > instability
> > in ppc:
> > 
> > https://autobuilder.yoctoproject.org/main/builders/nightly-ppc-lsb/
> > builds/881/steps/Running%20Sanity%20Tests/logs/stdio
> > 
> > basically the network seems very flaky. Doesn't happen every time
> > but
> > we are seeing a rising number of these kinds of 'random' failures.
> > Are
> > there any ppc changes or fixes which look like they're responsible,
> > I'm
> > pretty sure its something 4.1 kernel related...
> > 
> > The update also triggered a new 'error' for amd_nb in the error log
> > parsing which I just whitelisted, probably from some change in the
> > configuration options enabled.
> 
> I have a 4.1.30 update queued locally, and I'll double check to see
> what may have changed in the configuration that could explain any
> new warnings or instability.

Just to be clear, the amb_nd change was on qemux86* on 4.1

https://autobuilder.yoctoproject.org/main/builders/nightly-x86-64-lsb/builds/911/steps/Running%20Sanity%20Tests/logs/stdio

fixed with:

http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=26b0657b2f78751e60df6e695d5bc0dd703a5bc2

The ppc issue is a separate one.

Cheers,

Richard





More information about the Openembedded-core mailing list