[PATCH 0/4] kernel-yocto: 6.16 fixups and genericarm64

[PATCH 0/4] kernel-yocto: 6.16 fixups and genericarm64

[bruce.ashfield]

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

Richard,

These should cover the first set of warnings / issues that were
seen with the 6.16 reference kernel.

The first fixes vboxguestdrivers in meta-oe

The second is the qemux86 configuration warning fixup

The third is to get genericarm64 building and uses the changes sent by Mikko.

Cheers,

Bruce

Bruce Ashfield (4):
  linux-yocto/6.16: cfg: DRM tweaks for guests
  linux-yocto/6.16: cfg: x86 BIGSMP removal
  yocto-bsp: introduce 6.16 bbappend
  linux-yocto/6.16: genericarm64 config

 .../recipes-kernel/linux/linux-yocto_6.16.bbappend     | 10 ++++++++++
 meta/recipes-kernel/linux/linux-yocto-rt_6.16.bb       |  2 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_6.16.bb     |  2 +-
 meta/recipes-kernel/linux/linux-yocto_6.16.bb          |  2 +-
 4 files changed, 13 insertions(+), 3 deletions(-)
 create mode 100644 meta-yocto-bsp/recipes-kernel/linux/linux-yocto_6.16.bbappend

-- 
2.39.2

[PATCH 1/4] linux-yocto/6.16: cfg: DRM tweaks for guests

[bruce.ashfield]

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

This also fixes the build of vboxguest drivers against the
reference kernel.

1/1 [
    Author: Bruce Ashfield
    Email: bruce.ashfield@gmail.com
    Subject: cfg/drm: add CONFIG_DRM_TTM and CONFIG_DRM_VMWGFX
    Date: Tue, 9 Sep 2025 14:14:18 -0400

    drm-bochs is used as a baseline featur efor DRM that guests
    may need.

    We add these two options to get symbols into the kernel required
    to build guest support kernel modules.

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

Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
---
 meta/recipes-kernel/linux/linux-yocto-rt_6.16.bb   | 2 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_6.16.bb | 2 +-
 meta/recipes-kernel/linux/linux-yocto_6.16.bb      | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_6.16.bb b/meta/recipes-kernel/linux/linux-yocto-rt_6.16.bb
index cf8f86504d..76654ff516 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_6.16.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_6.16.bb
@@ -15,7 +15,7 @@ python () {
 }
 
 SRCREV_machine ?= "c631c6cf05de829937afe048e6ae2fea15634cc8"
-SRCREV_meta ?= "c8f3f45cdd56085242916804754ccad79d2573c9"
+SRCREV_meta ?= "29767181a0c0a97c8ba4941f6834044d9ffaed86"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine;protocol=https \
            git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-6.16;destsuffix=${KMETA};protocol=https"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_6.16.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_6.16.bb
index 1e5ed856b1..c2953c5619 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_6.16.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_6.16.bb
@@ -18,7 +18,7 @@ KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
 SRCREV_machine ?= "01bcf423b031a36a070c7a983e45992e634fceb7"
-SRCREV_meta ?= "c8f3f45cdd56085242916804754ccad79d2573c9"
+SRCREV_meta ?= "29767181a0c0a97c8ba4941f6834044d9ffaed86"
 
 PV = "${LINUX_VERSION}+git"
 
diff --git a/meta/recipes-kernel/linux/linux-yocto_6.16.bb b/meta/recipes-kernel/linux/linux-yocto_6.16.bb
index f37c1a62c0..7bafd22ef4 100644
--- a/meta/recipes-kernel/linux/linux-yocto_6.16.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_6.16.bb
@@ -29,7 +29,7 @@ SRCREV_machine:qemux86 ?= "01bcf423b031a36a070c7a983e45992e634fceb7"
 SRCREV_machine:qemux86-64 ?= "01bcf423b031a36a070c7a983e45992e634fceb7"
 SRCREV_machine:qemumips64 ?= "2459c29bf2c3d221fd6d3222c7200b368156986e"
 SRCREV_machine ?= "01bcf423b031a36a070c7a983e45992e634fceb7"
-SRCREV_meta ?= "c8f3f45cdd56085242916804754ccad79d2573c9"
+SRCREV_meta ?= "29767181a0c0a97c8ba4941f6834044d9ffaed86"
 
 # set your preferred provider of linux-yocto to 'linux-yocto-upstream', and you'll
 # get the <version>/base branch, which is pure upstream -stable, and the same
-- 
2.39.2

[PATCH 2/4] linux-yocto/6.16: cfg: x86 BIGSMP removal

[bruce.ashfield]

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

Integrating the following commit(s) to linux-yocto/.:

1/1 [
    Author: Bruce Ashfield
    Email: bruce.ashfield@gmail.com
    Subject: x86: drop CONFIG_BIG_SMP
    Date: Tue, 9 Sep 2025 16:07:38 -0400

    commit 0abf508675c0dbbca6a387842f90db60756c4af5
    Author: Arnd Bergmann <arnd@arndb.de>
    Date:   Wed Feb 26 22:37:06 2025 +0100

        x86/smp: Drop 32-bit "bigsmp" machine support

        The x86-32 kernel used to support multiple platforms with more than eight
        logical CPUs, from the 1999-2003 timeframe: Sequent NUMA-Q, IBM Summit,
        Unisys ES7000 and HP F8. Support for all except the latter was dropped
        back in 2014, leaving only the F8 based DL740 and DL760 G2 machines in
        this catery, with up to eight single-core Socket-603 Xeon-MP processors
        with hyperthreading.

        Like the already removed machines, the HP F8 servers at the time cost
        upwards of $100k in typical configurations, but were quickly obsoleted
        by their 64-bit Socket-604 cousins and the AMD Opteron.

        Earlier servers with up to 8 Pentium Pro or Xeon processors remain
        fully supported as they had no hyperthreading. Similarly, the more
        common 4-socket Xeon-MP machines with hyperthreading using Intel
        or ServerWorks chipsets continue to work without this, and all the
        multi-core Xeon processors also run 64-bit kernels.

        While the "bigsmp" support can also be used to run on later 64-bit
        machines (including VM guests), it seems best to discourage that
        and get any remaining users to update their kernels to 64-bit builds
        on these. As a side-effect of this, there is also no more need to
        support NUMA configurations on 32-bit x86, as all true 32-bit
        NUMA platforms are already gone.

        Signed-off-by: Arnd Bergmann <arnd@arndb.de>
        Signed-off-by: Ingo Molnar <mingo@kernel.org>
        Cc: Linus Torvalds <torvalds@linux-foundation.org>
        Link: https://lore.kernel.org/r/20250226213714.4040853-3-arnd@kernel.org

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

Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
---
 meta/recipes-kernel/linux/linux-yocto-rt_6.16.bb   | 2 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_6.16.bb | 2 +-
 meta/recipes-kernel/linux/linux-yocto_6.16.bb      | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_6.16.bb b/meta/recipes-kernel/linux/linux-yocto-rt_6.16.bb
index 76654ff516..1d44936da4 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_6.16.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_6.16.bb
@@ -15,7 +15,7 @@ python () {
 }
 
 SRCREV_machine ?= "c631c6cf05de829937afe048e6ae2fea15634cc8"
-SRCREV_meta ?= "29767181a0c0a97c8ba4941f6834044d9ffaed86"
+SRCREV_meta ?= "a338639c47e0a260b656415d336aaf599699d491"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine;protocol=https \
            git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-6.16;destsuffix=${KMETA};protocol=https"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_6.16.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_6.16.bb
index c2953c5619..8764c21490 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_6.16.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_6.16.bb
@@ -18,7 +18,7 @@ KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
 SRCREV_machine ?= "01bcf423b031a36a070c7a983e45992e634fceb7"
-SRCREV_meta ?= "29767181a0c0a97c8ba4941f6834044d9ffaed86"
+SRCREV_meta ?= "a338639c47e0a260b656415d336aaf599699d491"
 
 PV = "${LINUX_VERSION}+git"
 
diff --git a/meta/recipes-kernel/linux/linux-yocto_6.16.bb b/meta/recipes-kernel/linux/linux-yocto_6.16.bb
index 7bafd22ef4..4bf5fa53c5 100644
--- a/meta/recipes-kernel/linux/linux-yocto_6.16.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_6.16.bb
@@ -29,7 +29,7 @@ SRCREV_machine:qemux86 ?= "01bcf423b031a36a070c7a983e45992e634fceb7"
 SRCREV_machine:qemux86-64 ?= "01bcf423b031a36a070c7a983e45992e634fceb7"
 SRCREV_machine:qemumips64 ?= "2459c29bf2c3d221fd6d3222c7200b368156986e"
 SRCREV_machine ?= "01bcf423b031a36a070c7a983e45992e634fceb7"
-SRCREV_meta ?= "29767181a0c0a97c8ba4941f6834044d9ffaed86"
+SRCREV_meta ?= "a338639c47e0a260b656415d336aaf599699d491"
 
 # set your preferred provider of linux-yocto to 'linux-yocto-upstream', and you'll
 # get the <version>/base branch, which is pure upstream -stable, and the same
-- 
2.39.2

[PATCH 3/4] yocto-bsp: introduce 6.16 bbappend

[bruce.ashfield]

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

Adding support for our remaining reference boards with the 6.16
kernel by introducing this bbappend.

We no longer need the patches in the 6.12 kernel bbappend as they've
been pulled into the kernel tree itself.

Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
---
 .../recipes-kernel/linux/linux-yocto_6.16.bbappend     | 10 ++++++++++
 1 file changed, 10 insertions(+)
 create mode 100644 meta-yocto-bsp/recipes-kernel/linux/linux-yocto_6.16.bbappend

diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_6.16.bbappend b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_6.16.bbappend
new file mode 100644
index 0000000000..d28ea78e5c
--- /dev/null
+++ b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_6.16.bbappend
@@ -0,0 +1,10 @@
+COMPATIBLE_MACHINE:genericarm64 = "genericarm64"
+COMPATIBLE_MACHINE:beaglebone-yocto = "beaglebone-yocto"
+COMPATIBLE_MACHINE:genericx86 = "genericx86"
+COMPATIBLE_MACHINE:genericx86-64 = "genericx86-64"
+
+KMACHINE:beaglebone-yocto ?= "beaglebone"
+KMACHINE:genericx86 ?= "common-pc"
+KMACHINE:genericx86-64 ?= "common-pc-64"
+
+KBRANCH:genericarm64 ?= "v6.16/standard/genericarm64"
-- 
2.39.2

[PATCH 4/4] linux-yocto/6.16: genericarm64 config

[bruce.ashfield]

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

Integrating the following commit(s) to linux-yocto/.:

1/3 [
    Author: Bruce Ashfield
    Email: bruce.ashfield@gmail.com
    Subject: Revert "serial: 8250: unexport serial8250_rpm_*() functions"
    Date: Tue, 9 Sep 2025 22:22:53 -0400

    1/2 [
        Author: Mikko Rapeli
        Email: mikko.rapeli@linaro.org
        Subject: Revert "serial: 8250: unexport serial8250_rpm_*() functions"
        Date: Thu, 28 Aug 2025 09:33:16 +0300

        This reverts commit 7ba4f02e12e6f2409c5b2afae2963089b5673482.
        Needed by revert of 8700a7ea5519fb0b3bad2362adfeac358c2119ce
        which causes kernel hangs when starting getty's on BeaglePlay.

        [ YOCTO #15704 ]
        https://bugzilla.yoctoproject.org/show_bug.cgi?id=15704

        Upstream-Status: Inappropriate

        Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org>
        Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
    ]

    2/2 [
        Author: Ross Burton
        Email: ross.burton@arm.com
        Subject: Revert "serial: 8250_omap: Drop pm_runtime_irq_safe()"
        Date: Thu, 28 Aug 2025 09:33:17 +0300

        This reverts commit 8700a7ea5519fb0b3bad2362adfeac358c2119ce.

        The genericarm64 machine sets SERIAL_CONSOLES to a number of potential
        devices:

        SERIAL_CONSOLES ?= "115200;ttyAMA0 115200;hvc0 115200;ttyS0 115200;ttyS1 115200;ttyS2"

        With sysvinit this turns into getty lines in inittab, and with systemd
        the systemd-serialgetty recipe creates explicit units to spawn gettys.

        This worked fine with 6.6, but since "serial: 8250_omap: Drop
        pm_runtime_irq_safe()"[1] in 6.7 onwards we see kernel hangs:

        BUG: scheduling while atomic: getty/957/0x00000002
        Call trace:
        dump_stack+0x1c/0x30
        __schedule_bug+0x60/0x90
        __schedule+0x83c/0xcf8
        schedule+0x40/0x158
        schedule_timeout+0xb0/0x1b0
        wait_for_completion_timeout+0x84/0x188
        ti_sci_set_device_state+0x134/0x220
        ti_sci_cmd_get_device_exclusive+0x24/0x40
        ti_sci_pd_power_on+0x34/0x68 [ti_sci_pm_domains]
        _genpd_power_on+0xa4/0x178
        genpd_power_on+0xb4/0x190
        genpd_runtime_resume+0xc8/0x260
        __rpm_callback+0x54/0x200
        rpm_callback+0x78/0x90
        rpm_resume+0x420/0x690
        __pm_runtime_resume+0x5c/0xb0
        omap8250_set_mctrl+0x38/0xe0 [8250_omap]
        serial8250_set_mctrl+0x2c/0x60
        uart_update_mctrl+0x98/0x120
        uart_shutdown+0x124/0x180
        uart_hangup+0x7c/0x180
        __tty_hangup.part.0+0x408/0x440
        tty_vhangup_session+0x24/0x40
        disassociate_ctty.part.0+0x48/0x1b0
        disassociate_ctty+0x30/0x48
        (full backtrace elided)

        With many thanks to TI, my understanding is that it was determined that
        the problem here is that we have a getty connected to ttyS1 which is
        actually the expansion port uart and on the BeaglePlay wired up to the
        wifi controller's debug port. The getty receives noise it doesn't know
        what to do with, and at some point the power management code does a
        suspend/result cycle of the device.  The serial drivers assume that
        child nodes use the serdev driver and they manage runtime_pm, but the
        getty opening the tty breaks a series of bad assumptions in the drivers.

        So, there are two bugs:
        1) The kernel shouldn't crash if this tty is opened
        2) The only serial port for a console on the BeaglePlay is ttyS2,
           despite others existing.

        TI are looking at (1) and other patches to follow will deal with (2).
        Until one of these is resolved entirely, reverting this change to power
        management stops the crashes.

        [ YOCTO #15704 ]
        https://bugzilla.yoctoproject.org/show_bug.cgi?id=15704

        [1] linux 8700a7ea5519fb0b3bad2362adfeac358c2119ce

        Upstream-Status: Inappropriate

        Signed-off-by: Ross Burton <ross.burton@arm.com>
        Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org>
        Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
    ]

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

2/3 [
    Author: Bruce Ashfield
    Email: bruce.ashfield@gmail.com
    Subject: genericarm64: temporarily use a branch
    Date: Tue, 9 Sep 2025 22:23:13 -0400

    There are two reverts needed for genericarm64 serial that we
    don't want to have on the common branches. So for now, we create
    a BSP branch to hold those reverts.

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

3/3 [
    Author: Mikko Rapeli
    Email: mikko.rapeli@linaro.org
    Subject: genericarm64.cfg: fix warnings from v6.16.2 kernel
    Date: Wed, 27 Aug 2025 13:08:52 +0300

    New kernel version has changed config dependencies and
    these need to be enabled explicitly. Fixes multiple
    do_kernel_configcheck warnings about ineffective configs.
    Tested kernel boot and oeqa runtime tests on arm64 build
    machine with qemu and qemu kvm and on AMD KV260

    https://ledge.validation.linaro.org/scheduler/job/119012

    Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org>
    Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
]

Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
---
 meta/recipes-kernel/linux/linux-yocto-rt_6.16.bb   | 2 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_6.16.bb | 2 +-
 meta/recipes-kernel/linux/linux-yocto_6.16.bb      | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_6.16.bb b/meta/recipes-kernel/linux/linux-yocto-rt_6.16.bb
index 1d44936da4..7725bcf20b 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_6.16.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_6.16.bb
@@ -15,7 +15,7 @@ python () {
 }
 
 SRCREV_machine ?= "c631c6cf05de829937afe048e6ae2fea15634cc8"
-SRCREV_meta ?= "a338639c47e0a260b656415d336aaf599699d491"
+SRCREV_meta ?= "5b4b90bbad3ada455c7c124bf704c519c6013aa1"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine;protocol=https \
            git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-6.16;destsuffix=${KMETA};protocol=https"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_6.16.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_6.16.bb
index 8764c21490..befced7a98 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_6.16.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_6.16.bb
@@ -18,7 +18,7 @@ KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
 SRCREV_machine ?= "01bcf423b031a36a070c7a983e45992e634fceb7"
-SRCREV_meta ?= "a338639c47e0a260b656415d336aaf599699d491"
+SRCREV_meta ?= "5b4b90bbad3ada455c7c124bf704c519c6013aa1"
 
 PV = "${LINUX_VERSION}+git"
 
diff --git a/meta/recipes-kernel/linux/linux-yocto_6.16.bb b/meta/recipes-kernel/linux/linux-yocto_6.16.bb
index 4bf5fa53c5..2ea54a5301 100644
--- a/meta/recipes-kernel/linux/linux-yocto_6.16.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_6.16.bb
@@ -29,7 +29,7 @@ SRCREV_machine:qemux86 ?= "01bcf423b031a36a070c7a983e45992e634fceb7"
 SRCREV_machine:qemux86-64 ?= "01bcf423b031a36a070c7a983e45992e634fceb7"
 SRCREV_machine:qemumips64 ?= "2459c29bf2c3d221fd6d3222c7200b368156986e"
 SRCREV_machine ?= "01bcf423b031a36a070c7a983e45992e634fceb7"
-SRCREV_meta ?= "a338639c47e0a260b656415d336aaf599699d491"
+SRCREV_meta ?= "5b4b90bbad3ada455c7c124bf704c519c6013aa1"
 
 # set your preferred provider of linux-yocto to 'linux-yocto-upstream', and you'll
 # get the <version>/base branch, which is pure upstream -stable, and the same
-- 
2.39.2

Patchtest results for [PATCH 3/4] yocto-bsp: introduce 6.16 bbappend

[patchtest]

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

Thank you for your submission. Patchtest identified one
or more issues with the patch. Please see the log below for
more information:

---
Testing patch /home/patchtest/share/mboxes/3-4-yocto-bsp-introduce-6.16-bbappend.patch

FAIL: test target mailing list: Series sent to the wrong mailing list or some patches from the series correspond to different mailing lists (test_mbox.TestMbox.test_target_mailing_list)

PASS: test Signed-off-by presence (test_mbox.TestMbox.test_signed_off_by_presence)
PASS: test author valid (test_mbox.TestMbox.test_author_valid)
PASS: test commit message presence (test_mbox.TestMbox.test_commit_message_presence)
PASS: test commit message user tags (test_mbox.TestMbox.test_commit_message_user_tags)
PASS: test max line length (test_metadata.TestMetadata.test_max_line_length)
PASS: test mbox format (test_mbox.TestMbox.test_mbox_format)
PASS: test non-AUH upgrade (test_mbox.TestMbox.test_non_auh_upgrade)
PASS: test shortlog format (test_mbox.TestMbox.test_shortlog_format)
PASS: test shortlog length (test_mbox.TestMbox.test_shortlog_length)

SKIP: pretest pylint: No python related patches, skipping test (test_python_pylint.PyLint.pretest_pylint)
SKIP: pretest src uri left files: No modified recipes, skipping pretest (test_metadata.TestMetadata.pretest_src_uri_left_files)
SKIP: test CVE check ignore: No modified recipes or older target branch, skipping test (test_metadata.TestMetadata.test_cve_check_ignore)
SKIP: test CVE tag format: No new CVE patches introduced (test_patch.TestPatch.test_cve_tag_format)
SKIP: test Signed-off-by presence: No new CVE patches introduced (test_patch.TestPatch.test_signed_off_by_presence)
SKIP: test Upstream-Status presence: No new CVE patches introduced (test_patch.TestPatch.test_upstream_status_presence_format)
SKIP: test bugzilla entry format: No bug ID found (test_mbox.TestMbox.test_bugzilla_entry_format)
SKIP: test lic files chksum modified not mentioned: No modified recipes, skipping test (test_metadata.TestMetadata.test_lic_files_chksum_modified_not_mentioned)
SKIP: test lic files chksum presence: No added recipes, skipping test (test_metadata.TestMetadata.test_lic_files_chksum_presence)
SKIP: test license presence: No added recipes, skipping test (test_metadata.TestMetadata.test_license_presence)
SKIP: test pylint: No python related patches, skipping test (test_python_pylint.PyLint.test_pylint)
SKIP: test series merge on head: Merge test is disabled for now (test_mbox.TestMbox.test_series_merge_on_head)
SKIP: test src uri left files: No modified recipes, skipping pretest (test_metadata.TestMetadata.test_src_uri_left_files)
SKIP: test summary presence: No added recipes, skipping test (test_metadata.TestMetadata.test_summary_presence)

---

Please address the issues identified and
submit a new revision of the patch, or alternatively, reply to this
email with an explanation of why the patch should be accepted. If you
believe these results are due to an error in patchtest, please submit a
bug at https://bugzilla.yoctoproject.org/ (use the 'Patchtest' category
under 'Yocto Project Subprojects'). For more information on specific
failures, see: https://wiki.yoctoproject.org/wiki/Patchtest. Thank
you!

Re: [PATCH 0/4] kernel-yocto: 6.16 fixups and genericarm64

[Richard Purdie]

On Wed, 2025-09-10 at 01:08 -0400, bruce.ashfield@gmail.com wrote:
> These should cover the first set of warnings / issues that were
> seen with the 6.16 reference kernel.
> 
> The first fixes vboxguestdrivers in meta-oe
> 
> The second is the qemux86 configuration warning fixup
> 
> The third is to get genericarm64 building and uses the changes sent
> by Mikko.

Thanks!

I don't know if I missed a patch or something else went wrong but the
number of warnings went up. The ones I spotted are:

qemuarm:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/16/builds/2386
https://autobuilder.yoctoproject.org/valkyrie/#/builders/40/builds/2343
qemuarmv5:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/80/builds/2207
qemuriscv64:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/45/builds/449
https://autobuilder.yoctoproject.org/valkyrie/#/builders/56/builds/468
qemux86 + poky-tiny:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/50/builds/2384

Also warnings in other layers:
meta-agl-core:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/55/builds/2209
meta-arm:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/75/builds/2245

and meta-virt which I suspect you know about.

The build failures are resolved though, so progress, thanks!

Cheers,

Richard

Re: [PATCH 0/4] kernel-yocto: 6.16 fixups and genericarm64

[Bruce Ashfield]

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

On Wed, Sep 10, 2025 at 7:16 AM Richard Purdie <
richard.purdie@linuxfoundation.org> wrote:

> On Wed, 2025-09-10 at 01:08 -0400, bruce.ashfield@gmail.com wrote:
> > These should cover the first set of warnings / issues that were
> > seen with the 6.16 reference kernel.
> >
> > The first fixes vboxguestdrivers in meta-oe
> >
> > The second is the qemux86 configuration warning fixup
> >
> > The third is to get genericarm64 building and uses the changes sent
> > by Mikko.
>
> Thanks!
>
> I don't know if I missed a patch or something else went wrong but the
> number of warnings went up. The ones I spotted are:
>
> qemuarm:
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/16/builds/2386
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/40/builds/2343
> qemuarmv5
> <https://autobuilder.yoctoproject.org/valkyrie/#/builders/40/builds/2343qemuarmv5>
> :
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/80/builds/2207
> qemuriscv64
> <https://autobuilder.yoctoproject.org/valkyrie/#/builders/80/builds/2207qemuriscv64>
> :
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/45/builds/449
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/56/builds/468
> qemux86
> <https://autobuilder.yoctoproject.org/valkyrie/#/builders/56/builds/468qemux86>
> + poky-tiny:
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/50/builds/2384
>
> Also warnings in other layers:
> meta-agl-core:
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/55/builds/2209
> meta-arm
> <https://autobuilder.yoctoproject.org/valkyrie/#/builders/55/builds/2209meta-arm>
> :
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/75/builds/2245
>
> and meta-virt which I suspect you know about.
>

Yup for meta-virt.

Something must be missing, everything is warning free here.

Is your queue on master-next ?

Bruce


> The build failures are resolved though, so progress, thanks!
>
> 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

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

Re: [PATCH 0/4] kernel-yocto: 6.16 fixups and genericarm64

[Richard Purdie]

On Wed, 2025-09-10 at 08:56 -0400, Bruce Ashfield wrote:
> 
> 
> On Wed, Sep 10, 2025 at 7:16 AM Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > On Wed, 2025-09-10 at 01:08 -0400, bruce.ashfield@gmail.com wrote:
> > > These should cover the first set of warnings / issues that were
> > > seen with the 6.16 reference kernel.
> > > 
> > > The first fixes vboxguestdrivers in meta-oe
> > > 
> > > The second is the qemux86 configuration warning fixup
> > > 
> > > The third is to get genericarm64 building and uses the changes
> > > sent
> > > by Mikko.
> > 
> > Thanks!
> > 
> > I don't know if I missed a patch or something else went wrong but
> > the
> > number of warnings went up. The ones I spotted are:
> > 
> > qemuarm:
> > https://autobuilder.yoctoproject.org/valkyrie/#/builders/16/builds/2386
> > https://autobuilder.yoctoproject.org/valkyrie/#/builders/40/builds/2343
> > qemuarmv5:
> > https://autobuilder.yoctoproject.org/valkyrie/#/builders/80/builds/2207
> > qemuriscv64:
> > https://autobuilder.yoctoproject.org/valkyrie/#/builders/45/builds/449
> > https://autobuilder.yoctoproject.org/valkyrie/#/builders/56/builds/468
> > qemux86 + poky-tiny:
> > https://autobuilder.yoctoproject.org/valkyrie/#/builders/50/builds/2384
> > 
> > Also warnings in other layers:
> > meta-agl-core:
> > https://autobuilder.yoctoproject.org/valkyrie/#/builders/55/builds/2209
> > meta-arm:
> > https://autobuilder.yoctoproject.org/valkyrie/#/builders/75/builds/2245
> > 
> > and meta-virt which I suspect you know about.
> > 
> 
> 
> Yup for meta-virt.
> 
> Something must be missing, everything is warning free here.
> 
> Is your queue on master-next ? 

Yes, this was with master-next.

Cheers,

Richard

Re: [PATCH 0/4] kernel-yocto: 6.16 fixups and genericarm64

[Mikko Rapeli]

Hi,

I missed "poky: bump default kernel reference to 6.16" from
emails and can't find from list archives, but it's leaving
"poky-altcfg" distro with 6.12 kernel. Is this the plan?

When building "poky-altcfg" distro, the machines can't override
kernel version. I would like to see genericarm64 systemd
builds, e.g. "poky-altcfg" distro with the new kernel.

Plain old "poky" sysvinit without systemd, udev etc is hard
to support on broad range of HW. Thus I am testing genericarm64
with "poky-altcfg", which can't easily update to 6.16 kernel,
at least without https://lists.yoctoproject.org/g/poky/message/13742

Cheers,

-Mikko

Re: [PATCH 0/4] kernel-yocto: 6.16 fixups and genericarm64

[Richard Purdie]

On Wed, 2025-09-10 at 16:26 +0300, Mikko Rapeli wrote:
> I missed "poky: bump default kernel reference to 6.16" from
> emails and can't find from list archives, but it's leaving
> "poky-altcfg" distro with 6.12 kernel. Is this the plan?
> 
> When building "poky-altcfg" distro, the machines can't override
> kernel version. I would like to see genericarm64 systemd
> builds, e.g. "poky-altcfg" distro with the new kernel.
> 
> Plain old "poky" sysvinit without systemd, udev etc is hard
> to support on broad range of HW. Thus I am testing genericarm64
> with "poky-altcfg", which can't easily update to 6.16 kernel,
> at least without https://lists.yoctoproject.org/g/poky/message/13742

The policy has always been to test one kernel in one configuration and
the other kernel in the other configuration so this is intentional.

Cheers,

Richard

Re: [PATCH 0/4] kernel-yocto: 6.16 fixups and genericarm64

[Mikko Rapeli]

Hi,

On Wed, Sep 10, 2025 at 02:28:55PM +0100, Richard Purdie wrote:
> On Wed, 2025-09-10 at 16:26 +0300, Mikko Rapeli wrote:
> > I missed "poky: bump default kernel reference to 6.16" from
> > emails and can't find from list archives, but it's leaving
> > "poky-altcfg" distro with 6.12 kernel. Is this the plan?
> > 
> > When building "poky-altcfg" distro, the machines can't override
> > kernel version. I would like to see genericarm64 systemd
> > builds, e.g. "poky-altcfg" distro with the new kernel.
> > 
> > Plain old "poky" sysvinit without systemd, udev etc is hard
> > to support on broad range of HW. Thus I am testing genericarm64
> > with "poky-altcfg", which can't easily update to 6.16 kernel,
> > at least without https://lists.yoctoproject.org/g/poky/message/13742
> 
> The policy has always been to test one kernel in one configuration and
> the other kernel in the other configuration so this is intentional.

Is some AB build config testing "poky" distro and the new kernel with systemd?

At least on genericarm64 this is working on the HW I have access to.

If "poky-altcfg" would not override kernel version to 6.12, basically patch
above, then some machines like genericarm64 could update to 6.16 a bit
sooner.

Cheers,

-Mikko