From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dan.rpsys.net (5751f4a1.skybroadband.com [87.81.244.161]) by mail.openembedded.org (Postfix) with ESMTP id A8850731C6 for ; Wed, 24 Aug 2016 11:25:56 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by dan.rpsys.net (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id u7OBPtkA008443; Wed, 24 Aug 2016 12:25:55 +0100 Received: from dan.rpsys.net ([127.0.0.1]) by localhost (dan.rpsys.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id PoSMhp90f7Lz; Wed, 24 Aug 2016 12:25:55 +0100 (BST) Received: from hex ([192.168.3.34]) (authenticated bits=0) by dan.rpsys.net (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id u7OBPq95008438 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT); Wed, 24 Aug 2016 12:25:54 +0100 Message-ID: <1472037952.16712.129.camel@linuxfoundation.org> From: Richard Purdie To: Bruce Ashfield Date: Wed, 24 Aug 2016 12:25:52 +0100 In-Reply-To: <4baf8dd3-5bb8-aef8-a339-0aad7224329a@windriver.com> References: <1471533301.16712.11.camel@linuxfoundation.org> <19315d97-49eb-da07-d137-c28d51b3e7d0@windriver.com> <1471533645.16712.13.camel@linuxfoundation.org> <4baf8dd3-5bb8-aef8-a339-0aad7224329a@windriver.com> X-Mailer: Evolution 3.16.5-1ubuntu3.1 Mime-Version: 1.0 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: Wed, 24 Aug 2016 11:25:57 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit On Fri, 2016-08-19 at 10:57 -0400, Bruce Ashfield wrote: > On 2016-08-18 11:20 AM, Richard Purdie wrote: > > 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 > > > > > --- > > > > > 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-l > > sb/builds/911/steps/Running%20Sanity%20Tests/logs/stdio > > > > fixed with: > > > > http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=26b0657b2f7875 > > 1e60df6e695d5bc0dd703a5bc2 > > I had a look at this, and I don't have a root cause for why this is > just popping up now. I'm trying to track down an older build, so I > can > compare the .configs. > > The kernel code, and Kconfig files themselves haven't changed in some > time, and the symbol in question AMD_NB is default 'y' if the > dependencies are met. We include cfg/amd.scc in all of the qemux86* > builds, so it gets enabled (as it should have before). > > I could force that option off, but the whitelist is an appropriate > fix, > since this is an interaction between qemu and the kernel, whereas the > files that include amd.scc are targeted at a range of platforms. > > > > > The ppc issue is a separate one. > > I've been blasting away on my 4.1.30 qemuppc build, and I'm not > seeing > anything yet, but I will keep trying. Its still going on even with the recent updates: https://autobuilder.yoctoproject.org/main/builders/nightly-ppc-lsb/builds/889/steps/Running%20Sanity%20Tests/logs/stdio Seems the network works intermittently, dropping connections... Cheers, Richard