[PATCH 0/9] kernel-yocto: consolidated pull request

[PATCH 0/9] kernel-yocto: consolidated pull request

[bruce.ashfield]

From: Bruce Ashfield <bruce.ashfield@gmail.com>

Hi all,

I've kept the v5.4 content changes, as well as the kernel version default
changes out of this series and instead focused it on the collection of
kernel-yocto and kern-tools tweaks that I've gethered over the past few
weeks.

I have Martin's gold linker fixes included, as well as the re-org'ing of
the linux-yocto tasks that Paul Barker did to make it usable as a single
inherit of the bbclass.

I also have a defconfig detection fix included that was sent to the list.

I was able to confirm that my configuration was the same with this series
enabled, and I was able to boot.

That being said, I'll keep my eye out for any AB fallout and will continue
some more build locally .. but I wanted to get this out today as promised.

Cheers,

Bruce

The following changes since commit 3c6978c8db59f152693f9fae65dbab13ecfcaad4:

  kernel-yocto.bbclass: export LD in the environment used by kconf_check (2020-02-04 15:56:29 +0000)

are available in the Git repository at:

  git://git.pokylinux.org/poky-contrib zedd/kernel
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel

Bruce Ashfield (2):
  kern-tools: tweak symbol_why to be python safe
  kern-tools: integrate merge_config fix for gold linker

Gavin Li (1):
  kernel-yocto: fix defconfig detection in find_sccs()

Martin Jansa (3):
  kern-tools-native: use more common S value and oe_runmake
  kernel-yocto.bbclass: set KERNEL_LD also for merge_config.sh
  kernel-yocto.bbclass: do_kernel_configme: don't use +errexit,
    merge_config_build.log and fail when /.config wasn't created

Paul Barker (3):
  kernel-yocto: Move defaults and tasks from linux-yocto.inc into
    bbclass
  kernel-yocto: Drop setting of unused variables in do_kernel_metadata
  kernel-yocto: Only override CONFIG_LOCALVERSION if
    LINUX_VERSION_EXTENSION is set

 meta/classes/kernel-yocto.bbclass             | 43 +++++++++++++------
 .../kern-tools/kern-tools-native_git.bb       | 13 +++---
 meta/recipes-kernel/linux/linux-yocto.inc     | 21 ---------
 3 files changed, 37 insertions(+), 40 deletions(-)

-- 
2.19.1

[PATCH 1/9] kern-tools: tweak symbol_why to be python safe

[bruce.ashfield]

From: Bruce Ashfield <bruce.ashfield@gmail.com>

Updating the SRCREV to pickup tweaks to symbol_why.py to be
python3 safe:

  - we explicitly call /usr/bin/env python3
  - we full specifiy our symbols
  - do not assume that 'None' can be converted to a string

Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
---
 meta/recipes-kernel/kern-tools/kern-tools-native_git.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
index a4c0b6fb8a..57ec1abc6d 100644
--- a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
+++ b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
@@ -4,7 +4,7 @@ LIC_FILES_CHKSUM = "file://git/tools/kgit;beginline=5;endline=9;md5=9c30e971d435
 
 DEPENDS = "git-native"
 
-SRCREV = "7465c8497893ef8f6503c918aeede969f7e9753b"
+SRCREV = "5358eb293399867db05fd73d04ce908d69a03bed"
 PR = "r12"
 PV = "0.2+git${SRCPV}"
 
-- 
2.19.1

[PATCH 2/9] kern-tools: integrate merge_config fix for gold linker

[bruce.ashfield]

From: Bruce Ashfield <bruce.ashfield@gmail.com>

Bumping the SRCREV to pickup the following fix:

   Author: Martin Jansa <Martin.Jansa@gmail.com>
   Date:   Wed Feb 5 03:26:57 2020 +0100

       merge_config.sh: pass LD variable from shell environment to make

       * since 5.4 kernel Kconfig will fail immediately when it detects
         that LD points to gold linker:

         scripts/Kconfig.include:39:  gold linker 'i686-oe-linux-ld' not supported

       * in OE we already pass bfd linker in KERNEL_LD variable to merge_config.sh
         but we need to pass it also into the make call here

       Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>

Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
---
 meta/recipes-kernel/kern-tools/kern-tools-native_git.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
index 57ec1abc6d..3f9cfe7fe5 100644
--- a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
+++ b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
@@ -4,7 +4,7 @@ LIC_FILES_CHKSUM = "file://git/tools/kgit;beginline=5;endline=9;md5=9c30e971d435
 
 DEPENDS = "git-native"
 
-SRCREV = "5358eb293399867db05fd73d04ce908d69a03bed"
+SRCREV = "388b67974deb2176c06994a325676cbf23e5fce8"
 PR = "r12"
 PV = "0.2+git${SRCPV}"
 
-- 
2.19.1

[PATCH 3/9] kern-tools-native: use more common S value and oe_runmake

[bruce.ashfield]

From: Martin Jansa <martin.jansa@gmail.com>

Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
---
 .../kern-tools/kern-tools-native_git.bb               | 11 +++++++----
 1 file changed, 7 insertions(+), 4 deletions(-)

diff --git a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
index 3f9cfe7fe5..f263421234 100644
--- a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
+++ b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
@@ -1,6 +1,6 @@
 SUMMARY = "Tools for managing Yocto Project style branched kernels"
 LICENSE = "GPLv2"
-LIC_FILES_CHKSUM = "file://git/tools/kgit;beginline=5;endline=9;md5=9c30e971d435e249624278c3e343e501"
+LIC_FILES_CHKSUM = "file://tools/kgit;beginline=5;endline=9;md5=9c30e971d435e249624278c3e343e501"
 
 DEPENDS = "git-native"
 
@@ -11,14 +11,17 @@ PV = "0.2+git${SRCPV}"
 inherit native
 
 SRC_URI = "git://git.yoctoproject.org/yocto-kernel-tools.git"
-S = "${WORKDIR}"
+S = "${WORKDIR}/git"
 UPSTREAM_CHECK_COMMITS = "1"
 
+do_configure() {
+	:
+}
+
 do_compile() { 
 	:
 }
 
 do_install() {
-	cd ${S}/git
-	make DESTDIR=${D}${bindir} install
+	oe_runmake DESTDIR=${D}${bindir} install
 }
-- 
2.19.1

[PATCH 4/9] kernel-yocto: Move defaults and tasks from linux-yocto.inc into bbclass

[bruce.ashfield]

From: Paul Barker <pbarker@konsulko.com>

This allows the kernel-yocto bbclass to be inherited in a recipe without
needing to include linux-yocto.inc. The bbclass should stand on its own
and linux-yocto.inc does a few things which may not be desired in other
kernel recipes (such as modifying KERNEL_FEATURES).

The LINUX_VERSION_EXTENSION default is not moved as other kernel recipes
may not want this setting in place.

Signed-off-by: Paul Barker <pbarker@konsulko.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
---
 meta/classes/kernel-yocto.bbclass         | 21 +++++++++++++++++++++
 meta/recipes-kernel/linux/linux-yocto.inc | 21 ---------------------
 2 files changed, 21 insertions(+), 21 deletions(-)

diff --git a/meta/classes/kernel-yocto.bbclass b/meta/classes/kernel-yocto.bbclass
index 141eeafeb9..a0362f6acb 100644
--- a/meta/classes/kernel-yocto.bbclass
+++ b/meta/classes/kernel-yocto.bbclass
@@ -3,6 +3,22 @@ SRCTREECOVEREDTASKS += "do_kernel_configme do_validate_branches do_kernel_config
 PATCH_GIT_USER_EMAIL ?= "kernel-yocto@oe"
 PATCH_GIT_USER_NAME ?= "OpenEmbedded"
 
+# The distro or local.conf should set this, but if nobody cares...
+LINUX_KERNEL_TYPE ??= "standard"
+
+# KMETA ?= ""
+KBRANCH ?= "master"
+KMACHINE ?= "${MACHINE}"
+SRCREV_FORMAT ?= "meta_machine"
+
+# LEVELS:
+#   0: no reporting
+#   1: report options that are specified, but not in the final config
+#   2: report options that are not hardware related, but set by a BSP
+KCONF_AUDIT_LEVEL ?= "1"
+KCONF_BSP_AUDIT_LEVEL ?= "0"
+KMETA_AUDIT ?= "yes"
+
 # returns local (absolute) path names for all valid patches in the
 # src_uri
 def find_patches(d,subdir):
@@ -475,3 +491,8 @@ python () {
     if 'do_diffconfig' in d:
         bb.build.addtask('do_diffconfig', None, 'do_kernel_configme', d)
 }
+
+# extra tasks
+addtask kernel_version_sanity_check after do_kernel_metadata do_kernel_checkout before do_compile
+addtask validate_branches before do_patch after do_kernel_checkout
+addtask kernel_configcheck after do_configure before do_compile
diff --git a/meta/recipes-kernel/linux/linux-yocto.inc b/meta/recipes-kernel/linux/linux-yocto.inc
index f191946f2a..91df9c1cd5 100644
--- a/meta/recipes-kernel/linux/linux-yocto.inc
+++ b/meta/recipes-kernel/linux/linux-yocto.inc
@@ -39,22 +39,6 @@ KERNEL_FEATURES_append = " ${@bb.utils.contains('MACHINE_FEATURES', 'numa', 'fea
 # and it can be specific to the machine or shared
 # KMACHINE = "UNDEFINED"
 
-# The distro or local.conf should set this, but if nobody cares...
-LINUX_KERNEL_TYPE ??= "standard"
-
-# KMETA ?= ""
-KBRANCH ?= "master"
-KMACHINE ?= "${MACHINE}"
-SRCREV_FORMAT ?= "meta_machine" 
-
-# LEVELS:
-#   0: no reporting
-#   1: report options that are specified, but not in the final config
-#   2: report options that are not hardware related, but set by a BSP
-KCONF_AUDIT_LEVEL ?= "1"
-KCONF_BSP_AUDIT_LEVEL ?= "0"
-KMETA_AUDIT ?= "yes"
-
 LINUX_VERSION_EXTENSION ??= "-yocto-${LINUX_KERNEL_TYPE}"
 
 # Pick up shared functions
@@ -69,10 +53,5 @@ do_install_append(){
 	fi
 }
 
-# extra tasks
-addtask kernel_version_sanity_check after do_kernel_metadata do_kernel_checkout before do_compile
-addtask validate_branches before do_patch after do_kernel_checkout
-addtask kernel_configcheck after do_configure before do_compile
-
 # enable kernel-sample for oeqa/runtime/cases's ksample.py test
 KERNEL_FEATURES_append_qemuall=" features/kernel-sample/kernel-sample.scc"
-- 
2.19.1

[PATCH 5/9] kernel-yocto: Drop setting of unused variables in do_kernel_metadata

[bruce.ashfield]

From: Paul Barker <pbarker@konsulko.com>

The machine_branch and machine_srcrev variables were set but not used in
do_kernel_metadata.

Signed-off-by: Paul Barker <pbarker@konsulko.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
---
 meta/classes/kernel-yocto.bbclass | 7 -------
 1 file changed, 7 deletions(-)

diff --git a/meta/classes/kernel-yocto.bbclass b/meta/classes/kernel-yocto.bbclass
index a0362f6acb..9a4d2864eb 100644
--- a/meta/classes/kernel-yocto.bbclass
+++ b/meta/classes/kernel-yocto.bbclass
@@ -99,13 +99,6 @@ do_kernel_metadata() {
 		fi
 	fi
 
-	machine_branch="${@ get_machine_branch(d, "${KBRANCH}" )}"
-	machine_srcrev="${SRCREV_machine}"
-	if [ -z "${machine_srcrev}" ]; then
-		# fallback to SRCREV if a non machine_meta tree is being built
-		machine_srcrev="${SRCREV}"
-	fi
-
 	# In a similar manner to the kernel itself:
 	#
 	#   defconfig: $(obj)/conf
-- 
2.19.1

[PATCH 6/9] kernel-yocto: Only override CONFIG_LOCALVERSION if LINUX_VERSION_EXTENSION is set

[bruce.ashfield]

From: Paul Barker <pbarker@konsulko.com>

CONFIG_LOCALVERSION may already be set in a defconfig or config fragment
and this should not be unconditionally overridden.

Signed-off-by: Paul Barker <pbarker@konsulko.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
---
 meta/classes/kernel-yocto.bbclass | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/meta/classes/kernel-yocto.bbclass b/meta/classes/kernel-yocto.bbclass
index 9a4d2864eb..e8a9b1f18e 100644
--- a/meta/classes/kernel-yocto.bbclass
+++ b/meta/classes/kernel-yocto.bbclass
@@ -359,8 +359,10 @@ do_kernel_configme() {
 		bbfatal_log "Could not configure ${KMACHINE}-${LINUX_KERNEL_TYPE}"
 	fi
 
-	echo "# Global settings from linux recipe" >> ${B}/.config
-	echo "CONFIG_LOCALVERSION="\"${LINUX_VERSION_EXTENSION}\" >> ${B}/.config
+	if [ ! -z "${LINUX_VERSION_EXTENSION}" ]; then
+		echo "# Global settings from linux recipe" >> ${B}/.config
+		echo "CONFIG_LOCALVERSION="\"${LINUX_VERSION_EXTENSION}\" >> ${B}/.config
+	fi
 }
 
 addtask kernel_configme before do_configure after do_patch
-- 
2.19.1

[PATCH 7/9] kernel-yocto.bbclass: set KERNEL_LD also for merge_config.sh

[bruce.ashfield]

From: Martin Jansa <martin.jansa@gmail.com>

* when ld-is-gold is used, merge_config.sh silently fails and doesn't generate anything
  useful in .config (and also include directory isn't created):

  tmp-glibc-bfd-qemux86-do_kernel_configme/work/qemux86-oe-linux/linux-yocto/5.4.15-r0/linux-qemux86-standard-build:
  total 164K
  drwxr-xr-x 4 martin martin 4.0K Feb  5 02:27 .
  drwxrwxr-x 7 martin martin 4.0K Feb  5 02:27 ..
  -rw-rw-r-- 1 martin martin 133K Feb  5 02:28 .config
  -rw-rw-r-- 1 martin martin   39 Feb  5 02:27 .gitignore
  drwxr-xr-x 4 martin martin 4.0K Feb  5 02:27 include
  -rw-rw-r-- 1 martin martin  201 Feb  5 02:27 Makefile
  drwxrwxr-x 4 martin martin 4.0K Feb  5 02:27 scripts
  lrwxrwxrwx 1 martin martin   61 Feb  5 02:27 source -> /OE/build/oe-core/tmp-glibc/work-shared/qemux86/kernel-source

  tmp-glibc-gold-qemux86-do_kernel_configme/work/qemux86-oe-linux/linux-yocto/5.4.15-r0/linux-qemux86-standard-build:
  total 28K
  drwxr-xr-x 3 martin martin 4.0K Feb  5 02:26 .
  drwxrwxr-x 7 martin martin 4.0K Feb  5 02:26 ..
  -rw-rw-r-- 1 martin martin   74 Feb  5 02:26 .config
  -rw-rw-r-- 1 martin martin   39 Feb  5 02:26 .gitignore
  -rw-rw-r-- 1 martin martin  201 Feb  5 02:26 Makefile
  drwxrwxr-x 4 martin martin 4.0K Feb  5 02:26 scripts
  lrwxrwxrwx 1 martin martin   61 Feb  5 02:26 source -> /OE/build/oe-core/tmp-glibc/work-shared/qemux86/kernel-source

  $ cat tmp-glibc-gold-qemux86-do_kernel_configme/work/qemux86-oe-linux/linux-yocto/5.4.15-r0/linux-qemux86-standard-build/.config
  CONFIG_LOCALVERSION="-yocto-standard"

* and because the failure is silent, it will happily start building
  kernel with default defconfig, which even builds OK for qemux86-64
  but on qemux86 I've noticed this issue, because incorrectly
  configured kernel build fails with:

  $ tail -n 20 tmp-glibc-gold-qemux86/work/qemux86-oe-linux/linux-yocto/5.4.15-r0/temp/log.do_compile
    LD       /OE/build/oe-core/tmp-glibc/work/qemux86-oe-linux/linux-yocto/5.4.15-r0/linux-qemux86-standard-build/tools/objtool/libsubcmd-in.o
    AR       /OE/build/oe-core/tmp-glibc/work/qemux86-oe-linux/linux-yocto/5.4.15-r0/linux-qemux86-standard-build/tools/objtool/libsubcmd.a
    HOSTCC  scripts/mod/mk_elfconfig
    CC      scripts/mod/devicetable-offsets.s
    CC      scripts/mod/empty.o
  cc1: error: code model 'kernel' not supported in the 32 bit mode
  cc1: sorry, unimplemented: 64-bit mode not compiled in
  make[2]: *** [/OE/build/oe-core/tmp-glibc/work-shared/qemux86/kernel-source/scripts/Makefile.build:99: scripts/mod/devicetable-offsets.s] Error 1
  make[2]: *** Waiting for unfinished jobs....
  cc1: error: code model 'kernel' not supported in the 32 bit mode
  cc1: sorry, unimplemented: 64-bit mode not compiled in
  make[2]: *** [/OE/build/oe-core/tmp-glibc/work-shared/qemux86/kernel-source/scripts/Makefile.build:266: scripts/mod/empty.o] Error 1
  make[1]: *** [/OE/build/oe-core/tmp-glibc/work-shared/qemux86/kernel-source/Makefile:1111: prepare0] Error 2
  make[1]: *** Waiting for unfinished jobs....
    LD       /OE/build/oe-core/tmp-glibc/work/qemux86-oe-linux/linux-yocto/5.4.15-r0/linux-qemux86-standard-build/tools/objtool/objtool-in.o
  /OE/build/oe-core/tmp-glibc/work-shared/qemux86/kernel-source/tools/objtool
    LINK     /OE/build/oe-core/tmp-glibc/work/qemux86-oe-linux/linux-yocto/5.4.15-r0/linux-qemux86-standard-build/tools/objtool/objtool
  make: *** [/OE/build/oe-core/tmp-glibc/work-shared/qemux86/kernel-source/Makefile:179: sub-make] Error 2
  WARNING: exit code 1 from a shell command.

* the issue happens in log.do_kernel_configme, but the log is completely useless:

  cat tmp-glibc-gold-qemux86-do_kernel_configme/work/qemux86-oe-linux/linux-yocto/5.4.15-r0/temp/log.do_kernel_configme
  DEBUG: Executing python function extend_recipe_sysroot
  NOTE: Direct dependencies are ['virtual:native:/OE/build/oe-core/openembedded-core/meta/recipes-devtools/bison/bison_3.5.bb:do_populate_sysroot', '/OE/build/oe-core/openembedded-core/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb:do_populate_sysroot', 'virtual:native:/OE/build/oe-core/openembedded-core/meta/recipes-extended/bc/bc_1.07.1.bb:do_populate_sysroot', '/OE/build/oe-core/openembedded-core/meta/recipes-devtools/binutils/binutils-cross_2.33.bb:do_populate_sysroot', '/OE/build/oe-core/openembedded-core/meta/recipes-devtools/quilt/quilt-native_0.66.bb:do_populate_sysroot', '/OE/build/oe-core/openembedded-core/meta/recipes-devtools/gcc/gcc-cross_9.2.bb:do_populate_sysroot']
  NOTE: Installed into sysroot: ['bison-native', 'bc-native', 'binutils-cross-i686', 'gcc-cross-i686', 'autoconf-native', 'xz-native', 'flex-native', 'gnu-config-native', 'automake-native', 'libtool-native', 'texinfo-dummy-native', 'gettext-minimal-native', 'readline-native', 'zlib-native', 'gmp-native', 'libmpc-native', 'mpfr-native', 'linux-libc-headers', 'm4-native', 'ncurses-native', 'pkgconfig-native']
  NOTE: Skipping as already exists in sysroot: ['kern-tools-native', 'quilt-native']
  DEBUG: sed -e 's:^[^/]*/:/OE/build/oe-core/tmp-glibc/work/qemux86-oe-linux/linux-yocto/5.4.15-r0/recipe-sysroot-native/:g' /OE/build/oe-core/tmp-glibc/sysroots-components/x86_64/bison-native/fixmepath /OE/build/oe-core/tmp-glibc/sysroots-components/x86_64/gcc-cross-i686/fixmepath /OE/build/oe-core/tmp-glibc/sysroots-components/x86_64/autoconf-native/fixmepath /OE/build/oe-core/tmp-glibc/sysroots-components/x86_64/gnu-config-native/fixmepath /OE/build/oe-core/tmp-glibc/sysroots-components/x86_64/automake-native/fixmepath /OE/build/oe-core/tmp-glibc/sysroots-components/x86_64/libtool-native/fixmepath /OE/build/oe-core/tmp-glibc/sysroots-components/x86_64/gmp-native/fixmepath /OE/build/oe-core/tmp-glibc/sysroots-components/x86_64/ncurses-native/fixmepath /OE/build/oe-core/tmp-glibc/sysroots-components/x86_64/pkgconfig-native/fixmepath | xargs sed -i -e 's:FIXMESTAGINGDIRTARGET:/OE/build/oe-core/tmp-glibc/work/qemux86-oe-linux/linux-yocto/5.4.15-r0/recipe-sysroot:g; s:FIXMESTAGINGDIRHOST:/OE/build/oe-core/tmp-glibc/work/qemux86-oe-linux/linux-yocto/5.4.15-r0/recipe-sysroot-native:g' -e 's:FIXME_PSEUDO_SYSROOT:/OE/build/oe-core/tmp-glibc/sysroots-components/x86_64/pseudo-native:g' -e 's:FIXME_HOSTTOOLS_DIR:/OE/build/oe-core/tmp-glibc/hosttools:g' -e 's:FIXME_PKGDATA_DIR:/OE/build/oe-core/tmp-glibc/pkgdata/qemux86:g' -e 's:FIXME_PSEUDO_LOCALSTATEDIR:/OE/build/oe-core/tmp-glibc/work/qemux86-oe-linux/linux-yocto/5.4.15-r0/pseudo/:g' -e 's:FIXME_LOGFIFO:/OE/build/oe-core/tmp-glibc/work/qemux86-oe-linux/linux-yocto/5.4.15-r0/temp/fifo.10476:g'
  DEBUG: Python function extend_recipe_sysroot finished
  DEBUG: Executing shell function do_kernel_configme
  DEBUG: Shell function do_kernel_configme finished

  ]because merge_config.sh is redirected to work-shared/qemux86/kernel-source/.kernel-meta/cfg/merge_config_build.log
  and bbfatal_log called in do_kernel_configme only when merge_config.sh fails which it should in this case
  but doesn't.

  The merge_config_build.log shows 5.4 specific error:
    scripts/Kconfig.include:39:  gold linker 'i686-oe-linux-ld' not supported
  but then it happily continues reporting what isn't applied in not created
  .config file

  --- tmp-glibc-bfd-qemux86-do_kernel_configme/work-shared/qemux86/kernel-source/.kernel-meta/cfg/merge_config_build.log  2020-02-05 02:28:01.455520207 +0100
  +++ tmp-glibc-gold-qemux86-do_kernel_configme/work-shared/qemux86/kernel-source/.kernel-meta/cfg/merge_config_build.log 2020-02-05 02:26:30.656470909 +0100
  @@ -171,586 +171,5113 @@
     HOSTCC  scripts/kconfig/symbol.o
     HOSTLD  scripts/kconfig/conf
   scripts/kconfig/conf  --alldefconfig Kconfig
  -./.tmp.config.jDjIEYi9Yq:2208:warning: unexpected data:  #
  -./.tmp.config.jDjIEYi9Yq:2209:warning: unexpected data:  # Generic Driver Options
  -./.tmp.config.jDjIEYi9Yq:2210:warning: unexpected data:  #
  -./.tmp.config.jDjIEYi9Yq:3102:warning: symbol value 'm' invalid for SAMPLE_SECCOMP
  -./.tmp.config.jDjIEYi9Yq:3119:warning: symbol value 'm' invalid for NF_CT_PROTO_GRE
  -./.tmp.config.jDjIEYi9Yq:3120:warning: symbol value 'm' invalid for NF_CT_PROTO_SCTP
  -./.tmp.config.jDjIEYi9Yq:3121:warning: symbol value 'm' invalid for NF_CT_PROTO_UDPLITE
  -#
  -# configuration written to .config
  -#
  +scripts/Kconfig.include:39:  gold linker 'i686-oe-linux-ld' not supported
  +make[2]: *** [/OE/build/oe-core/tmp-glibc/work-shared/qemux86/kernel-source/scripts/kconfig/Makefile:73: alldefconfig] Error 1
  +make[1]: *** [/OE/build/oe-core/tmp-glibc/work-shared/qemux86/kernel-source/Makefile:567: alldefconfig] Error 2
   make[1]: Leaving directory '/OE/build/oe-core/tmp-glibc/work/qemux86-oe-linux/linux-yocto/5.4.15-r0/linux-qemux86-standard-build'
  +make: *** [Makefile:179: sub-make] Error 2
  +grep: /OE/build/oe-core/tmp-glibc/work/qemux86-oe-linux/linux-yocto/5.4.15-r0/linux-qemux86-standard-build/.config: No such file or directory
  +Value requested for CONFIG_LOCALVERSION not in final .config
  +Requested value:  CONFIG_LOCALVERSION=""
  +Actual value:
  +
  +grep: /OE/build/oe-core/tmp-glibc/work/qemux86-oe-linux/linux-yocto/5.4.15-r0/linux-qemux86-standard-build/.config: No such file or directory
  +Value requested for CONFIG_LOCALVERSION_AUTO not in final .config
  +Requested value:  # CONFIG_LOCALVERSION_AUTO is not set
  +Actual value:

* I don't know why merge_config.sh uses separate more difficult to find merge_config_build.log
  instead of leaving the output to end in log.do_kernel_configme, I'll send it as separate
  commit so that it can be discussed there.

Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
---
 meta/classes/kernel-yocto.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/classes/kernel-yocto.bbclass b/meta/classes/kernel-yocto.bbclass
index e8a9b1f18e..f71aa7d0a6 100644
--- a/meta/classes/kernel-yocto.bbclass
+++ b/meta/classes/kernel-yocto.bbclass
@@ -354,7 +354,7 @@ do_kernel_configme() {
 		bbfatal_log "Could not find configuration queue (${meta_dir}/config.queue)"
 	fi
 
-	CFLAGS="${CFLAGS} ${TOOLCHAIN_OPTIONS}"	HOSTCC="${BUILD_CC} ${BUILD_CFLAGS} ${BUILD_LDFLAGS}" HOSTCPP="${BUILD_CPP}" CC="${KERNEL_CC}" ARCH=${ARCH} merge_config.sh -O ${B} ${config_flags} ${configs} > ${meta_dir}/cfg/merge_config_build.log 2>&1
+	CFLAGS="${CFLAGS} ${TOOLCHAIN_OPTIONS}"	HOSTCC="${BUILD_CC} ${BUILD_CFLAGS} ${BUILD_LDFLAGS}" HOSTCPP="${BUILD_CPP}" CC="${KERNEL_CC}" LD="${KERNEL_LD}" ARCH=${ARCH} merge_config.sh -O ${B} ${config_flags} ${configs} > ${meta_dir}/cfg/merge_config_build.log 2>&1
 	if [ $? -ne 0 ]; then
 		bbfatal_log "Could not configure ${KMACHINE}-${LINUX_KERNEL_TYPE}"
 	fi
-- 
2.19.1

[PATCH 8/9] kernel-yocto.bbclass: do_kernel_configme: don't use +errexit, merge_config_build.log and fail when /.config wasn't created

[bruce.ashfield]

From: Martin Jansa <martin.jansa@gmail.com>

* for whatever reason, instead of silently continuing to build default kernel config

Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
---
 meta/classes/kernel-yocto.bbclass | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/meta/classes/kernel-yocto.bbclass b/meta/classes/kernel-yocto.bbclass
index f71aa7d0a6..d961901b74 100644
--- a/meta/classes/kernel-yocto.bbclass
+++ b/meta/classes/kernel-yocto.bbclass
@@ -327,8 +327,6 @@ do_kernel_configme[depends] += "virtual/${TARGET_PREFIX}gcc:do_populate_sysroot"
 do_kernel_configme[depends] += "bc-native:do_populate_sysroot bison-native:do_populate_sysroot"
 do_kernel_configme[dirs] += "${S} ${B}"
 do_kernel_configme() {
-	set +e
-
 	# translate the kconfig_mode into something that merge_config.sh
 	# understands
 	case ${KCONFIG_MODE} in
@@ -354,8 +352,9 @@ do_kernel_configme() {
 		bbfatal_log "Could not find configuration queue (${meta_dir}/config.queue)"
 	fi
 
-	CFLAGS="${CFLAGS} ${TOOLCHAIN_OPTIONS}"	HOSTCC="${BUILD_CC} ${BUILD_CFLAGS} ${BUILD_LDFLAGS}" HOSTCPP="${BUILD_CPP}" CC="${KERNEL_CC}" LD="${KERNEL_LD}" ARCH=${ARCH} merge_config.sh -O ${B} ${config_flags} ${configs} > ${meta_dir}/cfg/merge_config_build.log 2>&1
-	if [ $? -ne 0 ]; then
+	CFLAGS="${CFLAGS} ${TOOLCHAIN_OPTIONS}" HOSTCC="${BUILD_CC} ${BUILD_CFLAGS} ${BUILD_LDFLAGS}" HOSTCPP="${BUILD_CPP}" CC="${KERNEL_CC}" LD="${KERNEL_LD}" ARCH=${ARCH} merge_config.sh -O ${B} ${config_flags} ${configs}
+
+	if [ $? -ne 0 -o ! -f ${B}/.config ]; then
 		bbfatal_log "Could not configure ${KMACHINE}-${LINUX_KERNEL_TYPE}"
 	fi
 
-- 
2.19.1

[PATCH 9/9] kernel-yocto: fix defconfig detection in find_sccs()

[bruce.ashfield]

From: Gavin Li <gavinli@thegavinli.com>

The current code would cause a file like "config.bin" to added to the
config sources list. I am sure the intention was to add any files with
defconfig in its name and not the other way around.

Signed-off-by: Gavin Li <gavinli@thegavinli.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
---
 meta/classes/kernel-yocto.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/classes/kernel-yocto.bbclass b/meta/classes/kernel-yocto.bbclass
index d961901b74..918d101d3d 100644
--- a/meta/classes/kernel-yocto.bbclass
+++ b/meta/classes/kernel-yocto.bbclass
@@ -47,7 +47,7 @@ def find_sccs(d):
         base, ext = os.path.splitext(os.path.basename(s))
         if ext and ext in [".scc", ".cfg"]:
             sources_list.append(s)
-        elif base and base in 'defconfig':
+        elif base and 'defconfig' in base:
             sources_list.append(s)
 
     return sources_list
-- 
2.19.1

✗ patchtest: failure for kernel-yocto: consolidated pull request

[Patchwork]

== Series Details ==

Series: kernel-yocto: consolidated pull request
Revision: 1
URL   : https://patchwork.openembedded.org/series/22442/
State : failure

== Summary ==


Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been executed on the proposed
series by patchtest resulting in the following failures:



* Patch            [8/9] kernel-yocto.bbclass: do_kernel_configme: don't use +errexit, merge_config_build.log and fail when /.config wasn't created
 Issue             Commit shortlog is too long [test_shortlog_length] 
  Suggested fix    Edit shortlog so that it is 90 characters or less (currently 122 characters)



If you believe any of these test results are incorrect, please reply to the
mailing list (openembedded-core@lists.openembedded.org) raising your concerns.
Otherwise we would appreciate you correcting the issues and submitting a new
version of the patchset if applicable. Please ensure you add/increment the
version number when sending the new version (i.e. [PATCH] -> [PATCH v2] ->
[PATCH v3] -> ...).

---
Guidelines:     https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest
Test suite:     http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe

Re: [PATCH 0/9] kernel-yocto: consolidated pull request

[Richard Purdie]

Hi Bruce,

On Wed, 2020-02-05 at 18:12 -0500, bruce.ashfield@gmail.com wrote:
> From: Bruce Ashfield <bruce.ashfield@gmail.com>
> 
> Hi all,
> 
> I've kept the v5.4 content changes, as well as the kernel version
> default
> changes out of this series and instead focused it on the collection
> of
> kernel-yocto and kern-tools tweaks that I've gethered over the past
> few
> weeks.
> 
> I have Martin's gold linker fixes included, as well as the re-org'ing 
> of
> the linux-yocto tasks that Paul Barker did to make it usable as a
> single
> inherit of the bbclass.
> 
> I also have a defconfig detection fix included that was sent to the
> list.
> 
> I was able to confirm that my configuration was the same with this
> series
> enabled, and I was able to boot.
> 
> That being said, I'll keep my eye out for any AB fallout and will
> continue
> some more build locally .. but I wanted to get this out today as
> promised.

qemuarm64 seems unhappy:

https://autobuilder.yoctoproject.org/typhoon/#/builders/42/builds/1524

(the builds on the arm native machine also failed but it looks related)

I think everything else passed testing for this series.

Cheers,

Richard

Re: [PATCH 0/9] kernel-yocto: consolidated pull request

[Bruce Ashfield]

On Thu, Feb 6, 2020 at 4:03 AM Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
>
> Hi Bruce,
>
> On Wed, 2020-02-05 at 18:12 -0500, bruce.ashfield@gmail.com wrote:
> > From: Bruce Ashfield <bruce.ashfield@gmail.com>
> >
> > Hi all,
> >
> > I've kept the v5.4 content changes, as well as the kernel version
> > default
> > changes out of this series and instead focused it on the collection
> > of
> > kernel-yocto and kern-tools tweaks that I've gethered over the past
> > few
> > weeks.
> >
> > I have Martin's gold linker fixes included, as well as the re-org'ing
> > of
> > the linux-yocto tasks that Paul Barker did to make it usable as a
> > single
> > inherit of the bbclass.
> >
> > I also have a defconfig detection fix included that was sent to the
> > list.
> >
> > I was able to confirm that my configuration was the same with this
> > series
> > enabled, and I was able to boot.
> >
> > That being said, I'll keep my eye out for any AB fallout and will
> > continue
> > some more build locally .. but I wanted to get this out today as
> > promised.
>
> qemuarm64 seems unhappy:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/42/builds/1524

Bugger. I'll fix and resend a v2 pull request.

Bruce

>
> (the builds on the arm native machine also failed but it looks related)
>
> I think everything else passed testing for this series.
>
> Cheers,
>
> Richard
>


-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II

[PATCH 0/9] kernel-yocto: consolidated pull request

[bruce.ashfield]

From: Bruce Ashfield <bruce.ashfield@gmail.com>

Richard,

Here's the next set of -stable updates to the active reference kernels.
I also have updates back to 5.4 that I'll send to the various stable
branches shortly.

I also have a couple of kern-tools fixes. One to solve a problem reported
on the list about some directory structures (typically created from KAS)
to break the meta-data phase of the kernel build. I've fixed that issue,
then fixed the other regressions that fix caused, and have everything
passing sanity. There shouldn't be any fallout, but I'll be keeping a
close eye on things.

I also have Khem's MDIO configuration change in the queue, along with
a previously hidden kern-tools feature that allows it to not warn if
something is 'enabled' (y or m).

Cheers,

Bruce

The following changes since commit fa86bfd3617b54dbf7e44093ae0e6f35538bdabc:

  diffoscope: upgrade 220 -> 221 (2022-09-17 07:47:08 +0100)

are available in the Git repository at:

  git://git.yoctoproject.org/poky-contrib zedd/kernel
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel

Bruce Ashfield (8):
  linux-yocto/5.15: update to v5.15.63
  linux-yocto/5.19: update to v5.19.5
  linux-yocto/5.19: update to v5.19.7
  linux-yocto/5.15: update to v5.15.65
  kern-tools: fix queue processing in relative TOPDIR configurations
  kern-tools: allow 'y' or 'm' to avoid config audit warnings
  linux-yocto/5.19: update to v5.19.9
  linux-yocto/5.15: update to v5.15.68

Khem Raj (1):
  linux-yocto: Enable mdio for qemu

 .../kern-tools/kern-tools-native_git.bb       |  2 +-
 .../linux/linux-yocto-rt_5.15.bb              |  6 ++--
 .../linux/linux-yocto-rt_5.19.bb              |  6 ++--
 .../linux/linux-yocto-tiny_5.15.bb            |  6 ++--
 .../linux/linux-yocto-tiny_5.19.bb            |  6 ++--
 meta/recipes-kernel/linux/linux-yocto_5.15.bb | 26 ++++++++---------
 meta/recipes-kernel/linux/linux-yocto_5.19.bb | 28 +++++++++----------
 7 files changed, 40 insertions(+), 40 deletions(-)

-- 
2.19.1

Re: [PATCH 0/9] kernel-yocto: consolidated pull request

[Richard Purdie]

On Mon, 2022-09-19 at 10:28 -0400, bruce.ashfield@gmail.com wrote:
> Here's the next set of -stable updates to the active reference kernels.
> I also have updates back to 5.4 that I'll send to the various stable
> branches shortly.
> 
> I also have a couple of kern-tools fixes. One to solve a problem reported
> on the list about some directory structures (typically created from KAS)
> to break the meta-data phase of the kernel build. I've fixed that issue,
> then fixed the other regressions that fix caused, and have everything
> passing sanity. There shouldn't be any fallout, but I'll be keeping a
> close eye on things.
> 
> I also have Khem's MDIO configuration change in the queue, along with
> a previously hidden kern-tools feature that allows it to not warn if
> something is 'enabled' (y or m).

Thanks, those sound like good fixes. Unfortunately this showed an issue
with TMPDIR in perf somewhere in testing:

Reproducible error:
https://autobuilder.yoctoproject.org/typhoon/#/builders/117/builds/1570

and warnings:
https://autobuilder.yoctoproject.org/typhoon/#/builders/61/builds/5871

https://autobuilder.yoctoproject.org/typhoon/#/builders/73/builds/5832
https://autobuilder.yoctoproject.org/typhoon/#/builders/42/builds/5862
https://autobuilder.yoctoproject.org/typhoon/#/builders/15/builds/6153
https://autobuilder.yoctoproject.org/typhoon/#/builders/131/builds/1255
https://autobuilder.yoctoproject.org/typhoon/#/builders/60/builds/5848
https://autobuilder.yoctoproject.org/typhoon/#/builders/44/builds/5910
and more, seems to be on all arches.

Diffoscope output is here:
http://autobuilder.yocto.io/pub/repro-fail/oe-reproducible-20220919-7ypfzvog/packages/diff-html/

which shows an issue in debug symbols and it looks to be python
related:

PYTHON·BUILD_STR('/home/pokybuild/yocto-worker/reproducible/build/build-st/reproducibleA/tmp/work/qemux86_64-poky-linux/perf/1.0-r9/recipe-sysroot-native/usr/bin/python3-native/python3')

Cheers,

Richard

Re: [PATCH 0/9] kernel-yocto: consolidated pull request

[Richard Purdie]

On Mon, 2022-09-19 at 10:28 -0400, bruce.ashfield@gmail.com wrote:
> From: Bruce Ashfield <bruce.ashfield@gmail.com>
> 
> Richard,
> 
> Here's the next set of -stable updates to the active reference kernels.
> I also have updates back to 5.4 that I'll send to the various stable
> branches shortly.
> 
> I also have a couple of kern-tools fixes. One to solve a problem reported
> on the list about some directory structures (typically created from KAS)
> to break the meta-data phase of the kernel build. I've fixed that issue,
> then fixed the other regressions that fix caused, and have everything
> passing sanity. There shouldn't be any fallout, but I'll be keeping a
> close eye on things.
> 
> I also have Khem's MDIO configuration change in the queue, along with
> a previously hidden kern-tools feature that allows it to not warn if
> something is 'enabled' (y or m).

I have a patch in master-next I'm testing for the perf issue. On
testing that, this set of config warnings became clear for poky-tiny:

https://autobuilder.yoctoproject.org/typhoon/#/builders/15/builds/6157

Cheers,

Richard

Re: [PATCH 0/9] kernel-yocto: consolidated pull request

[Bruce Ashfield]

On Tue, Sep 20, 2022 at 8:22 AM Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
>
> On Mon, 2022-09-19 at 10:28 -0400, bruce.ashfield@gmail.com wrote:
> > From: Bruce Ashfield <bruce.ashfield@gmail.com>
> >
> > Richard,
> >
> > Here's the next set of -stable updates to the active reference kernels.
> > I also have updates back to 5.4 that I'll send to the various stable
> > branches shortly.
> >
> > I also have a couple of kern-tools fixes. One to solve a problem reported
> > on the list about some directory structures (typically created from KAS)
> > to break the meta-data phase of the kernel build. I've fixed that issue,
> > then fixed the other regressions that fix caused, and have everything
> > passing sanity. There shouldn't be any fallout, but I'll be keeping a
> > close eye on things.
> >
> > I also have Khem's MDIO configuration change in the queue, along with
> > a previously hidden kern-tools feature that allows it to not warn if
> > something is 'enabled' (y or m).
>
> I have a patch in master-next I'm testing for the perf issue. On
> testing that, this set of config warnings became clear for poky-tiny:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/15/builds/6157

That's very likely due to this change from Andrei :
https://git.yoctoproject.org/yocto-kernel-cache/commit/?h=yocto-5.19&id=d334505d98a85ffe7549026d10e43cccd897e19c

Was that a qemuarm64 configuration ?

Bruce


>
> Cheers,
>
> Richard



-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II

Re: [PATCH 0/9] kernel-yocto: consolidated pull request

[Richard Purdie]

On Tue, 2022-09-20 at 08:53 -0400, Bruce Ashfield wrote:
> On Tue, Sep 20, 2022 at 8:22 AM Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > 
> > On Mon, 2022-09-19 at 10:28 -0400, bruce.ashfield@gmail.com wrote:
> > > From: Bruce Ashfield <bruce.ashfield@gmail.com>
> > > 
> > > Richard,
> > > 
> > > Here's the next set of -stable updates to the active reference kernels.
> > > I also have updates back to 5.4 that I'll send to the various stable
> > > branches shortly.
> > > 
> > > I also have a couple of kern-tools fixes. One to solve a problem reported
> > > on the list about some directory structures (typically created from KAS)
> > > to break the meta-data phase of the kernel build. I've fixed that issue,
> > > then fixed the other regressions that fix caused, and have everything
> > > passing sanity. There shouldn't be any fallout, but I'll be keeping a
> > > close eye on things.
> > > 
> > > I also have Khem's MDIO configuration change in the queue, along with
> > > a previously hidden kern-tools feature that allows it to not warn if
> > > something is 'enabled' (y or m).
> > 
> > I have a patch in master-next I'm testing for the perf issue. On
> > testing that, this set of config warnings became clear for poky-tiny:
> > 
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/15/builds/6157
> 
> That's very likely due to this change from Andrei :
> https://git.yoctoproject.org/yocto-kernel-cache/commit/?h=yocto-5.19&id=d334505d98a85ffe7549026d10e43cccd897e19c
> 
> Was that a qemuarm64 configuration ?

It warned on qemux86:
https://autobuilder.yoctoproject.org/typhoon/#/builders/15/builds/6157/steps/12/logs/stdio

qemux86-64:
https://autobuilder.yoctoproject.org/typhoon/#/builders/15/builds/6157/steps/16/logs/stdio

qemuarm64:
https://autobuilder.yoctoproject.org/typhoon/#/builders/15/builds/6157/steps/18/logs/stdio

so on all the arches we test for tiny.

Cheers,

Richard

Re: [PATCH 0/9] kernel-yocto: consolidated pull request

[Bruce Ashfield]

On Tue, Sep 20, 2022 at 8:55 AM Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
>
> On Tue, 2022-09-20 at 08:53 -0400, Bruce Ashfield wrote:
> > On Tue, Sep 20, 2022 at 8:22 AM Richard Purdie
> > <richard.purdie@linuxfoundation.org> wrote:
> > >
> > > On Mon, 2022-09-19 at 10:28 -0400, bruce.ashfield@gmail.com wrote:
> > > > From: Bruce Ashfield <bruce.ashfield@gmail.com>
> > > >
> > > > Richard,
> > > >
> > > > Here's the next set of -stable updates to the active reference kernels.
> > > > I also have updates back to 5.4 that I'll send to the various stable
> > > > branches shortly.
> > > >
> > > > I also have a couple of kern-tools fixes. One to solve a problem reported
> > > > on the list about some directory structures (typically created from KAS)
> > > > to break the meta-data phase of the kernel build. I've fixed that issue,
> > > > then fixed the other regressions that fix caused, and have everything
> > > > passing sanity. There shouldn't be any fallout, but I'll be keeping a
> > > > close eye on things.
> > > >
> > > > I also have Khem's MDIO configuration change in the queue, along with
> > > > a previously hidden kern-tools feature that allows it to not warn if
> > > > something is 'enabled' (y or m).
> > >
> > > I have a patch in master-next I'm testing for the perf issue. On
> > > testing that, this set of config warnings became clear for poky-tiny:
> > >
> > > https://autobuilder.yoctoproject.org/typhoon/#/builders/15/builds/6157
> >
> > That's very likely due to this change from Andrei :
> > https://git.yoctoproject.org/yocto-kernel-cache/commit/?h=yocto-5.19&id=d334505d98a85ffe7549026d10e43cccd897e19c
> >
> > Was that a qemuarm64 configuration ?
>
> It warned on qemux86:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/15/builds/6157/steps/12/logs/stdio
>
> qemux86-64:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/15/builds/6157/steps/16/logs/stdio
>
> qemuarm64:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/15/builds/6157/steps/18/logs/stdio
>
> so on all the arches we test for tiny.
>

I've reproduced it locally .. the fix is a bit fiddly. I'm going to
try some things tonight / tomorrow and will send a patch that goes
onto the end of the series to fix it up.

Bruce

> Cheers,
>
> Richard



-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II

[PATCH 0/9] kernel-yocto: consolidated pull request

[Bruce Ashfield]

From: Bruce Ashfield <bruce.ashfield@gmail.com>

Richard,

Here are the gathered changes for our active lnux-yocto references, as well
as some pre-work for moving to 5.13+ as the reference. I've also included
a patch to add some BSP/SRC_URI information after the kernel meta data has
been gathered .. this was requested just before the previous release, and
I finally got time to pull something together.

No big surprises and everything looked fine locally, and my AB run was
clean (outside of an arm64 ptest timeout that doesn't look related).

Bruce

The following changes since commit fb26a7c9b86488f46aef707c7836c2cd406d9b8a:

  meson: update patch status (2021-05-17 09:53:15 +0100)

are available in the Git repository at:

  git://git.yoctoproject.org/poky-contrib zedd/kernel
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel

Bruce Ashfield (9):
  kernel-yocto: provide debug / summary information for metadata
  linux-yocto/5.10: update to v5.10.35
  linux-yocto/5.4: update to v5.4.117
  linux-yocto/5.10: ktypes/standard: disable obsolete crypto options by
    default
  linux-yocto/5.10: update to v5.10.36
  linux-yocto/5.4: update to v5.4.118
  linux-yocto/5.10: update to v5.10.37
  linux-yocto/5.4: update to v5.4.119
  kernel-devsrc: adjust NM and OBJTOOL variables for target

 meta/classes/kernel-yocto.bbclass             | 17 +++++++++++++
 meta/recipes-kernel/linux/kernel-devsrc.bb    |  2 ++
 .../linux/linux-yocto-rt_5.10.bb              |  6 ++---
 .../linux/linux-yocto-rt_5.4.bb               |  6 ++---
 .../linux/linux-yocto-tiny_5.10.bb            |  8 +++----
 .../linux/linux-yocto-tiny_5.4.bb             |  8 +++----
 meta/recipes-kernel/linux/linux-yocto_5.10.bb | 24 +++++++++----------
 meta/recipes-kernel/linux/linux-yocto_5.4.bb  | 22 ++++++++---------
 8 files changed, 56 insertions(+), 37 deletions(-)

-- 
2.19.1

[PATCH 0/9] kernel-yocto: consolidated pull request

[Bruce Ashfield]

Hi all,

Here is my queue of changes for kernel-yocto.

These are mainly -stable updates, but contained in those updates are the gcc8
fixes that we need to get gcc8 working for the reference kernels in master.

I've also fixed a couple of issues that were found in the last
4.12 update.

Note: I'll be dropping 4.12 and 4.15 from master in my next set of
      updates, keeping 4.14 and moving to a 4.17+ kernel as the latest.

There's also a minor kern-tools fix that was sent in my direction.

And finally we were seeing intermittent failures when configuring linux-yocto
for 4.16+. The failures were sometimes obvious (configure failure) or not so
obvious (dropped options). When I dug into the problem, I found that 4.16+ has
new checks for x86 that require native binaries, and the compiler that will be
used to build the kernel. The fix was to put the required dependencies on the
kernel_configme task for linux-yocto (since it runs before do_configure, it
doesn't have the default kernel DEPENDS in place), and to ensure that CC= and
HOSTCC are set in the environment for the configure invokations.

Cheers,

Bruce

The following changes since commit 1c7ad49bfd3e60c44281a8f49d69f4b96c359703:

  bitbake: bitbake: Update version to post release 1.39 (2018-06-06 13:35:15 +0100)

are available in the git repository at:

  git://git.pokylinux.org/poky-contrib zedd/kernel
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel

Bruce Ashfield (9):
  linux-yocto/4.14: update to v4.14.30
  linux-yocto/4.15: update to v4.15.18
  linux-yocto/4.14/4.15: gcc8 fixes
  linux-yocto/4.12: fix ppc cryptodev build
  kernel: specify dependencies for compilation for config tasks
  kern-tools: avoid merge_config concatenation issues
  linux-yocto/4.12: gcc8 + platform support
  linux-yocto: add kernel sample configuration fragment
  linux-yocto/4.14: update to v4.14.48

 meta/classes/kernel-yocto.bbclass                    |  5 ++++-
 meta/classes/kernel.bbclass                          |  2 +-
 .../kern-tools/kern-tools-native_git.bb              |  2 +-
 meta/recipes-kernel/linux/linux-yocto-rt_4.12.bb     |  2 +-
 meta/recipes-kernel/linux/linux-yocto-rt_4.14.bb     |  6 +++---
 meta/recipes-kernel/linux/linux-yocto-rt_4.15.bb     |  6 +++---
 meta/recipes-kernel/linux/linux-yocto-tiny_4.12.bb   |  2 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_4.14.bb   |  6 +++---
 meta/recipes-kernel/linux/linux-yocto-tiny_4.15.bb   |  6 +++---
 meta/recipes-kernel/linux/linux-yocto_4.12.bb        | 16 ++++++++--------
 meta/recipes-kernel/linux/linux-yocto_4.14.bb        | 20 ++++++++++----------
 meta/recipes-kernel/linux/linux-yocto_4.15.bb        | 20 ++++++++++----------
 12 files changed, 48 insertions(+), 45 deletions(-)

-- 
2.5.0

[PATCH 0/9] kernel-yocto: consolidated pull request

[Bruce Ashfield]

Hi all,

This is the latest consolidated kernel pull request. It contains -stable updates,
the kernel-devsrc re-work, and a libc-headers version bump.

The -stable updates are routine, and are required to pick up the latest CVE and
bug fixes from korg.

The kernel-devsrc re-structure has already gone through two revisions, and this
v3 of that patch addresses mips + powerpc + ARM issues that were found during
the on target kernel module compilation testing.

There's one minor fix for kernel class handling of crtsaveres.o, and that same fix
was required for kernel-devsrc.

And finally, there is also have a libc-headers version bump to deal with a
regression introduced in the 4.15 kernel uapi headers. This was picked up due
to the breakage of several packages, and has since been nominated for -stable
inclusion. Patching libc-headers is a last resort, so instead I've tracked the
-stable version to pick up the change. All the details are in the patches
commit log:

--->--->--->--->--->--->--->
   Subject: [PATCH 2/9] linux-libc-headers: update to 4.15.7

   While we don't normally follow all the -stable updates for libc-headers, there
   was one userspace header that was broken in the 4.15 cycle, and it has now
   been fixed in -stable.

   The offending header breaks the build for several packages, so we update to
   pick up this change:

      Author: Hauke Mehrtens <hauke@hauke-m.de>
      Date:   Mon Feb 12 23:59:51 2018 +0100

          uapi/if_ether.h: move __UAPI_DEF_ETHHDR libc define

          commit da360299b6734135a5f66d7db458dcc7801c826a upstream.

          This fixes a compile problem of some user space applications by not
          including linux/libc-compat.h in uapi/if_ether.h.

          linux/libc-compat.h checks which "features" the header files, included
          from the libc, provide to make the Linux kernel uapi header files only
             provide no conflicting structures and enums. If a user application mixes
          kernel headers and libc headers it could happen that linux/libc-compat.h
          gets included too early where not all other libc headers are included
          yet. Then the linux/libc-compat.h would not prevent all the
          redefinitions and we run into compile problems.
          This patch removes the include of linux/libc-compat.h from
          uapi/if_ether.h to fix the recently introduced case, but not all as this
          is more or less impossible.

          It is no problem to do the check directly in the if_ether.h file and not
          in libc-compat.h as this does not need any fancy glibc header detection
          as glibc never provided struct ethhdr and should define
          __UAPI_DEF_ETHHDR by them self when they will provide this.

          The following test program did not compile correctly any more:

          #include <linux/if_ether.h>
          #include <netinet/in.h>
          #include <linux/in.h>

          int main(void)
          {
              return 0;
          }

          Fixes: 6926e041a892 ("uapi/if_ether.h: prevent redefinition of struct ethhdr")
          Reported-by: Guillaume Nault <g.nault@alphalink.fr>
          Cc: <stable@vger.kernel.org> # 4.15
          Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
          Signed-off-by: David S. Miller <davem@davemloft.net>
          Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

   We also add a new muslc patch to adjust the ethhdr change in the uapi. As is
   suggested in the kernel commit, we can protect musl directly in if_ether itself.

   Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
--->--->--->--->--->--->--->

Cheers,

Bruce

The following changes since commit e5f258cecef6c51a4d7ebeedbaa29d2126e566e3:

  util-linux: add taskset to alternatives list (2018-03-06 06:43:11 -0800)

are available in the git repository at:

  git://git.pokylinux.org/poky-contrib zedd/kernel
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel

Bruce Ashfield (9):
  kernel-devsrc: restructure for out of tree (and on target) module
    builds
  linux-libc-headers: update to 4.15.7
  linux-yocto/4.15: update to v4.15.7
  linux-yocto/4.14: update to v4.14.24
  linux-yocto/4.12: fix aufs compile warning
  linux-yocto/4.12: memleak and build warning fixes
  linux-yocto: aufs and systemtap
  linux-yocto/4.12: warning: drm/i915/cfl: Coffee Lake works on Kaby
    Lake PCH
  kernel: make copying of crtsavres.o conditional

 meta/classes/kernel.bbclass                        |   6 +-
 ...move-muslc-ethhdr-protection-to-uapi-file.patch |  30 ++++
 ...eaders_4.15.bb => linux-libc-headers_4.15.7.bb} |   6 +-
 meta/recipes-kernel/linux/kernel-devsrc.bb         | 192 ++++++++++++++++-----
 meta/recipes-kernel/linux/linux-yocto-rt_4.12.bb   |   4 +-
 meta/recipes-kernel/linux/linux-yocto-rt_4.14.bb   |   6 +-
 meta/recipes-kernel/linux/linux-yocto-rt_4.15.bb   |   6 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_4.12.bb |   4 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_4.14.bb |   6 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_4.15.bb |   6 +-
 meta/recipes-kernel/linux/linux-yocto_4.12.bb      |  18 +-
 meta/recipes-kernel/linux/linux-yocto_4.14.bb      |  20 +--
 meta/recipes-kernel/linux/linux-yocto_4.15.bb      |  20 +--
 13 files changed, 235 insertions(+), 89 deletions(-)
 create mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers/0001-if_ether-move-muslc-ethhdr-protection-to-uapi-file.patch
 rename meta/recipes-kernel/linux-libc-headers/{linux-libc-headers_4.15.bb => linux-libc-headers_4.15.7.bb} (62%)

-- 
2.5.0

[PATCH 0/9] kernel-yocto: consolidated pull request

[Bruce Ashfield]

Hi all,

This is the last set of -stable and meta data changes for the 2.4
release window. I've also brough aufs4 into the 4.12 tree to keep
it feature consistent with all the previous linux-yocto kernels
(and given some bug reports, folks are using the aufs support).

They are -stable updates, some configuration tweaks and a round of
CVE fixes that won't make -stable before we release.

I'm still trying to track down the reported race in meta data
gathering and the rcu stalls in qemuppc, but no sense holding onto
these while those issues churn.

Cheers,

Bruce

The following changes since commit e3a69364eb1fdbf1dcb98a04b3ddfc8f9841a7fa:

  staging: gracefully abort if two recipes conflict in the sysroot (2017-09-11 17:30:30 +0100)

are available in the git repository at:

  git://git.pokylinux.org/poky-contrib zedd/kernel
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel

Bruce Ashfield (9):
  linux-yocto/meta: configuration feature additions
  linux-yocto/4.12: update to v4.12.12
  linux-yocto/4.9: update to v4.9.49
  linux-yocto/4.4: update to v4.4.87
  linux-yocto/4.12: integrate aufs4 core support
  linux-yocto/4.10: bluetooth: CVE-2017-1000251
  linux-yocto/4.12: bluetooth: CVE-2017-1000251
  linux-yocto/4.9: bluetooth: CVE-2017-1000251
  linux-yocto/4.4: bluetooth: CVE-2017-1000251

 meta/recipes-kernel/linux/linux-yocto-rt_4.10.bb   |  4 ++--
 meta/recipes-kernel/linux/linux-yocto-rt_4.12.bb   |  6 +++---
 meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb    |  6 +++---
 meta/recipes-kernel/linux/linux-yocto-rt_4.9.bb    |  6 +++---
 meta/recipes-kernel/linux/linux-yocto-tiny_4.10.bb |  4 ++--
 meta/recipes-kernel/linux/linux-yocto-tiny_4.12.bb |  6 +++---
 meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb  |  6 +++---
 meta/recipes-kernel/linux/linux-yocto-tiny_4.9.bb  |  6 +++---
 meta/recipes-kernel/linux/linux-yocto_4.10.bb      | 18 +++++++++---------
 meta/recipes-kernel/linux/linux-yocto_4.12.bb      | 20 ++++++++++----------
 meta/recipes-kernel/linux/linux-yocto_4.4.bb       | 20 ++++++++++----------
 meta/recipes-kernel/linux/linux-yocto_4.9.bb       | 20 ++++++++++----------
 12 files changed, 61 insertions(+), 61 deletions(-)

-- 
2.5.0

[PATCH 0/9] kernel-yocto: consolidated pull request

[Bruce Ashfield]

Hi all,

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.

Cheers,

Bruce


The following changes since commit 04dc76713b57f28457742dd863caa663591d4866:

  devtool/copy_buildsystem: adds meta-skeleton layer in the eSDK installation. (2017-08-19 22:15:39 +0100)

are available in the git repository at:

  git://git.pokylinux.org/poky-contrib zedd/kernel
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel

Bruce Ashfield (9):
  kernel-yocto: configuration updates: x86 features
  linux-yocto/4.1: fix fsl-ls10xx sdhci
  linux-yocto: add usb-net configs by default
  linux-yocto: introduce 4.12 recipes
  linux-yocto: remove 4.1 recipes
  libc-headers: update to 4.12
  qemu: bump default version to 4.12
  kernel-yocto: ensure that only valid BSPs are built
  linux-yocto/4.10: CVE & misc fixes

 meta/classes/kernel-yocto.bbclass                  |  3 +++
 meta/conf/distro/include/tcmode-default.inc        |  2 +-
 meta/conf/machine/include/x86-base.inc             |  2 +-
 meta/conf/machine/qemuarm.conf                     |  2 +-
 .../kern-tools/kern-tools-native_git.bb            |  2 +-
 ...-headers_4.10.bb => linux-libc-headers_4.12.bb} |  4 ++--
 meta/recipes-kernel/linux/linux-yocto-rt_4.10.bb   |  4 ++--
 ...inux-yocto-rt_4.1.bb => linux-yocto-rt_4.12.bb} | 12 +++++-----
 meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb    |  2 +-
 meta/recipes-kernel/linux/linux-yocto-rt_4.9.bb    |  2 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_4.10.bb |  4 ++--
 ...-yocto-tiny_4.1.bb => linux-yocto-tiny_4.12.bb} | 12 +++++-----
 meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb  |  2 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_4.9.bb  |  2 +-
 meta/recipes-kernel/linux/linux-yocto_4.10.bb      | 18 +++++++--------
 .../{linux-yocto_4.1.bb => linux-yocto_4.12.bb}    | 26 ++++++++++++----------
 meta/recipes-kernel/linux/linux-yocto_4.4.bb       |  2 +-
 meta/recipes-kernel/linux/linux-yocto_4.9.bb       |  2 +-
 18 files changed, 56 insertions(+), 47 deletions(-)
 rename meta/recipes-kernel/linux-libc-headers/{linux-libc-headers_4.10.bb => linux-libc-headers_4.12.bb} (71%)
 rename meta/recipes-kernel/linux/{linux-yocto-rt_4.1.bb => linux-yocto-rt_4.12.bb} (76%)
 rename meta/recipes-kernel/linux/{linux-yocto-tiny_4.1.bb => linux-yocto-tiny_4.12.bb} (52%)
 rename meta/recipes-kernel/linux/{linux-yocto_4.1.bb => linux-yocto_4.12.bb} (56%)

-- 
2.5.0

Re: [PATCH 0/9] kernel-yocto: consolidated pull request

[Richard Purdie]

On Sun, 2017-08-20 at 22:58 -0400, Bruce Ashfield wrote:
> Hi all,
> 
> 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.

I added an extra patch for the ones you missed in meta-yocto-bsp ;-)

Also, https://autobuilder.yocto.io/builders/build-appliance/builds/425/
steps/BuildImages_1/logs/stdio

Error: 
 Problem: conflicting requests
  - nothing provides /bin/awk needed by kernel-devsrc-1.0-r0.0.qemux86_64

Cheers,

Richard

Re: [PATCH 0/9] kernel-yocto: consolidated pull request

[Bruce Ashfield]

[-- Attachment #1: Type: text/plain, Size: 2371 bytes --]

On Mon, Aug 21, 2017 at 7:42 AM, Richard Purdie <
richard.purdie@linuxfoundation.org> wrote:

> On Sun, 2017-08-20 at 22:58 -0400, Bruce Ashfield wrote:
> > Hi all,
> >
> > 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.
>
> I added an extra patch for the ones you missed in meta-yocto-bsp ;-)
>
> Also, https://autobuilder.yocto.io/builders/build-appliance/builds/425/
> steps/BuildImages_1/logs/stdio
>
> Error:
>  Problem: conflicting requests
>   - nothing provides /bin/awk needed by kernel-devsrc-1.0-r0.0.qemux86_64
>

Hmm. I've built that exact combination on two different builders in the
past week
and have never seen this.

How do I find out about the environment on that machine ? Because I'm not
going
to be able to reproduce it here.

Bruce


>
> Cheers,
>
> Richard
>
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end"

[-- Attachment #2: Type: text/html, Size: 3721 bytes --]

Re: [PATCH 0/9] kernel-yocto: consolidated pull request

[Bruce Ashfield]

[-- Attachment #1: Type: text/plain, Size: 3420 bytes --]

On Mon, Aug 21, 2017 at 8:11 AM, Bruce Ashfield <bruce.ashfield@gmail.com>
wrote:

>
>
> On Mon, Aug 21, 2017 at 7:42 AM, Richard Purdie <
> richard.purdie@linuxfoundation.org> wrote:
>
>> On Sun, 2017-08-20 at 22:58 -0400, Bruce Ashfield wrote:
>> > Hi all,
>> >
>> > 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.
>>
>> I added an extra patch for the ones you missed in meta-yocto-bsp ;-)
>>
>> Also, https://autobuilder.yocto.io/builders/build-appliance/builds/425/
>> steps/BuildImages_1/logs/stdio
>> <https://autobuilder.yocto.io/builders/build-appliance/builds/425/steps/BuildImages_1/logs/stdio>
>>
>> Error:
>>  Problem: conflicting requests
>>   - nothing provides /bin/awk needed by kernel-devsrc-1.0-r0.0.qemux86_64
>>
>
> Hmm. I've built that exact combination on two different builders in the
> past week
> and have never seen this.
>
> How do I find out about the environment on that machine ? Because I'm not
> going
> to be able to reproduce it here.
>

A little bit more information. Saul fixed this earlier this year, and I'm
still carrying
a patch that ensures that /usr/bin/awk is in the ver_linux script instead
of /bin/awk.
That fix used to satisfy a similar requirement.

That being said, I did notice that Saul's change was accepted upstream and
the
patch I'm carrying is not correctly applied (but it should be an invalid
patch, not
a reference to /bin/awk).

I've fixed that patch, and am building the build-appliance image now.

I will have a new set of SRCREVs for linux-yocto-4.12, but I can't say if
they'll
fix the particular issue that the autobuilder is seeing.

Bruce


>
> Bruce
>
>
>>
>> Cheers,
>>
>> Richard
>>
>>
>> --
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>>
>
>
>
> --
> "Thou shalt not follow the NULL pointer, for chaos and madness await thee
> at its end"
>



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end"

[-- Attachment #2: Type: text/html, Size: 5750 bytes --]

Re: [PATCH 0/9] kernel-yocto: consolidated pull request

[Richard Purdie]

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/429/steps/BuildImages/logs/stdio
https://autobuilder.yocto.io/builders/nightly-packagemanagers/builds/77/steps/BuildImages/logs/stdio
https://autobuilder.yocto.io/builders/nightly-packagemanagers/builds/77/steps/BuildImages_1/logs/stdio
https://autobuilder.yocto.io/builders/nightly-packagemanagers/builds/77/steps/BuildImages_2/logs/stdio
[and so on]

Cheers,

Richard

Re: [PATCH 0/9] kernel-yocto: consolidated pull request

[Bruce Ashfield]

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/429/steps/BuildImages/logs/stdio
> https://autobuilder.yocto.io/builders/nightly-packagemanagers/builds/77/steps/BuildImages/logs/stdio
> https://autobuilder.yocto.io/builders/nightly-packagemanagers/builds/77/steps/BuildImages_1/logs/stdio
> https://autobuilder.yocto.io/builders/nightly-packagemanagers/builds/77/steps/BuildImages_2/logs/stdio
> [and so on]
> 

Again, I'm not going to be much good on fixing this.

I of course have built (and run perf on target) for all the
architectures or I never would have sent the pull request.

I'll see if I can find something wrong on what my building
was producing, but otherwise, I have no way to reproduce it.

Bruce


> Cheers,
> 
> Richard
> 
> 
> 

Re: [PATCH 0/9] kernel-yocto: consolidated pull request

[Bruce Ashfield]

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/429/steps/BuildImages/logs/stdio
> https://autobuilder.yocto.io/builders/nightly-packagemanagers/builds/77/steps/BuildImages/logs/stdio
> https://autobuilder.yocto.io/builders/nightly-packagemanagers/builds/77/steps/BuildImages_1/logs/stdio
> https://autobuilder.yocto.io/builders/nightly-packagemanagers/builds/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.

Bruce

> Cheers,
> 
> Richard
> 
> 
> 

Re: [PATCH 0/9] kernel-yocto: consolidated pull request

[Richard Purdie]

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:

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?

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?

Cheers,

Richard

Re: [PATCH 0/9] kernel-yocto: consolidated pull request

[Bruce Ashfield]

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
> 

Re: [PATCH 0/9] kernel-yocto: consolidated pull request

[Richard Purdie]

On Tue, 2017-08-22 at 10:54 -0400, Bruce Ashfield wrote:
> On 08/22/2017 10:24 AM, Richard Purdie wrote:
> > 
> > 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.

Ok, Should I merge my patch for now and you and then deal with it in
due course or do you want to do that directly?

I can take care of the mips issue but we have one final problem:

"oe-selftest -r runqemu.RunqemuTests.test_boot_machine_iso"

is failing, it works with 4.10, fails with 4.12. Did some key config
option for booting isos go missing?

Cheers,

Richard

Re: [PATCH 0/9] kernel-yocto: consolidated pull request

[Bruce Ashfield]

On 08/22/2017 11:28 AM, Richard Purdie wrote:
> On Tue, 2017-08-22 at 10:54 -0400, Bruce Ashfield wrote:
>> On 08/22/2017 10:24 AM, Richard Purdie wrote:
>>>   
>>> 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.
> 
> Ok, Should I merge my patch for now and you and then deal with it in
> due course or do you want to do that directly?

I can send you a v4 of the 4.12 patch in the next half an hour,
that's easiest for me to do.

.. but if it isn't for you, go ahead and do the merge and I'll
sort it out in a follow up.

> 
> I can take care of the mips issue but we have one final problem:
> 
> "oe-selftest -r runqemu.RunqemuTests.test_boot_machine_iso"
> 
> is failing, it works with 4.10, fails with 4.12. Did some key config
> option for booting isos go missing?

Not that I'm aware of, but I admit that I've never done any ISO
booting of the images so wouldn't see it.

I'll diff the configs here and see if anything jumps out. Otherwise,
I'll do a boot test myself and debug from there.

Bruce

> 
> Cheers,
> 
> Richard
> 

Re: [PATCH 0/9] kernel-yocto: consolidated pull request

[Richard Purdie]

On Tue, 2017-08-22 at 11:34 -0400, Bruce Ashfield wrote:
> I can send you a v4 of the 4.12 patch in the next half an hour,
> that's easiest for me to do.
> 
> .. but if it isn't for you, go ahead and do the merge and I'll
> sort it out in a follow up.

The above works, I'm still trying to get to the bottom of the other
issues that are going on.

> > I can take care of the mips issue but we have one final problem:
> > 
> > "oe-selftest -r runqemu.RunqemuTests.test_boot_machine_iso"
> > 
> > is failing, it works with 4.10, fails with 4.12. Did some key
> > config
> > option for booting isos go missing?
> Not that I'm aware of, but I admit that I've never done any ISO
> booting of the images so wouldn't see it.
> 
> I'll diff the configs here and see if anything jumps out. Otherwise,
> I'll do a boot test myself and debug from there.

After running the failing test case, I was able to manually boot with:

tmp/work/x86_64-linux/qemu-helper-native/1.0-r1/recipe-sysroot-native/usr/bin//qemu-system-x86_64 -device virtio-net-pci,netdev=net0,mac=52:54:00:12:34:02 -netdev tap,id=net0,ifname=tap0,script=no,downscript=no -cdrom tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64-20170822154904.iso -no-reboot -vga vmware -show-cursor -usb -device usb-tablet -device virtio-rng-pci  -nographic   -cpu core2duo -m 256

and then quickly "down, enter" to select the serial console option
which gave me this:

[    4.980303] netconsole: network logging started
[    4.980981] rtc_cmos 00:00: setting system clock to 2017-08-22 15:56:12 UTC (1503417372)
[    5.036130] Freeing unused kernel memory: 1440K
[    5.036320] Write protecting the kernel read-only data: 14336k
[    5.039206] Freeing unused kernel memory: 864K
[    5.072281] Freeing unused kernel memory: 1232K
[    5.173842] usb 1-1: new full-speed USB device number 2 using uhci_hcd
starting version 234
[    5.349596] input: QEMU QEMU USB Tablet as /devices/pci0000:00/0000:00:01.2/usb1/1-1/1-1:1.0/0003:0627:0001.0001/input/input4
[    5.361353] hid-generic 0003:0627:0001.0001: input: USB HID v0.01 Mouse [QEMU QEMU USB Tablet] on usb-0000:00:01.2-1/input0
[    5.504201] input: ImExPS/2 Generic Explorer Mouse as /devices/platform/i8042/serio1/input/input3
[    6.408140] BUG: unable to handle kernel NULL pointer dereference at           (null)
[    6.408651] IP: ide_cdrom_prep_fn+0x63/0x180
[    6.408802] PGD beed067 
[    6.408834] P4D beed067 
[    6.408935] PUD 0 
[    6.409028] 
[    6.409251] Oops: 0002 [#1] PREEMPT SMP
[    6.409524] Modules linked in:
[    6.409811] CPU: 0 PID: 117 Comm: udevd Not tainted 4.12.7-yocto-standard #4
[    6.410012] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.10.2-0-g5f4c7b1-prebuilt.qemu-project.org 04/01/2014
[    6.410399] task: ffff9366cbd87080 task.stack: ffff9778c0304000
[    6.410613] RIP: 0010:ide_cdrom_prep_fn+0x63/0x180
[    6.410749] RSP: 0018:ffff9778c0307ad8 EFLAGS: 00000002
[    6.410902] RAX: 0000000000000002 RBX: ffff9366cc3ef800 RCX: 0000000000000000
[    6.411089] RDX: 0000000000000000 RSI: ffff9366cbf1ec00 RDI: 000000000000a1fc
[    6.411318] RBP: ffff9778c0307ad8 R08: 0000000000000000 R09: 0000000000000001
[    6.411510] R10: 0000000000000020 R11: 0000000020112a00 R12: ffff9366cbf1ec00
[    6.411717] R13: 00000000ffffff87 R14: 00000000fffffffb R15: 0000000000000000
[    6.411938] FS:  00007fd6fa79e300(0000) GS:ffff9366cf200000(0000) knlGS:0000000000000000
[    6.412153] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    6.412351] CR2: 0000000000000000 CR3: 000000000beec000 CR4: 00000000000006f0
[    6.412686] Call Trace:
[    6.413793]  blk_peek_request+0x189/0x2d0
[    6.414010]  blk_fetch_request+0x12/0x30
[    6.414142]  ? _raw_spin_unlock_irq+0x23/0x30
[    6.414276]  do_ide_request+0x37d/0x660
[    6.414382]  ? cfq_group_service_tree_add+0x94/0xc0
[    6.414559]  ? cfq_service_tree_add+0x258/0x300
[    6.414695]  ? ktime_get+0x40/0xa0
[    6.414800]  __blk_run_queue+0x33/0x40
[    6.414908]  queue_unplugged+0x2f/0xc0
[    6.415017]  blk_flush_plug_list+0x1f9/0x240
[    6.415138]  blk_finish_plug+0x2c/0x40
[    6.415255]  __do_page_cache_readahead+0x1bd/0x260
[    6.415408]  force_page_cache_readahead+0xb5/0x110
[    6.415550]  ? force_page_cache_readahead+0xb5/0x110
[    6.415687]  page_cache_sync_readahead+0x3f/0x50
[    6.415815]  generic_file_read_iter+0x54b/0x700
[    6.415965]  blkdev_read_iter+0x35/0x40
[    6.416085]  __vfs_read+0xbf/0x110
[    6.416182]  vfs_read+0x8e/0x110
[    6.416279]  SyS_read+0x46/0xb0
[    6.416369]  ? SyS_lseek+0x87/0xb0
[    6.416469]  entry_SYSCALL_64_fastpath+0x1a/0xa5
[    6.416747] RIP: 0033:0x7fd6f9b06891
[    6.416854] RSP: 002b:00007fff59e50a08 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
[    6.417057] RAX: ffffffffffffffda RBX: 00007fff59e4f950 RCX: 00007fd6f9b06891
[    6.417248] RDX: 0000000000000200 RSI: 00007fff59e50ac0 RDI: 000000000000000c
[    6.417439] RBP: 00007fff59e4f950 R08: 0000000000000000 R09: 00007fd6f98751c0
[    6.417643] R10: 000000000000006d R11: 0000000000000246 R12: 00007fff59e509d8
[    6.417832] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
[    6.418057] Code: 2f 01 00 00 b9 01 00 00 00 bf 01 00 00 00 48 8b 46 60 48 99 48 f7 ff 48 89 c7 8b 46 58 31 d2 c1 e8 09 f7 f1 48 8b 8e 50 01 00 00 <48> c7 01 00 00 00 00 48 c7 41 08 00 00 00 00 f6 46 44 01 48 8b 
[    6.418825] RIP: ide_cdrom_prep_fn+0x63/0x180 RSP: ffff9778c0307ad8
[    6.419017] CR2: 0000000000000000
[    6.419324] ---[ end trace dd02c5282d34fc7b ]---
[    6.419558] note: udevd[117] exited with preempt_count 1
Waiting for removable media...

Something in the IDE CDROM driver?

Cheers,

Richard

Re: [PATCH 0/9] kernel-yocto: consolidated pull request

[Bruce Ashfield]

On 08/22/2017 12:00 PM, Richard Purdie wrote:
> On Tue, 2017-08-22 at 11:34 -0400, Bruce Ashfield wrote:
>> I can send you a v4 of the 4.12 patch in the next half an hour,
>> that's easiest for me to do.
>>
>> .. but if it isn't for you, go ahead and do the merge and I'll
>> sort it out in a follow up.
> 
> The above works, I'm still trying to get to the bottom of the other
> issues that are going on.

Patch sent as a v4 (although I now realize I forgot to put
v4 in the subject, only in the summary).

> 
>>> I can take care of the mips issue but we have one final problem:
>>>
>>> "oe-selftest -r runqemu.RunqemuTests.test_boot_machine_iso"
>>>
>>> is failing, it works with 4.10, fails with 4.12. Did some key
>>> config
>>> option for booting isos go missing?
>> Not that I'm aware of, but I admit that I've never done any ISO
>> booting of the images so wouldn't see it.
>>
>> I'll diff the configs here and see if anything jumps out. Otherwise,
>> I'll do a boot test myself and debug from there.
> 
> After running the failing test case, I was able to manually boot with:
> 
> tmp/work/x86_64-linux/qemu-helper-native/1.0-r1/recipe-sysroot-native/usr/bin//qemu-system-x86_64 -device virtio-net-pci,netdev=net0,mac=52:54:00:12:34:02 -netdev tap,id=net0,ifname=tap0,script=no,downscript=no -cdrom tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64-20170822154904.iso -no-reboot -vga vmware -show-cursor -usb -device usb-tablet -device virtio-rng-pci  -nographic   -cpu core2duo -m 256
> 
> and then quickly "down, enter" to select the serial console option
> which gave me this:
> 
> [    4.980303] netconsole: network logging started
> [    4.980981] rtc_cmos 00:00: setting system clock to 2017-08-22 15:56:12 UTC (1503417372)
> [    5.036130] Freeing unused kernel memory: 1440K
> [    5.036320] Write protecting the kernel read-only data: 14336k
> [    5.039206] Freeing unused kernel memory: 864K
> [    5.072281] Freeing unused kernel memory: 1232K
> [    5.173842] usb 1-1: new full-speed USB device number 2 using uhci_hcd
> starting version 234
> [    5.349596] input: QEMU QEMU USB Tablet as /devices/pci0000:00/0000:00:01.2/usb1/1-1/1-1:1.0/0003:0627:0001.0001/input/input4
> [    5.361353] hid-generic 0003:0627:0001.0001: input: USB HID v0.01 Mouse [QEMU QEMU USB Tablet] on usb-0000:00:01.2-1/input0
> [    5.504201] input: ImExPS/2 Generic Explorer Mouse as /devices/platform/i8042/serio1/input/input3
> [    6.408140] BUG: unable to handle kernel NULL pointer dereference at           (null)
> [    6.408651] IP: ide_cdrom_prep_fn+0x63/0x180
> [    6.408802] PGD beed067
> [    6.408834] P4D beed067
> [    6.408935] PUD 0
> [    6.409028]
> [    6.409251] Oops: 0002 [#1] PREEMPT SMP
> [    6.409524] Modules linked in:
> [    6.409811] CPU: 0 PID: 117 Comm: udevd Not tainted 4.12.7-yocto-standard #4
> [    6.410012] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.10.2-0-g5f4c7b1-prebuilt.qemu-project.org 04/01/2014
> [    6.410399] task: ffff9366cbd87080 task.stack: ffff9778c0304000
> [    6.410613] RIP: 0010:ide_cdrom_prep_fn+0x63/0x180
> [    6.410749] RSP: 0018:ffff9778c0307ad8 EFLAGS: 00000002
> [    6.410902] RAX: 0000000000000002 RBX: ffff9366cc3ef800 RCX: 0000000000000000
> [    6.411089] RDX: 0000000000000000 RSI: ffff9366cbf1ec00 RDI: 000000000000a1fc
> [    6.411318] RBP: ffff9778c0307ad8 R08: 0000000000000000 R09: 0000000000000001
> [    6.411510] R10: 0000000000000020 R11: 0000000020112a00 R12: ffff9366cbf1ec00
> [    6.411717] R13: 00000000ffffff87 R14: 00000000fffffffb R15: 0000000000000000
> [    6.411938] FS:  00007fd6fa79e300(0000) GS:ffff9366cf200000(0000) knlGS:0000000000000000
> [    6.412153] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [    6.412351] CR2: 0000000000000000 CR3: 000000000beec000 CR4: 00000000000006f0
> [    6.412686] Call Trace:
> [    6.413793]  blk_peek_request+0x189/0x2d0
> [    6.414010]  blk_fetch_request+0x12/0x30
> [    6.414142]  ? _raw_spin_unlock_irq+0x23/0x30
> [    6.414276]  do_ide_request+0x37d/0x660
> [    6.414382]  ? cfq_group_service_tree_add+0x94/0xc0
> [    6.414559]  ? cfq_service_tree_add+0x258/0x300
> [    6.414695]  ? ktime_get+0x40/0xa0
> [    6.414800]  __blk_run_queue+0x33/0x40
> [    6.414908]  queue_unplugged+0x2f/0xc0
> [    6.415017]  blk_flush_plug_list+0x1f9/0x240
> [    6.415138]  blk_finish_plug+0x2c/0x40
> [    6.415255]  __do_page_cache_readahead+0x1bd/0x260
> [    6.415408]  force_page_cache_readahead+0xb5/0x110
> [    6.415550]  ? force_page_cache_readahead+0xb5/0x110
> [    6.415687]  page_cache_sync_readahead+0x3f/0x50
> [    6.415815]  generic_file_read_iter+0x54b/0x700
> [    6.415965]  blkdev_read_iter+0x35/0x40
> [    6.416085]  __vfs_read+0xbf/0x110
> [    6.416182]  vfs_read+0x8e/0x110
> [    6.416279]  SyS_read+0x46/0xb0
> [    6.416369]  ? SyS_lseek+0x87/0xb0
> [    6.416469]  entry_SYSCALL_64_fastpath+0x1a/0xa5
> [    6.416747] RIP: 0033:0x7fd6f9b06891
> [    6.416854] RSP: 002b:00007fff59e50a08 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
> [    6.417057] RAX: ffffffffffffffda RBX: 00007fff59e4f950 RCX: 00007fd6f9b06891
> [    6.417248] RDX: 0000000000000200 RSI: 00007fff59e50ac0 RDI: 000000000000000c
> [    6.417439] RBP: 00007fff59e4f950 R08: 0000000000000000 R09: 00007fd6f98751c0
> [    6.417643] R10: 000000000000006d R11: 0000000000000246 R12: 00007fff59e509d8
> [    6.417832] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
> [    6.418057] Code: 2f 01 00 00 b9 01 00 00 00 bf 01 00 00 00 48 8b 46 60 48 99 48 f7 ff 48 89 c7 8b 46 58 31 d2 c1 e8 09 f7 f1 48 8b 8e 50 01 00 00 <48> c7 01 00 00 00 00 48 c7 41 08 00 00 00 00 f6 46 44 01 48 8b
> [    6.418825] RIP: ide_cdrom_prep_fn+0x63/0x180 RSP: ffff9778c0307ad8
> [    6.419017] CR2: 0000000000000000
> [    6.419324] ---[ end trace dd02c5282d34fc7b ]---
> [    6.419558] note: udevd[117] exited with preempt_count 1
> Waiting for removable media...
> 
> Something in the IDE CDROM driver?

I keep getting sent changes to drop IDE support completely, but
they aren't in play here, I'm still waiting on a 4.10 linux-yocto
to configure so I can diff the .configs and fire up some comparison
boot tests.

Bruce

> 
> Cheers,
> 
> Richard
> 

Re: [PATCH 0/9] kernel-yocto: consolidated pull request

[Richard Purdie]

On Tue, 2017-08-22 at 12:04 -0400, Bruce Ashfield wrote:
> On 08/22/2017 12:00 PM, Richard Purdie wrote:
> > 
> > On Tue, 2017-08-22 at 11:34 -0400, Bruce Ashfield wrote:
> > > 
> > > I can send you a v4 of the 4.12 patch in the next half an hour,
> > > that's easiest for me to do.
> > > 
> > > .. but if it isn't for you, go ahead and do the merge and I'll
> > > sort it out in a follow up.
> > The above works, I'm still trying to get to the bottom of the other
> > issues that are going on.
> Patch sent as a v4 (although I now realize I forgot to put
> v4 in the subject, only in the summary).

Thanks, I'll pull that into subsequent test runs.

> > Something in the IDE CDROM driver?
> I keep getting sent changes to drop IDE support completely, but
> they aren't in play here, I'm still waiting on a 4.10 linux-yocto
> to configure so I can diff the .configs and fire up some comparison
> boot tests.

I did diff the configs and nothing jumped out to me at
least, CONFIG_INITRAMFS_COMPRESSION=".gz" went missing but doesn't look
relevant as it only affects built in initramfs afaict.

Cheers,

Richard

Re: [PATCH 0/9] kernel-yocto: consolidated pull request

[Bruce Ashfield]

On 08/22/2017 12:07 PM, Richard Purdie wrote:
> On Tue, 2017-08-22 at 12:04 -0400, Bruce Ashfield wrote:
>> On 08/22/2017 12:00 PM, Richard Purdie wrote:
>>>
>>> On Tue, 2017-08-22 at 11:34 -0400, Bruce Ashfield wrote:
>>>>
>>>> I can send you a v4 of the 4.12 patch in the next half an hour,
>>>> that's easiest for me to do.
>>>>
>>>> .. but if it isn't for you, go ahead and do the merge and I'll
>>>> sort it out in a follow up.
>>> The above works, I'm still trying to get to the bottom of the other
>>> issues that are going on.
>> Patch sent as a v4 (although I now realize I forgot to put
>> v4 in the subject, only in the summary).
> 
> Thanks, I'll pull that into subsequent test runs.
> 
>>> Something in the IDE CDROM driver?
>> I keep getting sent changes to drop IDE support completely, but
>> they aren't in play here, I'm still waiting on a 4.10 linux-yocto
>> to configure so I can diff the .configs and fire up some comparison
>> boot tests.
> 
> I did diff the configs and nothing jumped out to me at
> least, CONFIG_INITRAMFS_COMPRESSION=".gz" went missing but doesn't look
> relevant as it only affects built in initramfs afaict.

Likewise, I'm seeing only noise in the diff (i.e. new selected options)
and nothing that should break this.

Could be a valid issue with the driver. I'm onto some boot testing
now.

Bruce

> 
> Cheers,
> 
> Richard
> 
> 

Re: [PATCH 0/9] kernel-yocto: consolidated pull request

[Bruce Ashfield]

On 08/22/2017 12:07 PM, Richard Purdie wrote:
> On Tue, 2017-08-22 at 12:04 -0400, Bruce Ashfield wrote:
>> On 08/22/2017 12:00 PM, Richard Purdie wrote:
>>>
>>> On Tue, 2017-08-22 at 11:34 -0400, Bruce Ashfield wrote:
>>>>
>>>> I can send you a v4 of the 4.12 patch in the next half an hour,
>>>> that's easiest for me to do.
>>>>
>>>> .. but if it isn't for you, go ahead and do the merge and I'll
>>>> sort it out in a follow up.
>>> The above works, I'm still trying to get to the bottom of the other
>>> issues that are going on.
>> Patch sent as a v4 (although I now realize I forgot to put
>> v4 in the subject, only in the summary).
> 
> Thanks, I'll pull that into subsequent test runs.
> 
>>> Something in the IDE CDROM driver?
>> I keep getting sent changes to drop IDE support completely, but
>> they aren't in play here, I'm still waiting on a 4.10 linux-yocto
>> to configure so I can diff the .configs and fire up some comparison
>> boot tests.
> 
> I did diff the configs and nothing jumped out to me at
> least, CONFIG_INITRAMFS_COMPRESSION=".gz" went missing but doesn't look
> relevant as it only affects built in initramfs afaict.

I am seeing the same thing, and can't see anything obvious.

I'm now doing a git bisect between 4.10 and 4.12.

Bruce

> 
> Cheers,
> 
> Richard
> 
> 

Re: [PATCH 0/9] kernel-yocto: consolidated pull request

[Bruce Ashfield]

On 08/22/2017 12:07 PM, Richard Purdie wrote:
> On Tue, 2017-08-22 at 12:04 -0400, Bruce Ashfield wrote:
>> On 08/22/2017 12:00 PM, Richard Purdie wrote:
>>>
>>> On Tue, 2017-08-22 at 11:34 -0400, Bruce Ashfield wrote:
>>>>
>>>> I can send you a v4 of the 4.12 patch in the next half an hour,
>>>> that's easiest for me to do.
>>>>
>>>> .. but if it isn't for you, go ahead and do the merge and I'll
>>>> sort it out in a follow up.
>>> The above works, I'm still trying to get to the bottom of the other
>>> issues that are going on.
>> Patch sent as a v4 (although I now realize I forgot to put
>> v4 in the subject, only in the summary).
> 
> Thanks, I'll pull that into subsequent test runs.
> 
>>> Something in the IDE CDROM driver?
>> I keep getting sent changes to drop IDE support completely, but
>> they aren't in play here, I'm still waiting on a 4.10 linux-yocto
>> to configure so I can diff the .configs and fire up some comparison
>> boot tests.
> 
> I did diff the configs and nothing jumped out to me at
> least, CONFIG_INITRAMFS_COMPRESSION=".gz" went missing but doesn't look
> relevant as it only affects built in initramfs afaict.

I found the commit that is causing the problem (after three hours
of bisecting). That's the good news. The bad news is it isn't something
I can revert .. or easily fix, since the commit is large and is pretty
much tree wide. There's a lot of commits stacked on top if that change,
so it can't be reverted.

------------

commit 82ed4db499b8598f16f8871261bff088d6b0597f
Author: Christoph Hellwig <hch@lst.de>
Date:   Fri Jan 27 09:46:29 2017 +0100

     block: split scsi_request out of struct request

     And require all drivers that want to support BLOCK_PC to allocate it
     as the first thing of their private data.  To support this the legacy
     IDE and BSG code is switched to set cmd_size on their queues to let
     the block layer allocate the additional space.

     Signed-off-by: Christoph Hellwig <hch@lst.de>
     Signed-off-by: Jens Axboe <axboe@fb.com>

---------

I was able to boot with the following in the command line:

-drive 
file=tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64-20170822200708.iso,if=virtio,media=cdrom

--------

IMHO we need to stop using the ancient IDE support, since it continually
is broken (not usually this badly .. but often in more subtle ways).

So switching to a virtio backed CDROM, while the issue is reported
upstream is probably the best bet.

Bruce

> 
> Cheers,
> 
> Richard
> 
> 

Re: [PATCH 0/9] kernel-yocto: consolidated pull request

[Richard Purdie]

On Tue, 2017-08-22 at 16:34 -0400, Bruce Ashfield wrote:
> On 08/22/2017 12:07 PM, Richard Purdie wrote:
> I found the commit that is causing the problem (after three hours
> of bisecting). That's the good news. The bad news is it isn't
> something
> I can revert .. or easily fix, since the commit is large and is
> pretty
> much tree wide. There's a lot of commits stacked on top if that
> change,
> so it can't be reverted.
> 
> ------------
> 
> commit 82ed4db499b8598f16f8871261bff088d6b0597f
> Author: Christoph Hellwig <hch@lst.de>
> Date:   Fri Jan 27 09:46:29 2017 +0100
> 
>      block: split scsi_request out of struct request
> 
>      And require all drivers that want to support BLOCK_PC to
> allocate it
>      as the first thing of their private data.  To support this the
> legacy
>      IDE and BSG code is switched to set cmd_size on their queues to
> let
>      the block layer allocate the additional space.
> 
>      Signed-off-by: Christoph Hellwig <hch@lst.de>
>      Signed-off-by: Jens Axboe <axboe@fb.com>
> 
> ---------
> 
> I was able to boot with the following in the command line:
> 
> -drive 
> file=tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64-
> 20170822200708.iso,if=virtio,media=cdrom
> 
> --------
> 
> IMHO we need to stop using the ancient IDE support, since it
> continually
> is broken (not usually this badly .. but often in more subtle ways).
> 
> So switching to a virtio backed CDROM, while the issue is reported
> upstream is probably the best bet.

That seems reasonable to me and should be a simple change to the
runqemu script. The hint above should let me test that so I'll try and
and see how the builds work out. Thanks for the help in figuring a
workaround!

Cheers,

Richard