<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugzilla.yoctoproject.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.6"
          urlbase="https://bugzilla.yoctoproject.org/"
          
          maintainer="it-coreprojects-helpdesk@linuxfoundation.org"
>

    <bug>
          <bug_id>13283</bug_id>
          
          <creation_ts>2019-04-14 15:21:28 +0000</creation_ts>
          <short_desc>Yocto does not update configuration with .cfg file</short_desc>
          <delta_ts>2019-04-17 02:30:57 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>6</classification_id>
          <classification>Yocto Project Subprojects</classification>
          <product>Kernel</product>
          <component>kernel-configuration</component>
          <version>unspecified</version>
          <rep_platform>x86</rep_platform>
          <op_sys>Multiple</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>NOTABUG</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>Undecided</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter>xerofoify</reporter>
          <assigned_to name="Bruce Ashfield">bruce.ashfield</assigned_to>
          <cc>yp.kernel.watcher</cc>
    
    <cc>yp.watcher</cc>
          
          
          <cf_os>---</cf_os>
          <cf_regression_type>---</cf_regression_type>
          
          <cf_docchange>Don&apos;t know</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>83541</commentid>
    <comment_count>0</comment_count>
      <attachid>4476</attachid>
    <who name="">xerofoify</who>
    <bug_when>2019-04-14 15:21:28 +0000</bug_when>
    <thetext>Created attachment 4476
Kernel Configuration file

I was trying to update my kernel compile and build with:
 bitbake -C fetch virtual/kernel

to have no smp. It shows two cores when running in qemu when through I just updated my layer with the attached .cfg file as run with diffconfig after disabling smp in processor settings. This is is on the latest thud release branch. If you need my bbappend file let me know as it&apos;s not attached due it to being the standard example from the Yocto kernel development manual.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>83542</commentid>
    <comment_count>1</comment_count>
    <who name="Bruce Ashfield">bruce.ashfield</who>
    <bug_when>2019-04-15 00:15:22 +0000</bug_when>
    <thetext>This works just fine here. In fact, if it didn&apos;t work, none of the reference kernels would be building and booting at all, meta-virtualization, etc, wouldn&apos;t be able to modify configurations and any number of core elements would be broken.

So unfortunately, yes. We&apos;ll need everything to reproduce this. Your machine, any local.conf settings, your layers, your kernel bbappend. Something that can just be added to a build and reproduce the issue. 

I tried 5 or 6 different layer combos and changed settings, and they all worked here.

(Note: that if some other setting is selecting SMP, you can&apos;t turn it off in a fragment, so that&apos;s why we need the complete set of layers, machine, kernel recipe).</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>83544</commentid>
    <comment_count>2</comment_count>
    <who name="">xerofoify</who>
    <bug_when>2019-04-15 01:41:36 +0000</bug_when>
    <thetext>(In reply to comment #1)
&gt; This works just fine here. In fact, if it didn&apos;t work, none of the reference
&gt; kernels would be building and booting at all, meta-virtualization, etc,
&gt; wouldn&apos;t be able to modify configurations and any number of core elements
&gt; would be broken.
&gt; 
&gt; So unfortunately, yes. We&apos;ll need everything to reproduce this. Your
&gt; machine, any local.conf settings, your layers, your kernel bbappend.
&gt; Something that can just be added to a build and reproduce the issue. 
&gt; 
&gt; I tried 5 or 6 different layer combos and changed settings, and they all
&gt; worked here.
&gt; 
&gt; (Note: that if some other setting is selecting SMP, you can&apos;t turn it off in
&gt; a fragment, so that&apos;s why we need the complete set of layers, machine,
&gt; kernel recipe).

OK its running on qemu with this command:
runqemu qemux86 qemuparams=&quot;-smp 2&quot;

It&apos;s just the default yocto-poky on Ubuntu 18.04. The only things were I added 
a layer with:
bitbake-layers create-layer examples
bitbake-layers add-layer examples

For the bbappend and local.conf those are attached as well.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>83545</commentid>
    <comment_count>3</comment_count>
      <attachid>4477</attachid>
    <who name="">xerofoify</who>
    <bug_when>2019-04-15 01:42:14 +0000</bug_when>
    <thetext>Created attachment 4477
BBappend file for yocto kernel</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>83546</commentid>
    <comment_count>4</comment_count>
      <attachid>4478</attachid>
    <who name="">xerofoify</who>
    <bug_when>2019-04-15 01:42:50 +0000</bug_when>
    <thetext>Created attachment 4478
local.conf</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>83547</commentid>
    <comment_count>5</comment_count>
    <who name="">xerofoify</who>
    <bug_when>2019-04-15 02:16:05 +0000</bug_when>
    <thetext>Sorry the commands I ran were:
bitbake-layers create-layer  ypbook
bitbake-layers add-layer ypbook
cd ypbook/
mkdir -p recipes-kernel/linux
mkdir -p recipes-kernel/linux/files
cd recipes-kernel/

Those other commands were for another layer.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>83553</commentid>
    <comment_count>6</comment_count>
    <who name="Bruce Ashfield">bruce.ashfield</who>
    <bug_when>2019-04-15 14:39:57 +0000</bug_when>
    <thetext>I&apos;ll take this for a spin and see if I can reproduce the issue, or offer an explanation why things are working as expected.

I&apos;ll be testing this on master, so if this is incorrect, update the bug with your branch details.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>83564</commentid>
    <comment_count>7</comment_count>
    <who name="Bruce Ashfield">bruce.ashfield</who>
    <bug_when>2019-04-17 02:30:57 +0000</bug_when>
    <thetext>Is that really the bbappend you are using ? If so, you have a typo and are not adding your fragment to the SRC_URI, you have &quot;SRC_URL&quot;.

I can confirm with that typo fixed, I can definitely override the SMP setting

build2 [/home/bruc...0a3acff-r0]&gt; grep CONFIG_SMP linux-qemux86-standard-build/.config 
# CONFIG_SMP is not set</thetext>
  </long_desc>
      
          <attachment
              isobsolete="0"
              ispatch="0"
              isprivate="0"
          >
            <attachid>4476</attachid>
            <date>2019-04-14 15:21:28 +0000</date>
            <delta_ts>2019-04-14 15:21:28 +0000</delta_ts>
            <desc>Kernel Configuration file</desc>
            <filename>smp.cfg</filename>
            <type>application/octet-stream</type>
            <size>247</size>
            <attacher>xerofoify</attacher>
            
              <data encoding="base64">Q09ORklHX0JST0tFTl9PTl9TTVA9eQojIENPTkZJR19TTVAgaXMgbm90IHNldApDT05GSUdfTlJf
Q1BVU19SQU5HRV9CRUdJTj0xCkNPTkZJR19OUl9DUFVTX1JBTkdFX0VORD0xCkNPTkZJR19OUl9D
UFVTX0RFRkFVTFQ9MQpDT05GSUdfTlJfQ1BVUz0xCkNPTkZJR19VUF9MQVRFX0lOSVQ9eQpDT05G
SUdfWDg2X1VQX0FQSUM9eQojIENPTkZJR19YODZfVVBfSU9BUElDIGlzIG5vdCBzZXQKQ09ORklH
X05FRURfUEVSX0NQVV9LTT15Cg==
</data>

          </attachment>
          <attachment
              isobsolete="0"
              ispatch="0"
              isprivate="0"
          >
            <attachid>4477</attachid>
            <date>2019-04-15 01:42:14 +0000</date>
            <delta_ts>2019-04-15 01:42:14 +0000</delta_ts>
            <desc>BBappend file for yocto kernel</desc>
            <filename>linux-yocto_4.18.bbappend</filename>
            <type>application/octet-stream</type>
            <size>115</size>
            <attacher>xerofoify</attacher>
            
              <data encoding="base64">IyBJbmNsdWRlIGtlcm5lbCBjb25maWd1cmF0aW9uIGZyYWdtZW50CkZJTEVTRVhUUkFQQVRIU19w
cmVwZW5kIDo9ICIke1RISVNESVJ9L2ZpbGVzOiIKU1JDX1VSTCArPSAiZmlsZTovL3NtcC5jZmci
Cg==
</data>

          </attachment>
          <attachment
              isobsolete="0"
              ispatch="0"
              isprivate="0"
          >
            <attachid>4478</attachid>
            <date>2019-04-15 01:42:50 +0000</date>
            <delta_ts>2019-04-15 01:42:50 +0000</delta_ts>
            <desc>local.conf</desc>
            <filename>layer.conf</filename>
            <type>application/octet-stream</type>
            <size>564</size>
            <attacher>xerofoify</attacher>
            
              <data encoding="base64">IyBXZSBoYXZlIGEgY29uZiBhbmQgY2xhc3NlcyBkaXJlY3RvcnksIGFkZCB0byBCQlBBVEgKQkJQ
QVRIID0uICIke0xBWUVSRElSfToiCgojIFdlIGhhdmUgcmVjaXBlcy0qIGRpcmVjdG9yaWVzLCBh
ZGQgdG8gQkJGSUxFUwpCQkZJTEVTICs9ICIke0xBWUVSRElSfS9yZWNpcGVzLSovKi8qLmJiIFwK
ICAgICAgICAgICAgJHtMQVlFUkRJUn0vcmVjaXBlcy0qLyovKi5iYmFwcGVuZCIKCkJCRklMRV9D
T0xMRUNUSU9OUyArPSAieW9jdG8iCkJCRklMRV9QQVRURVJOX3lvY3RvID0gIl4ke0xBWUVSRElS
fS8iCkJCRklMRV9QUklPUklUWV95b2N0byA9ICI1IgoKTEFZRVJTRVJJRVNfQ09NUEFUX3lvY3Rv
ID0gInRodWQiCgojIFRoaXMgc2hvdWxkIG9ubHkgYmUgaW5jcmVtZW50ZWQgb24gc2lnbmlmaWNh
bnQgY2hhbmdlcyB0aGF0IHdpbGwKIyBjYXVzZSBjb21wYXRpYmlsaXR5IGlzc3VlcyB3aXRoIG90
aGVyIGxheWVycwpMQVlFUlZFUlNJT05feW9jdG8gPSAiMyIKCkxBWUVSREVQRU5EU195b2N0byA9
ICJjb3JlIgoKUkVRVUlSRURfUE9LWV9CQkxBWUVSU19DT05GX1ZFUlNJT04gPSAiMiIK
</data>

          </attachment>
      

    </bug>

</bugzilla>