public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/6] linux-yocto/4.1: bump to v4.1.29
Date: Thu, 18 Aug 2016 16:20:45 +0100	[thread overview]
Message-ID: <1471533645.16712.13.camel@linuxfoundation.org> (raw)
In-Reply-To: <19315d97-49eb-da07-d137-c28d51b3e7d0@windriver.com>

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@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




  reply	other threads:[~2016-08-18 15:20 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-15 18:26 [PATCH 0/6] kernel-yocto: consolidated pull request Bruce Ashfield
2016-08-15 18:26 ` [PATCH 1/6] linux-yocto/4.1: netfilter: x_tables: fix stable backport Bruce Ashfield
2016-08-15 18:26 ` [PATCH 2/6] linux-yocto/4.1: bump to v4.1.29 Bruce Ashfield
2016-08-18 15:15   ` Richard Purdie
2016-08-18 15:16     ` Bruce Ashfield
2016-08-18 15:20       ` Richard Purdie [this message]
2016-08-19 14:57         ` Bruce Ashfield
2016-08-24 11:25           ` Richard Purdie
2016-08-24 13:14             ` Bruce Ashfield
2016-08-15 18:26 ` [PATCH 3/6] linux-yocto/4.1: config updates Bruce Ashfield
2016-08-15 18:26 ` [PATCH 4/6] linux-yocto/4.4: -rt update patch meta-data to remove () Bruce Ashfield
2016-08-15 18:26 ` [PATCH 5/6] kernel-yocto: streamline patch, configuration and audit phases Bruce Ashfield
2016-08-30  9:05   ` André Draszik
2016-08-30 13:05     ` Bruce Ashfield
2016-08-30 14:19       ` André Draszik
2016-08-30 18:35         ` Bruce Ashfield
2016-08-31  8:54           ` André Draszik
2016-08-31 20:17             ` Bruce Ashfield
2016-09-01 16:14               ` André Draszik
2016-09-01 20:21                 ` Bruce Ashfield
2016-09-02  3:18                 ` Bruce Ashfield
2016-09-02  4:37                   ` Bruce Ashfield
2016-08-15 18:27 ` [PATCH 6/6] yocto-bsp/yocto-kernel: update to work with the latest kern-tools Bruce Ashfield
2016-08-16 16:00 ` [PATCH 0/6] kernel-yocto: consolidated pull request Burton, Ross
2016-08-16 16:01   ` Bruce Ashfield
2016-08-16 16:10     ` Burton, Ross
2016-08-16 16:11       ` Bruce Ashfield
2016-08-16 16:15         ` Burton, Ross

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1471533645.16712.13.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bruce.ashfield@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox