Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 7579BE00C52; Wed, 14 Nov 2018 07:55:03 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,HTML_MESSAGE autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 0.0 HTML_MESSAGE BODY: HTML included in message X-Greylist: delayed 901 seconds by postgrey-1.32 at yocto-www; Wed, 14 Nov 2018 07:55:00 PST Received: from webmail.dornerworks.com (mail.dornerworks.com [12.207.209.150]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id AF8BFE00C4E for ; Wed, 14 Nov 2018 07:55:00 -0800 (PST) From: Corrin Meyer To: "yocto@yoctoproject.org" Thread-Topic: Inconsistent kernel builds with custom defconfig Thread-Index: AdR8MFSmWoHzi2RzTG+nwmQFmD5Qvw== Date: Wed, 14 Nov 2018 15:38:55 +0000 Message-ID: Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.27.14.41] MIME-Version: 1.0 Subject: Inconsistent kernel builds with custom defconfig X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Nov 2018 15:55:03 -0000 Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_d034352040c54d5bbf7713836410e622dornerworkscom_" --_000_d034352040c54d5bbf7713836410e622dornerworkscom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I am trying to build a Linux kernel with a custom defconfig and am getting = inconsistent builds. On a fresh/new run of "bitbake virtual/kernel" I get = an incorrect kernel (zImage is ~1.1M in size). If I then do a "bitbake -c = cleanall virtual/kernel" and then rerun "bitbake virtual/kernel" I get a go= od kernel (zImage is ~4.6M). I am using Yocto Sumo and standard Poky from = git.yoctoproject.org/poky.git and only my custom kernel recipe and machine = via a custom meta layer. My meta layer can be found at https://gitlab.com/cjmeyer/meta-socfpga and t= he builds I am running target the "arria10" machine. The defconfig I am us= ing in the recipe is generated using "ARCH=3Darm make socfpga_defconfig" wi= th the same Kernel sources being used in the recipe. I then copy the gener= ated ".config" file to my "defconfing" in my kernel recipe. To reproduce the bad zImage after a successful run, I delete all files and = directories from the Yocto build directory except for the "conf" directory.= After doing this, rerunning "bitbake virtual/kernel" results in a bad zIm= age again (~1.1M in size). Comparing the ".config" in the kernel build dir= ectory in my Yocto build directory after a bad zImage is generated shows ma= ny, many differences to the defconfig from the recipe (I used a diff tool t= hat understands kernel config files so it diffed the config, next the text)= . This leads me to believe that the configuration steps in my builds are not = running consistently or correctly but I am not sure why. cmeyer --_000_d034352040c54d5bbf7713836410e622dornerworkscom_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I am trying to build a Linux kernel with a custom de= fconfig and am getting inconsistent builds.  On a fresh/new run of = 220;bitbake virtual/kernel” I get an incorrect kernel (zImage is ~1.1= M in size).  If I then do a “bitbake –c cleanall virtual/k= ernel” and then rerun “bitbake virtual/kernel” I get a good kernel (z= Image is ~4.6M).  I am using Yocto Sumo and standard Poky from git.yoc= toproject.org/poky.git and only my custom kernel recipe and machine via a c= ustom meta layer.

 

My meta layer can be found at https://gitlab.com/cjmeyer/meta-socfpga and the builds I am running tar= get the “arria10” machine.  The defconfig I am using in th= e recipe is generated using “ARCH=3Darm make socfpga_defconfig”= with the same Kernel sources being used in the recipe.  I then copy the generated “.config” file to my “defconfing̶= 1; in my kernel recipe.

 

To reproduce the bad zImage after a successful run, = I delete all files and directories from the Yocto build directory except fo= r the “conf” directory.  After doing this, rerunning ̶= 0;bitbake virtual/kernel” results in a bad zImage again (~1.1M in size).  Comparing the “.config” in the kernel build di= rectory in my Yocto build directory after a bad zImage is generated shows m= any, many differences to the defconfig from the recipe (I used a diff tool = that understands kernel config files so it diffed the config, next the text).

 

This leads me to believe that the configuration step= s in my builds are not running consistently or correctly but I am not sure = why.

 

cmeyer

 

--_000_d034352040c54d5bbf7713836410e622dornerworkscom_--