Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <bruce.ashfield@gmail.com>, <richard.purdie@linuxfoundation.org>
Cc: <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [meta][PATCH 03/06] linux-yocto/7.2: introduce reference kernel recipes
Date: Thu, 27 Aug 2026 17:37:01 +0200	[thread overview]
Message-ID: <DKZU60DTZ0YA.193MLWMYN7AU6@bootlin.com> (raw)
In-Reply-To: <18CF953235C263D2.642712@lists.openembedded.org>

On Thu Aug 27, 2026 at 8:20 AM CEST, Mathieu Dubois-Briand via lists.openembedded.org wrote:
> On Fri Aug 21, 2026 at 1:25 PM CEST, Bruce Ashfield via lists.openembedded.org wrote:
>> From: Bruce Ashfield <bruce.ashfield@gmail.com>
>>
>> 7.2 is our next versioned reference kernel. The standard, preempt-rt
>> (v7.2-rc4-rt3) and tiny variants are all generated and available.
>>
>> Signed SRCREVs point at the freshly generated v7.2 branches; the kmeta
>> tracks the yocto-7.2 branch.
>>
>> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
>> ---
>
> Hi Bruce,
>
> I tested the 7.2 kernel, using this commit in meta-yocto:
>
> https://git.yoctoproject.org/meta-yocto/commit/?h=contrib/mathieu/master-next-tests-72&id=98c8b2ca0c149201f6b2ee52157ca460fd0a2eb4
>
> So far, I saw two different errors.
>
>
> First, a fail of kernelmodule.KernelModuleTest.test_kernel_module on qemux86:
> Traceback (most recent call last):
>   File "/srv/pokybuild/yocto-worker/qemux86/build/layers/openembedded-core/meta/lib/oeqa/core/decorator/__init__.py", line 35, in wrapped_f
>     return func(*args, **kwargs)
>   File "/srv/pokybuild/yocto-worker/qemux86/build/layers/openembedded-core/meta/lib/oeqa/core/decorator/__init__.py", line 35, in wrapped_f
>     return func(*args, **kwargs)
>   File "/srv/pokybuild/yocto-worker/qemux86/build/layers/openembedded-core/meta/lib/oeqa/core/decorator/__init__.py", line 35, in wrapped_f
>     return func(*args, **kwargs)
>   [Previous line repeated 2 more times]
>   File "/srv/pokybuild/yocto-worker/qemux86/build/layers/openembedded-core/meta/lib/oeqa/runtime/cases/kernelmodule.py", line 48, in test_kernel_module
>     self.assertEqual(status, 0, msg='\n'.join([cmd, output]))
>     ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> AssertionError: 2 != 0 : cd /usr/src/kernel && make scripts prepare
> ...
> In file included from ./include/uapi/linux/elf.h:5,
>                  from arch/x86/tools/vdso2c.c:66:
> ./include/uapi/linux/types.h:10:2: warning: #warning "Attempt to use kernel headers from user space, see https://kernelnewbies.org/KernelHeaders" [-Wcpp]
>    10 | #warning "Attempt to use kernel headers from user space, see https://kernelnewbies.org/KernelHeaders"
>       |  ^~~~~~~
> arch/x86/tools/vdso2c.c:74:9: error: unknown type name 'bool'
>    74 |         bool export;
>       |         ^~~~
> arch/x86/tools/vdso2c.c:69:1: note: 'bool' is defined in header '<stdbool.h>'; this is probably fixable by adding '#include <stdbool.h>'
> ...
> make: *** [Makefile:248: __sub-make] Error 2
>
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/30/builds/4474
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/20/builds/4437
>
> And then, failure in runtime_test.RustKernel.test_kernel_rust_sample
> selftest:
> 2026-08-26 14:11:09,216 - oe-selftest - INFO - runtime_test.RustKernel.test_kernel_rust_sample (subunit.RemotedTestCase)
> 2026-08-26 14:11:09,221 - oe-selftest - INFO -  ... FAIL
>
> Stderr:
> 2026-08-26 13:52:43,328 - oe-selftest - INFO - Adding: "include selftest.inc" in /srv/pokybuild/yocto-worker/oe-selftest-debian/build/build-st-803204/conf/local.conf
> 2026-08-26 13:52:43,328 - oe-selftest - INFO - Adding: "include bblayers.inc" in bblayers.conf
> WARNING: test: LICENSE is using "CLOSED", which is deprecated. Convert to using a license ref pointing to an actual license file, e.g.
> LICENSE = "LicenseRef-test-CLOSED"
> WARNING: test: LICENSE is using "CLOSED", which is deprecated. Convert to using a license ref pointing to an actual license file, e.g.
> LICENSE = "LicenseRef-test-CLOSED"
> ERROR: When reparsing /tmp/selftest-fetch8rb2fo4w/test.bb:do_checkuri, the basehash value changed from eaf531c7d0304fd45f77fab173d0399db2b76e45cd46487426eb74bae7d4b7bb to 2cdec1b5839750d0c5998dd35b7ab7380727d2fa3a33aed864144428d3a78f7d. The metadata is not deterministic and this needs to be fixed.
> ERROR: The following commands may help:
> ERROR: $ bitbake test -cdo_checkuri -Snone
> ERROR: Then:
> ERROR: $ bitbake test -cdo_checkuri -Sprintdiff
>
> I suspect the warning about the LICENSE value is unrelated, but is
> something else I should fix.
>
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/35/builds/4680
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/4502
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/23/builds/4724
>
> Thanks,
> Mathieu

Hi Bruce,

Thankfully Richard reminded me of something: warnings are not shown on a
rebuild, when sstate-cache is used. And as I messed up my first build, I
do had to rebuild.

So here's a new mail to summarize the warnings I've got. Basically there
just two different things here.

We have a first group of warnings, both on beaglebone and
beaglebone-alt:
WARNING: linux-yocto-7.2+git-r0 do_kernel_configcheck: [kernel config]: specified values did not make it into the kernel's final configuration:

    [NOTE]: 'CONFIG_FB_MODE_HELPERS' last val (y) and .config val (n) do not match
    [INFO]: CONFIG_FB_MODE_HELPERS : n
    [INFO]: raw config text:

        config FB_MODE_HELPERS
        	bool
        	depends on FB && HAS_IOMEM
        	help
        	  This enables functions for handling video modes using the
        	  Generalized Timing Formula and the EDID parser. A few drivers rely
        	  on this feature such as the radeonfb, rivafb, and the i810fb. If
        	  your driver does not take advantage of this feature, choosing Y will
        	  just increase the kernel size by about 5K.

        Config 'FB_MODE_HELPERS' has the following Direct dependencies (FB_MODE_HELPERS=y):
                FB(=y) && HAS_IOMEM(=y)
        Parent dependencies are:
             FB [y] HAS_IOMEM [y]
    [INFO]: config 'CONFIG_FB_MODE_HELPERS' was set, but it wasn't assignable, check (parent) dependencies

    [INFO]: selection details for 'CONFIG_FB_MODE_HELPERS':
        Symbols currently n-selecting this symbol (no effect):
          - FB_CLPS711X
          - FB_IMX
          - FB_UVESA
          - FB_ATMEL
          - FB_RIVA
          - FB_I740
          - FB_I810
          - FB_RADEON
          - FB_SAVAGE
          - FB_NEOMAGIC
          - FB_3DFX
          - FB_TRIDENT
          - FB_VT8500
          - FB_WM8505
          - FB_PXA
          - FB_FSL_DIU
          - FB_SMSCUFX
          - FB_UDL
          - FB_SM750

https://autobuilder.yoctoproject.org/valkyrie/#/builders/2/builds/4500
https://autobuilder.yoctoproject.org/valkyrie/#/builders/2/builds/4500

And then a second group, with qemuarm MACHINE:

WARNING: linux-yocto-7.2+git-r0 do_kernel_configcheck: [kernel config]: This BSP contains fragments with warnings:
[INFO]: the following symbols were not found in the active configuration:
     - CONFIG_CRYPTO_AES_ARM

https://autobuilder.yoctoproject.org/valkyrie/#/builders/40/builds/4469
https://autobuilder.yoctoproject.org/valkyrie/#/builders/50/builds/4529
https://autobuilder.yoctoproject.org/valkyrie/#/builders/50/builds/4529

Thanks,
Mathieu

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



  parent reply	other threads:[~2026-08-27 15:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-21 11:25 [PATCH 0/6] kernel-yocto: 6.18 and 7.2 RFC/prep bruce.ashfield
2026-08-21 11:25 ` [meta][PATCH 01/06] linux-yocto/6.18: update to v6.18.44 bruce.ashfield
2026-08-21 11:25 ` [meta][PATCH 02/06] linux-libc-headers: update to 7.2 bruce.ashfield
2026-08-21 11:25 ` [meta][PATCH 03/06] linux-yocto/7.2: introduce reference kernel recipes bruce.ashfield
2026-08-27  6:20   ` [OE-core] " Mathieu Dubois-Briand
     [not found]   ` <18CF953235C263D2.642712@lists.openembedded.org>
2026-08-27  7:05     ` Mathieu Dubois-Briand
2026-08-27 15:37     ` Mathieu Dubois-Briand [this message]
2026-08-21 11:25 ` [meta][PATCH 04/06] kernel-devsrc: strip riscv vdso-cfi-offsets .cmd file bruce.ashfield
2026-08-21 11:25 ` [meta][PATCH 05/06] kernel-devsrc: copy arch/x86 vdso2c sources for on-target prepare bruce.ashfield
2026-08-21 11:25 ` [meta-yocto-bsp][PATCH 06/06] linux-yocto/6.18: update to v6.18.44 bruce.ashfield
2026-08-21 11:33   ` Patchtest results for " patchtest
2026-08-21 15:43 ` [OE-core] [PATCH 0/6] kernel-yocto: 6.18 and 7.2 RFC/prep Khem Raj
2026-08-21 21:51   ` Khem Raj
2026-08-21 21:45 ` Richard Purdie

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DKZU60DTZ0YA.193MLWMYN7AU6@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=bruce.ashfield@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox