From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail5.wrs.com (mail5.windriver.com [192.103.53.11]) by mail.openembedded.org (Postfix) with ESMTP id 9018F78170 for ; Tue, 22 Aug 2017 14:54:30 +0000 (UTC) Received: from ALA-HCA.corp.ad.wrs.com (ala-hca.corp.ad.wrs.com [147.11.189.40]) by mail5.wrs.com (8.15.2/8.15.2) with ESMTPS id v7MEsUmQ019444 (version=TLSv1 cipher=AES128-SHA bits=128 verify=OK); Tue, 22 Aug 2017 07:54:30 -0700 Received: from [128.224.56.93] (128.224.56.93) by ALA-HCA.corp.ad.wrs.com (147.11.189.50) with Microsoft SMTP Server id 14.3.361.1; Tue, 22 Aug 2017 07:54:29 -0700 To: Richard Purdie References: <1503330934.32591.64.camel@linuxfoundation.org> <74bfd0a2-59a7-c98b-690d-8749ca7a989a@windriver.com> <1503411893.32591.108.camel@linuxfoundation.org> From: Bruce Ashfield Message-ID: <7f1c93bd-0d0d-b4c4-d084-2a75d7362481@windriver.com> Date: Tue, 22 Aug 2017 10:54:29 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <1503411893.32591.108.camel@linuxfoundation.org> Cc: openembedded-core@lists.openembedded.org Subject: Re: [PATCH 0/9] kernel-yocto: consolidated pull request 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: Tue, 22 Aug 2017 14:54:30 -0000 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit On 08/22/2017 10:24 AM, Richard Purdie wrote: > On Mon, 2017-08-21 at 12:12 -0400, Bruce Ashfield wrote: >> On 2017-08-21 11:55 AM, Richard Purdie wrote: >>> >>> On Sun, 2017-08-20 at 22:58 -0400, Bruce Ashfield wrote: >>>> >>>> Here's the collected set of kernel changes that are ready for the >>>> M3 >>>> builds. >>>> >>>> We have some kernel meta data changes: >>>> >>>> kernel-yocto: configuration updates: x86 features >>>> linux-yocto/4.1: fix fsl-ls10xx sdhci >>>> linux-yocto: add usb-net configs by default >>>> >>>> Some bug fixes: >>>> >>>> kernel-yocto: ensure that only valid BSPs are built >>>> linux-yocto/4.10: CVE & misc fixes >>>> >>>> And the important changes are the addition of the 4.12 kernel + >>>> libc headers >>>> and the removal of the 4.1 kernel. >>>> >>>> I also have some -stable updates queued for the active kernel >>>> versions, but >>>> they will come out once this series has made it into the tree, >>>> since I'm >>>> trying to isolate any 4.12 issues from other -stable updates. >>>> >>>> I built and booted all the qemu targets for 4.12, and have built >>>> for >>>> core-image-sato, core-image-kernel-dev, glibc and muslc for all >>>> of the >>>> architectures. My testing didn't pick up any regressions, but I >>>> was battling >>>> some other build errors (non kernel related) during my testing, >>>> so I can >>>> never be 100% sure. >>>> >>>> I've sent patches to poky to remove/bump any references to the >>>> 4.1 kernel >>>> .. if I've missed any, I'm sure people will shout. >>> Thanks for the other fix, not got that tested yet as builds are >>> still >>> ongoing. However there appears to be a perf issue: >>> >>> https://autobuilder.yocto.io/builders/nightly-deb-non-deb/builds/42 >>> 9/steps/BuildImages/logs/stdio >>> https://autobuilder.yocto.io/builders/nightly-packagemanagers/build >>> s/77/steps/BuildImages/logs/stdio >>> https://autobuilder.yocto.io/builders/nightly-packagemanagers/build >>> s/77/steps/BuildImages_1/logs/stdio >>> https://autobuilder.yocto.io/builders/nightly-packagemanagers/build >>> s/77/steps/BuildImages_2/logs/stdio >>> [and so on] >>> >> Aha. There's a difference in the clibrary that I was using. I'll have >> a closer look once my switch over and build gets going. > > Thanks, I think you got that one but the /bin/awk issue remained after > your changes. Its easy to reproduce with "bitbake core-image-sato-sdk", > or IMAGE_INSTALL_append = " kernel-devsrc". I ended up with this change > to fix it: Yah, I noticed all of those references as well. Saul had dealt with the one that hit us before, but I wasn't able to trigger any installs of the other parts in the images I built .. so they were being left be for now, just to keep our footprint low. > > http://git.yoctoproject.org/cgit.cgi/poky/commit/?h=master-next&id=a28acfa6c5890df4f5cb09962ef0c53837ac3b37 > > which I appreciate you won't like but it illustrates the problem. Any > preference on what to do with that patch? I can merge it directly into linux-yocto, since that is what we did with Saul's change before, and at the same time, we can submit it upstream and drop it next release. > > We do also have a boot test issue on mips64: > > https://autobuilder.yocto.io/builders/nightly-mips64/builds/423/steps/Running%20Sanity%20Tests/logs/stdio > > and mips: > > https://autobuilder.yocto.io/builders/nightly-mips/builds/425/steps/Running%20Sanity%20Tests/logs/stdio > > I assume we just have to whitelist that error message? Yep. It is something that has been around for a while and comes from the general open firmware support. It is a warning only (obviously) and can safely be ignored. We keep the OF support on for compatibility so live with a few warnings like that. Bruce > > Cheers, > > Richard >