From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.windriver.com (mail.windriver.com [147.11.1.11]) by mail.openembedded.org (Postfix) with ESMTP id C959F766E1 for ; Thu, 18 Aug 2016 15:16:54 +0000 (UTC) Received: from ALA-HCA.corp.ad.wrs.com (ala-hca.corp.ad.wrs.com [147.11.189.40]) by mail.windriver.com (8.15.2/8.15.1) with ESMTPS id u7IFGqJF011161 (version=TLSv1 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 18 Aug 2016 08:16:52 -0700 (PDT) Received: from [128.224.56.48] (128.224.56.48) by ALA-HCA.corp.ad.wrs.com (147.11.189.50) with Microsoft SMTP Server id 14.3.248.2; Thu, 18 Aug 2016 08:16:51 -0700 To: Richard Purdie References: <1471533301.16712.11.camel@linuxfoundation.org> From: Bruce Ashfield Message-ID: <19315d97-49eb-da07-d137-c28d51b3e7d0@windriver.com> Date: Thu, 18 Aug 2016 11:16:51 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <1471533301.16712.11.camel@linuxfoundation.org> Cc: openembedded-core@lists.openembedded.org Subject: Re: [PATCH 2/6] linux-yocto/4.1: bump to v4.1.29 X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Aug 2016 15:16:54 -0000 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit 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 >> --- >> 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. Bruce > > Cheers, > > Richard >